Bug 524833 - [abrt] crash detected in firefox-3.5.3-1.fc12
[abrt] crash detected in firefox-3.5.3-1.fc12
Product: Fedora
Classification: Fedora
Component: xulrunner (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2009-09-22 08:53 EDT by Wolfgang Ulbrich
Modified: 2010-12-04 02:40 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-04 02:40:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (20.61 KB, text/plain)
2009-09-22 08:53 EDT, Wolfgang Ulbrich
no flags Details

  None (edit)
Description Wolfgang Ulbrich 2009-09-22 08:53:42 EDT
abrt detected a crash.

How to reproduce
1. save a link in another folder

I wanted to save a link. If i click on the button for open other link folders firefox crash.

Additional information

Attached files






Process was terminated by signal 11
Comment 1 Wolfgang Ulbrich 2009-09-22 08:53:45 EDT
Created attachment 362073 [details]
File: backtrace
Comment 2 Matěj Cepl 2009-09-22 10:39:24 EDT
Crash is somewhere in xulrunner when calling sqlite:

#0  0x00007fbb4e4971eb in raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42
No locals.
#1  0x00007fbb4ba28316 in ?? () from /usr/lib64/xulrunner-1.9.1/libxul.so
No symbol table info available.
#2  <signal handler called>
No symbol table info available.
#3  0x00000038df20c0b4 in ?? () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#4  0x00000038df2651b7 in ?? () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#5  0x00000038df254b58 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#6  0x00007fbb4c1c6787 in ?? () from /usr/lib64/xulrunner-1.9.1/libxul.so
No symbol table info available.

(and abrt didn't download xulrunner-debuginfo, jmoskovc???)
Comment 3 Bug Zapper 2009-11-16 07:45:41 EST
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
Comment 4 Bug Zapper 2010-11-04 05:52:53 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2010-12-04 02:40:09 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.