Results 1 to 9 of 9
Hi. I have TightVNC installed. It works fine serving Gnome and KDE3.x Desktops. But if I try to serve a KDE4 desktop i just get a black page in the ...
- 12-08-2008 #1
Does TughtVNC work with KDE4?
Hi. I have TightVNC installed. It works fine serving Gnome and KDE3.x Desktops. But if I try to serve a KDE4 desktop i just get a black page in the viewer on a windows or a Linux client.
I've tried two different computers as servers and two different computers as clients.
This server failure on KDE4 occurs in openSUSE 11.0 and 11.1 beta4 and 11.1RC1
Has anyone seen this problem or know of a solution or has a comment -- or any thoughts?
Thanks
Swerdna
- 12-08-2008 #2
Have you tried xorg_X11_vnc ??
- 12-08-2008 #3Linux Guru
- Join Date
- Nov 2004
- Posts
- 6,110
I think KDE4 uses hardware acceleration by default, so any accelerated effects would be bad news for a VNC server. Have you disabled those effects and restarted the VNC server?
- 12-08-2008 #4
The devs have installed Xvnc in xinetd (Yast Net services) and there's yet another VNC in Yast Remote Administration. The former works the latter doesn't. Xorg_X11 version might work too and is another option.
But I want to remain with TightVNC if I can. I have clients using it on windows across the city and don't wish to over complicate the administration with several versions. Already it's hard enough with the failure of TightVNC in vista. I'm trying to get KDE4 up for the future so it's not a life threatening event for the moment.
Thanks but for the moment I'll try to get TightVNC up/working in KDE4.
- 12-08-2008 #5
Thanks
I just now disabled hardware acceleration in Yast --> sax2, and restarted the server. The screen on the client machine is now gray instead of black. Here's a copy of the log file in location $HOME/.vnc, from starting "vncserver" through a connection/disconnection event:
Any ideas.09/12/2008 07:34:36 Xvnc version X.org/xf4vnc custom version
09/12/2008 07:34:36 Copyright (C) 2001-2004 Alan Hourihane.
09/12/2008 07:34:36 Copyright (C) 2000-2004 Constantin Kaplinsky
09/12/2008 07:34:36 Copyright (C) 1999 AT&T Laboratories Cambridge
09/12/2008 07:34:36 All Rights Reserved.
09/12/2008 07:34:36 See TightVNC: VNC-Based Free Remote Control Solution for information on TightVNC
09/12/2008 07:34:36 See http://xf4vnc.sf.net for xf4vnc-specific information
09/12/2008 07:34:36 Desktop name 'X' (linux-xxke:1)
09/12/2008 07:34:36 Protocol versions supported: 3.7, 3.3
09/12/2008 07:34:36 RGB format 5 6 5
09/12/2008 07:34:36 Listening for VNC connections on TCP port 5901
09/12/2008 07:34:36 Listening for HTTP connections on TCP port 5801
09/12/2008 07:34:36 URL http://linux-xxke:5801
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/uni, removing from list!
Could not init font path element /usr/share/fonts/CID, removing from list!
09/12/2008 07:36:04
09/12/2008 07:36:04 Got VNC connection from client 192.168.1.2
09/12/2008 07:36:04 Using protocol version 3.7
09/12/2008 07:36:04 Enabling TightVNC protocol extensions
09/12/2008 07:36:08 Full-control authentication passed by 192.168.1.2
09/12/2008 07:36:08 Pixel format for client 192.168.1.2:
09/12/2008 07:36:08 32 bpp, depth 24, little endian
09/12/2008 07:36:08 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
09/12/2008 07:36:08 Using copyrect encoding for client 192.168.1.2
09/12/2008 07:36:08 Using tight encoding for client 192.168.1.2
09/12/2008 07:36:08 Using compression level 1 for client 192.168.1.2
09/12/2008 07:36:08 Using image quality level 6 for client 192.168.1.2
09/12/2008 07:36:08 Enabling X-style cursor updates for client 192.168.1.2
09/12/2008 07:36:08 Enabling cursor position updates for client 192.168.1.2
09/12/2008 07:36:08 Enabling LastRect protocol extension for client 192.168.1.2
09/12/2008 07:36:08 rfbProcessClientNormalMessage: ignoring unknown encoding -223
09/12/2008 07:36:12 rfbClientConnectionGone
09/12/2008 07:36:12 VNC Client 192.168.1.2 gone
09/12/2008 07:36:12 Statistics:
09/12/2008 07:36:12 key events received 1, pointer events 57
09/12/2008 07:36:12 framebuffer updates 3, rectangles 668, bytes 21156
09/12/2008 07:36:12 LastRect markers 3, bytes 36
09/12/2008 07:36:12 cursor shape updates 1, bytes 82
09/12/2008 07:36:12 cursor position updates 1, bytes 12
09/12/2008 07:36:12 tight rectangles 663, bytes 21026
09/12/2008 07:36:12 raw bytes equivalent 5281988, compression ratio 251.212213
09/12/2008 07:36:12 GenerateVncDisconnectedEvent
- 12-11-2008 #6
A little more information:
I now get this log file which shows definite error status before the connection attempt aborts:
10/12/2008 21:08:05 Xvnc version X.org/xf4vnc custom version
10/12/2008 21:08:05 Copyright (C) 2001-2004 Alan Hourihane.
10/12/2008 21:08:05 Copyright (C) 2000-2004 Constantin Kaplinsky
10/12/2008 21:08:05 Copyright (C) 1999 AT&T Laboratories Cambridge
10/12/2008 21:08:05 All Rights Reserved.
10/12/2008 21:08:05 See TightVNC: VNC-Based Free Remote Control Solution for information on TightVNC
10/12/2008 21:08:05 See http://xf4vnc.sf.net for xf4vnc-specific information
10/12/2008 21:08:05 Desktop name 'X' (linux-xxke:1)
10/12/2008 21:08:05 Protocol versions supported: 3.7, 3.3
10/12/2008 21:08:05 RGB format 5 6 5
10/12/2008 21:08:05 Listening for VNC connections on TCP port 5901
10/12/2008 21:08:05 Listening for HTTP connections on TCP port 5801
10/12/2008 21:08:05 URL http://linux-xxke:5801
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/uni, removing from list!
Could not init font path element /usr/share/fonts/CID, removing from list!
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
klauncher(4082) kdemain: Waiting for already running klauncher to exit.
klauncher(4082) kdemain: Waiting for already running klauncher to exit.
klauncher(4082) kdemain: Another instance of klauncher is already running!
kdeinit4: Communication error with launcher. Exiting!
kdeinit4_wrapper: Warning:
connect(/home/john/.kde4/socket-linux-xxke/kdeinit4__1) failed: : Connection
refused
Could not register with D-BUS. Aborting.
startkde: Shutting down...
kdeinit4_wrapper: Warning:
connect(/home/john/.kde4/socket-linux-xxke/kdeinit4__1) failed: : Connection
refused
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
startkde: Done.
10/12/2008 21:09:47
10/12/2008 21:09:47 Got VNC connection from client 192.168.1.2
10/12/2008 21:09:47 Using protocol version 3.7
10/12/2008 21:09:47 Enabling TightVNC protocol extensions
10/12/2008 21:09:50 Full-control authentication passed by 192.168.1.2
10/12/2008 21:09:50 Pixel format for client 192.168.1.2:
10/12/2008 21:09:50 32 bpp, depth 24, little endian
10/12/2008 21:09:50 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
10/12/2008 21:09:50 Using copyrect encoding for client 192.168.1.2
10/12/2008 21:09:50 Using tight encoding for client 192.168.1.2
10/12/2008 21:09:50 Using compression level 1 for client 192.168.1.2
10/12/2008 21:09:50 Using image quality level 6 for client 192.168.1.2
10/12/2008 21:09:50 Enabling X-style cursor updates for client 192.168.1.2
10/12/2008 21:09:50 Enabling cursor position updates for client 192.168.1.2
10/12/2008 21:09:50 Enabling LastRect protocol extension for client 192.168.1.2
10/12/2008 21:09:50 rfbProcessClientNormalMessage: ignoring unknown encoding
-223
10/12/2008 21:09:55 rfbClientConnectionGone
10/12/2008 21:09:55 VNC Client 192.168.1.2 gone
10/12/2008 21:09:55 Statistics:
10/12/2008 21:09:55 key events received 0, pointer events 110
10/12/2008 21:09:55 framebuffer updates 3, rectangles 8, bytes 258
10/12/2008 21:09:55 LastRect markers 3, bytes 36
10/12/2008 21:09:55 cursor shape updates 1, bytes 162
10/12/2008 21:09:55 cursor position updates 1, bytes 12
10/12/2008 21:09:55 tight rectangles 3, bytes 48
10/12/2008 21:09:55 raw bytes equivalent 5281988, compression ratio
110041.416667
10/12/2008 21:09:55 GenerateVncDisconnectedEvent
Have a look at this segment:
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
klauncher(4082) kdemain: Waiting for already running klauncher to exit.
klauncher(4082) kdemain: Waiting for already running klauncher to exit.
klauncher(4082) kdemain: Another instance of klauncher is already running!
kdeinit4: Communication error with launcher. Exiting!
kdeinit4_wrapper: Warning:
connect(/home/john/.kde4/socket-linux-xxke/kdeinit4__1) failed: : Connection
refused
Could not register with D-BUS. Aborting.
startkde: Shutting down...
kdeinit4_wrapper: Warning:
connect(/home/john/.kde4/socket-linux-xxke/kdeinit4__1) failed: : Connection
refused
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
startkde: Done.
Any ideas?
- 12-12-2008 #7
TightVNC just may not work with KDE4. Have you ried other VNC solurions I know there was one made for KDE at least older versions. Do a search for vnc in Yast.
- 12-12-2008 #8
Thanks for the advice. I can get other flavours of VNC to work in KDE4. The problem lies only with Xvnc. TightVNC is really a wrapper for Xvnc, it has Xvnc as the engine. Currently I'm trying to find the bug that prevents TightVNC (i.e. Xvnc) from working in KDE4. The problem is clearly outlined in the extract from the the log file but I don't have adequate knowledge to devise a workaround. Any ideas?
- 09-20-2011 #9Just Joined!
- Join Date
- Sep 2011
- Posts
- 1



