[comp.sys.hp] Xserver causing problems on hp9000s300

njw@doc.ic.ac.uk (Nick Williams) (01/22/91)

The problem I have is with windows not being refreshed properly, and
other weirdness of a similar type, most often with windows belonging
to either Motif or Andrew...

* Windows will not be refreshed after they have been
overlapped by another window and then exposed.

* When a window is exposed, the rectangle that should be redrawn is
filled with a random colored garbage. This is most noticeable with
Motif text widgets.

* TWM title bars occasionally "lose" their decoration (resize button,
etc). Most often happens with applications that change their title
during run.

* TWM cursors get left behind in motif windows --- when you opaque
move a window (a TWM function which moves the window itself as opposed
to an outline of the window), several images of the current cursor are
left on the window, and never cleaned up. This happens mostly on motif
windows. Has been exhibited once or twice on other, random windows.

* The keys' auto-repeat is turned off on startup every now and again.

* The "middle" mouse button (on 2 button mouse) has its threshold time
(the difference between the times each button goes down to be
considered the middle button) decreased to some time which is
impossible to achieve.

All of the above problems are occasional in nature.


My setup:

hp9000s300 (350)

hpux 7.0

X11 --- complete R4 build from scratch, with the server taken from
that ftp site that was advertised a while ago:
@(#)X Window System, Version 11    HP-UX 7.03   A.03.02   $Revision: 9.30.1.1 $

Motif - as distributed with hpux7.0 (i.e. R3 linked. Argh).
Andrew - running remotely, with local fonts.


Any clues on what I can do to get this fixed?
I don't believe it is the applications' fault, since it happens with
such a range of applications, and running an application remotely
causes the observed effects only when displaying on the HP.


I can also reproducibly get the server to core dump. But for now,
that's another story :-)

--
Nick Williams.                        "It's all gone... *Horribly* wrong."
njw@doc.ic.ac.uk   ... Dept of Computing, Imperial College, London SW7 2B7.  UK
njw@athena.mit.edu ... Project Athena, M.I.T., Cambridge, MA 02139. USA

Disclaimer: Any opinions or views you may find hiding in this message are 
mine: noone else wants them.

harry@hpcvlx.cv.hp.com (Harry Phinney) (01/24/91)

Nick Williams writes:

> * Windows will not be refreshed after they have been
> overlapped by another window and then exposed.

> * When a window is exposed, the rectangle that should be redrawn is
> filled with a random colored garbage. This is most noticeable with
> Motif text widgets.

This is purely a guess.  Try turning off TWM's use of backingStore and
SaveUnders and see if that improves or changes the behavior.

> * TWM title bars occasionally "lose" their decoration (resize button,
> etc). Most often happens with applications that change their title
> during run.

Don't have any good idea of what's happening here.  The one guy here who
uses twm hasn't seen this problem.

> * TWM cursors get left behind in motif windows --- when you opaque
> move a window (a TWM function which moves the window itself as opposed
> to an outline of the window), several images of the current cursor are
> left on the window, and never cleaned up. This happens mostly on motif
> windows. Has been exhibited once or twice on other, random windows.

This certainly sounds like a reasonably straightforward server bug.
What display system is in your 350?  The most helpful would be the
number from the graphics card plugged into the SPU box (e.g.  98550A).

> * The keys' auto-repeat is turned off on startup every now and again.

The only time I've seen this is when the HIL loop has been disturbed
while the server is running.  Plugging and/or unplugging the keyboard,
mouse, or other input devices while the server is running will
definitely turn off auto-repeat.  It can be turned back on with xset.

> * The "middle" mouse button (on 2 button mouse) has its threshold time
> (the difference between the times each button goes down to be
> considered the middle button) decreased to some time which is
> impossible to achieve.

I've never seen this happen.  If you could somehow better pin-down the
conditions under which it happens we'd be glad to chase this.

> I can also reproducibly get the server to core dump.

Could you tell us how to reproduce it?

Harry Phinney   harry@hp-pcd.cv.hp.com