Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 450476 - x11-libs/gtk+-3.6.3 breaks mail-client/evolution, pango_font_description_hash segfault
Summary: x11-libs/gtk+-3.6.3 breaks mail-client/evolution, pango_font_description_hash...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-05 22:07 UTC by Bernd Feige
Modified: 2013-01-06 14:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
gdb evolution backtrace (gdb.txt,5.83 KB, text/plain)
2013-01-05 22:08 UTC, Bernd Feige
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Feige 2013-01-05 22:07:08 UTC
After upgrading to x11-libs/gtk+-3.6.3, mail-client/evolution-3.6.2-r1 crashes (most often) when opening a contact: 
Program received signal SIGSEGV, Segmentation fault.
pango_font_description_hash () from /usr/lib64/libpango-1.0.so.0
A gdb log of evolution, compiled with -ggdb, is appended. However, the issue is fixed when downgrading to x11-libs/gtk+-3.6.2.

Further info about the behavior:
I use an up-to-date gnome (current gentoo tree, no overlay), with gnome-shell-3.6.2-r1. The crash happens quite but not fully reliably when opening a contact for editing; if the contact can be edited, the crash happens after saving it. Sometimes it crashes gnome-shell as well, sometimes not.

Reproducible: Sometimes

Steps to Reproduce:
1. Open evolution contacts.
2. Click on a contact to edit it.
3. evolution crashes.
Comment 1 Bernd Feige 2013-01-05 22:08:05 UTC
Created attachment 334580 [details]
gdb evolution backtrace
Comment 2 Alexandre Rostovtsev (RETIRED) gentoo-dev 2013-01-05 23:39:04 UTC
Please test whether this is fixed in gtk+-3.6.3-r1
Comment 3 Bernd Feige 2013-01-06 14:20:54 UTC
(In reply to comment #2)
> Please test whether this is fixed in gtk+-3.6.3-r1

It does, thanks! - I see that your associated bug report https://bugzilla.gnome.org/show_bug.cgi?id=691186 still has status "unconfirmed" - can now be regarded as pretty well confirmed I think ;-)
Hope that it's okay that I mark this bug as resolved - fixed now, thanks Alexandre!