MAGEIA 9 BETA 1 This is not a bug but it bothers many less advanced users. When we mount a usb it is mounted read-only in the /run/user/ drive directory. I think it would be better to leave it as read and write.
level security: fileserver
QA Contact: security => (none)Component: Security => RPM Packages
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
I can't recreate. In m9 x86_64 kde plasma ... /dev/sdb1 on /run/media/dave/BACKUP type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2) Note the errors=remount-ro. Check dmesg or the journal for errors. Also make sure it's a file system that can be mounted rw. Not iso9660 for example.
CC: (none) => davidwhodgins
This complaint is so basic that every user would have complained since forever. Ricard, you need to be more specific about when a mounted USB cannot be written to. Dave's example line from (I suppose) 'mount' can be cross-checked by 'ls -l ...' the relevant directory; or the device Properties from a file manager. The end of the system journal, as Dave suggests, should help.
CC: (none) => lewyssmith
Sorry. Yes it's from the mount command. On my m8 system with the same device ... # mount|grep media /dev/sdf1 on /run/media/dave/BACKUP type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
Use (as root) "dmesg|tail -n 20" to get those messages.
I think this is related to the security level "fileserver". This security level has other rights than the "standard" one. So i don't see how this could confuse a user...
Note that ls -l will still show the directory as rw, but writes will fail if the device that directory is on is ro. The security level is not relevant (I tested with security level fileserver to be sure. It's either errors forcing it to remount as ro, or a file system type that can not be mounted rw such as iso9660. For file systems that support uid/gid such as ext4, the ownership and permissions of the directories and files matter too, on which users can write to it.
Today I tried again to recreate the bug on my computer from the dolphin program in mageia 9 beta 1. With a flash drive formatted as extfat, fat and ntfs like the other time and it hasn't given me any errors. I have deleted the /run/media/user directory because I thought it still kept the permissions modified by me and I have let the system create it without giving me any error this time. I think it would be better to close the error created by me by not being able to reproduce it and provide more data.
If you need me to try something, let me know. Sorry for the google translation
Closing as invalid. Please reopen if you can recreate and there is a problem with the Mageia packages.
Resolution: (none) => INVALIDStatus: UNCONFIRMED => RESOLVED