Bug 567

Alan:
Any idea what is going wrong here ?

jhobson:
I tried your suggestion with DPMS:
1. Using "xset" does not work because the Xprt server does not announce the DPMS
extension
2. Trying "Xprt -dpms ..." or "Xprt dpms ..." has no effect on the problem
3. Compiling without DPMS support ended in bug 570 ("Build with |#define
BuildDPMS NO| fails") ... ;-(

I managed to compile a Xprt binary with |#define BuildDPMS NO| - the problem
still happens...

... then I tried to turn everything OFF which may be responsible for the
problem:
-- snip --
#define BuildXIE                       NO
#define BuildDBE                       NO
#define BuildXKB                       NO
#define BuildRECORD                    NO
#define BuildDPMS                      NO
#define BuildXF86VidModeExt            NO
#define BuildXInputExt                 NO
#define BuildScreenSaverExt            NO
#define BuildXvExt                     NO
-- snip --
... but the problem did not go away.

Any ideas how we should proceed ?

Is the builtin screensaver off ("xset s 0")?

Otherwise I'd normally suggest using pstack, truss, or dbx trace to see what it's
doing when it's running away, but those are Solaris tools, and I don't know the 
Linux equivalents.

Alan Coopersmith wrote:
> Is the builtin screensaver off ("xset s 0")?

Using "xset" may not have any affect since the Xserver usually resets itself
after the last client exists (which affects Xprt, too).

... but your're right... the builtin screensaver is causing the problem.
I tried it with % Xprt -s 10000 ... # and the problem did not occur within the
last hour, trying to use % Xprt -s 1 ... # caused the problem to appear after a
minute.

Well yes - that's what xlogo is for - to keep the server from resetting while
you're testing things like this.  8-)

(And actually, for reasons I don't remember, the Solaris Xprt actually doesn't
 reset every time the last client connects.  I think it may have had something
 to do with clients trying to connect in the split second between the last client
 disconnect and the server reset, and getting their connection to the server 
 unceremoniously cut off.)

Alan Coopersmith wrote:
> Well yes - that's what xlogo is for - to keep the server from resetting while
> you're testing things like this.  8-)

Maybe that's the reason why CDE2.x has this dtprint deamon... :) ... I was
wondering what this thing is doing... :)

> (And actually, for reasons I don't remember, the Solaris Xprt actually doesn't
> reset every time the last client connects.  I think it may have had something
> to do with clients trying to connect in the split second between the last 
> client
> disconnect and the server reset, and getting their connection to the server 
> unceremoniously cut off.)

Uhm... can you open a bug and attach the patch for that, please ? That would be
a nice-to-have thing for the Xorg Xprt... :)

Created attachment 251 [details] [review]
Patch for 2004-04-26-trunk

The patch is only a workaround but I don't have a better idea how to fix this.
IMO it would be nice if the whole internal screensaver code could be #ifdef'ed
out since it is not used for Xprt... but I guess that's not possible since that
code is shared between multiple Xservers in the same build.

Patch checked-in (incl. fixed bugid number in Changelog) ...

Checking in xc/ChangeLog;
/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.13; previous revision: 1.12
done
Checking in xc/programs/Xserver/Xprint/Init.c;
/cvs/xorg/xc/programs/Xserver/Xprint/Init.c,v  <--  Init.c
new revision: 1.3; previous revision: 1.2
done
Mailing the commit message to xorg-commit@pdx.freedesktop.org...

... marking bug as FIXED.