The crash is consistent on several machines. One problem area may be that KDM 3.4.1 (I just tried 3.4.2 and it has the same problem) is used along with everything else KDE being 3.2.1. There did not seem to be package dependencies. KDM was bumped up to allow password expiration prompts to function with LDAP. KDM 3.2.1 would prompt the user to change his/her password. However, it would complain that the orginal password was incorrect, even though the prompt did not ask for it. -----Original Message----- From: Anders Johansson [mailto:andjoh@rydsbo.net] Sent: Thursday, August 11, 2005 5:53 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Kdesktop Locker Signal 11 (SIGSEGV) LDAP On Thursday 11 August 2005 23:41, Urciolo, Kevin wrote:
We are using Novell Desktop. We are using LDAP for authentication. An error is received when the screensaver exits: Kdesktop Locker signal 11 (SIGSEGV). The screensaver is set to require a password to unlock.
Any ideas what is happening?
Here is the trace:
It seems to be crashing inside one of the basic functions of qt, the creator function of QString. Usually, when these basic functions crash, it is a signal that there are hardware memory problems in the system. Does it always crash like this, and is the crash backtrace always identical? If it seems to be random, this would be further indication that it is a memory problem. Have you run the memtest program (found on the boot menu) on this machine? If it always crashes at exactly the same place, then it could still be a software error. Do you have all the latest updates installed? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com