Bug 495983

Summary:	Restarting plasmashell undesirably closes all vaults
Product:	[Plasma] plasmashell	Reporter:	Nate Graham <nate>
Component:	Vaults widget	Assignee:	Ivan Čukić <ivan.cukic>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	ivan.cukic
Priority:	NOR	Keywords:	usability
Version First Reported In:	6.0.0
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nate Graham 2024-11-08 18:47:59 UTC

SUMMARY
I want to keep company business super extra secure, so I store it all in a vault that I unlock at the beginning of the day and open some files inside, then lock again at the end of the work day. However, part of my job at this company is testing Plasma merge requests, which entails restarting plasmashell many times a day. Every time I do this, the open vault closes while I've still got files in the Vault open, potentially with unsaved changes!

STEPS TO REPRODUCE
1. Have a vault and unlock it
2. Open a text file in it that you'll be working with all day
3. Test a Plasma merge request by applying the MR and restarting plasmashell


OBSERVED RESULT
The vault is closed and open documents become inaccessible or un-save-able (depending on how the apps you had them open in handle open files that disappear) until the vault is manually opened again.


EXPECTED RESULT
The vault does not close


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.0
Kernel Version: 6.11.6-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon™ 780M Graphics
Memory: 14.9 GB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: HP
Product Name: HP Pavilion Plus Laptop 14-ey0XXX

Comment 1 Nate Graham 2024-11-08 18:48:41 UTC

If this is an intentional behavior, I'd like a way to opt out of it, since it's disruptive to my workflow. But it does feel like a bug; even if you don't have my weird use case, closing open vaults when Plasma crashes (it's been known to happen :) ) isn't great either.

Comment 2 Nate Graham 2024-12-28 22:03:00 UTC

This was user error on my part: I use a bash function to restart plasmashell, and had forgotten that it also restarts KDED. KDED of course is responsible for Vaults, making the behavior expected.