Version-Release number of selected component: midori-0.5.6-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/midori executable: /usr/bin/midori kernel: 3.12.6-300.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 JSC::JITCode::execute at /lib/libjavascriptcoregtk-1.0.so.0 #2 JSC::Interpreter::executeCall at /lib/libjavascriptcoregtk-1.0.so.0 #3 JSC::call at /lib/libjavascriptcoregtk-1.0.so.0 #4 WebCore::JSEventListener::handleEvent at /lib/libwebkitgtk-1.0.so.0 #5 WebCore::EventTarget::fireEventListeners at /lib/libwebkitgtk-1.0.so.0 #7 WebCore::Node::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0 #8 WebCore::EventContext::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0 #9 WebCore::EventDispatcher::dispatch at /lib/libwebkitgtk-1.0.so.0 #10 WebCore::EventDispatchMediator::dispatchEvent at /lib/libwebkitgtk-1.0.so.0
Created attachment 845192 [details] File: backtrace
Created attachment 845193 [details] File: cgroup
Created attachment 845194 [details] File: core_backtrace
Created attachment 845195 [details] File: dso_list
Created attachment 845196 [details] File: environ
Created attachment 845197 [details] File: limits
Created attachment 845198 [details] File: maps
Created attachment 845199 [details] File: open_fds
Created attachment 845200 [details] File: proc_pid_status
Created attachment 845201 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
Another user experienced a similar problem: New Fedora 20 install (System previously had Fedora Core 3-Fedora 18, but this install was clean). Run YUM upgrade. Run YUM install Seamonkey. Run Seamonkey to initialize. Close. Run Midori to initiailze. Close. Run Midori Private Browsing. Open new tab, go to https://www.google.com. Run search for "Fedora". Crash. reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: midori --private executable: /usr/bin/midori kernel: 3.13.5-202.fc20.i686 package: midori-0.5.7-1.fc20 reason: midori killed by SIGILL runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Crashed while browsing website. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: midori executable: /usr/bin/midori kernel: 3.11.10-301.fc20.i686+PAE package: midori-0.5.7-1.fc20 reason: midori killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: midori executable: /usr/bin/midori kernel: 3.14.3-200.fc20.i686+PAE package: midori-0.5.8-1.fc20 reason: midori killed by SIGILL runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Log into Facebook, scroll down news feed. Hangs for a few seconds, then exits with SIGILL. If it helps, I am using older hardware: AMD Athlon XP 1800+ (Doesn't have the newer instructions that most programs need now) 512 MB DDR 15 GB HDD (Btrfs) It's more than likely because my CPU doesn't support SSE2. reporter: libreport-2.2.2 backtrace_rating: 3 cmdline: midori executable: /usr/bin/midori kernel: 3.14.3-200.fc20.i686+PAE package: midori-0.5.8-1.fc20 reason: midori killed by SIGILL runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: browse onedrive.live.com. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/bin/midori executable: /usr/bin/midori kernel: 3.17.2-200.fc20.i686+PAE package: midori-0.5.8-1.fc20 reason: midori killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.