Created attachment 175045 [details] crash backtrace SUMMARY When ejecting a Blu-ray disc from a drive, plasmashell consistently crashes. Dolphin crashes as well if it's open. STEPS TO REPRODUCE 1. Insert a Blu-ray 2. Eject the Blu-ray OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070/PCIe/SSE2 ADDITIONAL INFORMATION Attaching trace for plasmashell. Dolphin trace is identical except for location of main() I started noticing this happening with Plasma 6.2.0. Also, sometimes the "Disks & Devices" system tray is sometimes showing duplicate entries for discs, although I'm not sure if that's related to the issue.
I can confirm the problem. It started with Plasma 6.2.0. Since then, after inserting a DVD into the drive, two identical entries always appear in the system tray pop-up message. It is possible to mount the disk and work with it, but after unmounting and ejecting, one entry always remains. Now in Plasma 6.2.1, two entries still appear and the disk can also be mounted, but the options for ejecting after mounting are not displayed in either entry. Regardless of whether the DVD is ejected from Dolphin, from the console with "eject" or with the button on the device, Plasma now crashes and restarts every time it is ejected. The problem does not occur with external removable disks such as a USB stick, but only with an internal drive. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.4-arch1-1 (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9400 CPU @ 2.90GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630
*** This bug has been marked as a duplicate of bug 493588 ***
*** This bug has been marked as a duplicate of bug 492578 ***