Report Bugs

so... Report Bugs for Photoshop has now been migrated to Photoshop.com? All they have is a "problem" comment box. Is that the only place to log a bug?

Philip is definately correct that you have to be careful drawing conclusions.
We know that these things are not ignored, but exactly what happens and how it works varies from product to product (they are read by member(s) of the product management team for the products; for InDesign, e.g., it's Chris Kitchener, according to InDesign Secrets podcast #151's interview with Douglas Waterfall). Some product teams may have more resources than others, or use this feature differently. I've heard it said that some other teams envy the Photoshop team's external engagement, for instance.
But just because a bug you reported is fixed doesn't mean your bug report was necessarily heeded -- it may have been independently reported or it may have been fixed for other reasons.
I think Noel's conclusion is probably incorrect. That the buggy behavior changed from a crash to being unusable is most likely an unrelated side effect of some other change. No self-respecting developer would intentionally "address" a bug by changing it from a crash to unusability; though I suppose they might have been aware that it was a side effect of some other change and lacked the resources (time, etc.) to apply a more proper fix.
Anyhow, I certainly don't want to discourage anyone from filling out the wishform. But I do think it is always better to log bug reports through Adobe Support and get a bug number. It is no worse than the wishform, that's for sure, and my impression is that it's likely quite a bit better.
The link in the Dreamweaver forum indeed goes to the wishform.

Similar Messages

Is this Oracle Reports bug – "break order property" in "group above" report

Is this Oracle Reports bug – “break order property” in "group above" report
Could anybody confirm that in "group above" report, we could only order the brake column's values with ""none" or "ascending" or "descending" provided by "break order property"?
In the following example, “Dept” is brake column. Oracle Reports allows us to order values in “Dept” with “descending” provided by “break order property”:
Dept 30
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 20
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 10
job ename salary
xxx xxx xxx
xxx xxx xxx
or “ascending” provided by “break order property”:
Dept 10
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 20
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 30
job ename salary
xxx xxx xxx
xxx xxx xxx
I need to do:
Dept 20
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 10
job ename salary
xxx xxx xxx
xxx xxx xxx
Dept 30
job ename salary
xxx xxx xxx
xxx xxx xxx
Could I do this? Could anybody confirm that we could never ever do this, or If yes, how?
Millions of thanks for advice.
M.Z.
Edited by: jielan on Sep 18, 2010 8:23 AM

Why should that be a bug? You have a custom requirement and have to find a way to fulfill it. But, what is your actual sorting order? Do you have only this three departments? If so, you could add an addtional column in your query like
DECODE(DEPT, 20, 1, 10, 2, 30, 3, 4) SORTINGput that column in the same group as dept and sort after that new column.

URL for reporting BUGS in iWeb. URL for reporting a WISH LIST for next iWeb

1
Can someone please send the URL for the page in which one can report bugs in iWeb?
2
Same thing for simple old Wishes and Hopes for the next iWeb if they are not one and the same URL/page.
Thank you.
Lorna in Southern California

Lorna....
All is well....actually doing a little jet-setting
over here and there...you can check the updates on my
website....thanks for your email...
Regarding the feedback to Apple....if you ever forget
the website, you can always look under the iWeb menu
while you are working (that's when you run into these
bugs anyways) and pick "Send Feedback to Apple".
That'll send you to the same webpage for feedback
submission!
Hi James I'm glad that you are ok. And thank you for the hint about the bug reports on iWeb menu. It makes a lot of sense putting it there; I just never noticed it.
iWeb has a bad blog bug
I'd like to stomp it royally
Instead I'll send a feedback hug
(She said, behaving loyally.)
All is said and all is done
Let's get the Raid bomb just for fun.

Reporting bugs in oracle products

Is there a webpage whre I can report bugs in oracle
products.
Thanks,
Artur...

The only place I'm aware of short of calling Oracle is metalink.oracle.com but you have to have paid for Oracle support to access
the web site. From there you can file a TAR(Technical Assistance Request) and a support person will research your problem and
either find an existing fix or classify it as a new bug.

Apps: Reporting bugs.

I've forgotten where to find the link that lets users report bugs in an installed app. Could someone remind me please?
Terry, UK
Message was edited by: Terry P

Thanks Demo, but I'm convinced I could do it more directly than that. I know this sounds vague, but it was something like a link that appeared after some other related operation (feedback to Apple?), offering something like 'Also report this to the developer'. If I'm right about that recollection, then this appears to have been dropped.
Terry, East Grinstead, UK

Where do we report bugs?

We're all excited about the development of Flash Catalyst. It would be great if we could report bugs to help Adobe improve the quality and stability of the product.
Here are some ideas:
Create one thread for reporting all bugs, keep it at the top of the list.
Create a template for bug reporting, e.g.
Summary -- what happened
Steps to Reproduce -- what do you think caused the issue
Workaround -- tips for getting around this problem until it's fixed
Description -- error messages, etc., perhaps screenshots
Version/Build -- version number in which the issue was found
Adobe Forum Admins, please give us a bit more structure so we can provide you with more valuable feedback.Thanks.

Try here:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[solved] Why is it possible to report bugs for pacman 3.5.4?

I thought we mustn't report bugs for outdated packages. What is the use case here?
Last edited by karol (2012-01-21 21:19:51)

I thought the deal was "you can use whatever version you want, as long as it's the latest one" :-)

Guidance for reporting bug upstream [kbd]

You can skip the background if you wish.
Background: We, Brazilians, use a different keyboard from the us one. It's basically a qwerty with some ponctuation keys in other places and some keys more. Things have worked fine until a black day, when some notebook manufacturers decided that have a key with / ? and ° was a waste of space and these characters should be placed at alt gr + { q, w, e} (some others use alt gr + e with the euro symbol and place ° somewhere else).
At graphical environments it's not a big hassle, these keys work as they should after the keyboard layout is set, the problem is at the console, where they won't work by default. There are workarounds (cd .. down to / and use tab-completion) but they're ugly. The solution is simple, just add some lines to a text file, but there's the...
Problem: The file that needs to be updated is owned by kbd:
pacman -Qo /usr/share/kbd/keymaps/i386/qwerty/br-abnt2.map.gz
/usr/share/kbd/keymaps/i386/qwerty/br-abnt2.map.gz is owned by kbd 1.14.1.20080309-2
but the url in the kbd package description is a ftp:
pacman -Qi kbd | grep '^URL'
URL : ftp://ftp.altlinux.org/pub/people/legion/kbd/
so I don't have the slightest of how report the bug upstream and send a patch.
Any thoughts?
TIA

FWIW, I think relying on package maintainers of a specific distro is unfair for those maintainers. They are already responsible for tracking the statuses of A LOT of packages and updating/patching them as necessary. If they were to go through every single bug reported and forward the relevant ones upstream, it would simply be overwhelming.
Newbie-oriented distros like Ubuntu might have people that simply track user reported bugs. But for Arch, the situation is actually better since most users are proficient enough in Linux so they are more than capable of reporting a bug upstream
Last edited by dcc24 (2010-07-01 07:03:59)

Installing a program,added password,all i get is a black square that says REPORT BUG and Setting up,in the middle says procesing login,what can i do? thanks

Hello everyone,I have an IMac that is stuck with a problem,after installing a program,bought from Apple store,inserting my password,started the installing it stopped everything and a black square in the middle of the screen says,REPORT BUG, setting up and in the middle of the square says processing login, I waited a few minuts but nothing else happens,I tried to shut down,but it's still there,what can i do? thanks for any info.Icarorsv.

I'm sorry. Too old to understand this stuff. I'm sure this seems real stupid to you. But I have no idea how one
would "right click on the Original iPhoto Library" (I know, I know, 'as stated").
Do I right click on the symbol in the dock?? Or open it first and then, . . I can't find a way to right click on the word iPhoto in the top bar.
Or should I open the program you had me download. There I can find something called "original iPhoto library".
When I "right click" on that I get some options. None of them are "original folders". There's "reveal library in finder", and "dupilicate library and "sort libraries". I have no idea if any of these are what you want, or if any of these might change something.
When I clicked on "reveal library in finder" earlier on it showed me the copy of the photo library that I made a while ago, sitting right where I know it is on my desktop. And if I click on that symbol it shows me all the pictures again. Just like in my regular iPhoto files - all the thumbs are there, but most can't be opened to full sized.
Are we making progress here? I'm sure this is frustrating to you. This is just pictures of family. Even the thumbs are nice to look at. But this is nothing critical - like work related or anything.
Thanks.
Mike
t

Safari's "Report Bugs to Apple" option in the Help menu

On submitting a bug report (via the "Report Bugs to Apple" option in the Help menu), I get a generic Windows XP message saying "Safari Web Browser has encountered a problem and needs to close. We are sorry for the inconvenience." after which Safari closes itself down.
Windows XP Pro

This appears to be part of a wider issue with clicking particular dialog buttons. See http://discussions.apple.com/thread.jspa?threadID=995474&tstart=0 for more info.

Report bug in last firmware nokia 130 and 130 dual...

report bug in last firmware nokia 130 and 130 dual sim rm-1037 and rm-1035.
Bug is when you choose phone book and the phone freezes on the menu and after 1 minute menu works but the second attempt to open the phone book phone freezes again. problem is present in the last firmware. I hope that the problem will be eliminated in the next firmware.
I tried also with Nokia Software Recovery Tool but without success, the phone still freezes when opening the phonebook.

1. Country Bulgaria
2. Try with three sim cards three different operators in Bulgaria, Mtel, Globul and Vivacom.
3. 100% of the problem is not in the SIM card, the problem is a bug in the software of nokia 130 and 130 dual.

My macbook pro for over an hour has on the screen report bug, setting up and processing log in

my macbook profor over an hour has on the screen report bug, setting up and processing log in? what should i do

my macbook profor over an hour has on the screen report bug, setting up and processing log in? what should i do

How to report bug?

Where do you report bugs to Apple? On the support page there is a link to leave feedback about iTunes. But, that page is restricted to requesting songs, artists, genres.
Thanks,
Mark

https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa
Thanks. But, it says I don't have access to the application.
Mark

[svn:fx-trunk] 12294: * Fix for error reporting bug.

Revision: 12294
Revision: 12294
Author:   [email protected]
Date:     2009-11-30 13:25:28 -0800 (Mon, 30 Nov 2009)
Log Message:
Fix for error reporting bug. The bug was caused by a warning being
reported during one compilation and then an error being reported in
a following compilation. Due to the warning, the Source's logger
was disconnected instead of being nulled out during the first
compilation. Then in the second compilation, we weren't reassigning
the logger, so the disconnected logger was being left in place. As
a result, it was throwing off expected error counts and caused an
assert to fire.
QE notes: There is probably an easier way to reproduce the assertion
          that George hit without having to create multiple projects
          and without having to manually copy SWC's around. I didn't
          realize this until I had a fix, though. One key aspect that
          George didn't note and might not have realized, is that the
          variable needs to cause a warning, so leaving off a
          namespace works, but making it public, private, etc doesn't.
Doc notes:
Bugs: SDK-24314
Reviewer: Corey
Tests run: checkintests
Is noteworthy for integration: fixes FB issue
Code-level description of changes:
Modified setLogger() to always reassign logger.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24314
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java

[svn:osmf:] 15984: FM-848: adding unit test that holds the code to reproduce the reported bug.

Revision: 15984
Revision: 15984
Author:   [email protected]
Date:     2010-05-10 05:50:23 -0700 (Mon, 10 May 2010)
Log Message:
FM-848: adding unit test that holds the code to reproduce the reported bug.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-848
Modified Paths:
    osmf/trunk/framework/OSMFTest/org/osmf/elements/compositeClasses/TestCompositeMetadata.as

My apologies about the wall of text. After I made my original post, I thought maybe it would better to go back and put it in a pastebin instead. I was not able to edit that post once I sent it.
In regards to your question, the permissions on the
/Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist file is "read and write" for system, wheel and everyone.

Report Bugs

Similar Messages

Maybe you are looking for