abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: midori component: midori crash_function: strcmp executable: /usr/bin/midori kernel: 2.6.35.6-48.fc14.i686 package: midori-0.2.8-1.fc14 rating: 4 reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290819383 uid: 500 How to reproduce ----- 1. 2. 3. opened program
Created attachment 463209 [details] File: backtrace
Package: midori-0.2.8-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. create bookmark http://www.youtube.com as the first in an empty shortcut page 2. click on that shortcut 3. crash Comment ----- It does not happen if I enter the URL directly to the address bar. The shortcuts are not saved, so I see an empty page again at the next start of Midori.
when you say shortcuts you mean the speed dial page? Or bookmarks?
(In reply to comment #3) Speed dial page. Crash occurs when the shortcut will be modified directly by click without using the sidebar. Recently tested additionally: creating a bookmark in the sidebar and creating over the sidebar a shortcut in the speed dial page. Both work.
Can you try the 0.2.9 midori scratch build at: http://kojipkgs.fedoraproject.org/scratch/kevin/task_2617792/ Does it do the same?
(In reply to comment #5) Same behaviour with 0.2.9 midori. Though, abrt does not seem to notice the crash.
Yeah, thats expected, since the package is not official. ;) I'll see what upstream makes of this.
What version of webkitgtk do you have there? rpm -q webkitgtk Upstream says "might be a corrupted pointer in webkit_web_view_get_resource". If you are using 1.3.6, I can file a webkit bug on it.
[raphael@lokalhorst /]$ rpm -q webkitgtk webkitgtk-1.3.6-1.fc14.x86_64
Filed upstream as: https://bugs.webkit.org/show_bug.cgi?id=50173
*** Bug 660715 has been marked as a duplicate of this bug. ***
*** Bug 665783 has been marked as a duplicate of this bug. ***
*** Bug 667092 has been marked as a duplicate of this bug. ***
I can also reproduce with Midori 0.3.0 midori-0.3.0-2.fc14.x86_64 webkitgtk-1.3.10-1.fc14.x86_64 about:version Version numbers in brackets show the version used at runtime. Command line /usr/bin/midori Midori 0.3.0 WebKitGTK+ 1.3.10 (1.3.10) GTK+ 2.22.0 (2.22.0) Glib 2.26.0 (2.26.0) libsoup 2.29.3 libnotify Yes libidn No libunique Yes libhildon No Platform Linux x86_64 Identification Midori/0.3 (X11; Linux; U; de-de) WebKit/534.16+
*** Bug 680752 has been marked as a duplicate of this bug. ***
Package: midori-0.2.9-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. try to add shortcut 2. select shortcut 3.
It seems to work better in version 0.3.0 of Midori, although the configuration (shortcuts) are not saved permanently and are only available for the current active and open tab. Crashes can occur also and randomly.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Upstream bug report at: https://bugs.launchpad.net/midori/+bug/736427
Why has this bug been reassigned to 0xFFFF?
Sorry about that. Moving back.
Package: midori-0.2.9-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. I added a new shortcut.
Works for me in Midori 0.3.6
*** Bug 742724 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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