Bug 1036926

Summary: [abrt] putty-0.63-1.fc19: button_clicked: Process /usr/bin/putty was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Davide Repetto <red>
Component: puttyAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: drizt72, jskarvad, tremble
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2b7295df7136d18fcd49cfe33c42fe3db8ec3b11
Whiteboard: abrt_hash:e3d893cc440c70cdcc16afaac6c33c83ba192391
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-10 16:12: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:
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 Davide Repetto 2013-12-02 22:21:43 UTC 
Description of problem:
Closed main app window while the "config window" was still open.

Version-Release number of selected component:
putty-0.63-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        putty
crash_function: button_clicked
executable:     /usr/bin/putty
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 button_clicked at ../unix/gtkdlg.c:1238
 #1 _g_closure_invoke_va at gclosure.c:840
 #4 gtk_real_button_released at gtkbutton.c:1712
 #5 _g_closure_invoke_va at gclosure.c:840
 #8 gtk_button_button_release at gtkbutton.c:1604
 #9 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #14 gtk_widget_event_internal at gtkwidget.c:5017
 #15 gtk_widget_event at gtkwidget.c:4814
 #16 gtk_propagate_event at gtkmain.c:2490
 #17 gtk_main_do_event at gtkmain.c:1685
Comment 1 Davide Repetto 2013-12-02 22:21:54 UTC 
Created attachment 831799 [details]
File: backtrace
Comment 2 Davide Repetto 2013-12-02 22:22:02 UTC 
Created attachment 831802 [details]
File: cgroup
Comment 3 Davide Repetto 2013-12-02 22:22:06 UTC 
Created attachment 831803 [details]
File: core_backtrace
Comment 4 Davide Repetto 2013-12-02 22:22:11 UTC 
Created attachment 831804 [details]
File: dso_list
Comment 5 Davide Repetto 2013-12-02 22:22:15 UTC 
Created attachment 831805 [details]
File: environ
Comment 6 Davide Repetto 2013-12-02 22:22:18 UTC 
Created attachment 831806 [details]
File: exploitable
Comment 7 Davide Repetto 2013-12-02 22:22:23 UTC 
Created attachment 831808 [details]
File: limits
Comment 8 Davide Repetto 2013-12-02 22:22:28 UTC 
Created attachment 831810 [details]
File: maps
Comment 9 Davide Repetto 2013-12-02 22:22:37 UTC 
Created attachment 831813 [details]
File: open_fds
Comment 10 Davide Repetto 2013-12-02 22:22:41 UTC 
Created attachment 831815 [details]
File: proc_pid_status
Comment 11 Davide Repetto 2013-12-02 22:22:45 UTC 
Created attachment 831816 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-01-09 20:45:47 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.