Summary: | kde-base/kdm-4.1.2 segfaults on login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Kahle (RETIRED) <tomka> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 277868 |
Description
Thomas Kahle (RETIRED)
2008-10-28 08:27:30 UTC
Here is some more information maybe related: When locking the screen using kde's lock mechanism, there are problems on deactivating the lock. To reproduce: 1.) Lock the screen, leave it locked for 5 minutes or more. 2.) Wait 5 Minutes 3.) Try to unlock using your password. 4.) Unlock failes and tells you to switch to console and kill the screensaver, if you have started X manually with startx you can see the following message: *** glibc detected *** kcheckpass: malloc(): memory corruption: 0x096aec38 I'm thinking now this is something related to glibc ..., but I have no clue about linking issues, etc. I have already reported this issue in http://bugs.gentoo.org/show_bug.cgi?id=239672 . The same thing is mentioned here: http://bugs.gentoo.org/show_bug.cgi?id=257339 However, it does not look as though this bug is getting any attention whatsoever. Are you able to reproduce with kdm-4.3.0 and updated system? (with latest stable gcc, etc). I cannot reproduce any of issues mentioned here (with kde-4.3.0), please verify whether it still applies to you. Seems fixed to me. I'm closing this one. @Andriy Your case falls under bug 257339 and please continue there. |