Public bug reported: Briefly: if one has a pair of systemd .socket/.service unit files to start Xorg via socket activation, the first X11 client which triggers this socket activation gets stuck (waits forever) , although Xorg starts properly. A second X11 client will then work as expected. For more details, see these upstream bug reports:
https://bugs.freedesktop.org/show_bug.cgi?id=93072 https://github.com/systemd/systemd/issues/2765 I've tested Xorg socket activation in Ubuntu 15.10 and 16.04 beta1, as well as openSUSE Leap 42.1 and Tumbleweed. Both Ubuntu releases are affected by this bug, but both openSUSE releases are immune to it. Thus I presume this is a Debian/Ubuntu specific issue. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1554662 Title: First client to invoke Xorg via systemd socket activation gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554662/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
