Hi, > Are you using xdm? If yes, then that might be the corner case. AFAIK > other DMs are not setting a XDM-AUTHORIZATION-COOKIE[1], so noone sees > this problem[2].
yes, I know that only xdm users are affected. On the other hand I couldn't believe that its userbase should be so small, especially in the old days when gnome and kde weren't that shiny... I don't know since how many years I'm experiencing this bug, but it's been quite some time. > I personally tend to think it is a bug in the Xserver. if it gets a new > connection with the same data, it should first look if the previous > connection has finished. I guess it's just a race condition that it > first tries the new connect before realizing the old is gone. I haven't looked at that part of the server yet. That would be an elegant solution, although the static-variable-in-solib thing leaves a bad taste as well... I'd really appreciate some input from upstream, but the bugreport at freedesktop.org is empty since Brice created it. > [1] You can also tell xdm to not set it by adding a > DisplayManager*authName: MIT-MAGIC-COOKIE-1 > to /etc/X11/xdm/xdm-config > > Perhaps that would be an sensible default for xdm? I don't think > using those cookies gives anysecurity benefit. Hm, if we want to go that way, we could even start shipping xdm with XDM-AUTH disabled at compile-time - there's a switch for it. > [2] Only people using xdm and only when using specifiy programs. > firefox had it relatively often for some time, but that changed, too. Most SDL programs seem to be affected presently - but that may also be due to some recent change in the way SDL handles X11. Regards, Jan
signature.asc
Description: Digital signature
