Bug 563229 - [abrt] crash in firefox-3.5.6-1.fc12
Summary: [abrt] crash in firefox-3.5.6-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 537519
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6611d21adaa98e0f4597cee96a7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-09 16:06 UTC by abrt-auto
Modified: 2010-02-09 17:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-09 17:49:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (63.25 KB, text/plain)
2010-02-09 16:07 UTC, abrt-auto 		no flags Details
View All

Description abrt-auto 2010-02-09 16:06:59 UTC 
abrt 1.0.4 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5.6/firefox
comment: The error occured while browsing a Flash page.
component: firefox
executable: /usr/lib64/firefox-3.5.6/firefox
kernel: 2.6.31.6-166.fc12.x86_64
package: firefox-3.5.6-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 abrt-auto 2010-02-09 16:07:03 UTC 
Created attachment 389784 [details]
File: backtrace
Comment 2 Chris Campbell 2010-02-09 17:48:02 UTC 
#2  <signal handler called>
No symbol table info available.
#3  _poppopupsenabledstate (npp=0x0) at nsNPAPIPlugin.cpp:2413
        inst = <value optimized out>




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Chris Campbell 2010-02-09 17:49:05 UTC 
Thank you for taking the time to submit this bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 537519 ***
Note You need to log in before you can comment on or make changes to this bug.