abrt 1.1.0 detected a crash.
Attached file: backtrace
comment: It crashed when opening a new tab from a link in an already opened tab. Perhaps this bug report is in webkitgtk instead of midori?
reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
1. Random crash
Created attachment 416371 [details]
This looks like a strange dns issue, possibly in webkitgtk.
Are you using ipv6 there?
Can you update to the 0.2.7 version of midori (in updates-testing) and see if it fixes the issue?
*** Bug 625618 has been marked as a duplicate of this bug. ***
*** Bug 628256 has been marked as a duplicate of this bug. ***
*** Bug 618666 has been marked as a duplicate of this bug. ***
My apologies for the delay, I was out of town for several weeks. Catching up as it were.
No, I'm not using IPv6 here. But there could be DNS problems I could blame on my ISP, DNS resolution is very slow lately; besides I know for a fact their infrastructure runs on win2003, meh!
OTOH, the midori 0.2.7-1 package in Koji doesn't install because it asks for an old libwebkitgtk-1.0.so.0 while the one installed is libwebkitgtk-1.0.so.2. Even rpm won't let me for a force install. :-(
I'll install mock, brew my own binaries and get back to you on this one.
What webkitgtk do you have installed now?
I have webkitgtk 1.2.0-1.fc13 installed. I just managed to compile midori-0.2.7-1 from the f14 srpm in Koji and it is working fine; no changes to the srpm needed at all.
I have to say that DNS resolution is working lightning fast with midori (not as much with Firefox 3.6 nor Google Chrome). Page loading is very quick too. Seems like a winner to me. :-)
There should be a f13 midori as well in updates-testing. ;)
f13 is on the 1.2.x webkitgtk versions, and f14 is on 1.3.x, so yes, a f14 one wouldn't just install on f13.
Unfortunately there is nothing in updates-testing :-(. Perhaps a bungled push from koji?
Oh, my mistake, this is f13. No, there isn't an update because in 0.2.7 the interface changed somewhat and we didn't want to push that to stable releases.
Aha! Well, I'll move to F14 in the beta cycle anyway... Meanwhile, another excuse to keep honing my, very scarce, hacking chops. :-)
*** Bug 636940 has been marked as a duplicate of this bug. ***
*** Bug 637587 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Can folks here try this scratch build:
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:
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.