Blame SOURCES/0002-startx-Fix-startx-picking-an-already-used-display-nu.patch

b9ec32
From 848dc9b7f3a95f14efd4ea34188cba51965c9f53 Mon Sep 17 00:00:00 2001
b9ec32
From: Hans de Goede <hdegoede@redhat.com>
b9ec32
Date: Fri, 20 Mar 2015 14:25:44 +0100
b9ec32
Subject: [PATCH xinit 2/3] startx: Fix startx picking an already used display
b9ec32
 number when -nolock is used
b9ec32
b9ec32
Currently startx relies on /tmp/.X?-lock being present for automatically
b9ec32
picking a free display number. This does not work if -nolock is used when
b9ec32
starting the server, or if the server is started with -displayfd as -displayfd
b9ec32
implies -nolock.
b9ec32
b9ec32
This is becoming a problem now that -displayfd is getting used by
b9ec32
display-managers (e.g. gdm), this fixes this by also checking for
b9ec32
/tmp/.X11-unix/X?
b9ec32
b9ec32
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
b9ec32
---
b9ec32
 startx.cpp | 2 +-
b9ec32
 1 file changed, 1 insertion(+), 1 deletion(-)
b9ec32
b9ec32
diff --git a/startx.cpp b/startx.cpp
b9ec32
index 8520399..fe49996 100644
b9ec32
--- a/startx.cpp
b9ec32
+++ b/startx.cpp
b9ec32
@@ -120,7 +120,7 @@ enable_xauth=1
b9ec32
 XCOMM Automatically determine an unused $DISPLAY
b9ec32
 d=0
b9ec32
 while true ; do
b9ec32
-    [ -e /tmp/.X$d-lock ] || break
b9ec32
+    [ -e "/tmp/.X$d-lock" -o -S "/tmp/.X11-unix/X$d" ] || break
b9ec32
     d=$(($d + 1))
b9ec32
 done
b9ec32
 defaultdisplay=":$d"
b9ec32
-- 
b9ec32
2.3.3
b9ec32