This seems to be (after some searching) a quite wide-spread problem, but no 
solutions are
available. The same problem happen on Suse, Slackware and some other distros:

http://osdir.com/ml/network.tight-vnc.general/2004-12/msg00016.html
http://www.spinics.net/lists/vnc/msg09018.html
http://www.realvnc.com/pipermail/vnc-list/2004-December/048458.html
http://www.realvnc.com/pipermail/vnc-list/2003-June/039698.html

The same problem seem to happen on tightvncserver and the old vnc3 version as 
well so it is
likely to be a very old problem. Well it is an old problem as it has been 
reported already in
2003...

The problem is not in Eclipse per see, but Eclipse probably have some way to 
handle pixmaps
which vnc do not handle very well.

The problem also happens when using Xnest so it is likely to be some X problem, 
and not really
in vnc code.


That's a shame, really. Eclipse is the first program I came across
that doesn't work under VNC. I'd have expected Gimp / Inkscape / VLC
to be more of a problem yet those work fine.

If you want me to help debugging this further, I can give you instructions on 
how to use gdb
However I'm not that good at gdb myself. I tend to use ddd that is a graphical 
shell around
gdb (from where you can actually see the gdb commands).

I'm happy to help of course, but seeing as the problem seems to be
reproducible to some degree maybe getting someone on the case who
knows more than I do might be beneficial. It'd save the handholding
round-trip-time.

Regards,

C.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to