Automount used to work yesterday and stopped to work today. No idea why. I didn't restart the computer, I only suspended to RAM. And I still didn't change anything on my configuration that used to work for the past months.
]]>1) Regarding external drives (and optical media, i.e. cd's and dvd's) I could not access them around the time I filed the bug report, but an update shortly thereafter fixed this issue. I am not sure which update it was (thunar, udev, or something else), but I later found I could access external media without any udisks.pkla file or polkit-gnome installed. So this is no longer an issue (for me).
2) Regarding partitions on the same hard drive as arch (both Linux and Windows partitions), as a normal user I could not access any of them except the arch partition until I installed polkit-gnome (or else used a udisks.pkla file). I was not even given the option to enter a password without using one of these two options. It is a problem if I can't access my drives (of any type), and am not given a prompt for a password. Fortunately that is not the case anymore.
I do not really want automount for my other partitions, but I would like to be able to access them when needed without too much of a headache. The way it is now (with polkit-gnome installed) is fine for me. If I try to access one of those partitions, I am prompted for root's password. The advantage I see is that others cannot so easily scan more private data that I have on some of those other partitions. I don't need Ft. Knox, but I don't want an open door either. My Mageia KDE OS works just like that for the Linux partitions, but automounts the Windows partitions.
I think I see what you are referring to here: https://wiki.archlinux.org/index.php/PolicyKit as an alternative to polkit-gnome or even udisks.pkla. Regarding fstab, I've used that method before in Mandriva. These appear to me as other roads to the same castle.
----
Some have stated that I have a misconfigured system. It's hard for me to see how when it's all working now (log out, restart, shutdown, suspend, hibernate, and disk access) with no user created .pkla files. I think some believe if you use slim (with Xfce), it must be a misconfigured system. I'm not so sure. Anyway, listed are (4) gnome packages that are needed for xfce, but adding a 5th gnome package becomes a workaround? Already it seems a mix-n-match.
]]>In another thread someone said I should follow this guide: https://wiki.archlinux.org/index.php/Ud … ormal_user. Now you say I should not touch pkla files.
Can someone please tell me why mounting works after I quit and restart ("startx") Xmonad (and the X server) but does not work after a reboot. I'm not using any login manager, my .xinitrc ends with:
exec ck-launch-session dbus-launch --exit-with-session xmonad
1. For those of you who can't mount EXTERNAL media (aka usb flash drives), please try to understand what the policy kit is and stop hacking every possible conf file in /etc. XFCE pkla files should have been removed long time ago because they were added when xfce didn't work well with *kit. You need 0 udev rules, 0 pkla files only thunar + gvfs + udisks + deps. On a xfce desktop you only need:
$ pacman -Qq | gr gnome
gnome-icon-theme
gnome-icon-theme-symbolic
libgnome-keyring
libsoup-gnome
plus dconf. That's it.
2. INTERNAL partitions (like /dev/sda69 on your HDD) are a different story, because accessing them might represent a security risk. It's plain stupid to enter root passwd or add your user to a wheel group every time you have to mount this partition, because it's an unnecesary priviledge escalation. Why is it you want to mount/unmount such partition 7 times a day? Usually fstab is utilized for these things. Alternatively, google "arch linux policykit" to include a 3 line file into your /etc/polkit-1, but please lock it down.
@cpcgm: Your problem is not a bug because of 1. and 2.
]]>We must wait for these changes? Are these planned in future?
]]>@wonder
How can we get default rules? Will it included into polkit package? When?
maybe i wasn't clear enough.
default rules won't be the same as the workaround used in this thread. it will be a more generic one that only allows users to use their own password if they are in wheel group. That's all
]]>@lampslave a separate policykit-desktop-privileges is again a bad idea. What is a good idea is upstream to provide sane default rules: https://bugs.freedesktop.org/show_bug.cgi?id=41008
what those do is that any user being in "wheel" group is allowed to do stuff that only root can. mounting internal partitions, do system configures like networkmanager and so on, with or without a password prompt.
]]>Looking at this briefly, I think that one of the files in /etc/pam.d/ is where behavior is changed regarding regarding authorization now for polkit.
]]>