Adobe bug report system broken

I've been having issues with Flash Pro CS6 that are getting progressively worse. I filed a few bug reports using their Bug Report form here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I just noticed today that I had some delivery failure notifications for those bug reports in my spam box.
Delivery has failed to these recipients or distribution lists:
[email protected]
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.
The form submits to a nonexistent email address. This is basically Adobe giving everyone the finger. Great.

Suhas,
It is not fixed. It is not even changed:
Delivery has failed to these recipients or distribution lists:
[email protected]
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

Similar Messages

Search for SCN Bug Reporting is broken

Hi
See my comments in the pic below. The bug search is broken.
I can enter a search term, and even the URL gets updated.
But the results are not refreshed. SAP IT has given me a new IE10 today (see further below).
can this be checked please.
( i have seen there are a bunch of other reports on broken searches, they seemed to be about different issues imo )
Pieter

I've checked in IE11. Its working fine for me.
Searching for "Link is"
Then I have changed the text as "Render"

How to report the Bug report system doesn't work?

After eagerly downloading and trying Flash CS6, one glaring bug hit me.
I'd tried to report it, in some detail, but I get a replay from a [email protected] that informs me my feedback cannot, and will not be delivered.
Can someone look at that?
The "bug" in Flash, if you'r interested, is that the compile time is so long that it is unusable.
While FlashDevelop compiles a project in under 2 seconds, the same project in Flash CS6, takes upto 5 MINUTES, while the interface hangs and says "Not Responding".
That means I would spend more time waiting than actually developing some days.

Is this the link you used to report?
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Adobe bug report submission?

I can't seem to find the link for submitting bugs to Adobe
like MM's old wish list page. Can anyone direct me to it? Or do we
now have to file a support request?
Thanks.

DocSwab wrote:
> I can't seem to find the link for submitting bugs to
Adobe like MM's old wish list page. Can anyone direct me to it? Or
do we now have to file a support request?
>
> Thanks.
www.adobe.com/go/wish
Regards
Urami
Happy New Year guys - all the best there is in the 2006 :)
<urami>
http://www.Flashfugitive.com
</urami>
<web junk free>
http://www.firefox.com
</web junk free>

Made a Bug Report - now what?

Hi guys
I just had myself a bit of a complaint in the good ol' bug report system for the first time:
http://bugs.archlinux.org/task/6306
Naturally my problem was solved within minutes by another kind ARCHer. In this case by "Jan de Groot (JGC)".
Thanks Jan!
Now, Jan provided the solution for my two machines, and therefore I can happily move on knowing how to handle that particular problem.
But what about the bug report I made?
Who owns it?
Who is supposed to either write it off as one stupid ARCH user (me), and basically close and perhaps delete the bug report. Or else forward the bug to the relevant package maintainer?
What should I do at this point to be a nice ARCHer?
Kind regards,
Henning

JGC is a member of the Arch development team. If he responded to your post, he will probably close it. If not, Romashka, the Arch bug-hunter, will do so. It won't be deleted. Either way, all you need to do is say thank you.
You give the impression that this may have been user error and not an actual bug, something I can't comment on with out the bug report number. If you want to avoid that in the future, I'd suggest asking here first, and/or the ML/IRC, before posting.

Automatic Bug Report

Hi!
Does anybody know a way to report bugs automaticaly when a runtime exception occur in a java program?
For example, I want to write into file with the stack trace when a NullPointerException occur.
Do you know how to implement a bug report system; like the Sun's "Bug Database"? I heard of BugRat, but I can't see how to use that...
Thanks!
David

can you recommend a good process control site?I like CMM http://www.sei.cmu.edu/cmm/cmm.html from what I can understand of it. There are others.
You might want to keep in mind several things.
-Process control has little if any impact if it is not actively supported by someone very high in the company. This usually means a vice-president or president. (One of the ACM/IEEE studies did a study on this.)
-The point of process control is to improve and control process. It is not a paper pushing excercise. If you are not careful people (developers and managers) end up focusing on the paper rather than the process.
-The hardest processes to control and understand are the ones that are most likely to have the most impact when they are controlled and understood. It is a lot easier to handle designs than it is to handle schedules. But the second has a much more visible impact than the first.
(Not to mention something like qualifying sales procedures.)

Adding insult to injury. Adobe's Wishlist / Bug reporting doesn't work.

I sure hope Adobe is reading these forums, because I haven't been able to submit a single bug / feature request through the proper channel, and I've given up trying. It's one thing to make is all BETA testers without warning us. It's just fanning the flames of fury when Adobe Staff tell us to submit a bug. It's at least implied that Adobe will not be reading / hearing the messages on this forum. And I can't even submit a bug report because that form is broken!
I've spent around 24 hours so far BETA testing their software for them, so I hope they are reading these forums with gratitude for our free services.
Unfortunately, I must get back to work, now. No more time for BETA testing today.

I haven't been able to submit a single bug / feature request through the proper channel,
Since it is not mentioned in this thread:
Copy/pasting is often the culprit when bug report/feature requests fail. The was a problem some time back when we were copy/pasting suggested text from a forum post. While it appeared there was a character limit (and there probably is), I suspected that invisible "junk" (html code or Word stuff) was being pasted. I have better luck pasting from a pure text editor. I have best luck typing it, and copying from the bug/feature form to keep a copy.
Another thread today complained they could not post a link in a bug report. I have had no difficulty posting a link to a forum thread.
There are of course times where web submissions fail for no good (apparent) reason. I find that very frustrating; don't get me started on Adobe forums and Jive. But as far as I know, the bug/feature system is not part of that.

FAQ: I found a bug. How do I write a useful bug report? Or send bug files to Adobe?

If you think you've found a bug in Photoshop CS6, please post your findings here on the forums.
Here is a list of the information we'll want for you to gather at a minimum:
Clear and concise steps so that someone who isn't in front of your comptuer can reproduce the issue you are seeing
Include information on the operating system/version you are running. (e.g. "Mac OS 10.7.3" or "Win XP Service Pack 3")
Here are some more detailed instructions for writing a useful, complete bug report for us on the forums:
Provide a descriptive title that includes your OS information:Example: "Photoshop crashes when I save a JPEG file using the File>Save For Web & Devices... command (Mac OS 10.7.3)"
Provide concise, step-by-step details on how to reproduce the issue you are seeing.
Example:
Open an 8-bit, RGB image by selecting File>Open...
Create a new layer by clicking the "Create New Layer" button on the bottom of the Layers panel
Paint on the layer created in Step #2 using the default Brush tool
Choose File>Save For Web & Devices...
Make sure the optimized format is set to "JPEG" and set the Quality setting to "80"
Click the Save button at the bottom of the Save For Web & Devices dialog, choose the desktop as the location for saving the file
Provide a description of the "Result" you are observing:
Example: "Result: Photoshop crashes"
If there is an error dialog, please include the exact wording displayed in the dialog or provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
If the error is a visual defect, either in the user interface or the image itself, provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
Provide a description of the "Expected Result":
Example: "Expected Result: Photoshop to save JPEG file to the desktop, no crash"
In some cases this may be obvious (such as in the case of a crash) but in others, what you expect to happen may be different than what the application was designed to do. Please be as specific as possible.
Provide the crash log by submitting all crash reports, including your email address, for every single crash your encounter:
You may also include the contents of your crash log in your forum posts as well, but always submit them using the above instructions as well.
Crash logs are located on Macintosh here: Users/<your user name>/Library/Logs/CrashReporter
Provide your System Info from Photoshop: What's even more useful is if you can share your System Info from Photoshop as it contains all kinds of useful information (OS/version, graphics card, driver version, 3rd party plug-ins used, etc) that will help the team track down your issue.
On occasion, the Photoshop engineers may request that you provide problematic files in order to reproduce and debug your issue.
In these cases, please post the file somewhere using your own servers or one your favorite online document/distribution services and provide a URL/instructions to download the file:
Dropbox
Adobe SendNow
YouSendIt
If the file isn't something you can post publically, you can request that someone from the engineering team contact you to figure out a secure way to get the affected files.
Thanks,
The Photoshop Development Team

First thing would be to realise the exact error. Second would be to check your logs to see what you have installed/upgraded which might be causing this error. Third, google your error and see if matches turn up. Fourth, search in Arch bugtracker to see if a match exist. Else file a report.

Do discussions (threads) in this forum ever get elevated to bug reports seen by the Adobe dev's?

This forum is a fertile source of user feedback for Adobe. Is there a system in place to create tickets or bug reports or something like that out of issue brought up here? Seems like a good idea.

User to User forum.
Adobe may read some items here. That's up to the development teams. If the dev team sees something and is interested then it may perhaps get logged, But you should never assume anything on the forums is actually logged anywhere but here.
If you've found a bug, you should log it using the feadback link at the bottom of this (or any) page.

Bug Report an Adobe senden

Da ich nach dem letzten Photoshop-Update eine für mich wichtige PSD-Datei nicht mehr öffnen kann und immer die Fehlermeldung »Der Vorgang konnte nicht ausgeführt werden, weil ein Programmfehler aufgetreten ist.« bekomme, wollte ich Adobe mal einen Bugreport inkl. der Datei zukommen lassen. Aber entweder ich bin zu blind und finde nur keine Möglichkeit dafür oder es gibt keine.
Weiß zufällig jemand eine Stelle, an die man sich da wenden kann? Der Fehler liegt definitiv an Photoshop, da ich über die Dropbox auch frühere Versionen der Datei wiederhergestellt habe und sich auch diese nicht öffnen lassen. Vorher war das alles kein Problem.
Wäre schön, wenn hier jemand helfen könnte.

Wenn Du einen Bug Report abgibst braucht Adobe folgende Infos:
Programm
Programm-Version
Build-Nummer des Installierten Programms
Operating System
Programmsprache
OS Sprache
Schwere des Bugs (Datenverlust/Crash, Schwerer Benutzungsfehler, leichter Fehler, optischer Fehler oder Verbesserungsvorschlag)
Verwendete Hardware einschließlich Periferie
Schrittweise Beschreibung was gemacht wurde
Was geschah oder nicht gescha (der eigentliche Bug)
Was man erwartet hätte, was geschehen sollte
Eventuell ein Workaround, der Hilft zum Ziel zu kommen
All das auf Englisch.
Sonst kannst Du das mir schicken, ich kann es auch weiterleiten.

[Bug Report!]Adobe Reader can not display 3D file normally!

I have a 3D pdf file,which is produced by Asymptote,and some labels in the 3D model, can not be displayed normally in the Adobe Reader,even the latest version 9.4.I got this file by
$asy -file pdf -render=4 file.asy
while all of them can be displayed in the OpenGL mode.
$asy -V file.asy
I hope you can give me a message about the reason and tip about how to solve the problem.
thank you very much!
code:
size(400);
import solids;
import graph3;
import three;
import math;
defaultpen(1pt+fontsize(7pt));
currentprojection=perspective(1,1,-1,up=-Z);
draw(unitsphere,palegray);//鐢荤悆
//浠ヤ笅閮ㄥ垎鐢绘敮鏌?draw(shift(1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("1",(1.07,0,0.5),yellow);
draw(shift(-1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("5",(-1.07,0,0.5),yellow);
draw(shift(0,1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0,1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("7",(0,1.07,0.5),yellow);
draw(shift(0,-1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0,-1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("3",(0,-1.07,0.5),yellow);
draw(shift(0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("8",(0.75,0.75,0.5),yellow);
draw(shift(-0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("6",(-0.75,0.75,0.5),yellow);
draw(shift(0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("2",(0.75,-0.75,0.5),yellow);
draw(shift(-0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("4",(-0.75,-0.75,0.5),yellow);
draw(shift(0,0,-1.05)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,-1.1)*xscale3(0.2)*yscale3(0.2)*zscale3(0.05)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,0.85)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitcylinder,palegray);//涓嬩汉瀛?draw(shift(0,0,1.05)*xscale3(0.2)*yscale3(0.2)*zscale3(0.05)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,1.0)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unithemisphere,palegray);//涓嬩汉瀛?draw(shift(0,0,-1.05)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitsphere,palegray);//涓嬩汉瀛?
path p=(1,0)..(0,1)..(-1,0)..(0,-1)..cycle;
path3 p3=path3(p);
surface sf=surface(patch(p3));
draw(shift(0,0,-1.05)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,-1.1)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,1.05)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,1.1)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
//浠ヤ笅缁樺埗鐜剨缂?draw(circle((0,0,sin(pi/8)),cos(pi/8)),gray);
draw(circle((0,0,sin(-pi/8)),cos(-pi/8)),gray);
draw(circle((0,0,sin(pi/4)),cos(pi/4)),gray);
draw(circle((0,0,sin(-pi/4)),cos(-pi/4)),gray);
draw(circle((0,0,sin(3pi/8)),cos(3pi/8)),gray);
draw(circle((0,0,sin(-3pi/8)),cos(-3pi/8)),gray);
xaxis3("$x$",-1.5,1.5);
yaxis3("$y$",-1.5,1.5);
zaxis3("$z$",-1.5,1.5);
surface Surf(triple center, triple A, triple B, triple C,triple D,int nu=3, int nv=nu) {
path3 p1=arc(center,A,B);
path3 p2=arc(center,B,C);
path3 p3=arc(center,C,D);
path3 p4=arc(center,D,A);
triple surf(pair t) {
real u=t.x;
real v=t.y;
path3 cr=arc(center,relpoint(p1,u),relpoint(reverse(p3),u));
return relpoint(cr,v);
return surface(surf,(0,0),(1,1),nu,nv,Spline);
real r=1+0.005;
triple A=r*unit((1,0,0.1));
triple B=r*unit((1,0,-0.1));
triple C=r*unit((-1,0,-0.1));
triple D=r*unit((-0.995,0.1,0.1));
//draw(Surf(O,A,B,C,D,4,4),yellow);
//draw(arc(O,A,B)^^arc(O,B,C)^^arc(O,C,D)^^arc(O,D,A),red+thick());
//浠ヤ笅缁樺埗閮ㄥ垎鐞冨３鏉?real r=1+0.001;
for(int i=0;i<16;++i){
triple Di_1=r*unit((sin(pi/16+i*pi/8)*cos(pi/8),cos(pi/16+i*pi/8)*cos(pi/8),sin(pi/8)));
triple Di_2=r*unit((sin(pi/16+i*pi/8)*cos(-pi/8),cos(pi/16+i*pi/8)*cos(pi/8),sin(-pi/8)));
draw(arc(O,Di_1,Di_2),gray);
for(int j=0;j<8;++j){
triple Fj_1=r*unit((sin(j*pi/4)*cos(pi/4),cos(j*pi/4)*cos(pi/4),sin(pi/4)));
triple Fj_2=r*unit((sin(j*pi/4)*cos(3pi/8),cos(j*pi/4)*cos(3pi/8),sin(3pi/8)));
draw(arc(O,Fj_1,Fj_2),gray);
triple Bj_1=r*unit((sin(j*pi/4)*cos(pi/4),cos(j*pi/4)*cos(pi/4),sin(-pi/4)));
triple Bj_2=r*unit((sin(j*pi/4)*cos(3pi/8),cos(j*pi/4)*cos(3pi/8),sin(-3pi/8)));
draw(arc(O,Bj_1,Bj_2),gray);
triple Ej_1=r*unit((sin(pi/8+j*pi/4)*cos(pi/4),cos(pi/8+j*pi/4)*cos(pi/4),sin(pi/4)));
triple Ej_2=r*unit((sin(pi/8+j*pi/4)*cos(pi/8),cos(pi/8+j*pi/4)*cos(pi/8),sin(pi/8)));
draw(arc(O,Ej_1,Ej_2),gray);
triple Cj_1=r*unit((sin(pi/8+j*pi/4)*cos(pi/4),cos(pi/8+j*pi/4)*cos(pi/4),sin(-pi/4)));
triple Cj_2=r*unit((sin(pi/8+j*pi/4)*cos(pi/8),cos(pi/8+j*pi/4)*cos(pi/8),sin(-pi/8)));
draw(arc(O,Cj_1,Cj_2),gray);
triple A_1=r*unit((sin(3pi/8)*cos(3pi/8),cos(3pi/8)*cos(3pi/8),sin(3pi/8)));
triple A_2=r*unit((sin(9pi/8)*cos(3pi/8),cos(9pi/8)*cos(3pi/8),sin(3pi/8)));
draw(arc(O,A_1,A_2),gray);
triple G_1=r*unit((sin(pi/8)*cos(-3pi/8),cos(pi/8)*cos(-3pi/8),sin(-3pi/8)));
triple G_2=r*unit((sin(11pi/8)*cos(-3pi/8),cos(11pi/8)*cos(-3pi/8),sin(-3pi/8)));
draw(arc(O,G_1,G_2),gray);
//浠ヤ笅閲囩敤鏃嬭浆鐨勬柟娉曠粯鍒惰摑鑹叉爣绀哄甫(閮ㄥ垎)
revolution belt=revolution(arc(O,1+0.006,83,0,97,0),Z,0,360);
draw(surface(belt),blue);
dot("1",r*(cos(pi/8)*cos(3pi/8),-sin(pi/8)*cos(3pi/8),sin(3pi/8)),red+0.1cm);//y鍊艰姝ｈ礋鍙樻崲锛寈y鍧愭爣瑕佹竻妤氥€?dot("2",r*(cos(9pi/8)*cos(3pi/8),-sin(9pi/8)*cos(3pi/8),sin(3pi/8)),red+0.1cm);
dot("3",r*(cos(pi/2)*cos(5pi/16),-sin(pi/2)*cos(5pi/16),sin(5pi/16)),red+0.1cm);
dot("4",r*(cos(pi/32)*cos(pi/4),-sin(pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("5",r*(cos(3pi/32)*cos(pi/4),-sin(3pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("6",r*(cos(13pi/32)*cos(pi/4),-sin(13pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("7",r*(cos(15pi/32)*cos(pi/4),-sin(15pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("8",r*(cos(17pi/32)*cos(pi/4),-sin(17pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("9",r*(cos(19pi/32)*cos(pi/4),-sin(19pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("10",r*(cos(22pi/32)*cos(pi/4),-sin(22pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("11",r*(cos(29pi/32)*cos(pi/4),-sin(29pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("12",r*(cos(19pi/16)*cos(pi/12),-sin(19pi/16)*cos(pi/12),sin(pi/12)),red+0.1cm);
dot("13",r*(cos(25pi/16)*cos(pi/12),-sin(25pi/16)*cos(pi/12),sin(pi/12)),red+0.1cm);
dot("14",r*(cos(13pi/32)*cos(pi/8),-sin(13pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("15",r*(cos(-19pi/32)*cos(pi/8),-sin(-19pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("16",r*(cos(-11pi/32)*cos(pi/8),-sin(-11pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("17",r*(cos(25pi/32)*cos(pi/4),-sin(25pi/32)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("18",r*(cos(69pi/64)*cos(pi/4),-sin(69pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("19",r*(cos(71pi/64)*cos(pi/4),-sin(71pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("20",r*(cos(73pi/64)*cos(pi/4),-sin(73pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("21",r*(cos(97pi/64)*cos(pi/4),-sin(97pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("22",r*(cos(105pi/64)*cos(pi/4),-sin(105pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("23",r*(cos(107pi/64)*cos(pi/4),-sin(107pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("24",r*(cos(109pi/64)*cos(pi/4),-sin(109pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("25",r*(cos(11pi/32),0,-sin(11pi/32)),red+0.1cm);
dot("26",r*(cos(10pi/32),0,-sin(10pi/32)),red+0.1cm);
dot("27",r*(cos(pi)*cos(10pi/32),-sin(pi)*cos(10pi/32),-sin(10pi/32)),red+0.1cm);
dot("28",1.05*(G_1+3*G_2)/4,red+0.1cm);
dot("29",r*(cos(3pi/4)*cos(-pi/8),-sin(3pi/4)*cos(-pi/8),-sin(3pi/4)),red+0.1cm);

Please note that this is a user-to-user forum, and therefore not the right place to file a bug report.
Try it here instead: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

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.

I did a bug report to Adobe, how i can track it?

I reported an issue as a bug days ago at Feature Request/Bug Report Form. However i haven't got any response from Adobe yet, and looks like there is no place (such as post history) that i can check the status.
I have no idea it is a bug or not, how i can get a reply?
Thanks.

The Feature Request/Bug form is just that, a report form.
If you file a case with Customer Support, you get a tracking number, and you might be called back for more information.
(Don't expect too much of it. Last serious bug I reported was shrugged off as "operator error", and subsequently closed, gainst my will.)

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

LR 4.1RC2 bug reports: 1) no saving of video metadata 2) out of place dynamiclinkmediaserver folder

Hi,
testing LR 4.1 RC2 x64 on a fresh Win 7 x64 system. Having noticed two bugs, I'm not sure where to report them... (and there is no official or Adobe-endorsed bug tracking system afaik).
1b)
I have a bunch of digicam videos from my Panasonic LX3, originally in Mjpeg-in-Mov format, that I convert to vanilla h264 avi for more ease of use/saving storage space. Each video comes with an out-of-camera low-res Jpeg sidecar.
Having imported the converted avi + jpeg into the LR catalog, it appears that metadata can be saved neither in the videos nor in the Jpeg sidecars. As a side-effect, videos permanently appear as "Metadata unsaved" in various LR filters/smart collections.
1b)
after import, the capture date of these videos is set to the converted file creation date (probably due to the lack of embedded capture date metadata in videos) which is wrong - there has to be a better solution than assuming filesystem stamps are reliable metadata.
And of course, here again this metadata can not be edited & saved. A tricky workaround is to read the capture date from the sidecar, set with a commandline utility the creation date of the video file, then import the video file.
Please consider fixing these two points: by allowing to read metadata first from videos, and if metadata missing, from companion sidecars (xmp, jpg...), then allowing to save edited metadata to these sidecar files (xmp, jpg...) if video files are not writable or their metadata too tricky to manage. Although not foolproof, that'd be better than no metadata capabilities for videos at all.
(Or perhaps allow users to permanently disable the video/Quicktime part of the software, leaving it to other third-part tools or the OS)
2)
Upon using LR 4 RC2, some "Adobe\dynamiclinkserver\6.0" empty directory tree is created under %User%\Documents. If deleted, the folder gets recreated after later use of LR4. Guess it relates to the video-management part of the software.
Please consider fixing this or, if such a folder is really needed, placing it out of the users' Documents...
(Or perhaps allow users to permanently disable the video/Quicktime part of the software, leaving it to other third-part tools or the OS)
• As a sidenote, LR 4.1RCs still complain about the incompatibility with Photoshop CS5.5. Not sure if there's any easy fix for this annoying fact, besides installing some trial Adobe PS CS6 [beta] on top of a fully-working CS 5.5 Suite.

Re video metadata not getting saved, please add your vote and opinion to this topic in the official forum for giving feedback to Adobe:
http://feedback.photoshop.com/photoshop_family/topics/lr4_beta_video_tagging_not_complete
Re the capture date of videos, please add your vote and opinion to this topic:
http://feedback.photoshop.com/photoshop_family/topics/inconsistent_dates_for_files_missing _date_time_metadata

Adobe bug report system broken

Similar Messages

Maybe you are looking for