Description of problem: Various bugs in VNC 3.3.3r2, mainly improperly handling window updates. Best handled by upgrading packages to 3.3.6 from available URL http://www.realvnc.com/dist/vnc-3.3.6-2.src.rpm related files: http://www.realvnc.com/dist/vnc-3.3.6-x86_linux.tar.gz http://www.realvnc.com/dist/vnc-3.3.6-2.i386.rpm http://www.realvnc.com/dist/vnc-3.3.6-unixsrc.tar.gz http://www.realvnc.com/dist/vnc-3.3.6-documentation.tar.gz Version-Release number of selected component (if applicable): 3.3.3r2-43 How reproducible: 100% Steps to Reproduce: 1. Mainly - run any terminal app (gnome-terminal, konsole, xterm) 2. hit it from a remote vnc viewer 3. notice updates of the window suck and are incomplete :) Actual results: Expected results: Additional info:
Much too late for this cycle.
Here's the VNC server from RHL 8.0 (same VNC as Phoebe) demonstrating the bad behavior for terminal windows. http://www.sublogic.com/james/files/faruked_screen.gif I'll go ahead and make it an attachment, too. Note that graphical things that don't have text-based areas (like Kate, the KDE editor) work fantastically (BitBlt usage broken, maybe?) Expected it would be deferred, just wanted to get it logged before I forgot for yet another cycle :)
Created attachment 89336 [details] sshot showing bad VNC server behavior for text-based terminal winow
Oh, that's already logged I think. Note that 'vnc-3.3.3r2-43' is actually TightVNC right now.
*** This bug has been marked as a duplicate of 72965 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.