Lil' help with systemd user session units

Question

I'm using systemd 207. i would like to change my desktop-session on the fly. in this suituation form razor to openbox. these are my configs located in ~/.config/systemd/user/
razor.config
[Unit]
Description=Razor Qt Desktop
Before=mystuff.target
After=xorg.target
After=environment.target
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/startrazor
#Restart=on-failure
Environment=DISPLAY=:0
KillMode=process
[Install]
WantedBy=de.target
de.target
[Unit]
Description=Desktop Enviroments
Wants=xorg.target
Wants=mystuff.target
Requires=dbus.socket
AllowIsolate=true
[Install]
Alias=default.target
openbox.service
[Unit]
Description=The Openbox Window Manager
After=xorg.target
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/openbox
Restart=on-failure
[Install]
WantedBy=openbox.target
openbox.target
[Unit]
Description=Openbox
Wants=xorg.target
Wants=mystuff.target
Requires=dbus.socket
AllowIsolate=true
mystuff.target
[Unit]
Description=Xinitrc Stuff
After=environment.target
Wants=razor.target
Wants=environment.target
[Install]
Alias=default.target
now...
systemctl --user isolate razor.target
...doesen't close razor-qt desktop to make place for a new wm session
what shall we do whith the system units....
what shall we do whith the system units....
what shall we do whith the system units....
early in the morning
Last edited by kriz (2013-09-25 12:25:43)

Answer 1

I have this problem too.  I had not seen this thread you linked to above before... but in my one reboot test (which shoud be taken with a bucket of salt since my machine sometimes shuts down okay) it worked great.  It would seem that 65kid's workaround is effective.  I'm going to reboot again to see if this is consistent. I'll udpate if it hangs.
Edit: So it didn't hang, but it looked like it was going to.  Often the session will seem to start to exit, but the root window will remain (the background).  It did just this, and then after a second, continued to the printing of the shutdown messages.  Success!
Edit2: I guess I should note the actual fix so that others don't have to follow that link.  As putting the workaround in more than one place is probably optimal.  So you need to add "TimeoutStopSec=2" to the [Service] section of the [email protected].  This can be done either by the .include function of unit files, or by the drop-in replacement functionality via /etc/systemd/system/user-session@<youruser>.d/<added-config>.conf.  I would imagine that you could play around with the value of the timeout.  Systemd's time capabilities are pretty extensive, so I imagine that you could actually configure it down to the ms here.
Last edited by WonderWoofy (2013-06-04 23:17:41)