Hi Carlos, thanks for the help. Multiple Leap 15.1 systems do different things for the *exact same USB sticks*. I.e. at least two machines with Leap 15.1 write onto those sticks just fine. Just ONE machine with a fresh install (with all updates) of Leap 15.1 does not want to write to the stick (unless I mount them with super user privileges from the CLI). Why would one system permanently think that all sticks are dirty while all other (identical) systems do not care? (Just tested. `fsck` does not make a difference.) Best regards, Sebastian Am 20.04.20 um 13:11 schrieb Carlos E. R.:
On 20/04/2020 13.07, Sebastian M. Ernst wrote:
Hi all,
I just installed a fresh Leap 15.1 system with KDE and btrfs. Nothing special, I have done this on countless machines.
This particular install has a wired issue: When I plug in in USB-drives (formatted with FAT32), KDE (through Dolphin) mounts them read-only (as I can see in the output of `mount`). Other Leap 15.1 systems mount the same sticks writeable without issues. If I mount the USB drives through a shell (as root) on the "broken" system, I can also write to them without an issue.
Any idea what is going on here?
An USB stick may be mounted read only if the system thinks it is dirty. Ie, needs fsck.