virtualx.eclass: Fix no display for an emerge following a failure
authorChris Mayo <aklhfex@gmail.com>
Fri, 26 Jul 2019 18:48:13 +0000 (19:48 +0100)
committerMatt Turner <mattst88@gentoo.org>
Tue, 30 Jul 2019 01:49:41 +0000 (18:49 -0700)
commit6f680e4fe73925ae130343e02adb416cb799ce7d
tree3ae2edc43e9213c935c02915c7fe3e4c6f230810
parent39a053a99e04391563810fe953112d2249317681
virtualx.eclass: Fix no display for an emerge following a failure

If using GNOME GDM, X is started on DISPLAY :0 but a lock file
/tmp/.X1024-lock is created instead of /tmp/.X0-lock.
virtx() will initially set XDISPLAY to 0 and attempt to start Xvfb on
DISPLAY :0 which fails but DISPLAY :1 (and greater) is not attempted if
a previous emerge left /tmp/.X1-lock behind.

Closes: https://bugs.gentoo.org/690778
Signed-off-by: Chris Mayo <aklhfex@gmail.com>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
eclass/virtualx.eclass