 |
 |
 |
 |
| Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum. |

18th May 2006, 01:52 AM
|
|
Registered User
|
|
Join Date: Aug 2004
Posts: 71

|
|
|
VNC - Unexpected Drop
Everytime I try to log into my VNC in :1 I'm getting this error...
Code:
Xvnc Free Edition 4.1.1
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 70000000, The X.Org Foundation
Wed May 17 20:47:43 2006
vncext: VNC extension running!
vncext: Listening for VNC connections on port 5901
vncext: Listening for HTTP connections on port 5801
vncext: created VNC server for screen 0
Could not init font path element /usr/share/X11/fonts/OTF, removing from list!
Could not init font path element /usr/share/X11/fonts/CID/, removing from list!
SESSION_MANAGER=local/localhost:/tmp/.ICE-unix/2813
Window manager warning: Log level 32: could not find XKB extension.
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Wed May 17 20:48:24 2006
Connections: accepted: 70.88.228.90::1823
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
SConnection: unexpected security type
Connections: closed: 70.88.228.90::1823 (unexpected security type)
Wed May 17 20:49:57 2006
Connections: accepted: 70.88.228.90::1825
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
SConnection: unexpected security type
Connections: closed: 70.88.228.90::1825 (unexpected security type)
Any way to fix this?
|

18th May 2006, 04:21 AM
|
|
Registered User
|
|
Join Date: Aug 2004
Posts: 71

|
|
|
Anyone here know about this?
|

18th May 2006, 04:34 AM
|
|
Registered User
|
|
Join Date: May 2006
Posts: 17

|
|
|
I'm getting the same issue. Any news?
|

18th May 2006, 08:40 AM
|
 |
"Fixed" by (vague) request
|
|
Join Date: Oct 2005
Location: GMT+ 1
Posts: 2,950

|
|
|
Nope, but I am definitely filing this bug...
|

18th May 2006, 03:39 PM
|
|
Registered User
|
|
Join Date: Feb 2005
Posts: 194

|
|
|
Go to realvnc and download the latest version it works fine for me on FC4.
|

18th May 2006, 04:16 PM
|
|
Registered User
|
|
Join Date: May 2006
Posts: 17

|
|
|
Even downloading the latest version from realvnc does not work for me on FC5.
|

18th May 2006, 04:20 PM
|
 |
Administrator (yeah, back again)
|
|
Join Date: Jul 2004
Location: Colton, NY; Junction of Heaven & Earth (also Routes 56 & 68).
Age: 67
Posts: 21,213

|
|
According to this thread: http://forums.fedoraforum.org/forum/...d.php?t=109753 there's a bugzilla filed on the problem. Might want to check if there's any solutions for you either on the thread or with the bugzilla.
__________________
Linux & Beer - That TOTALLY Computes!
Registered Linux User #362651
Don't use any of my solutions on working computers or near small children.
|

18th May 2006, 07:53 PM
|
|
Registered User
|
|
Join Date: May 2006
Posts: 17

|
|
|
No solutions yet. Has anybody upgraded and has a working VNC? This is killing me.
|

18th May 2006, 08:18 PM
|
|
Registered User
|
|
Join Date: Aug 2004
Posts: 2

|
|
|
Hi,
I just upgraded vnc, and about 80 other packages on 3 seperate linux boxes running FC5. On the one I restarted, I can no longer establish VNC sessions. I get a message from the VNC Client saying
"The connection closed unexpectedly. Do you wish to reconnect?". It always fails. I'm sure this is related to the update to fix the security problem recently published regarding VNC. I'm glad it's been fixed. But, I wish there was some documentation somewhere explaining what to do to get a vnc session back up. (I'm starting a vnc session via puTTY from a Window$XPSP2 laptop using the command 'vncserver -depth 24 -geometry 1440x900'. Then trying to log in using the vnc client on the XP box. (I tried upgrading to 4.1.2 on the client. It didn't help.) This has worked for me for a long time on a lot of different linux boxes.
Any Ideas would be appreciated.
Thanks,
Jerry Lumpkins
Programmer/Analyst
|

18th May 2006, 08:23 PM
|
|
Registered User
|
|
Join Date: May 2006
Posts: 17

|
|
|
You can find the error message in your VNC log file. This seems to be broken for everyone that upgrades. I hope the problem is fixed since I am now limited to shell access to my box.
|

18th May 2006, 09:23 PM
|
|
Registered User
|
|
Join Date: May 2006
Posts: 17

|
|
|
As per the Bug Report, a work around is to specify only Connect Using 3.3 Protocol on your Client
|

18th May 2006, 10:40 PM
|
|
Registered User
|
|
Join Date: Aug 2004
Posts: 2

|
|
|
Thanks, I missed that in the Bugzilla report.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 21:12 (Tuesday, 21-05-2013)
|
|
 |
 |
 |
 |
|
|