Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8820 - [pidgin 2.3.0] segfaults for no apparent reason, try to dump core file

Attached to Project: Arch Linux
Opened by Henrique C. Alves (freakcode) - Sunday, 02 December 2007, 20:45 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 06 December 2007, 00:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After the last upgrade, Pidgin just segfaults (aparently when I receive a message), and prints a message about dumping a core file - but doesn't do it. I'm unable to trace the crash reason using gdb.

Additional info:
* All plugins disabled
* Crashes silently
* Using only a MSN account (disabled XMMP account, according to some bug reports it can cause problems)

Steps to reproduce:
Just connected, and pidgin minimized to tray.

Please, seek if this bug is upstream or not.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Thursday, 06 December 2007, 00:01 GMT
Reason for closing:  Works for me
Additional comments about closing:  Bug was apparenlty caused by "purple-plugins" package. Requesting closure.
Comment by adam stokes (boris) - Monday, 03 December 2007, 01:55 GMT
I run into this same problem too -- tell me where on the wiki/other do I find information on installing the debugging libraries needed to debug this problem?
Comment by Henrique C. Alves (freakcode) - Monday, 03 December 2007, 02:18 GMT
Adamn, there is this page:

http://developer.pidgin.im/wiki/GetABacktrace

I tried to follow the instructions there, but the info was useless because the package was compiled without debugging symbols. So I needed to compile pidgin from source, but I either dont know how and dont have time to figure out how, so I tought the package manteiner could sneak this bug better than me.
Comment by adam stokes (boris) - Monday, 03 December 2007, 20:53 GMT
Yea thats my thing -- I need to do some more research on pulling down debugging symbols from arch packages b/c so far I don't think a seperate debug package is provided or I dont see a way to generate that other than building it from source.. But I'd like to debug it starting from arch install and on.

Ill keep looking
Comment by Henrique C. Alves (freakcode) - Monday, 03 December 2007, 23:53 GMT
FIY, Pidgin stoped crashing for me on the past days. I found that I had a package called "purple-plugins" installed, and while I had all Pidgin plugins disabled, looks like that only having the package installed was causing the SEGFAULTs. Currently, I'm running Pidgin with no plugins enabled (not even the oficial ones), and now fully using the MSN and XMPP accounts, so I guess it's not a problem with XMPP either.

Try to install the purple-plugins ([community]) and see if you get the SEGFAULTs too. My guess is that they started conflicting with the last Pidgin update.
Comment by Henrique C. Alves (freakcode) - Wednesday, 05 December 2007, 23:42 GMT
The bug doesn't persisted, so I bet it was caused by the purple-plugins package. Requesting closure.

Loading...