Bug 524479 - KWallet Manager - Close Behaviour "When unused for:" enabled - Wallet doesn't open
Summary: KWallet Manager - Close Behaviour "When unused for:" enabled - Wallet doesn't...
Status: RESOLVED DUPLICATE of bug 524500
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 26.04.3
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-08-20 09:15 UTC by Don Curtis
Modified: 2026-08-25 15:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
kwalletd open Wallet error (217.68 KB, text/plain)
2026-08-20 09:15 UTC, Don Curtis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Don Curtis 2026-08-20 09:15:49 UTC
Created attachment 195294 [details]
kwalletd open Wallet error

DESCRIPTION
If, in the System Settings, the Close Behaviour "When unused for:" is enabled, all configured Wallets close and, refuse to open.

STEPS TO REPRODUCE
1. Enable the Close Behaviour "When unused for:".

OBSERVED RESULT
All configured Wallets close and refuse to open.
The systemd Journal fills with 1378 lines with -
Aug 20 10:43:18 kwalletd6[14766]: QObject::killTimer(): Error: timer id 218103811 is not valid for object 0x7ffc7712eff0 (KWalletD, ), timer has not been killed

EXPECTED RESULT
That this behaviour doesn't happen.

SOFTWARE/OS VERSIONS
 > kinfo
Operating System: openSUSE Tumbleweed 20260818
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.1
Kernel Version: 7.1.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 34 GB of RAM (32.8 GB usable)
Graphics Processor: AMD Radeon 760M Graphics
 > 

ADDITIONAL INFORMATION
See attached systemd Journal entries.
Comment 1 Don Curtis 2026-08-25 09:26:10 UTC
This is possibly a duplicate of Bug 524500.
Comment 2 michaelk83 2026-08-25 15:39:48 UTC
(In reply to Don Curtis from comment #1)
> This is possibly a duplicate of Bug 524500.
It is.

*** This bug has been marked as a duplicate of bug 524500 ***