Description of problem: import bookmarks from html file second attempt successfull 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.11.10-301.mo.fc20.R.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4003 #1 midori_bookmarks_add_item_cb at /usr/src/debug/midori-0.5.6/panels/midori-bookmarks.c:225 #6 katze_array_add_item at /usr/src/debug/midori-0.5.6/katze/katze-array.c:281 #7 midori_bookmarks_db_add_item at /usr/src/debug/midori-0.5.6/midori/midori-bookmarks-db.c:638 #8 midori_bookmarks_db_import_array at /usr/src/debug/midori-0.5.6/midori/midori-bookmarks-db.c:777 #9 _action_bookmarks_import_activate at /usr/src/debug/midori-0.5.6/midori/midori-browser.c:4601 #14 _gtk_action_emit_activate at gtkaction.c:795 #15 _g_closure_invoke_va at gclosure.c:840 #18 gtk_widget_activate at gtkwidget.c:5048 #19 gtk_menu_shell_activate_item at gtkmenushell.c:1303
Created attachment 840898 [details] File: backtrace
Created attachment 840899 [details] File: cgroup
Created attachment 840900 [details] File: core_backtrace
Created attachment 840901 [details] File: dso_list
Created attachment 840902 [details] File: environ
Created attachment 840903 [details] File: limits
Created attachment 840904 [details] File: maps
Created attachment 840905 [details] File: open_fds
Created attachment 840906 [details] File: proc_pid_status
Created attachment 840907 [details] File: var_log_messages
Created attachment 840908 [details] File: exploitable
So it only crashes sometimes with the same set of bookmarks as input? Or can you see any pattern to the crashes? Any chance you could attach a bookmark set that causes the crash? Thanks.
Bookmarks same,but there were only two attempts, the second successful can try other 3?-Yes
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.