Summary: | net-im/pidgin-2.3.1: empty protocol list, when adding account | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Ochman <michoch> |
Component: | Current packages | Assignee: | Gentoo Net-im project <net-im> |
Status: | VERIFIED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Pidgin output |
Description
Michał Ochman
2008-02-12 22:05:18 UTC
Created attachment 143367 [details]
Pidgin output
Output of:
- pidgin --version
- pidgin --debug
i just upgrade pidgin to 2.3.1 but i can see a full protocols list to "add account" menu. what pidgin use flags did you enable? (In reply to comment #2) > i just upgrade pidgin to 2.3.1 but i can see a full protocols list to "add > account" menu. > > what pidgin use flags did you enable? Pidgin USE flags are as follows: USE="dbus gadu gstreamer gtk ncurses nls perl sasl spell -bonjour -debug -doc -eds -gnutls -groupwise -meanwhile -networkmanager -prediction -qq -silc -tcl -tk -zephyr" Additionally, this problem also exists in 2.2.1 (stable) and 2.2.2. I see a segfault in the log, please post a backtrace.. And dont build with -fomit-frame-pointer .. and try purging pidgin and re-merging it, there is something very strange on your system (In reply to comment #4) > I see a segfault in the log, please post a backtrace.. And dont build with > -fomit-frame-pointer .. and try purging pidgin and re-merging it, there is > something very strange on your system This segfault occured after trying to add an account without protocol selected (because there were no one). After removing all files connected to libpurple and pidgin, and then reemerging Pidgin, problem with empty protocol list disappeared and Pidgin seems to work correctly. I thought about "ABI version mismatch 2.3.x (need 2.1.x)" and i realised, that last version of Pidgin I used was 2.1.x. I suppose old libs were not deleted when unmerging Pidgin and caused this issue. The question is: Why emerging new version of Pidgin, these files were not overwritten by a new ones? Anyway, thanks for help. They should have been overwritten, I have no idea what could have caused that (disk full maybe?)... (In reply to comment #6) > They should have been overwritten, I have no idea what could have caused that > (disk full maybe?)... I have no idea, disk had a lot of free space when emerging. Pidgin compiled from source (found on pidgin.im, not from portage) worked perfectly. I am marking this bug as closed (and also I have changed resolution to invalid.) |