You are not logged in.
Pages: 1
Topic closed
I have updated my system by following command :
$ sudo pacman -Syyu
After updating, when I open a Drive it gets me :
Failed to mount "Drive Name".
Not authorized to perform operation.
I saw many threads about this problem my problem does not solved!!
Last edited by kamrava (2014-03-04 19:09:56)
Offline
What groups are you in?
Offline
What groups are you in?
How could I find it?
I think `%wheel`
Offline
you have installed polkit/lxpolkit?
Offline
Open a terminal and type "groups"...
Jin, Jîyan, Azadî
Offline
I got it to work using this rule:
Allow mounting a filesystem on a system device for any user
However, in this thread it did not work, at least not with automounting. Perhaps some of the other solutions mentioned work.
Last edited by Steef435 (2014-03-03 22:23:43)
Offline
Udiskie is what I use. Add it to your start up script for your WM and off you go.
Offline
I can confirm what woomia recommends. Also for me the Thunar/gvfs/thunar-volman combination does not work. See this bug report:
https://bugs.archlinux.org/task/38933#comment119964
Instead I am now using udiskie with udisks2 flag as well.
udiskie -2 -s &
Last edited by orschiro (2014-03-04 06:06:02)
Offline
you have installed polkit/lxpolkit?
It was the trick.. It works thank you.
But when I try to open Drive for first time, it aks me about root password. How do I prevent this treatment?
Offline
Have you tried this polkit rule I linked to earlier? Allow mounting a filesystem on a system device for any user
You could make a rule for your user or group only.
Offline
Have you tried this polkit rule I linked to earlier? Allow mounting a filesystem on a system device for any user
You could make a rule for your user or group only.
Solved. Thank you
Offline
So, just to confirm. Creating the polkit rule does enable even automounting for you?
This is not working for me, even with the udev rule: https://bugs.archlinux.org/task/38933#comment119964
Offline
maybe you are using udisks 2. edits made to "/usr/share/polkit-1/actions/org.freedesktop.udisks.policy" may no longer apply to every disk, especially when its flagged as "*-internal" (i dont know how udisks separates these, but i guess that all non-usb devices are "internal").
so take a look for "org.freedesktop.udisks2.policy" instead.
also check
loginctl show-session $XDG_SESSION_ID|grep Active
. If you are "active" set
<allow_active>yes</allow_active>
in
org.freedesktop.udisks2.filesystem-mount (default) and
org.freedesktop.udisks2.filesystem-mount-system
otherwise try to get active or edit <allow_any> or <allow_inactive>
works fine for me; this harrasses me, because i didn't notice udisks2 to became active.
Offline
Please don't necrobumpm, particularly solved threads: https://wiki.archlinux.org/index.php/Fo … Bumping.27
Closing
Offline
Pages: 1
Topic closed