-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not mounting encrypted partition without sudo #153
Comments
Hi, did you check https://github.com/coldfix/udiskie/wiki/Permissions ? Best, Thomas |
Thanks for the quick reaction. Please bear with me while I clumsily try to edit my issue. ^^' I will check the Permissions page! |
Hi, I just added the polkit rules and added myself to the
I'm especially confused because it works properly on my desktop. Update: I just cross-checked on desktop. It asks me for a root password when udiskie tries to mount it. My laptop does not, so that's probably the direction I should be looking into. I'm a little puzzled why it would ask for my root password when we are mounting instantly after unlocking, and not when I restart |
Hi, on reading a second time more thoroughly your issue: I am encountering problems with udisks2 delaying permissions as well (dating back couple of weeks). Everything works if retrying to mount a few seconds after unlocking. It seems that udisks2 changes permissions too late, Also, if you install the Can you confirm this is the same issue? (I will have to open an issue on the udisks2 tracker, as this will be affecting many others presumably) Best, Thomas |
Installing Judging from the log:
as in the first post (which I edited, again, by the way... sorry for being such a derp! -_-;;), it does kinda look like the unlock happens after the mount attempt. I'm not sure if this is just from the way udiskie logs or that this is indeed what is happening. In that case, maybe a temporary workaround might be to just sleep a few seconds until udisks2 changes permissions, although I will immediately admit that that is not an optimal solution. On a half-related note, I noticed that Thanks for taking your time with me! |
Seems to be the same issue.
No, it's just logged after for technical reasons, but the mount attempt only happens as result of being notified by udisks that the unlocking was successfull and a new block device with a filesystem on it has appeared.
Yes, I tried that and it seems to work. I will add it as temporary hack, but this is definitely broken and unreliable.
Unless you passed the |
Alright that clears things up! Best of luck in getting the issue fixed :) |
Forwarded to udisks issue tracker: storaged-project/udisks#473. I'll keep it open for now. |
Note that the workaround will be available in 1.7.3 but I'll keep this issue open until a proper fix is available. |
decided to close it anyway since there is nothing else that can be done in udiskie. |
Just chiming in to say that the workaround worked a charm. It's not a hack if it works, right? :P |
On my laptop running Arch ( kernel 4.14.4-1-ARCH ) I can't mount my LUKS-encrypted partition on a USB drive without running udiskie as sudo. I do get prompted for the device password, but other than unlocking, udiskie does nothing. If I run with sudo, everything works as expected. Terminal output:
I am launching udiskie from my
.xinitrc
with the lineudiskie &
.On my desktop (XFCE4, launching
udiskie -t
with xfce autostart rules), I have no issues; the volume unlocks and mounts properly as expected.I'm sure I'm doing something wrong, but I can't figure out what. Posting here because this might actually be a udiskie issue?
The text was updated successfully, but these errors were encountered: