[FreeNX-kNX] Image corruption in backing store, painting errors and hang

[jhonyl]

When I press CTRL+ALT+E it responds with a message box saying 'Deferred 
screen updated are now disabled' client 3.2.0-13. The windows need to 
repaint to be OK, minimize maximize for example. The session stays 
OKish, but if I suspend, and resume, then I need to press it once again.

(: And my freenx version is 0.7.3 :)

-----Original Message-----
From: Mario Becroft <mb at gem.win.co.nz>
To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
Sent: Sun, 5 Oct 2008 2:43 am
Subject: Re: [FreeNX-kNX] Image corruption in backing store, painting 
errors and hang

jhonyl <jhonyl at netscape.net> writes:

> Hi,
>
>  I run FreeNX 7.0.3 on debian, and I too have problems 1,2.
> In my case ctrl+alt+e helps 2, but then problem 1 starts.

That's interesting. Apparently, control-alt-e toggles "lazy encoding."
Does anyone know what that means?

Do you find that pressing control-alt-e just once (toggling the setting)
solves the problem, or does the problem remain solved even if you toggle
again (back to the original setting)? I will try it next time the
problem happens here.

Regarding the backing store (or perhaps more correctly, save under)
problem, you may find that disabling the backing store will prevent the
symptoms from appearing (I don't know if the same underlying problem is
manifested in other ways though). I find that disabling backing store in
the nxclient configuration is not sufficient; you actually must add this
line to your node.conf:

AGENT_EXTRA_OPTIONS_X="-bs"

(or add "-bs" to your existing AGENT_EXTRA_OPTIONS).

You can check whether it worked by running the following command in the
nx session:

xdpyinfo |grep backing

Normally it will say: "options:    backing-store YES, save-unders YES,"
but if the setting was successful, it will say NO and NO instead of YES
and YES.

Obviously, this will slow down the display when, for instance, menus are
unposted. From what I can tell, at least under gnome, backing store for
ordinary windows is not really used.

Anyway, I am glad I am not the only one having these problems. I wonder
if any of the nx developers have an idea of what might be causing them?

--
Mario Becroft <mb at gem.win.co.nz>
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________