Systemd as user, dual monitor, awesome, popups (long desc inside)?

Question

Okay, this is quite difficult to describe, so please bear with me.
I run systemd as user and awesomewm on a laptop which is normally plugged in to an external monitor for a dual screen. 64-bit Arch, fully updated, running [testing]
I've got my own homebrew script which basically just runs the appropriate xrandr command to enable all the current connected monitors (since AFAIK we still can't make that happen automatically at plugin/out of the VGA cable).
Additionally (may or may not be related), I run unagi for compositing and animated wallpapers using xscreensaver and xwinwrap. unagi is started as a systemd user service (as is awesome itself), as are the animated wallpapers (basically a homebrew service file calling a bash script). Also, I'm using infinality-bundle from bohoomil. None of this (I think) is important.
Now, not sure when this started happening, because I rarely do this, but if I start my laptop up with the external monitor plugged in, it mirrors the display at a fairly low res (I'm assuming 1024x768) which I don't bother about, because I just hit the keybinding for the above-mentioned script and get my full res dual monitor setup.
However, once this happens, any app which pops up, which in my case is synapse (app launcher), gmrun (launcher, run via xbindkeys) and keypassx (when requesting passwords) will always pop up on the primary screen. If launched from the primary screen, it'll turn up right in the center as expected. If launched from the second screen (on the right), it'll turn up on the primary screen, but centered in position w.r.t the second screen (different resolution) and to the right-most edge of the primary screen.
If I start the laptop without an external monitor and add it later on (plug in and then run xrandr) everything works as expected, popups are centered properly.
If I start awesome using gdm (and external monitor plugged in) it doesn't show the mirrored displays and everything works as expected.
Because of the last two statements, I doubt the awesomewm configuration is the problem, but I can't imagine how to proceed debugging this. Any suggestions?
EDIT: And as usual, immediately after worrying at this for a day and then posting this thread, I found something that 'works'. Restarting awesome in this case fixes it, and it remains fixed thereafter (till the next restart).
This raises another question though, I remember awesome would automatically restart with xrandr screen changes before, why isn't it doing so now? Or is it doing so too early perhaps?
Last edited by ngoonee (2013-06-27 07:13:29)

Answer 1

o_caino wrote:
Setting mpd as a systemd user service is very simple. This is what I did.
In ~/.config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd --no-daemon
ExecStop=/usr/bin/mpd --kill
[Install]
WantedBy=default.target
To enable
systemctl --user enable mpd
Done.
Well shit. I guess I didn't need to do all that other stuff. I only wish I'd known about this before wasting most of my day. Thank you very much, everything appears to be working flawlessly now.