Bug 598947 - [abrt] crash in midori-0.2.4-1.fc13: _action_location_submit_uri: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in midori-0.2.4-1.fc13: _action_location_submit_uri: Process /us...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d349d560bcbe36eea79e67b859b...
: 602543 607371 609527 621442 625624 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 12:03 UTC by Major Hayden 🤠
Modified: 2011-06-27 17:20 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-27 17:20:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (44.41 KB, text/plain)
2010-06-02 12:03 UTC, Major Hayden 🤠
no flags Details

Description Major Hayden 🤠 2010-06-02 12:03:43 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: midori
component: midori
crash_function: _action_location_submit_uri
executable: /usr/bin/midori
global_uuid: d349d560bcbe36eea79e67b859b5ea58190d14e7
kernel: 2.6.33.3-85.fc13.x86_64
package: midori-0.2.4-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Major Hayden 🤠 2010-06-02 12:03:44 UTC
Created attachment 419003 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-08-29 19:36:42 UTC
This looks like an odd crash somewhere in webkitgtk with memory allocations. 

Can you update to the latest midori available from Fedora and also the latest webkitgtk package and see if that causes the crash to stop? 

I will see about asking upstream to look at this for more ideas.

Comment 3 Kevin Fenzi 2010-08-29 19:40:34 UTC
*** Bug 602543 has been marked as a duplicate of this bug. ***

Comment 4 Kevin Fenzi 2010-08-29 19:40:38 UTC
*** Bug 607371 has been marked as a duplicate of this bug. ***

Comment 5 Kevin Fenzi 2010-08-29 19:40:42 UTC
*** Bug 609527 has been marked as a duplicate of this bug. ***

Comment 6 Kevin Fenzi 2010-08-29 19:40:45 UTC
*** Bug 621442 has been marked as a duplicate of this bug. ***

Comment 7 Kevin Fenzi 2010-08-29 19:40:49 UTC
*** Bug 625624 has been marked as a duplicate of this bug. ***

Comment 8 dedanna 2010-08-31 00:37:27 UTC
I was already on the latest midori when this happened to me. Had just installed it, actually.

Comment 9 Kevin Fenzi 2010-08-31 00:43:17 UTC
Which version? 0.2.6? 

You can 'yum --enablerepo=updates-testing update midori' and get the 0.2.7 version.

Comment 10 dedanna 2010-08-31 00:49:53 UTC
Just happened again. Bug # 628761 generated, but I can't tell for sure if it's a duplicate to this one or not. I'm not on testing on Fedora, and prefer not to go there at this time. I'm finding too many things with it as it is. Thanks, though.

Comment 11 Fedora Admin XMLRPC Client 2011-03-15 17:20:14 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Kevin Fenzi 2011-03-27 18:07:07 UTC
Can folks here try: 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2950913

and see if the problem persists?

Comment 13 Bug Zapper 2011-06-02 12:22:13 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 14 Bug Zapper 2011-06-27 17:20:07 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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