[FreeNX-kNX] Can you confirm gtk+ 1.2 freezing with NX?

[Gian Filippo Pinzari]

Thorsten Huefner wrote:
> With no AGENT_EXTRA_OPTIONS_X setting in node.conf gtk freezes and i get empty 
> snapshots. 

I don't know why GTK1 freezes, but it should not. Please check the man
page of XGetImage to see why XGetImage requests -may- return errors
or even fake data.

What NX is doing here is just following the letter of the X protocol.
That said, the 1.5.0 nxagent tries hard to make applications happy.
Probably GTK will be OK with the next version :-).

> The interesting thing is why tooltips should are images for gtk1. 
> Gtk 1 freezes in case of popping up of tooltips, and by clicking buttons 
> (which are most probably images).

Toolkits make a lot of things that are stupid. For example the latest
beta of a well-known OSS office suite -still- queries the remote frame-
buffer to do things that might have been easily done with a pixmap ;-).
It seems that nobody is interested in solving this problem, probably
because nobody is trying to use that well-known OSS office suite over
an Internet link. Except NX/FreeNX users, of course :-).

In the next spin of NX (not in 1.5.0 and probably not in 1.6.0) nxagent
will keep its own copy of the framebuffer, so this and all the other
problems will be gone.

If you wonder why we didn't let nxagent keep a copy of the framebuffer
already, the reason is that we expected that, in 2 years since when we
announced NX, people would have fixed all those applications that are so
dumb to query the framebuffer to do things as simple as rendering text
or compositing a simple image with its background. As you can see, we
were wrong ;-).

/Gian Filippo.