Bug 611193 - [abrt] crash in uzbl-core-0-0.13.20100410gitec473e124.fc13: raise: Process /usr/bin/uzbl-core was killed by signal 6 (SIGABRT)
[abrt] crash in uzbl-core-0-0.13.20100410gitec473e124.fc13: raise: Process /u...
Status: CLOSED DUPLICATE of bug 604268
Product: Fedora
Classification: Fedora
Component: uzbl (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Daiki Ueno
Fedora Extras Quality Assurance
abrt_hash:69b49df06bf8748d65d13954e47...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-04 03:33 EDT by Jens Petersen
Modified: 2010-07-05 21:10 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-05 21:10:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (40.60 KB, text/plain)
2010-07-04 03:33 EDT, Jens Petersen
no flags Details

  None (edit)
Description Jens Petersen 2010-07-04 03:33:07 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: uzbl-core --connect-socket /home/petersen/.cache/uzbl/event_daemon
component: uzbl
crash_function: raise
executable: /usr/bin/uzbl-core
global_uuid: 69b49df06bf8748d65d13954e473fc8caa181fae
kernel: 2.6.33.5-124.fc13.x86_64
package: uzbl-core-0-0.13.20100410gitec473e124.fc13
rating: 4
reason: Process /usr/bin/uzbl-core was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: can't get uzbl to start again - now crashes on startup
Comment 1 Jens Petersen 2010-07-04 03:33:10 EDT
Created attachment 429337 [details]
File: backtrace
Comment 2 Ben Boeckel 2010-07-04 09:51:27 EDT
Looks similar to Bug #604268. Could you try the instructions in comment #2 there?
Comment 3 Jens Petersen 2010-07-05 21:10:45 EDT
Thanks - yeah that helps - though uzbl plugin handling looks a little fragile?

*** This bug has been marked as a duplicate of bug 604268 ***

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