[SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

ewaller · 2012-10-15 03:33:32

I have to admit I am stymied here. I have been in the wiki and forums most of the day and am just not finding the solution here.

I have both udisks and udisks2 installed
I am running a pure systemd
I do not use a login manager
I use startx that has a switch clause based on an environmental variable to pick the environment I want.
For now, let's limit this to xfce4 and openbox.

I used to be able to log in and mount usb and SD volumes using Thunar, Dolphin, and palimpsest. I can no longer do that; I receive an error indicating I've not the proper privileges.

Even more fun, I log into a console and use udiskie, and can mount volumes without issue.
I start X with startx, launch a terminal program, and udiskie will no longer allow me to mount. I can read volumes mounted by udiskie before I started X.

I have tried various combinations of ck-launch-session, dbus-launch in concert with openbox-session and startxfce4. Nothing allows me to automount as a normal user. This used to work, but something has gone south, but I am not clear when.

Anyone have suggestions for a stable solution here?

A couple files as they exist right now:

ewaller@odin:~ 1005 %cat .xinitrc

#xset b off
setxkbmap -option ctrl:nocaps

case $WM in
openbox)
	exec ck-launch-session openbox-session
	;;
e17)
    dbus-launch
    enlightenment_start
    ;;
vb)
    VirtualBox -startvm "Windows XP" -fullscreen
    ;;
xfce4)
    exec ck-launch-session startxfce4
	;;
*)
	exec ck-launch-session startxfce4
	;;
esac
ewaller@odin:~ 1006 %cat /etc/polkit-1/localauthority/50-local.d/10-udisks.pkla
[Local Users udisk2]
Identity=unix-group:users
Action=org.freedesktop.udisks2.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes
[Local Users udisk]
Identity=unix-group:users
Action=org.freedesktop.udisks.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes
ewaller@odin:~ 1007 %
ewaller@odin:~[1] 1007 %

Last edited by ewaller (2012-10-16 03:28:49)

illusionist · 2012-10-15 03:57:17

what your

/usr/share/polkit-1/actions/org.freedesktop.udisks.policy

says.

ewaller · 2012-10-15 04:25:43

*/usr/share/polkit-1/actions/org.freedesktop.udisks.policy = https://gist.github.com/3890811

Well, that is an interesting file. A cursory look through it would indicate it blocks what I am trying to do. Does not my /etc/polkit-1/localauthority/50-local.d/10-udisks.pkla override those settings?

Edit: It has been a long week and a tough weekend -- I am going to hit the bed to try to get a solid 8 hours of sleep before the week starts. I'll pick this up in the morning,,, Thanks

Last edited by ewaller (2012-10-15 04:34:07)

illusionist · 2012-10-15 04:33:14

ewaller wrote:

Does not my /etc/polkit-1/localauthority/50-local.d/10-udisks.pkla override those settings?

I never touched that file, but here are my udisks and udisks2 files for your reference :
udisks2
udisks

ewaller · 2012-10-15 04:34:44

Edit. Thanks, I'll comb through those and get back tomorrow.

ZekeSulastin · 2012-10-15 04:35:56

Are you starting X onto the same vt you logged into i.e. startx -- vt1 for tty1 or startx -- vt$(fgconsole) (or falconindy's xserverrc) for a more general case? If you don't, systemd-logind cannot keep track of the session and the -kit permissions will thus break.

You can see sessions using loginctl:

 └$ loginctl
   SESSION        UID USER             SEAT            
         1       1000 zekesulastin     seat0           
         4       1000 zekesulastin     seat0           

2 sessions listed.

You can see information about your sessions using loginctl show-session $num - the session must be Active:

 └$ loginctl show-session 4
Id=4
Timestamp=Sun, 14 Oct 2012 23:18:56 -0400
TimestampMonotonic=49646619798
DefaultControlGroup=name=systemd:/user/zekesulastin/4
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=12771
Audit=4
Type=tty
Class=user
Active=yes  <-- This must be "yes"
State=active
KillProcesses=no
IdleHint=yes
IdleSinceHint=1350271136064237
IdleSinceHintMonotonic=49646611251
Name=zekesulastin

(I personally have a conditional in bash_profile to exec startx -- vt1 if I log in on tty1.)

Last edited by ZekeSulastin (2012-10-15 04:37:59)

R00KIE · 2012-10-15 09:25:29

I also start xfce with 'startx -- vt1', and my .xinitrc only has 'exec startxfce4' since xfce seems to start everything it needs to get the permissions to mount devices.

cirrus · 2012-10-15 23:42:20

same prob here solved with spacefm filemanager it mounts my usb disks as user pcmanfm gave me perm error. i use the automount usb script from wiki ,i start x via getty and autologin service. give spacefm a try works for me.

ewaller · 2012-10-16 03:27:29

ZekeSulastin wrote:

Are you starting X onto the same vt you logged into i.e. startx -- vt1 for tty1 or startx -- vt$(fgconsole)

There's the magic Thanks.

A few things I need to work through, though. For instance, I like having the console on which I logged in on one VT, and the X on a different VT. That way, I can see messages that get sent to the console, I can pause or background the entire X session; or even kill it outright from the log in console. I'll have to figure how to work that soon.

Rookie: I found that if I don't remove ck-session from my .xinitrc, bad things (TM) happen; I think console kit and systemd-login fight each other -- badly.

illusionist: I tried your suggestions, and they too seem to work. Purely personal taste, but I am going to use the -- vt1 switch instead. Thanks.

Thanks to all. I need to polish this a little bit, and I'll go back and see if I missed something subtle in the wiki. Maybe it will give me an excuse to update the wiki.

-- ewaller

ngoonee · 2012-10-16 03:59:22

ewaller wrote:

Thanks to all. I need to polish this a little bit, and I'll go back and see if I missed something subtle in the wiki. Maybe it will give me an excuse to update the wiki.
-- ewaller

Please do, I'm planning on making the switch (ck to systemd-login) in the mid-term future =p

headkase · 2012-10-16 04:02:49

ewaller wrote:

... For instance, I like having the console on which I logged in on one VT, and the X on a different VT. That way, I can see messages that get sent to the console, I can pause or background the entire X session; or even kill it outright from the log in console. I'll have to figure how to work that soon...

Perhaps this will help or can be adapted:

http://blog.falconindy.com/articles/bac … stemd.html

?

WonderWoofy · 2012-10-16 04:09:37

You know, I just snagged the polkit from tom gunderson, which is 107-1 and is patched to detect whether logind or ck is in use. I was then able to rid myself of consolekit. Though, I have to mention that I do not use a login manager, as those would pull in ck as a dep. I did however build xdm without the ck dep, but I don't really actually use it.

Edit: Since the goal is essentially to get rid of ck, I would assume that the testing polkit would provide the same as what i have done.

Last edited by WonderWoofy (2012-10-16 04:10:21)

headkase · 2012-10-16 04:16:18

The console-kit thread starts here:

http://mailman.archlinux.org/pipermail/ … 23763.html

Basically, I believe console kit will soon go the way of the dodo and packages that depend on it, like SLiM I'm using, will be rebuilt and the transition will be relatively painless for most users..

WonderWoofy · 2012-10-16 04:31:43

Yes it will, but I have had this on my system for a bit now (polkit 107-2 has been in testing for about a month now). I just felt like ck was a bit silly, and I wanted to try the logind, since it seemed much simpler to use something that was already inherently within my system.

headkase · 2012-10-16 04:47:07

I also would like to use logind. It is a service that you can't disable with systemd - unless I'm totally missing something - and it is redundant with console kit. Removing console kit, leaving only logind, will cut down on cruft. And as new installations are now systemd by default then it's time for console kit to go..

WonderWoofy · 2012-10-16 05:21:46

That is what I was thinking.

utops · 2012-10-16 15:14:14

Im geting this issue as well so i remove "--with-ck-launch" from .xinitrc and now i can mount,unmount etc,but power managment stoped to work - power managment options are greyed out. But i don't care that much, i turn off my computer clean via power button on rig case and reboot via x-term.
But i must admit i was used to do it usual way by xfce sesion power manager,so im waitng for clear solution how to make console-kit not so fascist.

WonderWoofy · 2012-10-16 15:18:42

@utops... soon, you will be shown the way....

But seriously, polkit 107-2 is in testing, and it is compiled w/o consolekit support, and just logind suppport. It has been in testing for a month now because I think the devs are trying to iron out some of the other deps that consolekit was a part of. So once they get everything straightened out, presumably, we will all have consolekit free setups! Yay!

czubek · 2012-10-17 00:55:01

With the advent of systemd I have removed slim, consolekit and syslog-ng.
Having discovered spacefm and udevil I have removed udisks, udisks2, pcmanfm, gvfs and gvfs-smb.

A little more effort to access network shares, but doable.

Polkit will have to wait.

Edit: Spacefm is pretty neat.

Last edited by czubek (2012-10-17 00:57:40)

Arch Linux

#1 2012-10-15 03:33:32

[SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#2 2012-10-15 03:57:17

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#3 2012-10-15 04:25:43

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#4 2012-10-15 04:33:14

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#5 2012-10-15 04:34:44

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#6 2012-10-15 04:35:56

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#7 2012-10-15 09:25:29

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#8 2012-10-15 23:42:20

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#9 2012-10-16 03:27:29

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#10 2012-10-16 03:59:22

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#11 2012-10-16 04:02:49

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#12 2012-10-16 04:09:37

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#13 2012-10-16 04:16:18

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#14 2012-10-16 04:31:43

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#15 2012-10-16 04:47:07

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#16 2012-10-16 05:21:46

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#17 2012-10-16 15:14:14

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#18 2012-10-16 15:18:42

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

#19 2012-10-17 00:55:01

Re: [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

Board footer