Policy Kit's defaults prevent users from mounting internal storage

[sojourner]

intrepid , all alphas to date , I cannot mount the other internal linux drives in my box as "user" the drives appear in places>computer and the nautilus side panel but will not mount by clicking on them as user , I can mount them as root and they are then accessible as user for the remainder of the session . I had originaly included this with my comments on bug # 251991 and this is now marked as "fixed upstream" however the referenced fix only addresses mounted drives showing up twice and not the cannot mount as user . external devices or cd/dvd's automount on hotplugging or insertion of a disk .this bug is similar to bug#159190 which I reported in hardy and was fixed there by an update but it has now recured in intrepid .

[sojourner (itsmealso2)]

note! the "mounted drives show up twice " (bug#251991) has been fixed and this bug is still there , I still cannot mount the other drives/partitions on my system as user .

[Cameron Gorrie (sastraxi)]

I too am affected by this bug, on intrepid. My internal windows (NTFS) partition does not come up, nor does a vfat or an NTFS partition on a USB hard drive. Finally, my USB stick and SD card do not mount, either. The only partition that gives a visible error is the NTFS partition on the USB hard drive.

[sojourner (itsmealso2)]

I just did a fresh install of alpha 4 from the live cd , while running from the live cd I could mount the other drives/partitions as user after installation and booting into the installed system I cannot mount them . I have added ALL groups to my user account and still no go .

[sojourner (itsmealso2)]

on a tip in the forum ( ibex dev ) I went to system>administration>authorizations and under storage> mount file systems from internal drives and changed anyone to yes and console to yes and can now mount them as user . I never had to do this before .

[nullack (nullack)]

Moved to invalid due to resolution with allowing security permissions for the task

[sojourner (itsmealso2)]

I do not believe that my resolution renders the bug invalid , in previous versions of ubuntu it has not been necessary to alter the permissions to mount drives as user , this is new behavior introduced with intrepid and if intended should be accompanied by a dialog box saying you do not have permission to mount this drive or something to that effect .

[plun (plun)]

Discussed within these 2 bugs

http://bugzilla.gnome.org/show_bug.cgi?id=520736

http://bugzilla.gnome.org/show_bug.cgi?id=536292

It MUST be better to automagic mount.....for a corporate environment this is up to the admin
to maybe adjust !

[Mackenzie Morgan (maco.m)]

Setting this bug to policykit because it regards PolicyKit's defaults.

[Bremm (bremm)]

If your message is:

org.freedesktop.hal.storage.mount-removable no <-- (action, result)

As workaround you can do:

$ sudo mousepad /etc/PolicyKit/PolicyKit.conf

And add these following lines:

    <match action="org.freedesktop.hal.storage.mount-removable">
       <return result="yes" />
    </match>

Then as result you probably will have this:

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="admin"/>

    <match action="org.freedesktop.hal.storage.mount-removable">
       <return result="yes" />
    </match>
</config>

After, restart "hal" service and everything will be fine.

$ sudo service hal restart

Credits to:

http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=5491879

http://cblfs.cross-lfs.org/index.php/PolicyKit

[Bremm (bremm)]

But eject via context menu stills unavailable...

"org.freedesktop.hal.storage.eject" no <-- (privilege, result)

[James Westby (james-w)]

Hi,

Could you please attach the output of "ck-list-sessions" to the bug?

Thanks,

James

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!