[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to start tightvncserver



On Fri, Jan 22, 2010 at 12:07 AM, Foss User <fossist@gmail.com> wrote:
> I am unable to start tightvncserver. Please see the output and help me.
>
> fossist@squeeze:~$ tightvncserver
>
> You will require a password to access your desktops.
>
> Password:
> Verify:
> Would you like to enter a view-only password (y/n)? n
>
> New 'X' desktop is squeeze:1
>
> Creating default startup script /home/fossist/.vnc/xstartup
> Starting applications specified in /home/fossist/.vnc/xstartup
> Log file is /home/fossist/.vnc/squeeze:1.log
>
> fossist@squeeze:~$ cat .vnc/squeeze\:1.log
> 22/01/10 00:01:33 Xvnc version TightVNC-1.3.9
> 22/01/10 00:01:33 Copyright (C) 2000-2007 TightVNC Group
> 22/01/10 00:01:33 Copyright (C) 1999 AT&T Laboratories Cambridge
> 22/01/10 00:01:33 All Rights Reserved.
> 22/01/10 00:01:33 See http://www.tightvnc.com/ for information on TightVNC
> 22/01/10 00:01:33 Desktop name 'X' (squeeze:1)
> 22/01/10 00:01:33 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
> 22/01/10 00:01:33 Listening for VNC connections on TCP port 5901
> Font directory '/usr/X11R6/lib/X11/fonts/misc' not found - ignoring
> Font directory '/usr/share/fonts/X11/cyrillic' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/cyrillic' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/100dpi/:unscaled' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/75dpi/:unscaled' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/Type1' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/100dpi' not found - ignoring
> Font directory '/usr/X11R6/lib/X11/fonts/75dpi' not found - ignoring
>
>
> fossist@squeeze:~$ cat /tmp/.X1-lock
>      4847
>
> fossist@squeeze:~$ ps -aef | grep 4847
> fossist     4987  3680  0 00:02 pts/3    00:00:00 grep 4847
>
> fossist@squeeze:~$ netstat -na | grep tcp | grep 59
> fossist@squeeze:~$
>

Any help with this? Should I report this as a bug?


Reply to: