Version-Release number of selected component: midori-0.5.6-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: midori crash_function: g_type_check_instance_cast executable: /usr/bin/midori kernel: 3.12.5-302.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4008 #1 midori_browser_save_resources at /usr/src/debug/midori-0.5.6/midori/midori-browser.c:1274 #2 midori_browser_save_uri at /usr/src/debug/midori-0.5.6/midori/midori-browser.c:1363 #3 _action_save_as_activate at /usr/src/debug/midori-0.5.6/midori/midori-browser.c:2727 #9 _gtk_action_emit_activate at gtkaction.c:795 #10 closure_accel_activate at gtkaction.c:1766 #15 gtk_accel_group_activate at gtkaccelgroup.c:891 #16 gtk_accel_groups_activate at gtkaccelgroup.c:928 #17 gtk_window_activate_key at gtkwindow.c:8355 #18 sokoke_window_activate_key at /usr/src/debug/midori-0.5.6/midori/sokoke.c:793 Potential duplicate: bug 961676
Created attachment 845274 [details] File: backtrace
Created attachment 845277 [details] File: cgroup
Created attachment 845279 [details] File: core_backtrace
Created attachment 845281 [details] File: dso_list
Created attachment 845283 [details] File: environ
Created attachment 845285 [details] File: limits
Created attachment 845287 [details] File: maps
Created attachment 845289 [details] File: open_fds
Created attachment 845290 [details] File: proc_pid_status
Created attachment 845291 [details] File: var_log_messages
Created attachment 845293 [details] File: exploitable
What were you doing when this happened? Can you duplicate the crash?
Another user experienced a similar problem: Trying to save wikipedia article on Cyrillic aplhabet reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: midori crash_function: g_type_check_instance_cast executable: /usr/bin/midori kernel: 3.12.9-301.fc20.x86_64 package: midori-0.5.7-1.fc20 reason: midori killed by SIGSEGV 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.