Summary: | kscreenlocker hangs after unlocking the screen | ||
---|---|---|---|
Product: | kscreensaver | Reporter: | Israel J. Pattison <pattison> |
Component: | locker | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | gilboad, kdelibs-bugs, onizuka92, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Output of 'valgrind /usr/lib64/kde4/libexec/kscreenlocker --forcelock'
Valgrind memcheck output pstack output |
Description
Israel J. Pattison
2010-07-21 16:30:00 UTC
well, this is obviously some memory corruption, so valgrinding instead of stracing would be more helpful. i would try step 6 after step 2 already. Created attachment 49525 [details]
Output of 'valgrind /usr/lib64/kde4/libexec/kscreenlocker --forcelock'
I ran the screen locker again using valgrind. I have attached a text file with the output.
I can confirm this bug, I'm seeing it consistently on two machines. Fedora 13, x86_64, KDE 4.5 rc2 and now rc3. pstack and valgrin output attached. Created attachment 49612 [details]
Valgrind memcheck output
Created attachment 49613 [details]
pstack output
P.S. I'm using nVidia proprietary drivers on both machines. (In-case it matters) fwiw, this may be a duplicate of bug #243067 The valgrind output does seem to suggest that locker is trashing memory, which could result in weird behaviour and crashes in random places. Never the less, at least in my case, I can reproduce it every time I unlock my machine and the callstack is far from being random. - Gilboa seems to be a dupe of bug #243067 (which is a dupe of bug #243540) indeed *** This bug has been marked as a duplicate of bug 243540 *** |