chris@softway.sw.oz.au (Chris Maltby) (09/24/90)
A while ago we installed X11R4 on our Sequent Balance from source, and on the whole, it works well. We are using Labtam i960 based mono X-terminals as servers. We have two interesting problems however: 1) xdm doesn't get the mit-magic-cookie for the terminal into the user's .xauthority file, so we can only use xdm in unsecure mode. I think I know where to start to debug this one. 2) the Xaw library "text" widget (as used by xclipboard) behaves weirdly. It fails to get the text displayed in the window when typed or pasted, but random (and I mean random) bits of it appear when the line becomes wide enough to scroll side-to-side. Things only appear when scrolling, and the result looks much better when the scrolling is very slow. This bug is extremely annoying, as is affects lots of clients that use the text widget. I have no idea where to look for the bug. Has anyone else run into this behaviour before? Can anyone suggest a strategy for debugging number 2? Thanks for your help in advance. Chris -- Chris Maltby - Softway Pty Ltd (chris@softway.sw.oz.au) PHONE: +61-2-698-2322 UUCP: uunet!softway.sw.oz.au!chris FAX: +61-2-699-9174 INTERNET: chris@softway.sw.oz.au
numb@cs.qmw.ac.uk (Matthew Humble Worm Newman) (09/25/90)
In <3628@softway.sw.oz.au> chris@softway.sw.oz.au (Chris Maltby) writes: >A while ago we installed X11R4 on our Sequent Balance from source, and >on the whole, it works well. We are using Labtam i960 based mono >X-terminals as servers. >We have two interesting problems however: >1) xdm doesn't get the mit-magic-cookie for the terminal > into the user's .xauthority file, so we can only use > xdm in unsecure mode. I think I know where to start > to debug this one. >2) the Xaw library "text" widget (as used by xclipboard) > behaves weirdly. It fails to get the text displayed in the > window when typed or pasted, but random (and I mean random) > bits of it appear when the line becomes wide enough to scroll > side-to-side. Things only appear when scrolling, and the result > looks much better when the scrolling is very slow. > This bug is extremely annoying, as is affects lots of clients > that use the text widget. I have no idea where to look for > the bug. >Has anyone else run into this behaviour before? Can anyone suggest >a strategy for debugging number 2? Thanks for your help in advance. I have mailed this group and the c.w.x group several times about this bug, and had quite a few email responses, but all were of the form "Gee, we have that problem too, you will let us know if you solve it?" which is nice in the sense that someone is listerning out there but still gets me no nearer to the solution. -- Matt Newman