Bug Report Submissions

Hi, I'm a developer. How do I know when apple has received my bug report submissions. Will they notify me? Can they contact me regarding the submission?

Will they notify me?
Not normally.
Can they contact me regarding the submission?
On rare occasions, Apple will ask for more details if they have reason to believe a bug exists and they are interested in correcting it.

Similar Messages

FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
The Premiere Pro team doesn’t necessarily see and record every post on every forum and social network, but we do see, record, and track every entry through the the official feature-request/bug-report form.
It also helps a lot if you opt into the Product Improvement Program.
Also, be sure to use the crash reporter.
We really do read all of the bug reports and feature requests, and the software really does get a lot of benefit from detailed crash reports.
Don’t forget about contacting Adobe Technical Support or Customer Service, too. For information on how to contact Adobe Technical Support, see this page. (Note that you must register your product before you can open a technical support case for it.)
If you have tried to get help from our support staff, but the service was inadequate, I can help you to escalate your issue if you send me your case number at kopriva at adobe dot com. You must provide me a case number. I am not offering to solve your problem myself; rather, I am willing to forward your information to someone if you have already hit a dead end with our Technical Support or Customer Service.
If you have feedback about the content of the Premiere Pro Help document, then please add a comment at the bottom of the relevant page. You can add comments to add information, to add links, to make corrections, or to ask for clarification.
If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
Oh, and I can’t resist this opportunity to remind you to update to the most recent version of the application. Don’t be surprised when the first thing that you hear back from us is that you need to install the latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

Hi qwerty,
Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

How and where can I submit a bug report to Nokia ?

How and where can I submit a bug report to Nokia ? I haven't found any Nokia's webpage where it is explained.

wait for the next nokia beta test program (they usually annouce it on this forum) and enrol
then you will have access to the developers to report bugs
the last beta test finished end of November.. so it will be a while b4 the next beta test
cheers
Nokia N95 8GB, 6234, 6101, N-Gage Classic, 8250, 3350, 3315

Where can we submit bug reports?

I'm unable to submit a bug report re: Lightroom's export resizing, because following the trail at feedback.photoshop.com leads you to sign in with your Adobe ID before you can submit the report but when I sign in, the page just says photoshop.com accounts can no longer be created. So, that website failure aside, the text of bug report I was trying to submit:
Lightroom 5's export isn't resizing exactly to specified long edge. For example, when I restrict long edge to 1920, the exported files are 1919. Same with 1024, I get 1023px files instead. If I export from Adobe Bridge, then the long edges are calculated correctly. This problem didn't happen with LR4. Files being exported were DNG and TIF.

Thanks Rob. I tried with both FF and Chrome, and didn't have cookies blocked, still no joy on that front. I already have an Adobe ID (signed in at adobe.com and in creative cloud) but I'll try again at the photoshop.com forums in a few days.
Didn't think about the original dimensions thing.. perhaps that might be it:
If I create a 4000px wide tif in photoshop, import it to LR5, then export to 1920 it outputs a 1920px file. If the source file is a DNG (or TIF after editing in PS) from my D800 (7360 x 4912 uncropped), then LR5 on export outputs a 1919px file instead of 1920. I also created a new file in PS with 7360x4912 dimensions, and after importing that into LR5, I get the same off-by-1 export resizing.
Doesn't seem to matter if the image is cropped (within LR5), if the source file's original dimensions are 7360x4912 (at least on my Win7 PC), LR5 outputs 1919px. If I create a 7380x4912 image, then LR5 resizes to 1920px correctly.
For now I'll just have to go through the extra step of exporting from Bridge, but hopefully someone at Adobe's LR team sees this thread and is able to reproduce & fix this bug.

Submit bug report

I'd like to submit a possible bug.
Bug: App Store doesn't close and the screen doesn't turn off after updating apps
I used App Store to update my apps remotely before bedtime. This morning, all the apps have been updated, but my iPad's screen was still on, and the battery power was 50%, from being almost fully charged the night before.

You can do so here. Under Feedback Type, select Bug Report.
http://www.apple.com/feedback/ipad.html
Just a thought, you should probably plug your iPad into a power source if you going to rely on Apple's automatic updates, backups, syncing, etc. Actually you do have to plug into power if you auto backup with iCloud and sync with iTunes. In any event, it's just a good idea to plug into power if the iPad is "functioning" while you are away from the device.
Its one thing to just let the iPad sleep at night and not plug it in, but if you want to update, backup, etc, you should plug into power. Just my opinion ...
I recharge my iPad every single night and I fail to understand why others don't do the same.

Who supports the Z3v? How to submit bug reports?

I love my Z3v, but I've encountered some significant bugs with the firmware and the software. What is the best way to submit a bug report and/or feature request?
For that matter, who officially supports the phone? I tried reporting a firmware bug to Verizon and they directed me to the manufacturer of the phone (Sony). I then tried to get support through Sony and the support rep claimed that, because the Z3v is a Verizon-specific model, only Verizon could support me.
Solved!
Go to Solution.

I'd say Verizon as it is them who would have modified the firmware and then given that to Sony for release - When it comes to network specific models and firmware then they are your 1st port of contact - but this is just my opinion based on what happens here in the UK however some features are generic in all models like the Walkman and Album apps etc
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. Richard P. Feynman

Why can't we submit bug reports for Flash Pro?

I've been looking to submit some bug reports regarding CS5.5 Pro and there just isn't an option in the "Report a Bug/Feature Request" form. WHY not?? I paid for CS5.5 and autoformat breaks my code, but there's no way to report it.

You aren't the first to have a problem with the choices provided. It would be nice if they listed "Flash Pro" uniquely in the list of options at...
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
... since they dio for the rest of the Adobe products. But you should feel free to pick any one of them. I'd choose "Flash Authoring" since I've no idea what it is other than maybe something to do with Flash Pro.

Be able to submit bug reports via LittleBigPlanet 2.

We all know that there's so many bugs and glitches out there in LittleBigPlanet 2, so how about an option to submit a bug report directly from the game? Who's with me?

Tom Gewecke wrote:
You'd be surprised.
With pleasure!
Try it with bugreport.apple.com. Need to be a registered ADC Member, but that frees. Be sure to pick a bug that is reproducible with a simple step by step recipe on the most current software.
So what is this bug you have been talking about?
Recurring complaint of mine:
March 2006 [If the RSS feeds contained pubDate and author that would be great!|http://discussions.apple.com/message.jspa?messageID=1892109#1892109]
April 2008 [better rss feeds without jf namespace prefix|http://discussions.apple.com/thread.jspa?threadID=1468264&tstart=189]
The RSS feeds are almost useful. They actually include the author and create date information, but do so in a format that neither safari or any other garden variety RSS reader handles.
Jive's own documentation on the subject [Jive Community: Content Syndication via RSS|http://www.jivesoftware.com/community/docs/DOC-1022] recommends reformatting the output to suit the needs of your audience in the section titled "*Displaying RSS (or, actually doing something with this stuff)*".
It seems the jf: prefixed tags aren't meant to be pushed out to the RSS clients. I certainly haven't found a RSS reader that deals with them correctly or lets you workaround them. So although the feeds have a creation date, modification date, author, and reply count, none of that information can be seen in a garden variety RSS reader. This is particularly a problem for the create date, since the create date of each article is replaced with the pub date of the feed. The pub date of the feed is the time when you pull it down, and that changes each time the feed is refreshed.
Anyway ... it seems to me that it would be a small and correct change that would take the existing RSS offerings that last inch into the realm of useful. Maybe I'll be surprised.

How do I submit a bug report?

There is a plethora of bugs in CC.
For instance, CC keeps pushing updates that I have already installed. I've seen other discussions regarding this phantom update issue in this forum. One discussion was no help at all and in another, two Adobe staff members offered, well, nothing really as they only guessed at some 'would be' solutions. Both employes failed to resolve the issue.
In CC this is just the tip of the iceberg.
While Adobe has made and continues to make incredibly useful, professional and fluid products, the new Creative Cloud service sucks! So far, I cannot find meaningful answers/resolutions in this forum. A cloud service is a very different beast compared to Adobe's traditional offerings. That new beast needs attention.
So, where can I file a comprehensive bug report where I could submit detailed analyses and keep track of them?
Best regards,
Mario Marceau
Message was edited for clarity by: Mario Marceau

Hi Romsinha,
Thank you for your suggestion but I already knew about that link. What I should haved mentioned is that on that page, in the "Product Name" selector pictured here (which must be set before proceeding further),
there is NO OPTION AVAILABLE for "Adobe Creative Cloud" or "Creative Cloud" or anything remotely related to the cloud service. There is also no "Other" option. All the products I own in that list work fine. So, again, where can I file a comprehensive bug report where I could submit detailed analyses and keep track of (my ticket) for the Creative Cloud product?
Creative Cloud is the service that is buggy. I have instances full of details ready to submit, including errors captured on my MacBook Pro via the Console. Unfortunately I have no way to submit them, not even via the link you provided.
As far as Creative Cloud is concerned, this forum has been no help at all. Judging by the shaky responses (or lack thereof) from Adobe staff members on the cloud service issues, I see no point in submitting detailed information on this forum. A "Creative Cloud" option should be added at once on the page you suggested.
Please do not take this response personally. I know you are doing your best to help. My frustration has to do with Adobe in general, considering the membership pricey premium we pay for the Creative Cloud service.
Best regards,
Mario Marceau

Is there a place to submit bug reports for iTunes 11?

I was wondering if anyone knows of any communities, or ways in which we can submit errors, or bug reports for the new version of iTunes, version 11.0? The 2 issues so far that I am seeing, is:
1. My account information: iTunes shows I have hidden purchases, when on all my iDevices, I have 0. (In fact, before the update, I un-hid all previously hidden purchases, and it showed correctly).
2. When syncing a device, on the last tab for items on device, on my iPhone 4, iOS 6.0.1, it shows I have 2 songs downloaded from my collection, when I know I have 0. (Verified by checking Settings>General>About>Songs = 0

Yes,
In iTunes;
Help (pulldown)
"Provide iTunes Feedback"
However, as of this writing iTunes 11 isn't listed in the 'Version list, so make sure that you state the version in your description.
-Alan
ps. If you dont see the Help pull-downmenu, press 'Alt' to toggle it.

It Says Broken Pipe When I Submit a Report at Apple's Bug Report Page

Hi. It says broken pipe when I try to submit on Apple's bug report page: https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn
I'm using Lion Safari (under Safe mode, coz' my iMac won't boot normally). What's the solution? Thank you in advance.
Gbu.

Hi. Thanks for the reply. It's ok now. I just logged in again. Reporting OS X and iOS X bugs and suggesting product feedbacks to Apple should be a little easier if they put it built-in in OS X and iOS.

How to submit a bug report for OSB? - restore fails if number of items per page is changed from the default of 30

In the OSB web gui, one of my users found that if the number of items per page is changed from the default of 30, the restore of the file will fail. He tested this using recent versions of Firefox and IE. We have verified this to also be the case using Chrome.
In a directory containing over 100,000 files, moving 30 at a time to find the one to be restored is a very frustrating user experience.
How do I file a bug report for this issue? Is there a workaround for this bug to enable my users to more easily find the file to restore without being restricted to the default of 30 items per page?

Yes there is a bug in the webtool in the current release. You can use the commandline obtool to do the restore, that is much faster and works fine.
Thanks
Rich

Reproducible Sloooooow Backup Bug (how do I submit a bug report?)

I've been having incredibly slow backup problems with my iPad. My wife was foolish enough to leave her iPad here today, so I'm doing some experiments, and I think I've identified the problem.
Her system had 2.5 gigs of stuff on it, and took less than 2 minutes to backup in iTunes on my desktop computer. I added ComicZeal, and copied 2 gigs of comics (261 issues) onto the machine. It took 90 minutes to back up.
Delete the comics, less than a minute to backup.
Add two gigs of music, less than 5 minutes to back up.
Add back two gigs of Comic Books in ComicZeal, and I gave up on the backup at the 75 minute mark (about 2/3 through).
So how do I file an official bug report?

Yep, this is consistent with what I'm seeing with cloudreader (and other pdf readers the in this case the files were pdfs but also coincidentally comic files as above). After an excruciating first back up the first time I synced, subsequent backups were reasonable (5-10 mins).. until I added a large number of pdfs to various installed pdf readers via itunes app sync tab (I was testing the different apps to see how they handled large pdfs). Adding the files to itunes took minutes but the subsequent backup the next time took hours - I've been following the hidden backup folder and the new back up files are similar in size to the pdfs. Using the time stamps on the backup files, one 100meg file took about 20 minutes to back up. I've tried both the original ipad cable and my iphone cable but little difference in speed. By contrast, my 8gb iphone backs up in 5 minutes is full but does not have any pdfs stored on it.
So Apple either needs to speed up / fix the sync or at least give the user more control over what is and isnt backed up.
Scott

How many bug reports must I submit before I get a patch?

It seems that at every turn, PRE9 on my mid 2010 MacBook Pro with 8GB RAM, crashes. Editing titles, scrubbing through a video, exporting...
Are the bug reports I am submitting getting there? I wanted more flexibility than iMovie, but more and more I find myself back in there to produce simple videos.
The footage I am working with are either from a Canon 7D or a Kodak Zi8. Both seem to have issues.
This is a paid for, and registered copy of PRE9 (otherwise I couldn't work with Canon 7D video at all).
Thank you,
-Joe

Video from your Kodak may be iffy -- but the video from your Canon EOS should work perfectly in the program, if you're using the proper project preset.
Have you ensured that your Premiere Elements project is set up to match the specs of your camcorder's video? This setting is specific to your camera -- it is NOT AVCHD! (It also doesn't hurt to install your camcorder's software on your computer, since it sometimes includes important codec information.)
And note that this camera shoots video in up to 6 different frame rates and specs -- so you must ensure that your project settings match whatever settings you're using to create your video. This match is vital to a successful project. (My books, by the way, include a chart for figuring out exactly which project presets work with which camera source and setting.)
BTW, how powerful is the processor in your Macbook and how much RAM and free space do you have on your hard drive? Remember that most laptop computers are built for portability, not power (This is particularly true with Macbooks), so you may not have the power or drive space to work with such intensive (H.264) video.
Finally, note that this is a user-to-user forum. If you're looking for help working through your issues, we're glad to help you. But if you merely want to report a bug or contact Adobe, you've come to wrong place.
To contact Adobe, click on the Contact button at the top of this web page. We're all civilians here.

Bug report: ube_ipa: internal error when compiling with -xO5

When compiling imlib2-1.1.2, one source file causes compilation to fail with the following error message:
ube_ipa: internal error
cc: ube_ipa failed for loader_tiff.c
The command which fails is (probably wrapped):
cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../src -I../loaders -I../libltdl -I/usr/X11R6/include -I/usr/openwin/include -I/opt/csw/include -I/opt/csw/include -I/opt/csw/include -g -fast -xarch=386 -xstrconst -v -xildoff -xO5 -c loader_tiff.c -KPIC -DPIC -o .libs/loader_tiff.o
Changing -xO5 to -xO4 works around the problem. The source file in question is imlib2-1.1.2/loaders/loader_tiff.c
Patch 112756-10 has been applied, and doesn't correct the problem. GCC doesn't have any problem compiling the file.
A quick note to any Sun employees reading this: it took me 45 minutes to find somewhere to submit this bug report. Searching sun.com for "submit bug report" turned up many forum postings where people asked "Where do I submit bug reports?", a bug report form for Sun One Java Studio, and not much else. It might be in your interest to make submitting bugs easier.

Internal errors, such as the one you encountered, are generally considered compiler bugs. They indicate that the compiler reached an unexpected state and therefore bailed out. I opened bug 20703141: internal error: pic_relocs(): hh reltype? to investigate. I see the same error message emitted by the current Studio development release; I will update this thread if I find a work-around.
Thanks,
Mark

Bug Report Submissions

Similar Messages

Maybe you are looking for