Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 256462 - kde-base/kmail - missing Qt patch triggers KMail 4.* crashes
Summary: kde-base/kmail - missing Qt patch triggers KMail 4.* crashes
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo KDE team
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-26 21:14 UTC by Tobias Leupold
Modified: 2009-01-31 12:17 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Leupold 2009-01-26 21:14:30 UTC 
Some time ago, I filed a KDE bug about KMail crashes: http://bugs.kde.org/show_bug.cgi?id=178718

A KDE developer told me that this could be triggered by a missing Qt patch, 0256-fix-recursive-backingstore-sync-crash.diff -- and I really don't know if that patch is applied in Gentoo, as the Qt ebuilds are split up.

So, is this patch being applied? If so, the bug is a real new KDE bug, if not, this is probably a Gentoo issue and the ebuilds should include the patch.

Reproducible: Always

Steps to Reproduce:
Comment 1 Christian Hesse 2009-01-30 16:49:27 UTC 
I see the same crashes with qt-4.4.2 (I think the split ebuild having problems is qt-gui-4.4.2-r1?). I just applied the patch (so it is not included right now). Still compiling... I hope this fixes the crashes.
Comment 2 Christian Hesse 2009-01-30 17:54:52 UTC 
The patch seems to fix the crashes, no more SIGSEGVs so far. (It crashed every third click for me before.) Please apply the patch. Thanks!
Comment 3 Christian Hesse 2009-01-31 09:15:33 UTC 
0256-fix-recursive-backingstore-sync-crash.diff is in x11-libs/qt-gui-4.4.2-r2 now. Thanks a lot!
Comment 4 Tomáš Chvátal (RETIRED) gentoo-dev 2009-01-31 12:17:53 UTC 
Since the patch is in 4.4.2-r2 and thus in the tree closing this bug as fixed.
Thanks for tracking this down.