https://bugs.kde.org/show_bug.cgi?id=476027
John <ilikef...@waterisgone.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
CC| |ilikef...@waterisgone.com
--- Comment #7 from John <ilikef...@waterisgone.com> ---
I can reproduce this on:
SOFTWARE/OS VERSIONS
Linux (Debian 13 - unstable repository)/KDE Plasma:
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.17-amd64 (64-bit)
Mesa Version: 25.0.0-1
Graphics Platform: Wayland
Dolphin: 24.12.2
HARDWARE SPECIFICATIONS
Hardware: Laptop Dell Inspiron 5770 (17" 1080p@60Hz screen)
CPU: Intel® Core™ i5-8250U CPU @ 1.60GHz
GPU 1: Intel® UHD Graphics 620 (main, Vulkan capable)
GPU 2: AMD Radeon R5 M465 Series
RAM: 8 GiB (7.7 GiB usable)
I just mounted a pen drive, navigated to a folder and opened the terminal in
it.
Then I minimized the terminal, without ever typing anything in it before.
After the minimization I tried to unmount the pen drive and strangely it
refused to do it, showing this message at the top:
"One or more files on this device are open within an application." on a red
background.
This message is clearly lying as there were no files opened on that device!
A folder was opened, if we can call opening the terminal in that folder as
opening the folder.
And not even an 'ls' or 'pwd' command was made.
I don't think simply opening the terminal in a folder should interrupt the
unmount.
If I just open the terminal by itself and navigate to the same folder with the
'cd' command interrupts the unmount too.
Which is also wrong.
This is the second or third time I notice this strange and unexpected behavior.
I think the unmount should work anyway as long as not folders or files are read
or written.
If you want you can improve Konsole a bit to show after the unmount a message
like:
This folder is not available anymore as the drive was unmounted
Maybe change the background of the path / working directory too.
--
You are receiving this mail because:
You are watching all bug changes.
