Public bug reported:

Binary package hint: gnome-mount

Binary package hint: gnome-mount

Related feature : MountAllLocalFilesystems

Description of the behavior :
Mounting local volume not present in fstab is denied by hal for non-root users. 
To be able to mount them by admin users, the MountAllLocalFilesystems 
specification implement a way to relaunch the gnome-mount command with gksu 
when the first attempt were denied.
In the first attempt, the settings are set by looking at the gconf tree  of the 
users. But in the second attempt (with gksu), the settings are set by looking 
at the gconf tree of root.

Problems:
There is different problems related to this behavior :
- vfat volume are mount by default with the options : 
"shortname=winnt,uid=,utf8,umask=077". When mounting with gksu, uid is set to 
uid=0 and this make the volume unreadable by user since umask=077.
- All users defined settings (the ones you can set in the volume tab of 
property ) are lost since gnome-mount will not look at the gconf tree 
/system/storage/drives/UDI_OF_DRIVE/ of the user, but at the one of root.

A solution :
I present here a way to deals with this problem, but there is probably others 
better.
When relaunching gnome-mount with gksu, we should keep the settings of the 
first attempt (the one of the user). This make sense since in definitive, it's 
the user who mount the volume, so the settings should be the user ones.
I will attach here a patch i use to make this happens.

Thanks.

** Affects: gnome-mount (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

-- 
[MountAllLocalFilesystems] gnome-mount should keep the same settings (options, 
fstype, mount-point) as previous attempt when retrying with gksu
https://launchpad.net/bugs/78314

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to