After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557138 - Nautilus doesn't detect when a read-only (ro) file system is remounted read-write (rw)
Nautilus doesn't detect when a read-only (ro) file system is remounted read-w...
Status: RESOLVED DUPLICATE of bug 703179
Product: nautilus
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-20 19:17 UTC by Wouter Bolsterlee (uws)
Modified: 2017-09-15 17:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Wouter Bolsterlee (uws) 2008-10-20 19:17:01 UTC
One file system I use is typically mounted read-only to make sure I don't accidently delete stuff there. When I *do* want to change the contents of this file system I remount the file system using "remount -o rw,remount" (actually, a small "remount.sh" shell script does this for me).

However, after the disk is remounted rw, Nautilus refuses to let me move files around: "cutting" files is disabled, as is "pasting" files. Refreshing (Ctrl-R) doesn't help either.
Comment 1 Wouter Bolsterlee (uws) 2008-10-20 19:19:04 UTC
Hmm. It seems that *dragging* files with my mouse *does work*. This results in a read-only emblem on the file in its new location though, though the actual file is "rw-r--r--". After refreshing the directory view the read-only emblem is gone again.
Comment 2 William Jon McCann 2012-08-20 22:53:25 UTC
Still an issue?
Comment 3 Ildar 2013-08-24 20:47:32 UTC
Yes.
Comment 4 Nelson Benitez 2017-09-15 17:51:05 UTC
Marking as dup of bug 703179 in spite of this one being older and with a better description, because the other one has more explanations, more CC list members, and a patch.

*** This bug has been marked as a duplicate of bug 703179 ***