Nautilus says the USB stick is read only when it is not

I have a problem with USB flashdrives as well. Everytime I insert my cruzer thubdrive it says it fails to mount, yet it mounts anyway. Normally this wouldn't be an issue, but when you go to unmount it properly it fails to do so..I am forced to just simply pull the flash driveo out.

Status changed to 'Confirmed' because the bug affects multiple users.

I have the same problem with memory cards too.

I can add that I had no problems with nautilu 'til 2-3 days ago. Afte upgrade to 12.04 everything was OK but it changed few days ago. So maybe it's result of some updated package/library?

I came across patched Nautilus from SoluOS project, installed it in few easy steps described here:

http://www.webupd8.org/2012/08/install-solusos-patched-nautilus-in-ubuntu-1204.html

And now Nautilus work OK :) So it's one of their patches, which solves the problem :-)

I'ts the same problem for me. I'm using a USB hard drive (Fantom Drives, Green Drive, 1TB)

I even formatted the drive using Ubuntu 12.04 itself. That is, in Unity Launcher on leftside, I right-clicked the drive icon and selected Format. I did tests using both EXT4 and FAT32. Same results.

As I type this Ubuntu 12.04 "Backup" has no problems writing to the drive. I have no problem writing to the drive in the Terminal. If I open Gedit and save to the drive, no problem...

But, anything I try in Nautilus (Create New Folder, Drag & Drop Copy) gives the error: "The destination is read-only."

Seeing the same on a VFAT 500GB USB drive on Ubuntu 12.04, nautilus 3.4.2. Symptoms are identical to the OP's.

Same problem for me. The problem appears when upgrade the package from 1:3.4.2-0ubuntu4 (originally installed when upgrade to precise 12.04 release) to 1:3.4.2-oubuntu5 during normal upgrades proposed.
In one laptop i use the 1:3.4.2-0ubuntu4 version and no problem at all, otherwise another 2 machines win 1:3.4.2-0ubuntu5 version is affected by the bug.

Same problem here with a SANSA player - super annoying.

Same supper annoying bug. Shoud be fixed anytime soon!

Not my case, but for sure many many Windwos users that try to use Ubuntu may face this bug.

Actually, use Ctrl+C and then Ctrl+V - works just fine.

Hello,
I have the same problem (referring to the original post) under 12.04 LTS with Nautilus 3.4.2 and a 2GB Kingston USB stick.

Copying via console and thunar (which I installed for testing) went fine. dmesg shows nothing strange, i.e.

[18395.837494] usb 2-1.2: new high-speed USB device number 11 using ehci_hcd
[18395.933263] scsi14 : usb-storage 2-1.2:1.0
[18396.932891] scsi 14:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS
[18396.934224] sd 14:0:0:0: Attached scsi generic sg2 type 0
[18397.773851] sd 14:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB)
[18397.774426] sd 14:0:0:0: [sdb] Write Protect is off
[18397.774437] sd 14:0:0:0: [sdb] Mode Sense: 23 00 00 00
[18397.775093] sd 14:0:0:0: [sdb] No Caching mode page present
[18397.775103] sd 14:0:0:0: [sdb] Assuming drive cache: write through
[18397.778319] sd 14:0:0:0: [sdb] No Caching mode page present
[18397.778330] sd 14:0:0:0: [sdb] Assuming drive cache: write through
[18397.779229] sdb: sdb1
[18397.781520] sd 14:0:0:0: [sdb] No Caching mode page present
[18397.781532] sd 14:0:0:0: [sdb] Assuming drive cache: write through
[18397.781542] sd 14:0:0:0: [sdb] Attached SCSI removable disk

so far, so bad...

ah, forgot: ctrl-v and ctrl-c don't work under nautilus. gksu nautilus didn't help.

One more person with this read-only problem :-(

When I put a SD Card into the slot in my laptop Nautilus opens the SD Card, but I also get the problem: The destination is read-only :-(

In a terminal everything works fine.

When I run sudo nautilus in the termnal everything also works fine and I can write to the SC Card - but why not when I'm running Nautilus as normal user :-(

Permissions look also fine to me:

jorgen@Jukebox:/media$ ls -l
totalt 40
drwxr-xr-x 2 jorgen jorgen 4096 dec 3 15:02 Cloner
drwxrws---+ 11 root data-rediger 4096 jan 28 17:28 Data
drwxrwsr-x+ 2 root multimedia-rediger 4096 nov 26 21:34 Multimedia
drwxrwsr-x+ 2 root multimedia-rediger 4096 nov 26 21:34 Raa-foto
drwx------ 5 jorgen jorgen 16384 feb 26 19:01 SD-CARD_512
drwxrwsrwx+ 2 root udveksling-rediger 4096 nov 26 21:34 Udveksling
drwxrwsr-x+ 2 root work-rediger 4096 nov 26 21:34 Work
jorgen@Jukebox:/media$

The following fixed the issue for me:

sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

This problem went away for me after I updated to 13.04

I need to stay on 12.04 LTS (!)
FWIW I found that restarting the machine and reinserting the usb stick, gave me a normally functional usb with nautilus.
Another fix was to install an alternative file manager Thunar, and make use of this while the problem occurred.

I got this problem after upgrading from 12.10 to 13.04.

This problem had gone away in 12.04 for a while, at least on external USB drives (but still on SD cards plugged in to a USB adapter), but came back with one of the updates made in the past few days.

This problem affects me on Ubuntu 13.04 64-bit, running nautilus 3.6.3 from default repositories. This is a fresh install with all available updates installed.
All USB drives show "Error while copying to "[name of drive]." The destination is read-only."

Tested with three working USB sticks, all formatted FAT-32 via Gparted. Able to use touch, cp, mv, mkdir via terminal with no problems. Simply unable to create folders, drag files, or copy/paste files though nautilus.

Here is the terminal output from running 'mount' with one of these USB drives plugged in, after receiving error message. Note, USB is last disk listed, /dev/sdh, mounted under /media/mike/SanDisk:

mike@cobbler:~$ mount
/dev/sda3 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
/dev/sdb2 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfsd-fuse on /run/user/mike/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=mike)
/dev/sdh1 on /media/mike/SanDisk type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)

Same problem for me with Ubuntu 13.04 64-bit and nautilus 3.6.3 .
I can have write access only when nautilus is launched using sudo from a terminal.

Well, I found a solution.
1. I renamed the /home/[my-username]/.config directory as /.config.old
2. After logout and new login, a new /.config directory is generated.
3. I replaced the old /.config.old/nautilus directory by the newly generated /.config/nautilus
4. /.config erased.
5. /.config.old renamed as /.config again
5. Logout and new login => problem solved.

could you diff those directories to try to find out what is different between those configs and creating the issue?

I had the same issue, but the procedure by Christophe works for me.
See attached the output of 'diff nautilus nautilus.old'.

I have the same issue on Ubuntu 13.04 and was able to workaround it using the Christophe's trick from comment #22

Thanks, Christophe, but we would like to know the rationale behind your workaround, in order to better know why the bug happens at the first place.

Had the same issue on 13.04. Trick from #22 also helped. The only difference between two configs is that the bad config has an extra line in the middle of it:
---
$ diff accels ~/.config/nautilus.old/accels
47a48
> ; (gtk_accel_path "<Actions>/ExtensionsMenuGroup/DejaDupNautilusExtension::restore_missing_item" "")
---

Well, this issue is always there using Ubuntu 13.04 & nautilus (3.8.0-31-generic #46-Ubuntu) !
The workaround I proposed earlier works (I don't know why) but the problems still comes back regularly.
Is anybody has found what triggers it ?

The very same problem exists on Mint 15 (based on 13.04) and Thunar 1.6.2.
I actually run Nautilus to work around the problem and copy the files.
The problem might be in lower levels.

Just happened to me all of a sudden (eg, have not observed this problem on 12.04 or 13.04 until today, but haven't used a USB stick for 2+ weeks). Unity desktop; Files 3.6.3 (whatever that is) produces a popup stating that target is read-only, which it isn't, of course. The config file identified in post #22 contains the line indicated there...
; (gtk_accel_path "<Actions>/ExtensionsMenuGroup/DejaDupNautilusExtension::restore_missing_item" "")
But it looks as though it is supposed to be there.
Would be happy to edit a defective line out, but is anyone sure which it is ?
uname -a...
Linux .... 3.8.0-34-generic #49-Ubuntu SMP Tue Nov 12 18:00:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a...
Description: Ubuntu 13.04
Codename: raring

(BTW, closing down for seasonal holiday soon... will check back in the new year)

Using 13:10. This is super super annoying bug. Will drive far away any windows user trying to use Ubuntu, for sure.

Please fix this soon.

I can copy files using Terminal as normal user. But with nautilus, it giving me "is read only" error.

I have the read-only bug under a slightly different condition: Its not a external USB-Stick but a remounted partition.

For security reasons I have an archive partition which is mounted read-only at startup of the notebook. When I mount the partition afterwards in readwrite-mode then nautilus tells me, the partition is still read-only. But all other tools, commandline etc. works fine.

So it seems to me, this bug has something to do with in-memory cached directory information in nautilus. Maybe this information gets cleared during logout/login, so it is not the observed line in the .config but the process of relogon which solves this problem?

I have this effect since at least two years and with different versions of ubuntu. For sure with 12.04, 13.04, 13.10 and all updates between them. For me this bug is allways fully reproducible.

I to have the same problem!
I have tried 2 diferent USB sticks & nothing can be saved to them. Either by drag & drop or saving from a text editor (JuffEd & Gedit) or even OpenOfice.
One of the USB sticks did let me moove a file when I firs got it but it stoped after I plged it into my Android.
I can open the USB sticks in "Windows!" & chaing the permissions.
But I am completly locked out with Ubuntu.
Is pluging the USB sticks into other OS's leaving a cooky that Ubuntu is objecting to?
Have fun.
d0m.

I reboot system on recovery mode, and did some of the support programs. Now it works

Affects me - another temporary workaround is to load nautilus as root from terminal which allows me to write to usb

This is really annoying please fix.

I did

sudo mount -o remount,rw /media/<mount point>

which works copying files in nautilus (until you pull out the usb stick of course)

I can confirm the observations of comment #20. On this basis, I'm raising the importance because this seems to me like a major usability issue.

Still a problem on 14.04 now. What's confusing is that the file system is properly mounted, and I can copy a file onto the drive using cp in a terminal, so it is a pure Nautilus issue.

Mount:
/dev/sdc1 on /media/sergei/16GB type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)

Dmesg:
[514464.082007] usb 3-8: USB disconnect, device number 30
[514465.866850] usb 3-8: new high-speed USB device number 31 using xhci_hcd
[514465.883728] usb 3-8: New USB device found, idVendor=0781, idProduct=5530
[514465.883737] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[514465.883742] usb 3-8: Product: Cruzer
[514465.883746] usb 3-8: Manufacturer: SanDisk
[514465.883749] usb 3-8: SerialNumber: 20060572701B1A23221D
[514465.884351] usb-storage 3-8:1.0: USB Mass Storage device detected
[514465.884525] scsi26 : usb-storage 3-8:1.0
[514466.882586] scsi 26:0:0:0: Direct-Access SanDisk Cruzer 1.03 PQ: 0 ANSI: 2
[514466.883096] sd 26:0:0:0: Attached scsi generic sg3 type 0
[514466.883864] sd 26:0:0:0: [sdc] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
[514466.884952] sd 26:0:0:0: [sdc] Write Protect is off
[514466.884962] sd 26:0:0:0: [sdc] Mode Sense: 03 00 00 00
[514466.885247] sd 26:0:0:0: [sdc] No Caching mode page found
[514466.885252] sd 26:0:0:0: [sdc] Assuming drive cache: write through
[514466.888280] sd 26:0:0:0: [sdc] No Caching mode page found
[514466.888289] sd 26:0:0:0: [sdc] Assuming drive cache: write through
[514466.891130] sdc: sdc1
[514466.893934] sd 26:0:0:0: [sdc] No Caching mode page found
[514466.893936] sd 26:0:0:0: [sdc] Assuming drive cache: write through
[514466.893938] sd 26:0:0:0: [sdc] Attached SCSI removable disk

I have the same problem. Can create/delet file from terminal. But operations from nautilus fails wit "destination read only error". The other interesting thing is the same usb drive used to work fine with nautilus till before I made a bootable disk on the usb device using dd. I tried coping the initial 20MB from another usb. But the "read only" error persists.

I appear to be having the same issue as SergeiS & tonysonney under 14.04,
file system permissions are correct and cp works fine from the command line for one of my USB hard drives, but drive consistently shows as 'Owner: root' in Nautilus - even though mount options are identical to an automounted SATA drive that shows as 'Owner: me'

Other USB devices, (flash drive, HD from a different manufacturer) mount with correct Ownership in nautilus.. (also, i noticed everything that mounts correctly has a little icon in the media folder - a thumb-drive, internal disk icon, etc. while the badly behaving "root" media device does not have a little icon on the folder)

Ubuntu automount point permissions:
bjv@saucy10:/media/bjv$ ls -lt /media/bjv
total 16
drwx------ 1 bjv bjv 4096 Nov 19 06:05 WD My Passport Ultra
drwx------ 1 bjv bjv 8192 Nov 18 07:56 WD Caviar Black

Ubuntu automount options:
bjv@saucy10:/media/bjv$ mount | tail -n2
/dev/sdc1 on /media/bjv/WD My Passport Ultra type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
/dev/sdb1 on /media/bjv/WD Caviar Black type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)

Dmesg:
[3345508.088038] usb 1-4: new high-speed USB device number 26 using ehci-pci
[3345508.269200] usb 1-4: New USB device found, idVendor=1058, idProduct=0820
[3345508.269206] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[3345508.269210] usb 1-4: Product: My Passport 0820
[3345508.269213] usb 1-4: Manufacturer: Western Digital
[3345508.269217] usb 1-4: SerialNumber: 575832314139344654415636
[3345508.269644] usb-storage 1-4:1.0: USB Mass Storage device detected
[3345508.270284] scsi18 : usb-storage 1-4:1.0
[3345509.268725] scsi 18:0:0:0: Direct-Access WD My Passport 0820 1012 PQ: 0 ANSI: 6
[3345509.269092] scsi 18:0:0:1: Enclosure WD SES Device 1012 PQ: 0 ANSI: 6
[3345509.269553] sd 18:0:0:0: Attached scsi generic sg2 type 0
[3345509.269840] scsi 18:0:0:1: Attached scsi generic sg3 type 13
[3345509.276843] sd 18:0:0:0: [sdc] Spinning up disk...
[3345510.280020] .ready
[3345515.207842] sd 18:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.81 TiB)
[3345515.209831] sd 18:0:0:0: [sdc] Write Protect is off
[3345515.209837] sd 18:0:0:0: [sdc] Mode Sense: 47 00 10 08
[3345515.211210] sd 18:0:0:0: [sdc] No Caching mode page found
[3345515.211215] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[3345515.216837] sd 18:0:0:0: [sdc] No Caching mode page found
[3345515.216845] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[3345515.217232] ses 18:0:0:1: Attached Enclosure device
[3345515.226127] sdc: sdc1
[3345515.229341] sd 18:0:0:0: [sdc] No Caching mode page found
[3345515.229352] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[3345515.229356] sd 18:0:0:0: [sdc] Attached SCSI disk

Ubuntu version
bjv@saucy10:~/Downloads$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

bjv@saucy10:~/Downloads$ dpkg -l | grep 'nautilus[ ].*ubuntu'
ii nautilus 1:3.10.1-0ubuntu9.3 ...

remounting per comment #20 (sudo mount -o remount,rw /media/<mount point>) did not work with nautilus 3.10.1-0ubuntu9.3 on 14.04

It occurred for me yesterday for the first time ever. I have Dell XPS netbook running 64bit 16.04, upgraded from 14.04. Been using Ubuntu for many many years on many machines, never seen this before.

Symptoms: With one of my thumb-drives, I could copy/move files in terminal without any problems, but Nautilus complained about the drive being read-only. Interestingly, using Nautilus, I could still delete files I copied using terminal. Today the bug doesn't occur with the same thumb-drive.

Thumb drive is not brand new (1~2 years old), but there are no problems with it as far as I can see.

Between yesterday and today: I didn't shut down the system on which bug showed up, however I suspended it. Also, I used the drive with other Ubuntu machine.

nautilus --version
GNOME nautilus 3.14.3

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

Any recommended steps to be taken (to gather more data) if I ever see this again?

Same here. Sorry I've got to say i'm so disapointed this bug has been reported since 2012 and it's like nobody cares... feels great preparing to use Linux at work and switching family to Linux and cant even write on a thumbdrive because of a 4+ years old bug... maybe those windows/mac guys are rigth after all...

Just had this on my ages 16.10 with even more aged USB's that have worked fine over the ages :-/. Like others I can copy using terminal but nautilus gives RO error message. "killall nautilus" seemed to clear the problem for me...

*correction* aged 16.04 (sorry)

I've the same issue and "killall nautilus" also fix the problem for me.

What kind of debug information can we provide to help fixing this issue?

Very nasty bug for a new comer, we really need to find a solution...

16.10 ... unbelievable :/

I confirm this bug also affects Nemo on Ubuntu 16.04 (at least).

I had the exact same problem as described but I am using Arch Linux. I made a simple uninstall with pacman -Rcsn. I know this isn't the same command for ubuntu but just use apt-get autoremove and make sure to add the option that also removes all configuration files. Some times some files are still there. In my case it was in my home folder under .config/nautilus and .local/nautilus both for my user and root. To be sure you have deleted everything I suggest using the command:
"find|grep nautilus" under both root and your home to make sure all files are deleted. After that I installed nautilus again. Maybe make a full restart before but I didn't have to. I use Gnome 3 on Arch Linux so hope this maybe apply to you as my discovery makes me think that it might be a fault with configuration files.

Status changed to 'Confirmed' because the bug affects multiple users.

I observe a variant of this bug in Ubuntu 16.04 LTS 64-bit (4.4.0-71-generic #92-Ubuntu): In Nautilus 3.14.3, an auto-mounted partition on a local drive is read-only (no issues before, nothing changed with the system (hardware) configuration). In addition, if I open files with apps (gedit, ...) from Nautilus by double click, I cannot save changes.

The variant is this: Even if I use now the terminal, the drive is read-only (I cannot create files -- touch: cannot touch 'test.txt': Read-only file system -- or save changes when editing files).

Workaround: I can still change content using the terminal or Krusader by remounting the partition, i.e.

sudo mount -o remount,rw '/media/<username>/<partitionname>

However, as soon as I go to the mount directory in Nautilus, it seems to be read-only again, so no chance to change contents. It looks to me like Nautilus really changes actively the information of the mounted drive.

Please let me know if you need further information to debug. I agree to previous users that this bug is really annoying, especially since nothing seems to happen for now almost FIVE YEARS!

I met this problem today, and after kill nautilus and remount problem solved, not sure how to reproduce this again.

I had this problem with Ubuntu 15.04. It was solved by:
mv ~/.config/nautilus ~/.config/nautilus-bak

Had this problem happen to me on 16.04.2. killall nautilus worked for me, and doesn't come back across multiple unplugs and restarts of nautilus.

Wow, it seems to be still present. Just experienced it on 16.10. This is weird, because this bug was driving me nuts on 15.10, and now this was first occurrence since I upgraded from 15.10 to 16.10, which was half a year ago.

P.S. “killall nautilus” and restarting it resolved the issue.

Same for me

I'm on 17.04 fully updated as at 30/5/2017. This is still happening. As per everything the OP had in 2012, I can confirm the same at this end.

No remounting or editing of permissions changed nautilus' permissions for me except for:

* Closing nautilus,
* Removing ~/.config/nautilus, *1
* logging out and back in again (for good measure—not a reboot) and
* restarting nautilus worked for me

*1 May not have been required, but done because I was working through several posts and it was one of the suggested solutions

Just occurred today:

16.04.2 LTS (Xenial Xerus)
4.8.0-54-generic

Same Thumbdrive is accessible and writeable:
14.04.05 Trusty Tahr
4.4.0-79-generic

Unable to mount other USB Drives:

Example:"Device /dev/sdc1 is already mounted at `/media/ubuntu/Debian 8.8.0 amd64 1'"

Here is the output of lsusb:

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 014: ID 18a5:0304 Verbatim, Ltd
Bus 003 Device 003: ID 05d9:a795 Axiohm Transaction Solutions
Bus 003 Device 002: ID 7392:a812 Edimax Technology Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I had upgraded from Ubuntu Gnome 14.04 to 16.04. All of a sudden this issue cropped up! None of my usb sticks would work properly. However, after following the comments here and running killall nautilus, then restarting it solved the problem.

This is almost certainly an upstream bug since I've encountered it in Fedora as well, including Fedora 25.

Still present in 17.10

Same problem for "Caja" on ubuntu 17.10 Mate
restart of Caja solve the problem.

On Latest 17.04, killall nautilus and restarting nautilus doesn't help. Maybe I am not doing the right thing in detail.

So for a couple of years now, every time I present something at a conference, I panic because I'm not going to be able to write my PDF file on a USB key in order to share it -- thanks to this bug. This is nutty.

This has been happening to me for years, and I always forget about it.

I think maybe writing this comment will help me remember the next time.

The same problem can happen in Thunar. For some cases Nautilus itself needs an additional patch, but the underlying problem was identified and fixed in glib. Unfortunately the fixed version is not available in Ubuntu yet. See the Thunar bug for more details, and thanks go to Nelson Benitez for fixing it:

https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1332623

Just experienced this problem with a Seagate Expansion Drive - In Nautilus ownership is 'me' and permission is 'create and delete files' but when trying to write to the file the popup appears saying read-only. I tried the killall Nautilus and access is restored.

The system is ubuntu 16.04 LTS; nautilus version 1:3.18.4.is.3.14.3-0ubuntu6

Before I was able to copy and remove files from USB fat32 drive with the terminal even though nemo might not be working but now cannot do it even with terminal. Cannot do it with command rm -r foldername or sudo rm -r foldername
The problem has got worse at least in my case using linux mint cinnamon 18.3 with latest updates.

I managed to fix my problem by reformating the USB drive. Now I have proper read write delete permissions for my usename.

When fdisk shows type is Empty, this happens in U16.04;

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sdf: 7.2 GiB, 7759462400 bytes, 15155200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x55c3dcb6

Device Boot Start End Sectors Size Id Type
/dev/sdf1 * 0 4620287 4620288 2.2G 0 Empty
/dev/sdf2 1544 2375 832 416K ef EFI (FAT-12/16/32)

I can confirm this is happening on archlinux with gnome DE

Status changed to 'Confirmed' because the bug affects multiple users.

I can confirm this is happening on Xubuntu 18.10 with Thunar as the file manager.
The workaround 'killall Thunar' after inserting the USB drive does work however!

After a recent update to my Ubuntu 16.04 LTS, this error pops in. The solution was to use the similar "killall nautilus" and it fixes it.

What error exactly did you see after that update?

I see that many people say that killall nautilus works for them but it doesn't change anything for me. Perhaps someone could spell out the exact sequence of actions so that I can make sure that I am the problem?

What I am doing right now is
insert USB
try to paste something into it using nautilus (same with using terminal though), see that it's read only.
run killall nautilus in terminal.
(restart or not, I've tried both)
nautilus window disappears.
I try to copy something onto the USB again using Nautilus
still doesn't work.

What am I doing wrong?
I am working on 16.04.6 LTS

Thanks!

@h23 if you are seeing the same behaviour in the terminal the Nautilus is
not the problem. Your USB is write protected or your computer is picking it
up like that for some reason.

You can insert the USB Stick and then run:

dmesg | tail

To see the system log. There you can see if the write protection is turned
on. If you see something like `Write Protect is off`then you should be
okay, otherwise the USB Stick is protected.

On Tue, 25 Jun 2019 at 09:35, li <email address hidden> wrote:

> I see that many people say that killall nautilus works for them but it
> doesn't change anything for me. Perhaps someone could spell out the
> exact sequence of actions so that I can make sure that I am the problem?
>
> What I am doing right now is
> insert USB
> try to paste something into it using nautilus (same with using terminal
> though), see that it's read only.
> run killall nautilus in terminal.
> (restart or not, I've tried both)
> nautilus window disappears.
> I try to copy something onto the USB again using Nautilus
> still doesn't work.
>
> What am I doing wrong?
> I am working on 16.04.6 LTS
>
> Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1021375
>
> Title:
> Nautilus says the USB stick is read only when it is not
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions
>

--
*Sergio Bobillier Ceballos*
Ing. de Sistemas
Universidad Nacional de Colombia
+57 (318) 676-3415

Ubuntu 19.04 (disco) will switch to read-only when a automatically mounted VFAT filesystem with errors is detected.
You have to umount the filesystem and then run "sudo fsck.vfat /dev/sdxxxx" multiple times, until fsck.vfat do no more ask to correct the new errors detected in the filesystem.
Maybe fsck.vfat should be modified so that after the question "Perform changes ? (y/n) y" it asks for "Re-check filesystem ? (y/n)" because its behaviour is confusing...

I know I'm not running the latest LTS, but 16.04, yet I tried Etienne's advice (because it seems to make perfect sense), but fsck wasn't allowed to fix a FAT-mismatch:

   sudo fsck.vfat /dev/sdf1
   fsck.fat 3.0.28 (2015-05-16)
   FATs differ but appear to be intact. Use which FAT ?
   1) Use first FAT
   2) Use second FAT
   ? 1
   Perform changes ? (y/n) y
   /dev/sdf1: 25 files, 445911/487648 clusters
   Writing 1950600 bytes at 2243584 failed: Operation not permitted

Seems like the readonly even applies to "sudo fsck". Permissions of the block device are:

   brw-rw---- 1 root disk 8, 81 Sep 28 23:04 /dev/sdf1

As it seems that this issue is still open, I hope that maybe someone might find this information useful for debugging.

Thanks for any hints!

Bug still present on 20.04

  biep@blok:/media/biep$ ls -la
  totaal 136
  drwxrwxrwx 3 biep biep 4096 feb 6 12:10 .
  drwxr-xr-x 3 root root 4096 apr 27 2020 ..
  drwxr-xr-x 5 biep biep 131072 feb 6 12:10 ventoy
  biep@blok:/media/biep$ chmod a+w ventoy
  biep@blok:/media/biep$ ls -l
  totaal 128
  drwxr-xr-x 5 biep biep 131072 feb 6 12:10 ventoy

Before this I had found that /media/biep was set to root (but the above is after I repaired that)
After 'chown'ing /media/biep to 'biep' I had this:

  biep@blok:~$ getfacl /media/biep
  getfacl: Voorafgaande '/' in absolute padnamen worden verwijderd
  # file: media/biep
  # owner: biep
  # group: biep
  user::rwx
  user:biep:r-x
  group::---
  mask::r-x
  other::---

I repaired that too, but no luck.