[Bug 47455] Re: KDM detected memory corruption

[windbourne]

Currently using Edgy with xen. Came across a lock up on my monitor. Upon checking the logs, I found similar messages. 
First off,  "Can't open default user face" is because the default faces are missing. Specifically,  I did the following:

<CODE>
cd /usr/share/apps/kdm/faces/
ln -s ../pics/users/root1.png root.face.icon
ln -s ../pics/users/default2.png .default.face.icon
</CODE>

Issue solved on that message.

Earlier, I had no issues with kdm (or was not aware of any :) ). But when looking though the log files, I noticed that the corruption occurs in the tls arena:
<TEXT>
*** glibc detected *** -:0: double free or corruption (fasttop): 0x08076c68 ***
======= Backtrace: =========
/lib/tls/i686/cmov/nosegneg/libc.so.6[0xb7df52ad]
/lib/tls/i686/cmov/nosegneg/libc.so.6(__libc_free+0x84)[0xb7df5434]
/lib/libpam.so.0(_pam_free_data+0x65)[0xb7ee22c5]
/lib/libpam.so.0(pam_end+0x39)[0xb7ee1c79]
</TEXT>

So I did the standard fix for Xen and the tls; basically, I moved it out of the way:
<CODE>
mv /lib/tls /lib/tls.disabled
</CODE>


This seems to get rid of the kdm mem corrptn issue. But it does not solve my input lock ups (even though it appears that the input is being grabbed). 

happy hunting.

-- 
KDM detected memory corruption
https://launchpad.net/bugs/47455