Bug 1052877

Summary: [abrt] pidgin: sighandler(): pidgin killed by SIGABRT
Product: [Fedora] Fedora Reporter: Marcel Wysocki <maci>
Component: pidginAssignee: Jan Synacek <jsynacek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: darthludi, itamar, jsynacek, stu, warlord
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fe66536ebe0631bd7813f0416b5119655637ce3b
Whiteboard: abrt_hash:d902f16d4338e6731aa74415258d220b24419327
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:26:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Marcel Wysocki 2014-01-14 09:48:24 UTC
Version-Release number of selected component:
pidgin-2.10.7-8.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        pidgin
crash_function: sighandler
executable:     /usr/bin/pidgin
kernel:         3.12.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 sighandler at gtkmain.c:179
 #4 g_str_hash at ghash.c:1732
 #5 sipe_ht_hash_nick at sipe-buddy.c:2110
 #6 g_hash_table_lookup_node at ghash.c:365
 #7 g_hash_table_lookup at ghash.c:1076
 #8 sipe_buddy_find_by_uri at sipe-buddy.c:343
 #9 process_add_group_response at sipe-group.c:97
 #10 process_input_message at sip-transport.c:1524
 #11 sip_transport_input at sip-transport.c:1611
 #12 pidgin_io_invoke at gtkeventloop.c:73

Potential duplicate: bug 981829

Comment 1 Marcel Wysocki 2014-01-14 09:48:30 UTC
Created attachment 849831 [details]
File: backtrace

Comment 2 Marcel Wysocki 2014-01-14 09:48:32 UTC
Created attachment 849832 [details]
File: cgroup

Comment 3 Marcel Wysocki 2014-01-14 09:48:36 UTC
Created attachment 849833 [details]
File: core_backtrace

Comment 4 Marcel Wysocki 2014-01-14 09:48:39 UTC
Created attachment 849834 [details]
File: dso_list

Comment 5 Marcel Wysocki 2014-01-14 09:48:43 UTC
Created attachment 849835 [details]
File: environ

Comment 6 Marcel Wysocki 2014-01-14 09:48:44 UTC
Created attachment 849836 [details]
File: limits

Comment 7 Marcel Wysocki 2014-01-14 09:48:50 UTC
Created attachment 849837 [details]
File: maps

Comment 8 Marcel Wysocki 2014-01-14 09:48:51 UTC
Created attachment 849838 [details]
File: open_fds

Comment 9 Marcel Wysocki 2014-01-14 09:48:53 UTC
Created attachment 849839 [details]
File: proc_pid_status

Comment 10 Marcel Wysocki 2014-01-14 09:48:56 UTC
Created attachment 849840 [details]
File: var_log_messages

Comment 11 Fedora Admin XMLRPC Client 2014-02-17 12:59:22 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora Admin XMLRPC Client 2014-02-17 13:00:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Derek Atkins 2014-06-23 07:56:30 UTC
Another user experienced a similar problem:

I was trying to set up a connection to Office 365 / Lync server.
After following the instructions I found at http://www.vincentpassaro.com/2013/02/01/configuring-pidgin-instant-messenger-for-office-365-lync/ and then hitting the error about lack of password I found http://sourceforge.net/p/sipe/discussion/688534/thread/7169e4fc/ -- where I tried to uncheck the Single Sign On.  After that, pidgin crashed.  (I haven't re-tried, yet, to see if it is reproducible).

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        pidgin
crash_function: sighandler
executable:     /usr/bin/pidgin
kernel:         3.14.8-200.fc20.x86_64
package:        pidgin-2.10.9-1.fc20
reason:         pidgin killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            9661

Comment 14 Derek Atkins 2014-06-23 08:01:17 UTC
I'll note that this happened during an attempt to set up the account and multiple failures.  After I restarted pidgin (after going through the effort to upload the stack trace) it came up just find and connected to all my IM hosts correctly (including the Office-365/Lync server)

Comment 15 Fedora End Of Life 2015-05-29 10:29:44 UTC
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.

Comment 16 Fedora End Of Life 2015-06-29 14:26:43 UTC
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.