Hide Forgot
Version-Release number of selected component: pidgin-2.10.7-8.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #2 sighandler at gtkmain.c:179 #4 ?? #9 purple_media_stream_info at media.c:904 #10 pidgin_media_delete_event_cb at gtkmedia.c:221 #11 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #16 gtk_widget_event_internal at gtkwidget.c:5017 #17 gtk_widget_event at gtkwidget.c:4814 #18 gtk_main_do_event at gtkmain.c:1587 #24 gtk_main at gtkmain.c:1257 Potential duplicate: bug 711051
Created attachment 839011 [details] File: backtrace
Created attachment 839012 [details] File: cgroup
Created attachment 839013 [details] File: core_backtrace
Created attachment 839014 [details] File: dso_list
Created attachment 839015 [details] File: environ
Created attachment 839016 [details] File: limits
Created attachment 839017 [details] File: maps
Created attachment 839018 [details] File: open_fds
Created attachment 839019 [details] File: proc_pid_status
Created attachment 839020 [details] File: var_log_messages
Another user experienced a similar problem: Unknown reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.12.9-301.fc20.x86_64 package: pidgin-2.10.7-8.fc20 reason: pidgin killed by SIGABRT runlevel: 5 3 type: CCpp uid: 1222
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Another user experienced a similar problem: Just received a message from a buddy, then selected the window to see what it was. reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.13.5-202.fc20.x86_64 package: pidgin-2.10.9-1.fc20 reason: pidgin killed by SIGABRT 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.
Another user experienced a similar problem: This crash happened while I was away having lunch, so I honestly have no idea what was going on. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/bin/pidgin --session 290b18ec5-e2a2-4d8b-8fc2-24d68afdb7ad --display :0.0 crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.19.8-100.fc20.x86_64 package: pidgin-2.10.10-3.fc20 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 9661
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.