Bug 610065 - [abrt] crash in midori-0.2.6-1.fc13: raise: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in midori-0.2.6-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:6cdc0c7ec30d2d20287094004ea...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-01 13:40 UTC by Manuel Schilt
Modified: 2010-08-28 23:53 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2010-08-28 23:53:17 UTC

Attachments (Terms of Use)
File: backtrace (29.92 KB, text/plain)
2010-07-01 13:40 UTC, Manuel Schilt
no flags Details

Description Manuel Schilt 2010-07-01 13:40:15 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: midori
comment: Crashes when starting from Startmenu.. have no Idea if the supplied parameter is the reason for this behavior.. (startmenu command is "midori %u")
component: midori
crash_function: raise
executable: /usr/bin/midori
global_uuid: 6cdc0c7ec30d2d20287094004ea6d95e9d91b057
package: midori-0.2.6-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.start Midori from startmenu --> crashes
2.start Midori from console --> works

Comment 1 Manuel Schilt 2010-07-01 13:40:18 UTC
Created attachment 428423 [details]
File: backtrace

Comment 2 Arnaud WOROBEL 2010-07-09 09:46:58 UTC
Package: midori-0.2.6-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)

How to reproduce
1. Just launch Midori
2. It's killed immediatly with a SIGABRT 6.


I've got a problem with my fresh install of Fedora 13 : i installed XFCE environment with Midori web browser but when i launch this one, it crash immediatly.

Best regards,
Arnaud W.

Comment 3 Kevin Fenzi 2010-08-28 23:53:17 UTC
This is a java plugin bug. 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.