Bug 1102948

Summary: [abrt] midori: midori_tab_update_actions_co(): midori killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: midoriAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bernhard567, jones.peter.busi, kevin, red, stephane.kaloustian
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ab073eafa3d7387e799a6b1139981a250592a2f4
Whiteboard: abrt_hash:58ca69773b8d16974fce1c51fbb23b467a33f5f6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:02:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Peter H. Jones 2014-05-29 21:28:47 UTC
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

Comment 1 Peter H. Jones 2014-05-29 21:28:51 UTC
Created attachment 900528 [details]
File: backtrace

Comment 2 Peter H. Jones 2014-05-29 21:28:53 UTC
Created attachment 900529 [details]
File: cgroup

Comment 3 Peter H. Jones 2014-05-29 21:28:54 UTC
Created attachment 900530 [details]
File: core_backtrace

Comment 4 Peter H. Jones 2014-05-29 21:28:56 UTC
Created attachment 900531 [details]
File: dso_list

Comment 5 Peter H. Jones 2014-05-29 21:28:58 UTC
Created attachment 900532 [details]
File: environ

Comment 6 Peter H. Jones 2014-05-29 21:28:59 UTC
Created attachment 900533 [details]
File: exploitable

Comment 7 Peter H. Jones 2014-05-29 21:29:01 UTC
Created attachment 900534 [details]
File: limits

Comment 8 Peter H. Jones 2014-05-29 21:29:03 UTC
Created attachment 900535 [details]
File: maps

Comment 9 Peter H. Jones 2014-05-29 21:29:05 UTC
Created attachment 900536 [details]
File: open_fds

Comment 10 Peter H. Jones 2014-05-29 21:29:07 UTC
Created attachment 900537 [details]
File: proc_pid_status

Comment 11 Peter H. Jones 2014-05-29 21:29:08 UTC
Created attachment 900538 [details]
File: var_log_messages

Comment 12 Kevin Fenzi 2014-05-29 21:32:48 UTC
What were you doing when this happened? 

Can you duplicate it?

Comment 13 Peter H. Jones 2014-09-09 19:05:57 UTC
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.

Comment 14 Peter H. Jones 2014-09-09 19:45:17 UTC
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 .

Comment 15 Peter H. Jones 2014-09-09 19:58:43 UTC
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.

Comment 16 Peter H. Jones 2014-09-09 21:03:02 UTC
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.

Comment 17 Kevin Fenzi 2014-09-10 19:12:58 UTC
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' ?

Comment 18 stephane.kaloustian 2014-11-11 13:50:00 UTC
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

Comment 19 Fedora End Of Life 2015-05-29 11:58:47 UTC
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.

Comment 20 Fedora End Of Life 2015-06-30 01:02:00 UTC
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.