Hi Sammy,
Could you please elaborate on what you've changed to solve your screen
update problem? (which config files/libraries/settings did you change
on which server(sunray server/application server?)) We're experiencing
similar problems with some parts of the screen not updated during
hefty scrolling/X activity, leaving parts of the screen black. These
problems seem to be sunray specific, as we've not seen them using our
Linux/XFree86 based X-terminals. In our setup the problems seems to be
specific to the X libraries used by our software (SAS on OpenVMS).
The default setting that fixed my poblem disables shared memory usage
in the art backend of GNUstep. I have no idea what exactly happens
behind the curtain, but using the shared memory option seems to trigger
a bug in the SRSS or it is a bug in the GNUstep backend. I hve really
no idea.
I did nothing onthe Sun Rays Server. I just disbaled some optimization
on the application server.
Regards,
Andreas
On Fri, Sep 15, 2006 at 02:50:37PM +0200, Andreas Höschler wrote:
Hi all,
we have discovered a very ugly Sun Ray Software related problem which
causes the display not to be updated correctly, e.g. when popping up
a
combobox and scrolling through the items, or when scrolling through a
text view or when clicking on items in a container view (actually
NSView sublcasses on some other NSView subclass). "Display is not
updated correctly" means that some stuff simply is not drawn.
This problem can't be Solaris related since it does not occur when we
access the machine via Secure Global Desktop or directly on the
console. It occurs only when using Sun Rays.
We haven't been able to reproduce this with GNOME apps, it occurs
only
with GNUstep apps. But I can't blame GNUstep alone, since it works
flawless on all flavors of Unix and even on Solaris when working on
the console or via a SGD connection. The problem only occurs in
combination with Sun Rays.
Any hints are greatly appreciated!
Richard Frith-Macdonald recommended the following:
Is the problem with both the art and xlib backends?
Is it with both GSX11HandlesWindowDecorations user default set to 1
and 0 ?
Is it with both XWindowBufferUseXShm user default set to 1 and 0?
Checking those variations could localise the problem.
and
defaults write NSGlobalDomain XWindowBufferUseXShm 0
indeed solved this problem. Live is great!!!
Regards,
Andreas
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
