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: [New Thread 1094642048 (LWP 1705)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? () #0 0xffffe410 in ?? () #1 0xbfff9a24 in ?? () #2 0x00000000 in ?? () #3 0x00000000 in ?? () #4 0x41199163 in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #5 0x407223d2 in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #6 <signal handler called> #7 0x40db4b89 in QString::QString () from /usr/lib/libqt-mt.so.3 #8 0x4168d3a2 in KClassicGreeter::KClassicGreeter () from /opt/kde3/lib/kde3/kgreet_classic.so #9 0x4168ddea in create () from /opt/kde3/lib/kde3/kgreet_classic.so #10 0x08052ae6 in PasswordDlg::PasswordDlg () #11 0x080550c1 in LockProcess::checkPass () #12 0x08056a07 in LockProcess::x11Event () #13 0x40765362 in KApplication::x11EventFilter () from /opt/kde3/lib/libkdecore.so.4 #14 0x08051614 in MyApp::x11EventFilter () #15 0x40a0bf07 in qt_x11EventFilter () from /usr/lib/libqt-mt.so.3 #16 0x40a189d9 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #17 0x40a2da85 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #18 0x40a96a31 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #19 0x40a96876 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #20 0x40a808df in QApplication::exec () from /usr/lib/libqt-mt.so.3 #21 0x08058d3f in main ()
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?
participants (2)
-
Anders Johansson
-
Urciolo, Kevin