Version: (using KDE 4.1.0) Installed from: Debian testing/unstable Packages OS: Linux kwallet crashed for me. I was doing nothing with kwallet. It was open and was just lying idle.
Application: KDE Wallet Service (kwalletd), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb7f65720 (LWP 6217)] [KCrash handler] #6 KWalletD::internalOpen (this=<value optimized out>, appid=<value optimized out>, wallet=<value optimized out>, isPath=<value optimized out>, w=<value optimized out>, modal=<value optimized out>) at /tmp/buildd/kde4libs-4.1.0/kwallet/backend/kwalletbackend.h:128 #7 0x410f5c15 in KWalletD::doTransactionOpen (this=<value optimized out>, appid=<value optimized out>, wallet=) at /tmp/buildd/kde4libs-4.1.0/kio/misc/kwalletd/kwalletd.cpp:349 #8 0x410f86af in KWalletD::processTransactions (this=<value optimized out>) at /tmp/buildd/kde4libs-4.1.0/kio/misc/kwalletd/kwalletd.cpp:160 #9 0x410f9244 in KWalletD::qt_metacall (this=<value optimized out>, _c=<value optimized out>, _id=<value optimized out>, _a=<value optimized out>) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kio/misc/kwalletd/kwalletd.moc:258 #10 0x412830c0 in QMetaObject::activate (sender=<value optimized out>, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=<value optimized out>) at kernel/qobject.cpp:3010 #11 0x41283e42 in QMetaObject::activate (sender=<value optimized out>, m=<value optimized out>, local_signal_index=<value optimized out>, argv=) at kernel/qobject.cpp:3080 #12 0x41289497 in QSingleShotTimer::timeout (this=) at .moc/release-shared/qtimer.moc:74 #13 0x412895bc in QSingleShotTimer::timerEvent (this=<value optimized out>) at kernel/qtimer.cpp:300 #14 0x4127dbaf in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1105 #15 0x4187d6ec in QApplicationPrivate::notify_helper ( this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3772 #16 0x418854be in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3366 #17 0x426db5ed in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /tmp/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311 #18 0x4126e571 in QCoreApplication::notifyInternal ( this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at kernel/qcoreapplication.cpp:587 #19 0x4129c5e1 in QTimerInfoList::activateTimers (this=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #20 0x41298c20 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:166 #21 0x410642f1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0x41067983 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x099b7c90 in ?? () #24 0x00000000 in ?? () #0 0xb7f8d424 in __kernel_vsyscall ()
Did that happen again with KDE 4.1.2? By the way, the backtrace show kwalletd was about to open a wallet, so maybe some application was trying to open it.
Haven't seen it crash again since the last one? Since it was a crash, I thought the bug must be a valid one and could unveil a genuine bug. BTW, When one submits a backtrace, how do you guys interpret it (in relation to the source code)? Is there a techbase link?
Interpreting the backtrace (for me) usually serves as a starting point to investigate what might have gone wrong. Usually it doesn't tell me more than where to look at. Then I usually find out where the bug might have happened. And I agree. Your backtrace points at some real bug - be it in kwalletd or not. Unfortunately the internalOpen method is quite long and without knowing how to reproduce the bug there's almost no chance to find out what was going wrong. I'll still leave the report open for now so you can add more information in case it strikes again.
Should I close it ? Haven't seen the issue pop again since long.
I'll close it. I think it's safe to assume it won't happen again. If it does, please reopen!
Michael, I'm reopening the bug. I saw the crash again, today. All I did was: * Logged In into KDE * Kopete autostarted. * Kopete requested kwallet And I think then kwallet crashed................. Application: KDE Wallet Service (kwalletd), signal SIGSEGV Thread 1 (Thread 0xb750a8d0 (LWP 9485)): [KCrash Handler] #6 KWalletD::internalOpen (this=0xbfa2a288, appid=@0x9caed44, wallet=@0x9caed50, isPath=false, w=54525953, modal=true, service=@0x9caed54) at ../../kwalletd/backend/kwalletbackend.h:132 #7 0xb7efb559 in KWalletD::doTransactionOpen (this=0xbfa2a288, appid=@0x9caed44, wallet=@0x9caed50, isPath=<value optimized out>, wId=<value optimized out>, modal=true, service=@0x9caed54) at ../../kwalletd/kwalletd.cpp:400 #8 0xb7efc61b in KWalletD::processTransactions (this=0xbfa2a288) at ../../kwalletd/kwalletd.cpp:182 #9 0xb7efc8b6 in KWalletD::qt_metacall (this=0xbfa2a288, _c=QMetaObject::InvokeMetaMethod, _id=57, _a=0xbfa29a28) at ./kwalletd.moc:275 #10 0x469cb270 in QMetaObject::activate (sender=<value optimized out>, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=<value optimized out>) at kernel/qobject.cpp:3031 #11 0x469cbff2 in QMetaObject::activate (sender=<value optimized out>, m=<value optimized out>, local_signal_index=<value optimized out>, argv=) at kernel/qobject.cpp:3101 #12 0x469d15c7 in QSingleShotTimer::timeout (this=) at .moc/release-shared/qtimer.moc:74 #13 0x469d16ec in QSingleShotTimer::timerEvent (this=<value optimized out>) at kernel/qtimer.cpp:294 #14 0x469c5d4f in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1120 #15 0x48498e9c in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3803 #16 0x484a0d1e in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3393 #17 0xb7a9173d in KApplication::notify (this=0xbfa2a2e4, receiver=0x9c3e930, event=0xbfa29ebc) at ../../kdeui/kernel/kapplication.cpp:307 #18 0x469b6771 in QCoreApplication::notifyInternal (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at kernel/qcoreapplication.cpp:587 #19 0x469e46d1 in QTimerInfoList::activateTimers (this=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #20 0x469e496b in QEventDispatcherUNIX::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:893 #21 0x485335d6 in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_x11.cpp:148 #22 0x469b4e3a in QEventLoop::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:143 #23 0x469b4ffa in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:194 #24 0x469b76b5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #25 0x48498d17 in QApplication::exec () at kernel/qapplication.cpp:3331 #26 0xb7ef1c79 in kdemain (argc=1, argv=0xbfa2a464) at ../../kwalletd/main.cpp:66 #27 0x08048592 in main (argc=) at kwalletd_dummy.cpp:3
The crash reported in Comment #7 is seen on KDE 4.2 Beta2.
Hi Ritesh, thanks for rereporting. I had a close look at your backtrace from c#7. Unfortunately you seem to have built kwalletd with some optimization and the method crashing isn't in the file the backtrace mentions (some strange messup). Could you please retry with a non-optimized build? The kwallet daemon is in kdebase/runtime/kwalletd.
(In reply to comment #9) > Could you please retry with a > non-optimized build? The kwallet daemon is in kdebase/runtime/kwalletd. > I should be able to, some time in January only. I rely on packaging done by Debian. But since, you're asking me to non-optimize build kwalletd, I'm assuming that that's only for kwalletd and not the whole kdebase. I'll re-build and get back with the information in the 1st week.
Hi Ritesh, have you been able to reproduce this bug with the KDE 4.2 final release?
(In reply to comment #11) > Hi Ritesh, > > have you been able to reproduce this bug with the KDE 4.2 final release? > No. With 4.2, I haven't the crash yet.
Bug 183398 and bug 183112 seems to be the same bug as this but in KDE4.2
This is fixed now. Marking it as a duplicate of a newer bug because the newer one is already closed. *** This bug has been marked as a duplicate of bug 183112 ***