Created attachment 512493 [details]
File: dso_list

Created attachment 512494 [details]
File: maps

Created attachment 512495 [details]
File: backtrace

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (x86_64)
#fx64 (F15)


Comment
-----
pidgin crashes when minimized to tray. no exact step by step to reproduce but crashes persistently every day.

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I was chatting over MSN.

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
opening many text files with gedit

workaround - instead of clicking the cross to close the application into task tray (task tray appears on mouse movement towards bottom right corner), right click the application title bar and do minimize.

visually 100% same effect, and 0 crashes.

ps the bug is in gnome bar, not pidgin; I've many applications crashing when clicking on close to minimize to system tray, and same application NOT crashing when doing minimize.

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
clicking on tray icon

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
It just crashed overnight.  I was not even at the computer.

Oh, and I'm a KDE user.

Package: pidgin-2.9.0-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I clicked "ignore" a user in an IRC channel. Accidentally, on myself.

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I was unable to reproduce this crash.

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
just crashed

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
No idea.. it was just running.. maybe I received a message ?

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
changed status from offline to online

Package: pidgin-2.9.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
pidgin closed unexpectatly

Package: pidgin-2.10.0-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)

Comment
-----
It happened after a file transfer. I was sendin a png file to a friend.

Package: pidgin-2.10.0-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I have no idea.

Package: pidgin-2.10.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
when i disable the skype account from pidgin the crash arises.

Package: pidgin-2.10.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
started typing in the chat field. Sudden crash

Package: pidgin-2.10.0-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
Was sending a file to a friend

Package: pidgin-2.10.0-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
Exited the app.

hi, 

The pidgin application was crash why i try to start it.
I had installed the pidgin-sipe plugin and configed communicator account. And the account was successfully connected.
But after i closed pidgin and try to start it again. It will always crash.


rating: 4
Package: pidgin-2.10.0-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Just using Jabber protocol text chat. No obvious cause.

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 555876 [details]
File: backtrace

Shutting down pidgin

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 557231 [details]
File: backtrace

Quit pidgin

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 559226 [details]
File: backtrace

I just clicked multiple times by left mouse button on Pidgin contact window and it crashed.

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 563870 [details]
File: backtrace

Seems like I received an IM from an MSN contact just before the crash.

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 566398 [details]
File: backtrace

tried to block someone who had taken over a friend's abandoned yahoo account (pidgin then crashed)

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 567142 [details]
File: backtrace

Crashed when lost network connection (WiFi) and 2 of 3 accounts were trying to reconnect.

backtrace_rating: 4
Package: pidgin-2.10.1-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 568664 [details]
File: backtrace

run pidgin..

backtrace_rating: 4
Package: pidgin-2.10.1-4.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Created attachment 570915 [details]
File: backtrace

Only try run pidgin and crash

backtrace_rating: 4
Package: pidgin-2.10.1-4.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Created attachment 570949 [details]
File: backtrace

*** Bug 798986 has been marked as a duplicate of this bug. ***

*** Bug 803341 has been marked as a duplicate of this bug. ***

opened the control center

backtrace_rating: 4
Package: control-center-3.3.5-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Created attachment 572234 [details]
File: backtrace

Just nothing.

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 572573 [details]
File: backtrace

After upgrading pidgin to version 2.10.2-1, whenever I send a file to one of my msn contacts, as soon as the transfer is completed, pidgin crashes. Also, it fails to notice whether a contact has logged off. I have to disable my account and re-enable it for the contact list to update. (should I open another ticket for this one?)

Steps to Reproduce:
1. Send file to contact.
2. Wait for the transfer to finish.
3. Pidgin crashes.


backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 573033 [details]
File: backtrace

I was AFK while pigin crashed, so I don't really know if something happened (e.g. if I was highlighted). I was not yet able to reproduce the crash either.

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Created attachment 573410 [details]
File: backtrace

just crashed after a user went offline

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 573726 [details]
File: backtrace

Another pidgin user - also on Fedora - tried to initiate a video call over jabber. my pidgin instantly crashes and this is fully reproducible.

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Created attachment 573947 [details]
File: backtrace

As this reliable allows a remote "attacker" to crash pidgin, I am upgrading the severity to "high" and adding the "security" keyword.

Has this ever been forwarded to the developers?

*** Bug 724030 has been marked as a duplicate of this bug. ***

Using MSN pluggin	

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 574922 [details]
File: backtrace

1. Receive a file transfer offer via XMPP/ICQ/...
2. Accept transfer
3. Crash...


backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 576605 [details]
File: backtrace

Version 2.10.3 from upstream addresses the issues we've been having lately and it was released almost a month ago. Should we contact the package maintainers?

opening MSN Chat windows

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 578459 [details]
File: backtrace

I don't think it can be reproduced.  The circumstances were:

1) Started a file transfer to a friend via Jabber.
2) Put machine to sleep.
3) Woke it up the next morning.
4) Tried to cancel file transfer.


backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Created attachment 578864 [details]
File: backtrace

If you are a power user and see constant crashes or you've found a way to
reliably reproduce the crash, please perform the steps outlined below.
Hopefully, this will help us to further track down the problems:

0) Open a terminal

1) Install gdb, the GNU Debugger (to generate the backtrace) and yum-utils (for
the debuginfo-install utility)
$ sudo yum install gdb yum-utils

2) Install the pidgin debugging symbols
$ sudo debuginfo-install pidgin

3) Open pidgin in GDB
$ gdb pidgin
GNU gdb (GDB) Fedora (7.3.50.20110722-13.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pidgin...Reading symbols from
/usr/lib/debug/usr/bin/pidgin.debug...done.
done.
(gdb)

4) Enter "r" into the open gdb session to launch gdb
(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Detaching after fork from child process 2225.
Detaching after fork from child process 2226.
Detaching after fork from child process 2227.

5) Keep the terminal open and use pidgin normally until it crashes or do
whatever has to be done to reproduce the crash.

6) In case of a crash, enter "bt full" into the gdb session.
Copy and paste all of the output into a file, remove potentially private
information, and attach the resulting file to this bug.

Thanks!

Created attachment 579181 [details]
gdb backtrace

Started pidgin, sent a line of text to a contact, then a jpeg file. Just as the transfer completed, pidgin crashed, though gdb kept its interface alive (but not responsive).

Just trying to start an audio chat

backtrace_rating: 3
Package: pidgin-2.10.2-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Send a File via MSN, after it has finished Pidgin crashed

backtrace_rating: 3
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 581697 [details]
File: backtrace

Created attachment 581707 [details]
gdb backtrace

Send file in Pidgin over MSN to another Pidgin User

launched pidgin. crashes immediately

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc16
OS Release: Fedora release 16 (Verne)

Created attachment 585224 [details]
File: backtrace

I invoke to run it, but it's crashed

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc17
Architecture: i686
OS Release: Fedora release 17 (Beefy Miracle)

FWIW pidgin 2.10.4 without farstream patch no longer has this issue. Stu, can you prepare a new package for testing?

Machine was put to suspend mode  and I was also changing between networks/proxies.

backtrace_rating: 4
Package: pidgin-2.10.2-1.fc17
OS Release: Fedora release 17 Alpha (Beefy Miracle)

Program start

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Just started at same time as Firefox and Thunderbird after Gnome login.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I just start Pidgin.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Disabled Skype Account

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

something with skype for pidgin i guess

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Simply started pidgin. Didn't even came up.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Just started pidgin and it immediately crashed.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

1. Install fedora
2. Run software update
3. yum install pidgin
4. yum install thunderbird libreoffice
5. yum install vim
6. reboot
7. Launch pidgin
8. Failure


backtrace_rating: 3
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Started up pidgin on a wireless connection at a coffee shop.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

crashed at startup

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Opening pidgin for the first time.

backtrace_rating: 4
Package: pidgin-2.10.4-1.fc17
Architecture: i686
OS Release: Fedora release 17 (Beefy Miracle)

I created a Pidgin ticket, hoping to get some progress/direction on this bug...

http://developer.pidgin.im/ticket/15185

   Egon

Quote from deryni (Pidgin developer):
==========
There are at least six different crashes indicated in this bug.

Some appear to be coming from the (third-party) sipe plugin. Some appear to be logreader related. Some are MSN related. Some are XMPP file transfer related. Some appear to be gstreamer related. Some appear to be deeper GTK+/cairo/pango/X related.
==========

-> I think Abrt combined multiple problems into 1 Bugzilla bug.

IMHO: In order to fix the issues the backtraces should be split into separate bugs and assigned to the different plugin-maintainers.
Otherwise I don't think this bug has any added value...

downloading oracle
reading a pdf
running virtualbox -- 1 client
firefox running
evolution running


backtrace_rating: 4
Package: pidgin-2.10.5-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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