Hi Brad On Thu, May 10, 2007 at 11:47:11AM -0400, Brad Barnett wrote: > On Thu, 10 May 2007 09:56:27 +0200 > Ola Lundqvist <[EMAIL PROTECTED]> wrote: > > > Hi Brad > > > > On Wed, May 09, 2007 at 01:21:52PM -0400, Brad Barnett wrote: > > > Package: xtightvncviewer > > > Version: 1.2.9-21 > > > Severity: important > > > > > > > > > When xtightvncviewer connects to localhost, it automatically assumes > > > that it should use raw encoding. For example, the output states "Same > > > machine: preferring raw encoding". > > > > > > However, this should not be the case, as many people use ssh (often > > > with -C) to get past firewalls and also because of ssh compression, > > > improve the speed of VNC. Prior versions of tightvnc did not do this, > > > and tightvnc should be able to dynamically switch encoding as it does > > > for normal links anyhow. > > > > I agree that this is something that should be changed. > > > > > Please remove this recently added featured, as it makes tightVNC > > > extremely annoying in many circumstances, and it should have no > > > problem switching to best-encoding on its own anyhow. > > > > What do you mean recent? This is a part of upstream functionality and > > have been like this since at least sarge (1.2.9-6). > > > > Hmm, perhaps so. Weird that I did not notice it until now, however. I'm > running AMD64, so perhaps the initial versions of tightvnc on the > AMD64 port were of a different version, before things synced up more with > the main archives?
Not likely. > All I know is that I noticed it now, after an upgrade, and it wasn't there > before. The speed change is quite significant. ;) I didn't have tightvnc > on hold either... Ok. > Hmm, come to think of it, it could be that I've just been using > 'xvncviewer' and that /etc/alternatives/ was pointed at xrealvncviewer and > not tight, and that has now changed after my upgrade to etch... > > Probably the last paragraph, is the correct one.. ;) That is the most likely thing. I'll see what I can do about this. I suggest you use normal vnc instead or vnc4. I think both have support for ssh tunneling. Regards, // Ola > Thanks! > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
