11.3 in use with KDE. When I plug in an USB stick or my HTC phone into the USB connector the device is recognised but can’t be opened in dolphin. This is the error message:
# fdisk -l
Disk /dev/sdi: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdi1 1 1937 15554048 c W95 FAT32 (LBA)
If it’s been used in windows, use it there again and make sure you safely remove it
No, it has never ever been used in windows (I do not have windows on any of my computers).
Well, I made another test, and plugged it into another desktop running 11.2. I got the usual pop up window, asking what I want to do. I clicked on “open with dolphin” and got another small pop up window saying that this needs root privileges and asks for the password. After that it mounts and opens the device and shows the contents.
On 2010-11-02 13:36, vodoo wrote:
>
> 11.3 in use with KDE. When I plug in an USB stick or my HTC phone into
> the USB connector the device is recognised but can’t be opened in
> dolphin. This is the error message:
>
>
> Code:
> --------------------
> org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
> org.freedesktop.hal.storage.mount-removable
> auth_admin_keep_always ← (action, result)
> --------------------
>
>
Try this:
11.2
Code:
cer@Telcontar:~> polkit-action --action
org.freedesktop.hal.storage.mount-removable
action_id: org.freedesktop.hal.storage.mount-removable
description: Mount file systems from removable drives.
message: System policy prevents mounting removable media
default_any: auth_admin_keep_always (factory default: no)
default_inactive: auth_admin_keep_always (factory default: no)
default_active: yes
11.3
Code:
cer@Elanor:~> polkit-action --action
org.freedesktop.hal.storage.mount-removable
action_id: org.freedesktop.hal.storage.mount-removable
description: Mount file systems from removable drives.
message: System policy prevents mounting removable media
default_any: no
default_inactive: no
default_active: yes
This is unknown territory to me, but I think you have to change something
there in your system to have access. Either that or dolphin is clueless.
I wonder if there is a polkit for dummies howto somewhere… :-?
I googled polkit and found just six entries, no docu. :-/
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
cer@Elanor:~> polkit-action --action org.freedesktop.hal.storage.mount-removable
action_id: org.freedesktop.hal.storage.mount-removable
description: Mount file systems from removable drives.
message: System policy prevents mounting removable media
default_any: no
default_inactive: no
default_active: yes
and I get (on 11.3):
vodoo@host:~> polkit-action --action org.freedesktop.hal.storage.mount-removable
action_id: org.freedesktop.hal.storage.mount-removable
description: Mount file systems from removable drives.
message: System policy prevents mounting removable media
default_any: auth_admin_keep_always (factory default: no)
default_inactive: auth_admin_keep_always (factory default: no)
default_active: yes
Slight differences, but I do not understand their significance. On my 11.2 system I get exactly the same as on 11.3. However, on 11.2 dolphin (I think it is dolphin) opens a window and asks for the root password; then it works. 11.3 opens dolphin right away and then fails with the error message.
> and I get (on 11.3):
>
>
> Code:
> --------------------
> vodoo@host:~> polkit-action --action org.freedesktop.hal.storage.mount-removable
> action_id: org.freedesktop.hal.storage.mount-removable
> description: Mount file systems from removable drives.
> message: System policy prevents mounting removable media
I think this has to be changed, but no idea how. However, I can mount
devices (gnome), so there must be something else somewhere.
I’d be inclined to check the security settings in YaST:
YaST > Security and Users > Local Security
In particular, the ‘Security Overview’ settings include ‘Use secure file permissions’. For reference, mine is set to ‘Easy’, but your’s may be different (ie ‘Secure’, or ‘Paranoid’)
There is also ‘Predefined Security Configurations’ which can be adjusted according to your system use - eg ‘Home Workstation’ vs ‘Network Server’
On 2010-11-06 09:06, deano ferrari wrote:
>
> I’d be inclined to check the security settings in YaST:
>
> YaST > Security and Users > Local Security
>
> In particular, the ‘Security Overview’ settings include ‘Use secure
> file permissions’. For reference, mine is set to ‘Easy’, but your’s may
> be different (ie ‘Secure’, or ‘Paranoid’)
I concur.
Your message rang a bell, so I looked in my archive and found a post from
someone having the same problem (with hibernation refused) and that was the
cause.
And I think I saw somewhere a post about a similar (easy, secure) setting
for polkit somewhere :-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I have had the same issues with an external usb-drive (encrypted). Hal would not mount with the same error message. So not even the possibility to put the password to mount it. I have file permissons to secure. You may solve this by opening a file manager in superuser rights, click on properties of the specific drive. Give read and write access to “others” for that drive. Then it works normally. Still this may not be very secure…? Owner of course stays root. To see the differences from before you have to log out and in again.
Carlos may now “shake head” if this is bad practice. As a workaround it functions.
On 2010-11-06 19:06, stakanov wrote:
>
> I have had the same issues with an external usb-drive (encrypted). Hal
> would not mount with the same error message. So not even the possibility
> to put the password to mount it. I have file permissons to secure.
Time go it was easy to understand permissions in linux, and what the suse
setting “secure” meant. Nowdays, with polkit involved, not, I don’t know.
> You
> may solve this by opening a file manager in superuser rights, click on
> properties of the specific drive. Give read and write access to “others”
> for that drive. Then it works normally. Still this may not be very
> secure…? Owner of course stays root. To see the differences from
> before you have to log out and in again.
> Carlos may now “shake head” if this is bad practice. As a workaround it
> functions.
Not really… I mount my encrypted media via root script. However, as I use
linux filesystems, even if mounted by root it can belong to a user. Just
adjust the permissions, they are stored on the disk.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Not really… I mount my encrypted media via root script. However, as I use linux filesystems, even if mounted by root it can belong to a user. Just adjust the permissions, they are stored on the disk.
In my case the memory sticks (and the memory chip in the phone) have a vfat file system. Can they store permissions too?
In any case, I had the file permissions in Yast set to “easy”, added the user to group “disk” but this did not help.
You name it. And I think that generally they are, or we would have tons of posts here in this forum.
Well. I did try what stakanov suggested in post #12. I inserted a vfat formatted memory stick, then started dolphin with kdesu and gave rw perms to others. The memstick is mounted as user root group root. I tried to change this too, but got an error mesage, saying I have no permission to do this (as user root).
Anyway, when I remove the stick and insert it again the permission change is gone. It is not permanent. The relevant line in /etc/mount just after automount looks like:
/dev/sdi1 on /media/USBSTICK type vfat (rw,nosuid,nodev,uid=0,utf8,shortname=mixed,flush)
So what I am probably looking for is some configuration snippet to make the automounter mount any external storage device readable and writeable for the group users or mount it for the user who has started the gui desktop.
Still does not automount at all here. I tried it with the 11.3 KDE Live CD and it (auto)mounts as user=linux uid=999 group=root. The uid is the only difference in mtab I can see. So far my conclusions are:
Nothing wrong with the hardware (mounts with Live CD)
Nothing wrong with the USB stick (mounts with Live CD)
Something is wrong with my configuration.
I have searched all options within the Yast security settings over and over. It is on “easy”. The only non-standard thing I did was to have global security settings at secure initially and then changed them back to easy. Probably some configuration was not changed back accordingly, but what is it?