Bug 675969 - [abrt] xulrunner-2.0-0.18b10.fc15: _dbus_abort: Process /usr/lib64/xulrunner-2/crashreporter was killed by signal 6 (SIGABRT)
Summary: [abrt] xulrunner-2.0-0.18b10.fc15: _dbus_abort: Process /usr/lib64/xulrunner-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3acf3f6b5636b9a5400d0635cef...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-08 13:28 UTC by Stefan Lehmann
Modified: 2011-12-07 13:11 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
File: backtrace (20.94 KB, text/plain)
2011-02-08 13:28 UTC, Stefan Lehmann
no flags Details

Description Stefan Lehmann 2011-02-08 13:28:25 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 21443 bytes
cmdline: /usr/lib64/xulrunner-2/crashreporter /home/derstef/.mozilla/firefox/8prsab0y.default/minidumps/138d24b0-f1e1-f999-57fa45bc-2e0bf189.dmp
comment: neither search nor adressfield will take inputs ... browser is always crashing
component: xulrunner
Attached file: coredump, 12431360 bytes
crash_function: _dbus_abort
executable: /usr/lib64/xulrunner-2/crashreporter
kernel: 2.6.38-0.rc3.git4.1.fc15.x86_64
package: xulrunner-2.0-0.18b10.fc15
rating: 4
reason: Process /usr/lib64/xulrunner-2/crashreporter was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1297171359
uid: 500

How to reproduce
-----
1. tried to type something to the search field of firefox
2.
3.

Comment 1 Stefan Lehmann 2011-02-08 13:28:29 UTC
Created attachment 477611 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:11:47 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.