https://bugs.kde.org/show_bug.cgi?id=474273
Bug ID: 474273
Summary: plasmashell restarted from a non-standard directory
may hold open mount points wrongly
Classification: Plasma
Product: plasmashell
Version: 5.27.7
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: omnipotentent...@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Mount a USB drive with the GUI widget
2. Shut down plasmashell and relaunch from a command line with a working
directory at or below the mount point of the USB drive
3. Attempt to safely remove the USB drive with the GUI widget
OBSERVED RESULT
The USB drive fails to unmount via the GUI widget, or indeed via umount, until
the plasmashell is closed and relaunched from a different working directory.
No diagnostic is given.
EXPECTED RESULT
plasmashell should be able to unmount this drive, (by, for instance, changing
its current working directory).
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS 23.05
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
ADDITIONAL INFORMATION
Encountered this issue after a plasmashell crash and I relaunched the
plasmashell from the nearest command line handy, which happened to be in a
subdirectory of the mounted drive, because I was using it to transfer files.
Because this process was quite time consuming, it wasn't until the next day
that I attempted to remove the drive, and I spent a few mystified minutes
trying to figure out what was holding the drive open. I don't think this would
be a commonly encountered issue, but it's also one that seems to be easy to fix
by changing the current working directory on launch, as plasmashell doesn't
seem to be sensitive to this value at all.
--
You are receiving this mail because:
You are watching all bug changes.
