View Single Post

  #8 (permalink)  
Old 03-29-2008
Salih
 
Posts: n/a
Default Re: VNC viewer is connected but blank screen

On Mar 28, 4:27 am, Jack Snodgrass <jacks_temp_id_bf2...@verizon.net>
wrote:
> On Thu, 27 Mar 2008 18:19:04 -0700, Salih wrote:
> > On Mar 24, 4:32 pm, Jack Snodgrass <jacks_temp_id_bf2...@verizon.net>
> > wrote:
> >> On Mon, 24 Mar 2008 13:35:46 -0700, Salih wrote:
> >> > I was able to run a vncserver and connect to it without a problem. After
> >> > switching to xfce from kde, viewer connects but all I get is a blank
> >> > screen with mouse working.

>
> >> > I am running the server on a Kubuntu machine. I tried connecting to it
> >> > via TightVNC from a Windows machine as well as via vncviewer to
> >> > localhost from the Linux server itself.

>
> >> > When I run the server I get the following log:

>
> >> > 4/03/08 13:32:12 Xvnc version 3.3.7 - built May 24 2007 12:47:11
> >> > 24/03/08 13:32:12 Copyright (C) 2002-2003 RealVNC Ltd. 24/03/08 13:32:12
> >> > Copyright (C) 1994-2000 AT&T Laboratories Cambridge. 24/03/08 13:32:12
> >> > All Rights Reserved. 24/03/08 13:32:12 Seehttp://www.realvnc.comfor
> >> > information on VNC 24/03/08 13:32:12 Desktop name 'X' (cellular:1)
> >> > 24/03/08 13:32:12 Protocol version supported 3.3 24/03/08 13:32:12
> >> > Listening for VNC connections on TCP port 5901

>
> >> > When I connect from the client using vncviewer, this additional message
> >> > is received:

>
> >> > 24/03/08 13:32:53 Got connection from client 0.0.0.0 24/03/08 13:32:53
> >> > Protocol version 3.3 24/03/08 13:32:55 Pixel format for client 0.0.0.0:
> >> > 24/03/08 13:32:55 8 bpp, depth 6
> >> > 24/03/08 13:32:55 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
> >> > 24/03/08 13:32:55 rfbProcessClientNormalMessage: ignoring unknown
> >> > encoding type -239
> >> > 24/03/08 13:32:55 rfbProcessClientNormalMessage: ignoring unknown
> >> > encoding type -223
> >> > 24/03/08 13:32:55 Using ZRLE encoding for client 0.0.0.0

>
> >> > I don't know how to debug it and logs do not tell much. Does anybody
> >> > have any idea what would be the cause?

>
> >> > Thanks...

>
> >> sounds like your not starting a xfce session manager if you want to run
> >> xfce. Do you have:

>
> >> /usr/bin/xfce4-session
> >> in your xstartup and does
> >> ps -aef | grep xfce
> >> show some xfce processes running after you start your vncserver?

>
> >> jack

>
> > Thank you Jack. Where is the "xstartup" file located? Do I need to
> > manually edit it to run the x-session?

>
> On my Fedora install, when you start vncserver for the first time,
> it creates a ~/.vnc directory with a xstartup script in it.
> I changed my xstartup scrript to do:
>
> #!/bin/sh
>
> # Uncomment the following two lines for normal desktop:
> # unset SESSION_MANAGER
> # exec /etc/X11/xinit/xinitrc
>
> /usr/bin/xfce4-session &
> wait
>
> so when vncserver starts, it starts an X session and the
> xstartup script starts my xfce4-session manager.
>
> --
> D.A.M. - Mothers Against Dyslexia
>
> seehttp://www.jacksnodgrass.comfor my contact info.
>
> jack - Grapevine/Richardson


Thank you for the detailed explanation. I actually uninstalled
Xubuntu using the directions at http://www.psychocats.net/ubuntu/purekde
and re-installed the KDE desktop. Everything works now. Note that
running simply "sudo apt-get remove xubuntu-desktop" does not work. I
will follow your directions if I decide to switch to xfce.
Reply With Quote