Red Hat Bugzilla – Bug 397641
error in gecko
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
I was unable to reproduce this problem. Since just completed the installation
and updates. I surfed the web to "youtube.com", and clicked on the a video
I received the attached error report with a notice to file this report
How reproducible: na
Created attachment 267951 [details]
gecko error report
could this be a duplicate of issue 398641 - or the other way around?
Reporter, sorry the attachment in comment 1 is currently useless for us. Are you
using upstream binary of firefox or the one from the Fedora package?
Anyway, to give us useful backtrace, please install firefox-debuginfo; in order
to do this you have to enable -debuginfo repository.
yum install --enablerepo=\*debuginfo firefox-debuginfo
(if you use x86_64 firefox, install firefox-debuginfo.x86_64 package).
Then run firefox with a parameter -g. That will start firefox running inside of
gdb debugger. Then use command run and do whatever you did to make firefox
crash. When it happens, you should go back to the gdb and run
(gdb) thread apply all backtrace
This produces usually many screens of the text. Copy all of them into a text
editor and attach the file to the bug as an uncompressed attachment.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
(another possible candidate for being a duplicate of is bug 407051 of course)
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
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.
[This is a mass-closing request, if you think that this bug shouldn't be closed,
please, reopen with additional information.]