From 825df618b69bdb20716c2b4a6922ba21ec8116e6 Mon Sep 17 00:00:00 2001 From: Eric Hameleers Date: Wed, 2 Dec 2015 23:03:20 +0100 Subject: Fix for the looping XDM when trying to start a Mate or Cinnamon X session. Evidence in ~live/.xsession-errors: XDM authorization key matches an existing client! cinnamon-session: Cannot open display: . Rationale copied from the page where I found the fix - http://freebsd.1045724.n5.nabble.com/Re-ports-154502-x11-xdm-authorization-failure-when-used-with-E17-window-manager-td5819660.html The cause is that the implementation of XDM-AUTHORIZATION-1 is broken if applications execve or unload/reload libX11/libxcb between connections to the X server. More information can be found in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486606 Since it is unclear whether XDM-AUTHORIZATION-1 will be fixed and if so, where, I think it is best to disable it in xdm. It looks like adding --disable-xdm-auth to xdm's configure flags will do this but I have not tested it. I think the security impact is minimal; gdm does not use XDM-AUTHORIZATION-1 either. --- xdm/xdm-config | 3 +++ 1 file changed, 3 insertions(+) (limited to 'xdm') diff --git a/xdm/xdm-config b/xdm/xdm-config index 135b211..01e45dc 100644 --- a/xdm/xdm-config +++ b/xdm/xdm-config @@ -26,3 +26,6 @@ DisplayManager*loginmoveInterval: 10 ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm DisplayManager.requestPort: 0 + +! Mate and Cinnamon fail without this: +DisplayManager*authName: MIT-MAGIC-COOKIE-1 -- cgit v1.2.3