Bug 677827

Summary: [abrt] pidgin-2.7.9-1.fc14: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Illya <dev>
Component: pidgin-otrAssignee: Paul Wouters <pwouters>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: b.thielman, bugzilla, djuran, fedora, ferox, itamar, pwouters, rdfsmits, rebus, rob.townley, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a814a0efe61aaa177ba8e2f98bd32be87150ee88
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 21:33:38 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

Description Illya 2011-02-16 00:04:21 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: pidgin
component: pidgin
executable: /usr/bin/pidgin
kernel: 2.6.35.11-83.fc14.x86_64
package: pidgin-2.7.9-1.fc14
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297810817
uid: 500

How to reproduce
-----
1. close pidgin
2.
3.

Comment 1 Illya 2011-02-16 00:04:24 UTC
Created attachment 478990 [details]
File: backtrace

Comment 2 Michal Ambroz 2011-02-18 02:38:08 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. pidgin was started from a session and instantly falled down
2.
3.

Comment 3 Mohammed Arafa 2011-02-18 23:18:33 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.no idea
2.switched back to my user on kde, kdm and found abrt reporting the crash
3.

Comment 4 Robert Townley 2011-02-20 01:05:50 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.pidgin 
2.
3.


Comment
-----
pidgin and empathy say "This resource is already connected to the server."

Comment 5 Bill Thielman 2011-02-20 18:04:46 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I did nothing (that I am aware of)
2.it just crashes always . . .
3.


Comment
-----
I did nothing (that I am aware of)
it just crashes always . . .

Comment 6 Fernando Pereira dos Santos 2011-02-21 19:44:08 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Don't remember
2. Sorry!
3.

Comment 7 Paul Wouters 2011-10-11 22:25:56 UTC
reported upstream.....

Comment 8 R Smits 2011-12-14 03:23:06 UTC
Hello!

OTR dev. here. Illya's backtrace does in fact point to OTR as the source of the crash while closing pidgin. Unfortunately I've had some trouble reproducing this.  

If someone can consistently reproduce the issue Illya has (pidgin crashes while closing, OTR plugin is also installed), I would appreciate if you could provide:

- The list of active account protocol types (i.e. AIM, XMPP, MSN, ...)
- The list of active plugins (especially if any active plugin has options that can change a conversation window's menus or decoration)
- Other details regarding when this crash does and does not occur, e.g. does this occur even if you simply open and close pidgin without initiating a conversation? Alternatively, is just one conversation enough to reproduce this?

If a generous user who can consistently reproduce this is willing to provide shell access on a machine where this happens, this would also greatly facilitate fixing this issue.

Thanks!

Comment 9 abrt-bot 2012-03-21 15:22:00 UTC
*** Bug 694746 has been marked as a duplicate of this bug. ***

Comment 10 Paul Wouters 2012-04-14 18:34:37 UTC
It seems to be it might be triggered by otr, but I don't think the actual crash is in otr, unless you believe the pidgin API does not allow g_hash_table_foreach() to be called with NULL as third argument?

I have noticed this bug in the past, but havent encountered it in a long while. It might have been addressed by pidgin ?

If no one can reproduce this anymore, I will close the bug soon, as it has been open for a year now.

Comment 11 Fedora End Of Life 2012-08-16 21:33:41 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping