Version-Release number of selected component: midori-0.5.8-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: midori crash_function: midori_tab_update_actions_co executable: /usr/bin/midori kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 3000 Truncated backtrace: Thread no. 1 (10 frames) #0 midori_tab_update_actions_co at /usr/src/debug/midori-0.5.8/midori/midori-tab.vala:291 #1 midori_tab_update_actions at /usr/src/debug/midori-0.5.8/midori/midori-tab.vala:36 #6 _gtk_action_emit_activate at gtkaction.c:795 #7 _g_closure_invoke_va at gclosure.c:840 #10 gtk_widget_activate at gtkwidget.c:5048 #11 gtk_menu_shell_enter_notify at gtkmenushell.c:969 #12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #17 gtk_widget_event_internal at gtkwidget.c:5017 #18 gtk_widget_event at gtkwidget.c:4814 #19 gtk_menu_shell_enter_notify at gtkmenushell.c:1003
Created attachment 900528 [details] File: backtrace
Created attachment 900529 [details] File: cgroup
Created attachment 900530 [details] File: core_backtrace
Created attachment 900531 [details] File: dso_list
Created attachment 900532 [details] File: environ
Created attachment 900533 [details] File: exploitable
Created attachment 900534 [details] File: limits
Created attachment 900535 [details] File: maps
Created attachment 900536 [details] File: open_fds
Created attachment 900537 [details] File: proc_pid_status
Created attachment 900538 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
Got it today on https://onlinebanking.tdbank.com/enroll/en_enroll_details.asp . I first tried to enter a Canadian SS number, which is of the form NNN-NNN-NNN. The form refuses to accept the third digit of the second set of three! I find it hard to believe a major would make such a silly mistake in its webpage. I'll try firefox, as it is part of TD's required software.
Tried on a custome live build. I found I had to first accept a customer agreement before the SSN fiels were displayed. Again, the second field only accepts 2 digits. I used midori-0.5.8-3.fc21.x86_64 .
Same happened when I installed and tried firefox-31.0-3.fc21.x86_64 and fedora-bookmarks-15-5.fc21.noarch I'll contact TD's customer service to get more help.
Turned out I was trying to use US site to access my Canadian account. Customer service redirected me, and also helped me get registered properly. So the only problem remaining is the occasional SIGSEV trace. I noticed TD requires Adobe Flash Player, so the crash might have been due to that. It would be nice if Adobe Flash Player could be isolated so crashes due to it would be diagnosed immediately instead of looking like browser bugs.
Odd. So, the crash is sporadic? Or can you tell what triggers it? It looks like in the backtrace flash is involved, but also 'undo' ?
Another user experienced a similar problem: I had 2 or 3 tabs openend, as well as the bookmarks. I just tried to click on the "Edit" menu entry. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: midori crash_function: midori_tab_update_actions_co executable: /usr/bin/midori kernel: 3.16.6-200.fc20.x86_64 package: midori-0.5.8-1.fc20 reason: midori killed by SIGSEGV 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.