With stdout and stderr directed to /dev/null, it becomes unreasonably difficult to get useful information from the process (and any subprocesses).
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Still a problem in FC5.
Still a problem in FC6.
Created attachment 144829 [details] Patch that would add -debug argument to firefox launcher script
Comment on attachment 144829 [details] Patch that would add -debug argument to firefox launcher script This patch adds -debug argument to firefox launcher script and if this argument is given directs all output and errors to /dev/stdout else it directs to /dev/null. Even though running firefox, not directing output to /dev/null, does not give much more feedback, this might fix the bug if it's not wontfix.
(In reply to comment #5) > This patch adds -debug argument to firefox launcher script and if this argument > is given directs all output and errors to /dev/stdout else it directs to > /dev/null. Even though running firefox, not directing output to /dev/null, does > not give much more feedback, Well, one would hope that it's not very noisy. In general, a properly running GUI program shouldn't be spewing a lot of console output. > this might fix the bug if it's not wontfix. I don't see how the script isn't simply broken. Swallowing output like this is Not Nice.
Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it here.]
Still an issue in Fedora 8.
Since this bugzilla report was filed, we have seriously upgraded Gecko-related packages, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their distribution available. Please, confirm to us that this bug is reproducible on the latest upgrade of the supported distribution (that's RHEL, or Fedora 7, 8, and Rawhide). Setting the bug to NEEDINFO. If I won't get confirmation of reproducability in 30 days, the bug will be closed as INSUFFICIENT_DATA. [This is mass-changing of bugs which seem to be too old and irrelevant anymore; we are sorry, if this bug should not be incldued.]
Still an issue.
At this point, we're going to only be taking security fixes and major stability fixes into this release of Fedora. However, we still want to ensure the bug is fixed in the next version. We'd appreciate if you could test Firefox 3, available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping as the default in Fedora rawhide and provide feedback as to whether it still exists so we can file a ticket upstream to try to fix it in Firefox 3 before it is released.
Packaging bug. Adding to F9Target.
i'll take it
Can you please check the F9 package? (firefox 3). Seems to be fixed.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
You don't *have* to do any such thing. I'm not in a position to test a development Firefox package at this time. I'll be happy to review this once F9 is released. If that feedback isn't valuable to you, do as you will.
Fixed for me. Please reopen if the final package contains this issue.