Bug 617426 - [abrt] crash in uzbl-core-0-0.13.20100410gitec473e124.fc13: raise: Process /usr/bin/uzbl-core was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in uzbl-core-0-0.13.20100410gitec473e124.fc13: raise: Process /u...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uzbl
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:011ef5e884e1c77fa5c8b75af9e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-23 02:25 UTC by Arnaud Bergmann
Modified: 2010-09-01 23:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-01 23:21:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (38.70 KB, text/plain)
2010-07-23 02:26 UTC, Arnaud Bergmann
no flags Details

Description Arnaud Bergmann 2010-07-23 02:25:59 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: uzbl-core --connect-socket /home/Arnaud/.cache/uzbl/event_daemon
comment: I just run uzbl for the first time and it crashed.
component: uzbl
crash_function: raise
executable: /usr/bin/uzbl-core
global_uuid: 011ef5e884e1c77fa5c8b75af9e643a4b25e76d2
kernel: 2.6.33.6-147.fc13.i686
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
-----
1. run uzbl
2.
3.

Comment 1 Arnaud Bergmann 2010-07-23 02:26:01 UTC
Created attachment 433860 [details]
File: backtrace

Comment 2 Daiki Ueno 2010-07-23 04:06:03 UTC
Looks similar to #604268, #606966, #608696, #611193, and #617426.
Could you try comment #2 of #604268?

If it fixes the crash, I'll close this bug as DUPLICATE.

Hmm, even surf and midori are getting similar bugs...

Comment 3 Ben Boeckel 2010-08-22 22:54:50 UTC
Could you please try with:

    java-1.6.0-openjdk-1.6.0.0-42.b18.fc13

I'll close at the end of the week if there's no response.

Comment 4 Ben Boeckel 2010-09-01 23:21:46 UTC
Closing. Reopen if the problem persists.


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