Bug 606051 - [abrt] crash in firefox-3.6.3-4.fc13: trace: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.3-4.fc13: trace: Process /usr/lib/firefox-3.6/fir...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:5980a9d7f49c26b8fc776c4f9c8...
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-20 07:39 UTC by Oyvind Rangoy
Modified: 2011-01-27 18:12 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2011-01-27 18:12:18 UTC

Attachments (Terms of Use)
File: backtrace (212.32 KB, text/plain)
2010-06-20 07:39 UTC, Oyvind Rangoy
no flags Details

Description Oyvind Rangoy 2010-06-20 07:39:03 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox
comment: In FC12, the Internet banking would word with openjdk, after upgrading Sun Java was neceessary. Lately, this has caused a lot of Firefox crashes.
component: firefox
crash_function: trace
executable: /usr/lib/firefox-3.6/firefox
global_uuid: 5980a9d7f49c26b8fc776c4f9c818927657716c2
package: firefox-3.6.3-4.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. Install SUN Java
2. Use Norwegian Internet banking solution from SparaBank1

Comment 1 Oyvind Rangoy 2010-06-20 07:39:10 UTC
Created attachment 425419 [details]
File: backtrace

Comment 2 d. johnson 2010-08-13 16:08:42 UTC
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update' or using the graphical updater, Software Update.

Disable extensions, plugins and non-default themes. Clear cookies and cache. Exit the browser completely.  Then restart the browser and attempt to replicate the crash.

Fedora Bugzappers volunteer triage team

Comment 3 Chris Campbell 2011-01-27 18:12:18 UTC
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 reporter's distribution.

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 information.


Fedora Bugzappers volunteer triage team

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