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?
>
> 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
>
>
I was able to get TightVNC to work from openSUSE 11.0 with KDE 4.0.4 to openSUSE 11.0 4.1.3. I had no problem with it, but I did get a black screen when I first started it up but after it connected to the remote machine it went away. Maybe check your VNC settings on your machines.
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
vendion;1905498 Wrote:
> swerdna wrote:
>
> >
> > 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
> >
> >
>
> I was able to get TightVNC to work from openSUSE 11.0 with KDE 4.0.4 to
> openSUSE 11.0 4.1.3. I had no problem with it, but I did get a black
> screen when I first started it up but after it connected to the remote
> machine it went away. Maybe check your VNC settings on your machines.
> –
> “We must plan for freedom, and not only for security, if for no other
> reason than only freedom can make security more secure.” Karl Popper
Thanks.
The only adjustable settings that I’m aware of are firewall ports and
the TightVNC startup script (xstartup) located in directory $HOME/.vnc/
My xstartup file contains this:
Code:
/usr/bin/kwin &
/usr/bin/startkde &
What does yours contain? And what other “settings” might I adjust to
get the same settings as you have?
IIRC there is only one RPM package for tightvnc with comes with the
tightvnc server and viewer programs.
All I use option wise with the viewer is -x11cursor everything else I
is the vnc viewer default, and my vnc server is the default (YaST ->
Network Services -> Remote Administration (VNC)) and it works. I also
tell it to use a certain screen rather than the port number.
–
“We must plan for freedom, and not only for security, if for no other
reason than only freedom can make security more secure.” Karl Popper
vendion;1905578 Wrote:
> IIRC there is only one RPM package for tightvnc with comes with the
> tightvnc server and viewer programs.
>
> All I use option wise with the viewer is -x11cursor everything else I
> is the vnc viewer default, and my vnc server is the default (YaST ->
> Network Services -> Remote Administration (VNC)) and it works. I also
> tell it to use a certain screen rather than the port number.
What’s in the file $HOME/.vnc/xstartup? Maybe I’ve got it wrong in
there?
vendion;1905605 Wrote:
> I don’t have a ~/.vnc/xstartup on any of my machines and VNC works fine,
> I searched all users $HOME and even in /root.
Then it’s not the TightVNC implementation of VNC. Remote Administration
activates one of the six VNC implementations in the xinetd GUI in Yast,
the first one (5901 port, desktop :1), which uses the executable
/usr/bin/Xvnc. TightVNC is a slightly different implementation. It might
be that it has seen its sun set since it is no longer usable in windows
(vista) and looks to be unusable in KDE4.
The viewer part of TightVNC does work in KDE4 and Windows Vista, had to
use it before so I know it works, the server part of it may not work but
you can use the viewer with the xinetd implementation of VNC which is
what I do.
–
“We must plan for freedom, and not only for security, if for no other
reason than only freedom can make security more secure.” Karl Popper
vendion;1905654 Wrote:
> The viewer part of TightVNC does work in KDE4 and Windows Vista, had to
> use it before so I know it works, the server part of it may not work but
> you can use the viewer with the xinetd implementation of VNC which is
> what I do.
Yes. The viewer works fine.
I want to stay with TightVNC as the server implementation of VNC – but
I don’t think I can because it doesn’t work so far in KDE4 – so I’ll
now look at Xvnc (which seems to be in the RPM xorg-X11-Xvnc) and at
x11vnc (which exports the running window like in ms windows).
Pity, TightVNC was good, up there with UltraVnc which Suse doesn’t
have. Oh well, another opensource bites the dust.
Maybe this log of a connection attempt will ring a bell with someone:
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’ (http://www.tightvnc.com/) 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.
I’ve made a bit of progress with TightVNC in openSUSE 11.1. It still
needs a bug fix by the Novell/KDE people but I’ve discovered a few
workarounds for the desperate like me.
In my ‘comment #5 of the bug report’
(https://bugzilla.novell.com/show_bug.cgi?id=457809#c5) you can start a
KDE4 server session these two (unsatisfying) ways:
Log in to runlevel 3 (no GUI) or Gnome, not KDE4, and KDE4 will be
served nicely when you start it with the normal “vncserver” CLI command.
use this init script in /home/yourname/.vnc/xstartup
Code:
#!/bin/sh
/usr/bin/startkde
In my ‘comment #6 of the bug report’
(https://bugzilla.novell.com/show_bug.cgi?id=457809#c6) I am able to
report that:
The KDE4 virtual desktop will start from within a KDE4 desktop
environment if this command is issued instead of the normal one:
dbus-start vncserver
A client will then have a password dialogue and successfully connect to
the
virtual desktop on issuing this command in a console: vncviewer
IPaddress:1
For access from the web browser (see my ‘comment #7 of the bug report’
(https://bugzilla.novell.com/show_bug.cgi?id=457809#c7)), you can use
this fix in a Linux client:
address the remote desktop as usual with this address in Firefox on
port
5801:
http://IPaddress_of_server:5801
The login screen appears. BEFORE YOU LOGIN, use the drop-down box at
top left, labelled “Options”, to select Cursor Shape Updates = Disable.
Then login and an enduring connection will be made.
So in conclusion at this stage the thing is still in need of fixing by
the developers but there are some useful workarounds now.
Pop over and vote for the bug if you want some progress.
For those still waiting on resolution of the VNC bug experienced in the
KDE4 Desktop Environment: The Novell assignee (Lubos Lunak) has today
lifted the priority from P5 (none) to P2 (high). https://bugzilla.novell.com/show_bug.cgi?id=457809