[Bug 1001554] New: A user cannot umount a FAT32 USB stick using Files
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554 Bug ID: 1001554 Summary: A user cannot umount a FAT32 USB stick using Files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: ronisbr@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi guys! After the update of Tumbleweed to GNOME 3.22, a user cannot umount a FAT32 USB stick using files. It shows the message: umount: /run/media/ronan.arraes/RONAN: umount failed: Operation not permitted Hence, the only way I found to umount the device was logging as root. I tried with an external HDD that has two partition: one FAT32 and another EXT4. The latter can be correctly umount by a user using Files, whereas the former cannot. This problem was not happening with GNOME 3.20. I could reproduce this behavior in two different Tumbleweed machines. Hence, it should not be a configuration problem. More information about my system: cat /etc/os-release 22:14:32 NAME="openSUSE Tumbleweed" # VERSION="20160924" ID=opensuse ID_LIKE="suse" VERSION_ID="20160924" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20160924" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c1
Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c2
--- Comment #2 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c3
--- Comment #3 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c4
--- Comment #4 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c5
--- Comment #5 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c6
--- Comment #6 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c7
Dominique Leuenberger
Guys,
I found something really weird. I cannot use `umount` as user to unmount the device. However, if I run the following command as an user:
udisksctl unmount -b /dev/sdb1
then the device is unmounted properly.
nothing weird - normal behavior; but udisk is what nautilus should fire off to do the umount too (well, through the dbus api) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c8
--- Comment #8 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c9
--- Comment #9 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c10
--- Comment #10 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c11
--- Comment #11 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c12
--- Comment #12 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554 http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c13 Kunigumi yen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i@kuni93.moe --- Comment #13 from Kunigumi yen --- I also got same problem when I upgrade to Tumbleweed 20160927 (Gnome 3.20 to 3.22). A user umount (or eject via Nautilus) the external device it not work, unless use gnome-disks or root user. Today up to Tumbleweed 20161003, the problem persists. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c14
--- Comment #14 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c15
--- Comment #15 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c16
--- Comment #16 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c17
--- Comment #17 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c18
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c19
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c20
--- Comment #20 from Dominique Leuenberger
For the record, I did a fresh Tumbleweed installation in VirtualBox yesterday (default KDE install, with the NET ISO), and /var/run/ was a symlink to /run/.
And ntp was/is installed, so it's maybe not the culprit (or the problem has been fixed already...)
Or the issue only happens with the DVD - installing from the live image means also using the NET installer - as Ronan said, then the problem does not appear; only when installing from the DVD -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c21
--- Comment #21 from Wolfgang Bauer
Or the issue only happens with the DVD - installing from the live image means also using the NET installer - as Ronan said, then the problem does not appear; only when installing from the DVD
Right, I just wanted to mention it. (And I forgot about the fact that the LiveCD is using the NET installer nowadays... Sorry for that.) May be related to the order in which the packages are installed too I suppose, might explain a difference between a KDE and a GNOME install. But probably not between a GNOME install using the DVD or the NET ISO... What may be a difference though is that the NET installer downloads the current versions from the online repos, while the DVD is fixed. So maybe it would be a good idea to retry with the latest DVD? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c22
--- Comment #22 from Ronan Chagas
Nice debug work Ronan!
Now up to finding why this would go wrong.
filesystem does, it it's pre-install script:
if not posix.stat("/var/run") then posix.symlink("/run","/var/run") end
Which can only mean that when the installation happened, /var/run existed already (otherwise it would have been symlinked)
So the big question will be to find what was evil enough to create this directory
Hi Dominique, Thanks! I installed Tumbleweed again disabling NTP at installation (using the standard DVD) and the problem continues. Any new ideas? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c23
--- Comment #23 from Ronan Chagas
What may be a difference though is that the NET installer downloads the current versions from the online repos, while the DVD is fixed. So maybe it would be a good idea to retry with the latest DVD?
Hi! I am already using the latest available Tumbleweed ISO. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c24
--- Comment #24 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c25
--- Comment #25 from Ronan Chagas
One question for my clarification: when you talk about the 'GNOME Live CD' that us the 'Tumbleweed GNOME Live CD', same snapshot number as the DVD, right?
Exactly! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c26
--- Comment #26 from Andrei Borzenkov
* ntp (it should likely also use /run - it's the only cause I can find)
ntp matches due to /var/lib/ntp/var/run so it cannot trigger /var/run creation. The worst case is if some script does "mkdir -p /var/run/foo" during installation. Not sure if there is feasible method to check it. Is it possible single-step installation? Then we could check after every package when /var/run appears. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c27
--- Comment #27 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c28
--- Comment #28 from Dominique Leuenberger
I started the installation and begin to continuously type `ls` in the console. I figured out that the /var/run directory is created during the process of deploying GNOME image. Does it make any sense?
yes. this is pretty much where I started looking in already and what I expected... from what I found in the images there is a stale zypp.pid in there for some reason. https://build.opensuse.org/package/rdiff/openSUSE:Factory:Live/openSUSE-images?linkrev=base&rev=27 is an attempt to get this fixed already (I reverted the first - was not happy with the partial clenaup only) - the next snapshot will show it to be true/false -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c29
Emanuel Castelo
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c30
--- Comment #30 from Emanuel Castelo
System: Host: linux-s4s1 Kernel: 4.7.5-1-default x86_64 (64 bit gcc: 6.2.1) Desktop: Cinnamon 3.0.7 dm: sddm,sddm Distro: openSUSE Tumbleweed
found file with possible reference to symlink, not sure if it pertains,
/usr/lib/dracut/modules.d/30convertfs/convertfs.sh -rwxr-xr-x 1 root root 6035 Nov 25 2015 convertfs.sh
https://gist.github.com/anonymous/64e1fb32751bb9611522982148d348cd file content as found and snippet: if [ ! -L $ROOT/var/run -a -e $ROOT/var/run ]; then echo "Converting /var/run to symlink" mv -f $ROOT/var/run $ROOT/var/run.runmove~ ln -sfn ../run $ROOT/var/run fi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
Ismail Donmez
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c31
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c32
--- Comment #32 from Ronan Chagas
Ronan,
Can you please test with the latest DVD (20161010) if this problem still exists or if my fix worked?
Sure! I'm downloading openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161010-Media.iso right now to test. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c33
--- Comment #33 from Ronan Chagas
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c34
Atri Bhattacharya
1) Reboot in maintenance mode (INIT 1); 2) Unmount /var/run (I guess it is bind mounted to /run); 3) rm -rf /var/run 4) cd /var 5) ln -sf ./run ../run
Is something like this really necessary? Shouldn't https://git.gnome.org/browse/gvfs/commit/?id=be0c464 fix things (at least the issue with nautilus being unable to unmount) automatically? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c35
--- Comment #35 from Ronan Chagas
(In reply to Ronan Chagas from comment #33)
1) Reboot in maintenance mode (INIT 1); 2) Unmount /var/run (I guess it is bind mounted to /run); 3) rm -rf /var/run 4) cd /var 5) ln -sf ./run ../run
Is something like this really necessary? Shouldn't https://git.gnome.org/browse/gvfs/commit/?id=be0c464 fix things (at least the issue with nautilus being unable to unmount) automatically?
Yes, this should fix this problem. However, AFAIK, /var/run must be a symlink to /run nowadays. Hence, I think other bugs can occur if this is not fixed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554
http://bugzilla.opensuse.org/show_bug.cgi?id=1001554#c36
Ronan Chagas
participants (1)
-
bugzilla_noreply@novell.com