After switching my Arch Linux installation over to systemd (pure systemd, no more ConsoleKit or initscripts) I am facing the same problems I had a while back when I hadn't used ck-launch-session in .xinitrc when launching a window manager. These problems are:
- Auto-mounting of USB drives or CD drives not working, and when I mount manually I need to be root, despite being in the storage group (though I have read that groups shouldn't even matter with systemd now.)
- I simply cannot access Samba shares - clicking 'Browse Networks' on the left hand side pane of Thunar yields 'Failed to open "/ on". Operation not supported.'
- Other little problems like the trash can not being around anywhere (GVFS - virtual filesystem problem?)
They're all problems I had back in ConsoleKit days when I didn't launch with ck-launch-session. What can I do? I am using Thunar as my file manager, i3 is my window manager.
For automounting, you can use a program like udevil or udiskie.
Doesn't seem like that would get to the root of the problem... Why would I need udevil or udiskie and not have needed them back before the change to systemd? There's also the Samba problem.
Last edited by kelinu (2013-01-25 23:29:12)
And how did you achieve automounting before you switched to systemd?
No udiskie or anything like that. It worked by default, provided I started my window manager with ck-launch-session.
If you run loginctl show-session $XDG_SESSION_ID, do you get Active=yes? Also you need polkit installed to have permissions.
I do get Active=yes, and yes, polkit is installed.
Managed to fix it for all the issues I had! Turns out I simply had to launch with dbus-launch. My /etc/slim.conf login_cmd line now reads as follows:
login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session
Last edited by kelinu (2013-01-29 19:48:14)