[gdm-list] handled=false xservers broken in 2.20.0 vs. 2.18.1



Hello,
We've been using gdm 2.18.1 for a while now, and we just tried 2.20.0
in ubuntu 7.10 and our setup breaks horribly.   I went through the
changelog between 2.18 and 2.20, but it looks like A LOT has changed.
If someone could give any ideas on which of the changes may be causing
this problem that would be very helpful instead of trying lots of gdm
version in between 2.18 and 2.20.  Maybe we need different parameters
in the gdm.conf now?

Basically, if you add handled=false to an x server in 2.20, gdm tries
to start it but it does not leave it up, and eventually you get the
"screen has shut down 6 times in 90 seconds" message.  Taking the
exact same setup and installing gdm 2.18, the handled=false xserver is
started and left up as desired.

With 2.20 you can see the x server running briefly with ps, and
/var/log/gdm/* and /var/log/Xorg* look normal, it just seems that gdm
is "reaping" the xserver for some reason?

example:
[server-Standard]
name=Standard server
command=/usr/bin/X -br -audit 0
flexible=false
handled=false

You're probably wondering why are we trying to start an unhandled x
server?  We run one unhandled x server across many displays, and then
run xephyr on each display for multi-user capability.  While that does
introduce many other variables that could cause problems, the simplest
case of handled=false doesn't work with gdm 2.20.0.

Any suggestions would be appreciated.

Thank You,
Michael Pardee
Open Sense Solutions LLC
http://open-sense.com
888-323-1742


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]