Hide Forgot
Description of problem: Midori has been closed when i tried to open link by clicking on it on actual page. i have new installed fedora. same thing is happening with terminal emulator. just closed almost few seconds after i opened it. Version-Release number of selected component: midori-0.5.5-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/bin/midori executable: /usr/bin/midori kernel: 3.11.10-301.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 JSC::JITCode::execute at /lib/libjavascriptcoregtk-1.0.so.0 #2 JSC::Interpreter::execute at /lib/libjavascriptcoregtk-1.0.so.0 #3 JSC::evaluate at /lib/libjavascriptcoregtk-1.0.so.0 #4 WebCore::ScriptController::evaluateInWorld at /lib/libwebkitgtk-1.0.so.0 #5 WebCore::ScriptController::executeScriptInWorld at /lib/libwebkitgtk-1.0.so.0 #6 WebCore::ScheduledAction::execute at /lib/libwebkitgtk-1.0.so.0 #8 WebCore::DOMTimer::fired at /lib/libwebkitgtk-1.0.so.0 #9 WebCore::ThreadTimers::sharedTimerFiredInternal at /lib/libwebkitgtk-1.0.so.0 #10 WebCore::ThreadTimers::sharedTimerFired at /lib/libwebkitgtk-1.0.so.0
Created attachment 844292 [details] File: backtrace
Created attachment 844293 [details] File: cgroup
Created attachment 844294 [details] File: core_backtrace
Created attachment 844295 [details] File: dso_list
Created attachment 844296 [details] File: environ
Created attachment 844297 [details] File: exploitable
Created attachment 844298 [details] File: limits
Created attachment 844299 [details] File: maps
Created attachment 844300 [details] File: open_fds
Created attachment 844301 [details] File: proc_pid_status
Created attachment 844302 [details] File: var_log_messages
Can you attach 'dmesg' output? Is it just terminals and midori that are crashing? Or other things?
Created attachment 844546 [details] dmesg dmesg printed by user, not root, hope its ok.
i have some more info: this is my second installation on not long time, and with this first, midori happend to close same way. i had to reinstall due to my not well maintained task on partitions (i am comletly fresh with linux). and minute ago, i tried to open some other programs to check if it happend not only with midora and terminal. i opened Blender, and even didn't start: Process /usr/bin/blender killed by signal 4 (SIGILL). maybe same problem. dont know: of course. and one thing more. i think that with this first installation, when i used some more time, the problem has been less annoying. i mean, i think, probably badly, problem has disappear by self-repair. ok. done it. sorry for my english. and i hope that i am doing it right to write this here not on pm. regards lukasz
Hum. SIGILL seems more like it might be a hardware error. Perhaps check all the fans and heat sinks on your machine to see if there's any overheating going on?
Hm. First, I upgraded Midori to latest version. Then, I changed few settings in BIOS related to temp, eg. disabled bios temp control of disk and cpu. It did not change a bit of working Midora. Still closing, specially with heavier loaded with pictures pages, even when dont show them. Just before I installed Fedora I was using Windows Vista on this PC, and many times was cpu was heavy occupied and nothing was happend. Maybe You can show me a way to disable system temp checkin to check if it is really problem with overheating? thks for really quick response, and sorry for my not so quick ;)
No problem on the delay... ;) Anyhow, I am not sure what to suggest next... there are some newer versions of midori available, so you could try just doing a full 'yum update' and see if things are better. Does the problem persist when you boot from a live media? That would tell us if it's hardware or something with your install.
Another user experienced a similar problem: Normal surfing, nothing unusual. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: midori executable: /usr/bin/midori kernel: 3.15.10-201.fc20.i686+PAE package: midori-0.5.8-1.fc20 reason: midori killed by SIGTRAP runlevel: N 5 type: CCpp uid: 3000
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.