Hi, Below is an old message sent to this list, for which I could find replies. I have recently encountered the same problem, but have additional info that may give someone more knowledgeable some clues as to the cause - and a possible solution. ...................................cut here.................................. List: [3]vnc-list Subject: address garbled in linux From: [4]Guy McArthur <[EMAIL PROTECTED]> Date: [5]1999-11-16 18:08:29 [[6]Download message RAW] Hello, I have RH 6.0 (glibc 2.1.1). When I try to run vncviewer I get an output like "Couldn't convert 'h&@h&@9.22' to host address" where it is garbling the first few bytes of the server address. I can telnet to the address on port 5900 and verify that the server is running. This happens with the linux binaries AND the executables compiled from the unix source distribution. Is there a problem I can fix on my end? -- Guy "Smiley" McArthur [home] 520.326.4555 [web] [7]www.seds.org/~smiley [EMAIL PROTECTED] [work] 520.881.8101 [icq] 17470307 --------------------------------------------------------------------- The VNC mailing list - see [8]http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- .......................................cut here............................... I also am running RedHat 6.0 and am using VNC 3.3.3 R1-3 and KDE as the Desktop manager. I have a small home LAN with no outside connections. What happens is: While in KDE as ROOT, if you start vncviewer from the Desktop executable prompt, ie., right-click background, the "widget" which prompts for input for the Server address appears, as it should. If you enter a valid ip number w/ display #, the "widget" just disappears. If, on the other hand, you open an x-term and enter 'vncviewer' the "widget" appears, but when the Host address is entered, you get a message 'couldn't convert <ipaddress(garbled)> to host address.' What makes this interesting is that it only happens as ROOT, and only in KDE. The other Desktop Managers I've tried, AfterStep, AnotherLevel, etc. seem not to have this problem. AND, if I log on as USER, in KDE, everything works as it should. As ROOT in KDE, if I open a x-term and type 'vncviewer' with ANY of its options ( -depth, -share, etc.) the "widget" works correctly. If I type 'vncviewer <ipaddress:display#>' it also works correctly. If, as ROOT, I bring up the "widget" from the Desktop executable, as above, but maximize it, or just grab in on the corner and make it bigger, it also works correctly. Making it smaller, or just moving it does nothing. This odd behavior manifests itself on both my Linux machines; both with RedHat 6.0 and KDE. Vncviewer misbehaves identically when I am ROOT on the other machine also. Vncviewer worked correctly when first installed, but shortly developed this strange behavior. I have re-installed it a number of times, but to no avail.. The simple "workaround" is to make a Desktop icon which executes vncviewer with the <depth> option - set to the value I happen to use anyway. If anyone can offer some insights as to a "proper" solution, I would be glad to attempt a fix. Please e-mail any suggestions directly to me at: [EMAIL PROTECTED] (My connection to the internet is via a "buggy" local library dial-up. Getting at the mailing list is not always easy. But, like Linux and VNC, its free and doesn't require a ton of ram to use.) Thanks in advance......... Tom ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj. --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
