Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8598 - auto-mounted device has bad owner (or group or privilege)

Attached to Project: Arch Linux
Opened by Piotr Beling (qwak) - Saturday, 10 November 2007, 16:59 GMT
Last edited by Jan de Groot (JGC) - Sunday, 15 February 2009, 00:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

I use GNOME 2.20 in arch64, installed just like here:
http://wiki.archlinux.org/index.php/Gnome
http://wiki.archlinux.org/index.php/HAL

When I:
1) log-in one user
2) switch to next one (log-in next one without log-out first)
3) plug-in my USB pan drive (with fat16 format)
Device is installed properly, and drive icon shows on desktop.
But all files in it (in /mnt/disk) are owned by first user and are in root group, so second user (current working one!) can't write anything to this drive (has no privilege to write).

I thing that after auto-mount new USB pan drive all users (or at least current one) should has privilege to write. Maybe files should be in other group (e.g. 'users' or 'storage') and group members should have write permition... or eventually should give full privilege to everyone.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 15 February 2009, 00:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Now that hal uses consolekit/policykit to authenticate mounts, this is fixed in archlinux.
Comment by Jan de Groot (JGC) - Saturday, 10 November 2007, 23:16 GMT
This is not really a fixable issue. What happens is that gnome-volume-manager running under one account mounts the device with permissions for that user to read/write the device. When you're logged into the system as a different user at the same time, that user won't be able to access it. If you want to change this behaviour, kill gnome-volume-manager before you switch to the other user.
Comment by Piotr Beling (qwak) - Sunday, 11 November 2007, 01:11 GMT
The same problem is (or was) in other linux ditro:
E.g. in ubuntu (looks like they have solved it): https://bugs.launchpad.net/ubuntu/+source/gnome-volume-manager/+bug/10581

This bug and some discution in gnome bugs raporting system: http://bugzilla.gnome.org/show_bug.cgi?id=324159
Comment by Piotr Beling (qwak) - Sunday, 11 November 2007, 01:29 GMT
I thing that problem can be solved by changing /system/storage/default_options/vfat/mount_options my gconf.
So /usr/share/gconf/schemas/gnome-mount.schemas could by patched.
Comment by Piotr Beling (qwak) - Sunday, 11 November 2007, 02:10 GMT
Group change method is here (at the bottom):
http://forums.archlinux.fr/topic1047.html
Comment by Roman Kyrylych (Romashka) - Friday, 11 January 2008, 11:45 GMT
Jan, decission on this?
Comment by Piotr Beling (qwak) - Friday, 11 January 2008, 12:54 GMT
Mayby ConsoleKit is the best solution:
http://www.freedesktop.org/wiki/Software/ConsoleKit
Comment by Greg (dolby) - Saturday, 17 May 2008, 17:18 GMT
This is marked as fixed upstream. Is it solved in Archlinux too?
Comment by Jan de Groot (JGC) - Tuesday, 22 July 2008, 20:33 GMT
No it's not, we have to implement consolekit/policykit in our distribution to get this bug fixed. In the meanwhile, gnome-volume-manager doesn't handle mounting anymore, but leaves it over to nautilus.

Loading...