First client to invoke Xorg via systemd socket activation gets stuck
Bug #1554662 reported by
Laércio de Sousa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
| xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
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:/
https:/
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.
| Changed in systemd (Ubuntu): | |
| status: | New → Won't Fix |
To post a comment you must log in.
