Bug 647359 - [abrt] xulrunner-1.9.2.10-1.fc14.1: XChangeProperty: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.10-1.fc14.1: XChangeProperty: Process /usr/lib64/xulru...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4baf021329f98813f1da183aad2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-28 04:22 UTC by Vector Thorn
Modified: 2011-12-07 13:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:23:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (64.97 KB, text/plain)
2010-10-28 04:22 UTC, Vector Thorn 		no flags Details
View All

Description Vector Thorn 2010-10-28 04:22:46 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /home/Vector/.mozilla/plugins/libflashplayer.so 2342 plugin
component: xulrunner
crash_function: XChangeProperty
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.35.4-28.fc14.x86_64
package: xulrunner-1.9.2.10-1.fc14.1
rating: 3
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288238275
uid: 500

How to reproduce
-----
1. I really
2. don't
3. know...
Comment 1 Vector Thorn 2010-10-28 04:22:49 UTC 
Created attachment 456148 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:23:50 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

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