Version-Release number of selected component: putty-0.63-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: putty crash_function: findrelpos234 executable: /usr/bin/putty kernel: 3.13.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 findrelpos234 at ../tree234.c:547 #1 find234 at ../tree234.c:624 #2 dlg_find_bywidget at ../unix/gtkdlg.c:223 #3 button_clicked at ../unix/gtkdlg.c:1237 #4 _g_closure_invoke_va at gclosure.c:840 #7 gtk_real_button_released at gtkbutton.c:1712 #8 _g_closure_invoke_va at gclosure.c:840 #11 gtk_button_button_release at gtkbutton.c:1604 #12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #17 gtk_widget_event_internal at gtkwidget.c:5017
Created attachment 870846 [details] File: backtrace
Created attachment 870847 [details] File: cgroup
Created attachment 870848 [details] File: core_backtrace
Created attachment 870849 [details] File: dso_list
Created attachment 870850 [details] File: environ
Created attachment 870851 [details] File: exploitable
Created attachment 870852 [details] File: limits
Created attachment 870853 [details] File: maps
Created attachment 870854 [details] File: open_fds
Created attachment 870855 [details] File: proc_pid_status
Created attachment 870856 [details] File: var_log_messages
Another user experienced a similar problem: I clicked the close button, changed my mind and clicked on "No" when asked whether I really wanted to close. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: putty crash_function: findrelpos234 executable: /usr/bin/putty kernel: 3.14.2-200.fc20.x86_64 package: putty-0.63-1.fc20 reason: putty killed by SIGBUS runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I exited the remote session with jobs running. PuTTY failed to close by itself, so I closed the window. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: putty crash_function: findrelpos234 executable: /usr/bin/putty kernel: 3.14.7-200.fc20.x86_64 package: putty-0.63-1.fc20 reason: putty 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.