DESCRIPTION The system logs are spammed with messages like: QObject::killTimer(): Error: timer id 1124073473 is not valid for object 0x7ffd51f1e360 (KWalletD, ), timer has not been killed. From my analysis, this appears to happen in the KWalletD::timerEvent function. This function calls KWalletD::close which calls KWalletD::walletForHandle which calls killTimer. killTimer is also then called at the end of the KWalletD::timerEvent function on the same already killed timer ID. STEPS TO REPRODUCE 1. Start kwalletd6 2. Open a wallet (e.g. with kwalletmanager) 3. Observe log spam OBSERVED RESULT Logs are spammed EXPECTED RESULT No log spam SOFTWARE/OS VERSIONS Operating System (available in the Info Center app, or by running `kinfo` in a terminal window): KDE Plasma Version: 6.7.4 KDE Frameworks Version: 6.29.0 Qt Version: 6.11.2 ADDITIONAL INFORMATION
DESCRIPTION After update to Frameworks 6.29 system logs are spammed with kwalletd6 messages several times per second. Aug 22 07:14:01 host kwalletd6[5925]: QObject::killTimer(): Error: timer id 234881031 is not valid for object 0x7ffed8295270 (KWalletD, ), timer has not been killed Aug 22 07:14:01 host kwalletd6[5925]: QObject::killTimer(): Error: timer id 251658249 is not valid for object 0x7ffed8295270 (KWalletD, ), timer has not been killed Aug 22 07:14:01 host kwalletd6[5925]: QObject::killTimer(): Error: timer id 268435466 is not valid for object 0x7ffed8295270 (KWalletD, ), timer has not been killed Aug 22 07:14:01 host kwalletd6[5925]: QObject::killTimer(): Error: timer id 285212676 is not valid for object 0x7ffed8295270 (KWalletD, ), timer has not been killed STEPS TO REPRODUCE 1. Start kwalletd6 with option "Close after timeout" 2. Open a wallet (e.g. with kwalletmanager) 3. Observe log spam WORKAROUND Disable "Close after timeout" OBSERVED RESULT Logs are spammed EXPECTED RESULT No log spam SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 16.0 KDE Plasma Version: 6.7.4 KDE Frameworks Version: 6.29.0 Qt Version: 6.11.2 Kernel Version: 6.12.0-160000.37-default (64-bit)
*** This bug has been marked as a duplicate of bug 524500 ***