| Summary: | x11-plugins/pidgin-msn-pecan crashes... predictably | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Giuseppe Marco Randazzo <zeld> <gmrandazzo> |
| Component: | Current packages | Assignee: | Bernard Cafarelli <voyageur> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | gogoprog |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
backtrace 1/3
backtrace 2/3 backtrace 3/3 emerge --info and emerge -qpv results pidgin output and emrge --info |
||
|
Description
Giuseppe Marco Randazzo <zeld>
2009-03-11 14:26:25 UTC
Created attachment 184697 [details]
backtrace 1/3
backtrace 1/3
Created attachment 184698 [details]
backtrace 2/3
Created attachment 184700 [details]
backtrace 3/3
Please post your "emerge--info" and the output of emerge -qpv pidgin pidgin-msn-pecan Re-open this bug when you provide the requested information. Created attachment 185089 [details]
emerge --info and emerge -qpv results
I've got the same bug, so here is soem additionnal information
Created attachment 185123 [details]
pidgin output and emrge --info
reopened the bug :-) Those are not in pidgin, but in msn-pecan. My advice is to use the built-in msn plugin, not pecan. Thanks for the report, can you recompile pidgin-msn-pecan (and maybe pidgin too) with debug informations enabled? http://www.gentoo.org/proj/en/qa/backtraces.xml Also upstream suggests to run pidgin as: # pidgin --debug > debug_log.txt This will help them track the problem. At first glance, I've not seen any recent commit that could fix your crash, and it works fine here so I cannot reproduce pidgin-msn-pecan-0.0.19 is in tree and fixes a few crashes, please test it. The announcement (and list of fixed items) is here: http://felipec.wordpress.com/2009/06/16/msn-pecan-0-0-19-released-more-stability-and-now-playing-support/ Please reopen if it is not fixed in this release |
