Your message dated Sat, 22 Nov 2025 16:43:23 -0500
with message-id
<caaajcmydjeek6fftrto8wfxno9rjxvpq4-h7x1cm7t6nlks...@mail.gmail.com>
and subject line closing old gnome-shell bugs
has caused the Debian Bug report #814081,
regarding Fails to keep USB key unmounted
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
814081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814081
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.14.4-1~deb8u1
Dear Maintainer,
I own a Kingston DataTraveler USB key. When I want to unplug it, I click
on the "Eject" button in GNOME Shell's notification bar.
The key is properly unmounted and disappears briefly from Nautilus, then
it is immediately mounted again, as if I just plugged it.
It annoys me because I can't be sure nothing is being written on the key
when I unplug it, which can lead to data loss.
I filed this bug for GNOME Shell because it doesn't happen with other
desktops (I tried with XFCE, MATE, Ubuntu with Unity, and even Windows
10). Unmounting from Nautilus works as it should, too. The 'eject'
command in a terminal works. It's really specific to GNOME Shell.
It happens only with this USB key : I have two other keys from other
brands and they are properly unmounted. I would assume it's just a bad
quality USB firmware if it didn't happen only in GS.
I can reproduce the bug on a fresh Jessie install.
My kernel version is 3.16.7-ckt20-1+deb8u3. I observe the bug on the
backported 4.3.0-0.bpo.1-amd64 kernel too.
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bích
--- End Message ---
