https://bugs.kde.org/show_bug.cgi?id=524500
--- Comment #11 from [email protected] --- (In reply to Bug Janitor Service from comment #10) > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/kwallet/-/merge_requests/179 This looks like it fixes a different bug than https://bugs.kde.org/show_bug.cgi?id=524621. This MR fixes an issue where "Idle Timeout" was read as milliseconds instead of minutes which is a more serious issue. I noticed that with "Close When Idle" set to true, I couldn't open a wallet in kwalletmanager without it being closed very quickly which is likely due to this misinterpretation of the units of "Idle Timeout". Fixing this issue will not resolve the killTimer error; It will only make it happen much less frequently. The bug in https://bugs.kde.org/show_bug.cgi?id=524621 is caused because there is a cycle of timers that are created. When an idle timer fires, it will attempt to close the wallet associated with the timer ID and then kill the timer, however, the KWalletD::close function calls the KWalletD::walletForHandle function which, when "Close When Idle" is set, kills the timer and starts a new timer associated with the wallet. Then after these function calls resolve, the old timer ID is killed again in the KWalletD::timerEvent function after closing the wallet causing the error in the logs. The error log will keep happening on the "Idle Timeout" interval indefinitely because a new timer is started every time the timerEvent fires and the previous timer is killed. -- You are receiving this mail because: You are watching all bug changes.
