Description of problem: Moving items added to my cart (was combo of items) to a wishlist on newegg.com after logging into my account. Had another tab open to my webmail client. Version-Release number of selected component: midori-0.5.10-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: midori crash_function: invalid_closure_notify executable: /usr/bin/midori global_pid: 28050 kernel: 4.1.5-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 invalid_closure_notify at gsignal.c:3721 #1 closure_invoke_notifiers at gclosure.c:256 #2 g_closure_invalidate at gclosure.c:562 #3 g_closure_unref at gclosure.c:584 #4 handler_unref_R at gsignal.c:637 #5 handler_match_free1_R at gsignal.c:466 #6 signal_handlers_foreach_matched_R at gsignal.c:2724 #7 g_signal_handlers_disconnect_matched at gsignal.c:2864 #8 soup_auth_manager_request_unqueued at soup-auth-manager.c:706 #13 soup_session_unqueue_item at soup-session.c:1542
Created attachment 1070810 [details] File: backtrace
Created attachment 1070811 [details] File: cgroup
Created attachment 1070812 [details] File: core_backtrace
Created attachment 1070813 [details] File: dso_list
Created attachment 1070814 [details] File: environ
Created attachment 1070815 [details] File: limits
Created attachment 1070816 [details] File: maps
Created attachment 1070817 [details] File: mountinfo
Created attachment 1070818 [details] File: namespaces
Created attachment 1070819 [details] File: open_fds
Created attachment 1070820 [details] File: proc_pid_status
Created attachment 1070821 [details] File: var_log_messages
http://secure.newegg.com/Shopping/ShoppingCart.aspx
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.