Hide Forgot
Description of problem: Nothing special, pidgin crashed whilst in the background. Version-Release number of selected component: pidgin-2.10.9-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: pidgin --session 10609a6ae5ce1e08e5140377765362224800000018750096 --display :0 crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 sighandler at gtkmain.c:179 #4 sip_sec_init_sec_context__tls_dsk at sip-sec-tls-dsk.c:80 #5 sip_sec_init_context_step at sip-sec.c:184 #6 initialize_auth_context at sip-transport.c:222 #7 auth_header at sip-transport.c:358 #8 sign_outgoing_message at sip-transport.c:447 #9 sip_transport_request_timeout at sip-transport.c:771 #10 sip_transport_request at sip-transport.c:818 #11 sip_transport_subscribe at sip-transport.c:911 #12 sipe_unsubscribe_cb at sipe-subscriptions.c:86
Created attachment 922225 [details] File: backtrace
Created attachment 922226 [details] File: cgroup
Created attachment 922227 [details] File: core_backtrace
Created attachment 922228 [details] File: dso_list
Created attachment 922229 [details] File: environ
Created attachment 922230 [details] File: limits
Created attachment 922231 [details] File: maps
Created attachment 922232 [details] File: open_fds
Created attachment 922233 [details] File: proc_pid_status
Created attachment 922234 [details] File: var_log_messages
This time, pidgin crashed when I undocked my laptop, hence disconnecting a screen.
Another user experienced a similar problem: Unsure how to reproduce, was running multiple conversations, including a couple of group chats. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.17.3-200.fc20.x86_64 package: pidgin-2.10.10-1.fc20 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp
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.