Description of problem: I had attempted a file transfer using Pidgin over google talk earlier. It did not succeed. I allowed my computer to hibernate. I awoke it. I attempted to "Stop" the (already failed) file transfer. Pidgin crashed. Note: I don't believe the crash involved them but I do have the OTR plugin (pidgin-otr) and a plugin to support lync (pidgin-sipe). Version-Release number of selected component: pidgin-2.10.5-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 sighandler at gtkmain.c:179 : #5 g_list_remove at glist.c:440 : #6 jabber_si_xfer_free at si.c:1317 : #7 jabber_si_xfer_cancel_send at si.c:1376 : #8 purple_xfer_cancel_local at ft.c:1527 : #9 _g_closure_invoke_va at gclosure.c:840 : #12 gtk_real_button_released at gtkbutton.c:1725 : #18 gtk_button_button_release at gtkbutton.c:1617 : #20 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 : #25 gtk_widget_event_internal at gtkwidget.c:5017
Created attachment 660141 [details] File: core_backtrace
Created attachment 660142 [details] File: environ
Created attachment 660143 [details] File: limits
Created attachment 660144 [details] File: backtrace
Created attachment 660145 [details] File: smolt_data
Created attachment 660146 [details] File: cgroup
Created attachment 660147 [details] File: xsession_errors
Created attachment 660148 [details] File: lamb.pdf
Created attachment 660149 [details] File: executable
Created attachment 660150 [details] File: maps
Created attachment 660151 [details] File: dso_list
Created attachment 660152 [details] File: proc_pid_status
Created attachment 660153 [details] File: var_log_messages
Created attachment 660154 [details] File: open_fds
Created attachment 660155 [details] File: build_ids
Click on the cancel button of the file transfer dialog box backtrace_rating: 4 Package: pidgin-2.10.5-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.