Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 21682 bytes cmdline: midori comment: Always reproduceable. The URL is not RFC conform and the base64 part is shortened from a larger version but it does the crash as well. component: midori Attached file: coredump, 2208243712 bytes executable: /usr/bin/midori kernel: 2.6.35.13-92.fc14.x86_64 package: midori-0.2.9-4.fc14 rating: 3 reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1311524873 uid: 500 How to reproduce ----- 1. Entering "data://text/plain;base64,iVBOR" into the address bar. 2. Choosing the "open" button. 3. Crash
Created attachment 514930 [details] File: backtrace
Can you try this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3226192
Tried, still crashes with address "data://text/plain;base64,iVBOR" and then clicking "open" button.
So, it's looking like a webkitgtk issue more than a midori one. Does the problem also occur with: /usr/libexec/webkitgtk/GtkLauncher (This is webkitgtk's reference browser).
Tested: $ /usr/libexec/webkitgtk/GtkLauncher "data://text/plain;base64,iVBOR" It does not crash but gives DEBUG and WARNING messages in shell, but looks safe.
Hum, so it's looking like a midori and webkitgtk issue. :( I'll see what I can do, but we can't upgrade webkitgtk in f14.
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