Since having run a world update on the 20th of April, Pidgin crashes each and every time I start it, citing a Pango-CRITICAL error and cairo-surface.c if run from a terminal window. Reproducible: Always Steps to Reproduce: 1. Start Pidgin. 2. Watch Pidgin crash. Actual Results: Pidgin crashes. When run from a terminal window, the following error is shown (where ## is the process ID of Pidgin at the time): (Pidgin:##): Pango-CRITICAL **: pango_font_description_set_size: assertion `size >=0' failed (Pidgin:##): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='DejaVu Sans 9.9990234375', text='Busy' (Pidgin:##): Pango-CRITICAL **: pango_font_description_set_size: assertion `size >=0' failed pidgin: cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Expected Results: Pidgin should have just started normally, showing my last saved status "Busy" and connecting to the various IM networks I use. (Mainly AIM & YIM.) I run Pidgin on the Openbox WM, have Tint2 as taskbar, Yakuake as terminal program, and uim-gtk as input manager. Beyond that, I use hsetroot to have a background image and I use the xscreensaver program to manage my screensaver.
Created attachment 270815 [details] gdb stacktrace of pidgin crash, 20110422
Please post your `emerge --info net-im/pidgin' output too.
Created attachment 270833 [details] emerge --info net-im/pidgin output
I have to wonder why the severity of this bug was downgraded from Critical (The software crashes, hangs, or causes you to lose data.) to Normal (It's a bug that should be fixed.)? The program crashes, does it not? It even does so before I can get to any kind of place where manual input is possible. So either the gentoo bugzilla should look at the bugreporting progress and fix the description of the severity options or this error is a Critical error and should remain noted as such. Putting severity back until a proper reason is given for the downgrade.
Yeah, that attitude is wonderful. I hope you're nicer to net-im/pidgin's maintainers.
What attitude? I just don't grok why you put it to "normal" while it's more than just 'a bug' that needs to be fixed. The program is rather unusable right now. o.o My apologies if it seemed different, but I merely wish to eliminate misunderstandings, hence why I requested an explanation.
Thank you for report, Maki. What version you had previously installed? I've dropped platform as currently nothing here indicates that this is platform specific bug. As for severity field we prefer to set it to Normal even if this is crash until this bug will be reproducible on other systems as well. Currently pidgin 2.7.11 is stable for some time, so lot's of users use it without any crash but that said I see at least two users with this problem, so I'll increase importance, although for me, until this is enhancement/blocker bugs this means nothing :) Now, please, backup pidgin settings ~/.purple/ and try to start pidgin. Will it crash? Will it crash after you enable AIM? YIM? Please, try to localize what settings cause crash. This should help us to debug further. Also I've posted this report upstream. May be you'll wish to subscribe to report there as well.
Please, get back to us answering questions in comment #7 and reopen bug report, then.
