Filemanager is unable to write to rw filesystem

Support & Help Requests
1

On startup I mount samba cifs in fstab RO to avoid accidental writing.

  1. I startup Filemanager.
  2. I do the mount -o remount,rw /media/smb
  3. Filemanager does not understand that it is RW now.
  4. Exit Filemanager and run it again.
  5. Filemanager shows it can write but when I try to copy or create file IT FAILS with an error that Filesystem is readonly

At this moment I can create/copy/write in terminal and Midnight Commander without any problem.

If I do not startup Filemanger but first do RW and only after that startup FileManager then everything is OK.

Is it a bug or such a nice feature?
I should say it comes a long time ago(more than 5 years) and on every Ubuntu.
Am I alone discovered this feature?
Is there a workaround? Should I kill something after each mount -o remount?

2

Hi @dnm2dnm ,

sounds like a permissions problem?, are you sure you are the owner of the files?. :smiley:

You might find something useful here?:

https://help.ubuntu.com/community/Samba

3

It could be a caching issue, try pressing F5 a few times inside that folder.

Otherwise, kill off the file manager: (it auto respawns)

Press ALT+F2 then type:

killall caja
1 Like
4

It is not permission problem because everything is OK in terminal.

5

Reload never helped in any ubuntu.
Exit filemanager never helped in any ubuntu.
killall caja DOES HELP which is very convenient. :slight_smile:
Thank you!

1 Like
6

And caja -q will restart Caja.

7

caja -q and killall caja looks working the same.

The interesting thing that the “feature” :slight_smile: stops working that way after first restart/killing caja.
After that Caja just closes the device which was remounted - also convenient stuff. But thank you God it allows to write. :slight_smile:

Very glad to meet the leader of the project!

Just to mention I started to use Mate a year ago and moved into it on all my systems.
I got familiar with Mate on Raspberry PI. Many thanks to that device for it.

Thanks to everybody for the help.

2 Likes
8

This looks a lot like this bug.

1 Like