Version: (using KDE 4.2.0) Installed from: SuSE RPMs Kwalletd crashes randomly when knetworkmanager-kde4 opens wallet to store a password. Unfortunately, I'm not able to get reproducible test case. Backtrace: Application: KDE Wallet Service (kwalletd), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] 0x00007f1d4be2ecb0 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f1d4f8a4750 (LWP 4191))] Thread 1 (Thread 0x7f1d4f8a4750 (LWP 4191)): [KCrash Handler] #5 KWalletD::internalOpen (this=0x7fff578e23b0, appid=@0x841138, wallet=@0x841148, isPath=<value optimized out>, w=422, modal=true, service=@0x841150) at /usr/src/debug/kdebase-runtime-4.2.0/kwalletd/backend/kwalletbackend.h:132 #6 0x00007f1d4f4b02b6 in KWalletD::doTransactionOpen (this=0x7fff578e23b0, appid=@0x841138, wallet=@0x841148, isPath=48, wId=422, modal=<value optimized out>, service=@0x841150) at /usr/src/debug/kdebase-runtime-4.2.0/kwalletd/kwalletd.cpp:400 #7 0x00007f1d4f4b1245 in KWalletD::processTransactions (this=0x7fff578e23b0) at /usr/src/debug/kdebase-runtime-4.2.0/kwalletd/kwalletd.cpp:182 #8 0x00007f1d4f4b1c85 in KWalletD::qt_metacall (this=0x7fff578e23b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff578e18a0) at /usr/src/debug/kdebase-runtime-4.2.0/build/kwalletd/kwalletd.moc:275 #9 0x00007f1d4d93e454 in QMetaObject::activate (sender=0x6cfb50, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x667530) at kernel/qobject.cpp:3031 #10 0x00007f1d4d9446ff in QSingleShotTimer::timerEvent (this=0x6cfb50) at kernel/qtimer.cpp:294 #11 0x00007f1d4d938da3 in QObject::event (this=0x6cfb50, e=0x195ea338) at kernel/qobject.cpp:1120 #12 0x00007f1d4c9f71bd in QApplicationPrivate::notify_helper (this=0x62d950, receiver=0x6cfb50, e=0x7fff578e1fa0) at kernel/qapplication.cpp:3803 #13 0x00007f1d4c9fef8a in QApplication::notify (this=0x7fff578e2460, receiver=0x6cfb50, e=0x7fff578e1fa0) at kernel/qapplication.cpp:3768 #14 0x00007f1d4e4cdb3b in KApplication::notify (this=0x7fff578e2460, receiver=0x6cfb50, event=0x7fff578e1fa0) at /usr/src/debug/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307 #15 0x00007f1d4d92a091 in QCoreApplication::notifyInternal (this=0x7fff578e2460, receiver=0x6cfb50, event=0x7fff578e1fa0) at kernel/qcoreapplication.cpp:587 #16 0x00007f1d4d9561c0 in QTimerInfoList::activateTimers (this=0x630e70) at kernel/qcoreapplication.h:209 #17 0x00007f1d4d95258d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:160 #18 0x00007f1d493e40db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f1d493e78ad in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x00007f1d493e7a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x00007f1d4d9524ef in QEventDispatcherGlib::processEvents (this=0x624e50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #22 0x00007f1d4ca879bf in QGuiEventDispatcherGlib::processEvents (this=0x684e38, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #23 0x00007f1d4d9289a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1468932800}) at kernel/qeventloop.cpp:143 #24 0x00007f1d4d928b2d in QEventLoop::exec (this=0x7fff578e2300, flags={i = 1468932880}) at kernel/qeventloop.cpp:194 #25 0x00007f1d4d92affd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #26 0x00007f1d4f4a7b6a in kdemain (argc=1, argv=0x7fff578e2758) at /usr/src/debug/kdebase-runtime-4.2.0/kwalletd/main.cpp:66 #27 0x00007f1d4bdab586 in __libc_start_main () from /lib64/libc.so.6 #28 0x0000000000400769 in _start () at ../sysdeps/x86_64/elf/start.S:113
Sorry, I just saw I didn't reply to this yet. Did the situation resolve already or does the problem still appear? If so, does it appear every time networkmanager-kde4 tries to use the wallet?
It doesn't appear anymore. :) Linux 2.6.27.8-9.1-default x86_64 openSUSE 11.1 (x86_64) Qt: 4.5.0-rc1 KDE: 4.2.00 (KDE 4.2.0) "release 102" Plasma Workspace: 0.3 x11-video-nvidiaG02-180.29-0.1
Really strange. I had several bugreports with similar backtraces. However I don't have a clue what might have caused that bug... Closing as REMIND for now. Please reopen if you can reproduce or provide additional pointers!