Summary: | Unlock results in crash after suspend | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | Bernhard Jungk <fire> |
Component: | locker | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | arekm, hobbyblobby, kdebugs, mail, onizuka92, paulo.miguel.dias, rct+bugs |
Priority: | NOR | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Bernhard Jungk
2010-06-28 19:44:02 UTC
*** Bug 243073 has been marked as a duplicate of this bug. *** *** Bug 243917 has been marked as a duplicate of this bug. *** Created attachment 49339 [details]
New crash information added by DrKonqi
kscreenlocker (2.0) on KDE Platform 4.4.93 (KDE 4.4.93 (KDE 4.5 >= 20100713)) using Qt 4.6.3
- What I was doing when the application crashed: suspend to ram -> resume -> unlock my screen. Application crashed after successful unlocking
-- Backtrace (Reduced):
#9 0x00007ff90105eec9 in Free_MarkMarkPos (st=0xa00730, lookup_type=<value optimized out>) at ../3rdparty/harfbuzz/src/harfbuzz-gpos.c:2904
#10 _HB_GPOS_Free_SubTable (st=0xa00730, lookup_type=<value optimized out>) at ../3rdparty/harfbuzz/src/harfbuzz-gpos.c:5824
#11 0x00007ff90105f8c4 in Free_SubTable (l=0x96e230, type=HB_Type_GPOS) at ../3rdparty/harfbuzz/src/harfbuzz-open.c:469
#12 Free_Lookup (l=0x96e230, type=HB_Type_GPOS) at ../3rdparty/harfbuzz/src/harfbuzz-open.c:568
#13 0x00007ff9010607c6 in _HB_OPEN_Free_LookupList (ll=<value optimized out>, type=HB_Type_GPOS) at ../3rdparty/harfbuzz/src/harfbuzz-open.c:655
*** Bug 243274 has been marked as a duplicate of this bug. *** these crashes are pretty obviously a result of memory corruption. as such a valgrind/memcheck trace would be more useful than the backtraces. After doing some debugging with valgrind today, I found the root cause of this issue. It is the same issue as in bug 243540. Just adding the patch from that bug to the kdelibs source tree that I used to build my 4.5.0 packages and rebuilding fixes this memory corruption for me. Note that this bug has been fixed in the 4.5 branch a bit after the first set of 4.5.0 tarballs were given to the packagers, however the 4.5.0 tarballs were re-done at a later point, so the "official" 4.5.0 released by KDE does not have this bug. If some distributions still have this bug in 4.5.0, this means that they ship kdelibs 4.5.0 from the pre-release tarball. *** This bug has been marked as a duplicate of bug 243540 *** |