Bug 512116

Summary:	Unplugging a usb device freezes kde plasma
Product:	[I don't know] kde	Reporter:	Kai <kn5i02tst>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	kdedev, kn5i02tst
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kai 2025-11-15 09:27:16 UTC

SUMMARY
When I unplug my nitrokey 3 the whole system freezes even the shortcut to switch to the other consoles doesn't work then anymore.
I don't know if this is really a problem with kde plasma, but maybe we can find the right direction.


STEPS TO REPRODUCE
1. Unplug the usb device (in my case a nitrokey 3)

OBSERVED RESULT
When I unplug my nitrokey 3 the notification for an unplugged device shows, then whole kde plasma freezes with the notification still open. Directly after the freeze I can still move my mouse, but this freezes also very shortly after that.
One time it happened during a online meeting. My usb adapter for the headset, network and the running application was still working because I could continue the call with the frozen screen.
I tried to switch to another tty when plasma is frozen, but nothing changed on my screen.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 16 GiB of RAM (15,5 GiB usable)
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: LENOVO
System Version: ThinkPad X380 Yoga

ADDITIONAL INFORMATION

Comment 1 Kai 2025-11-15 09:39:16 UTC

I have forgotten to add this.

This happens not every time but with a high probability and it started for a month or so.

Comment 2 TraceyC 2025-11-18 23:09:04 UTC

Thanks for the crash report. As the message at the top of the summary says, 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 ?

If there's no coredump, this isn't a crash, but a freeze and there are other things we can try.

Comment 3 Bug Janitor Service 2025-12-03 03:46:12 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 4 Bug Janitor Service 2025-12-18 03:46:18 UTC

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