Version: (using KDE 4.0.0) Installed from: Ubuntu Packages When KDE 4 is started, crash-handler gives feedback, that kdewallet manager hast crashed. starting manually works. This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [...] [Thread debugging using libthread_db enabled] [New Thread 47383185357264 (LWP 8851)] (no debugging symbols found) [...] 0x00002b183a326c05 in waitpid () from /lib/libc.so.6 [Current thread is 0 (process 8851)] Thread 1 (Thread 47383185357264 (LWP 8851)): #0 0x00002b183a326c05 in waitpid () from /lib/libc.so.6 #1 0x00002b1837f3344f in ?? () from /usr/lib/kde4/lib/libkdeui.so.5 #2 0x00002b1837f34099 in KCrash::defaultCrashHandler () from /usr/lib/kde4/lib/libkdeui.so.5 #3 <signal handler called> #4 0x000000000041d2e7 in _start () #0 0x00002b183a326c05 in waitpid () from /lib/libc.so.6
I can confirm this problem, but I have difficulties getting a useful backtrace. Once I manage to get one, I will post it here.
I can confirm too, i'm running kde 4.0 launchpad packages on a kubuntu 7.10 this is my backtrace: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [...] [Thread debugging using libthread_db enabled] [New Thread -1245235520 (LWP 5255)] (no debugging symbols found) [...] 0xffffe410 in __kernel_vsyscall () [Current thread is 0 (process 5255)] Thread 1 (Thread -1245235520 (LWP 5255)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb69dde70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb69ddca7 in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7b654c0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5 #4 0x00000001 in ?? () #5 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () that's all falks :)
Did yu left kwalletmanager open when logging out (thus saving it as part os the session)?
Am Sonntag, 20. Januar 2008 12:09:57 schrieb Pino Toscano: [bugs.kde.org quoted mail] I leave it open.
*** This bug has been marked as a duplicate of 153574 ***