Red Hat Bugzilla – Bug 1033114
[abrt] pidgin-2.10.7-8.fc20: purple_proxy_connect_data_destroy: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Last modified: 2015-06-29 09:06:02 EDT
Description of problem:
Trying to login using Pidgin, Connected with same settings as Fedora 19, but kept saying read error before the cash.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#6 purple_proxy_connect_data_destroy at proxy.c:585
#7 purple_proxy_connect_cancel at proxy.c:2562
#8 sipe_backend_transport_disconnect at purple-transport.c:312
#9 sip_transport_disconnect at sip-transport.c:1328
#10 sipe_core_connection_cleanup at sipe-core.c:350
#11 sipe_core_deallocate at sipe-core.c:409
#12 sipe_purple_close at purple-plugin.c:470
#13 _purple_connection_destroy at connection.c:275
#14 purple_account_disconnect at account.c:1284
#15 enabled_cb at gtkaccount.c:1995
Created attachment 827265 [details]
Created attachment 827266 [details]
Created attachment 827267 [details]
Created attachment 827268 [details]
Created attachment 827269 [details]
Created attachment 827270 [details]
Created attachment 827271 [details]
Created attachment 827272 [details]
Created attachment 827273 [details]
Created attachment 827274 [details]
I don't get the crash, but I do get the read errors. This worked with no issues in F-19.
Actually, I'm hitting bug #770682 in F20. For whatever reason, this worked in F19 and before.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Are you still experiencing the bug? Even with pidgin-2.10.9-1.fc20?
Created attachment 864206 [details]
Yes, still happening with pidgin-2.10.9-1.fc20, not sure it's the exact same bug though but that's what abrt seems to think...
Happened to me when I tried to disable a sipe account, after I lost my Wifi connection.
Another user experienced a similar problem:
I tried to disable an account (office communicator account) while it was attempting to sign in. I has started getting a certificate provisioning error and was trying to fix it by modifying settings. I changed a setting and was trying to disable the re enable the account to apply the new settings.
reason: pidgin killed by SIGABRT
runlevel: N 5
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'
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
Thank you for reporting this bug and we are sorry it could not be fixed.