Bug 597957 - [abrt] crash in midori-0.2.4-1.fc13: raise: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in midori-0.2.4-1.fc13: raise: Process /usr/bin/midori was kille...
Status: CLOSED DUPLICATE of bug 604499
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:1871c27524134b4e60c186e1ff9...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-31 05:36 UTC by wmak.othermail
Modified: 2010-08-28 23:41 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-08-28 23:41:46 UTC

Attachments (Terms of Use)
File: backtrace (28.08 KB, text/plain)
2010-05-31 05:36 UTC, wmak.othermail
no flags Details

Description wmak.othermail 2010-05-31 05:36:23 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: midori
comment: Midori cannot even be launched - crashes immediately.
component: midori
crash_function: raise
executable: /usr/bin/midori
global_uuid: 1871c27524134b4e60c186e1ff9c8585138499ad
package: midori-0.2.4-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: Crash on launch.

Comment 1 wmak.othermail 2010-05-31 05:36:27 UTC
Created attachment 418161 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-08-28 23:41:46 UTC
This is caused by the java plugin. See bug 604499

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

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