Bug 502449

Summary:	After creating a vault on desktop and moving it the session crashes
Product:	[Plasma] plasmashell	Reporter:	krblanc
Component:	Vaults widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	ivan.cukic, nate
Priority:	NOR
Version First Reported In:	6.3.4
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description krblanc 2025-04-05 13:29:28 UTC

SUMMARY
After a Vault with the mount point on Desktop and the Immediately trying to move the vault (drag and drop on Desktop to move where the folder icon is placed on Desktop) crashes the session - immediate black screen, with no error, and no response whatsoever when trying to use mouse or introduce commands. Changing user with tty shortcuts (e.g. Alt-Ctrl-F3) worked. I had to go to other user then terminate session and after logging back in everything seemed fine, the vault locked, moving the icon working (i do not have the know-how to check if the vault was properly locked or anything from the security standpoint).

STEPS TO REPRODUCE
1. Create new vault with the vaults App (GUI, I did not try from command line, if that exists for vaults).
2. Choose the mount point to be a folder on Desktop (I created a new folder before choosing it as mount point)
3. Finish creating the Vault. The vault is successfully created and unlocked.
4. Try to move the location of the folder (mount point) icon on the desktop via mouse drag and drop.

OBSERVED RESULT
Session crash - black screen. No error, and no response whatsoever when trying to use mouse or introduce commands. Changing user with tty shortcuts (e.g. Alt-Ctrl-F3) worked.

EXPECTED RESULT
Icon is moved on the new position Desktop.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.8-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × Intel® Core™ i9-7960X CPU @ 2.80GHz
Memory: 67.1 GB of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2

ADDITIONAL INFORMATION
I also had the "Vaults" Widget on Desktop, if that matters. I did not try without the widget, dd not think of it until writing this bug report.

Comment 1 Nate Graham 2025-04-07 19:06:44 UTC

Thanks for the bug report!

If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

Comment 2 krblanc 2025-04-09 05:03:00 UTC

So, I tried to crash the user again, an use coredumpctl to create a backtrace, as requested. When I managed to make coredump work, It only listed a few lines about kdewallet, but nothing about vault or anything else, I am not sure if the wallet actually had information.

BUT, I managed to fix the crash. Kind of. I couldn't use the coredumpctl at first because I didn't have enough permissions. This actually reminded me that the user is a Selinux confined user with user_r role. If I temporarily put selinux enforce on 0, coredumpctl worked. Also, when I tried to crash again the session with what I described above, it didn't crash anymore. So the problem was actually Selinux.

I am sorry to post a crash that was actually a Selinux. I know (i think i read somewhere) that fedora does not recommend using confined users yet since the default policies are not good enough to work without problems and the focus is now to make the sysadmin role work correctly and then work more on the other roles (or something like that). 

Next time I will encounter a crash or a bug, I will first test it without selinux, to make sure is not because of the confinement.

Is there anything useful I can provide for the crash in this instance? Is there a Selinux bugzilla group that would maybe be more interested?

Comment 3 Nate Graham 2025-04-09 16:35:02 UTC

Makes sense. I'm pretty sure this is a use case that is 100% untested with no guarantee of it working! But if you can get a useful-looking backtrace, I think it would be useful to keep this around to track it.

Comment 4 Bug Janitor Service 2025-04-24 03:47:31 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2025-05-09 03:46:44 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.