You are not logged in.

1

Monday, September 20th 2004, 9:45pm

Signal 11 error KDE will not start for root user: SuSE 9.0

I had to do a hard reboot due to a system lockup and now KDE will not start for *just* the root user.... all other users are not affected.

Is there any way to rebuild the root profile? Or figure out what this "signal 11" error is? Here is the error out put below:

Here's the error "backtrace":
(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)...
(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)...
(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)...[New Thread 16384 (LWP 3670)]
(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)...(no debugging symbols found)...
(no debugging symbols found)...0x41320a86 in waitpid ()
from /lib/i686/libpthread.so.0
#0 0x41320a86 in waitpid () from /lib/i686/libpthread.so.0
#1 0x40813a10 in KCrash::defaultCrashHandler(int) ()
from /opt/kde3/lib/libkdecore.so.4
#2 0x4131f96c in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3 <signal handler called>
#4 0x414ebdea in strcmp () from /lib/i686/libc.so.6
#5 0x408ea9c0 in _KDE_IceGetPoValidAuthIndices ()
from /opt/kde3/lib/libDCOP.so.4
#6 0x408e8c3d in KDE_IceOpenConnection () from /opt/kde3/lib/libDCOP.so.4
#7 0x408dbbde in DCOPClient::attachInternal(bool) ()
from /opt/kde3/lib/libDCOP.so.4
#8 0x408dc632 in DCOPClient::registerAs(QCString const&, bool) ()
from /opt/kde3/lib/libDCOP.so.4
#9 0x407a3c97 in KApplication::dcopAutoRegistration() ()
from /opt/kde3/lib/libkdecore.so.4
#10 0x407a32a5 in KApplication::init(bool) ()
from /opt/kde3/lib/libkdecore.so.4
#11 0x407a239d in KApplication::KApplication(bool, bool) ()
from /opt/kde3/lib/libkdecore.so.4
#12 0x4007ef67 in main () from /opt/kde3/lib/konqueror.so
#13 0x41489d17 in __libc_start_main () from /lib/i686/libc.so.6
#14 0x08048591 in _start ()

seb

Professional

Posts: 622

Location: Sydney

Occupation: Student

  • Send private message

2

Tuesday, September 21st 2004, 8:58am

try removing the folders

/tmp/kde-user

where user is your username

3

Tuesday, September 21st 2004, 1:53pm

Quoted

Original von seb

try removing the folders

/tmp/kde-user

where user is your username


I removed kde-root and it still crashes with signal 11

Anything else I can try?

seb

Professional

Posts: 622

Location: Sydney

Occupation: Student

  • Send private message

4

Tuesday, September 21st 2004, 2:55pm

A Sig11 shouldn't really be due to the kde settings, it is to do with how an application was compiled. Sig11 is a segmentation fault. You can find more info here:
http://www.bitwizard.nl/sig11/


but, if you want to try with original settings, remove

/root/.kde

this way, when you log back into kde with root, the default kde configurations will be set.

5

Wednesday, September 22nd 2004, 2:56am

Quoted

Original von seb

A Sig11 shouldn't really be due to the kde settings, it is to do with how an application was compiled. Sig11 is a segmentation fault. You can find more info here:
http://www.bitwizard.nl/sig11/


but, if you want to try with original settings, remove

/root/.kde

this way, when you log back into kde with root, the default kde configurations will be set.


OK... I'll try that when I get home... thanks for the help!