[SOLVED] Install of vncserver causes blank screen on reboot - Raspberry Pi Forums

i have fresh install of downloaded image of raspbian on new pi 2 has had minimum settings changed in raspi-config , backup made before proceeding.

after installing tightvncserver pi boots blank screen else working. procedure followed:

install tightvncserver:

code: select all

apt-get install tightvncserver

start server:

code: select all

tightvncserver

reports server running on x1

follow faithfully, instructions given here:
https://www.raspberrypi.org/documentati ... ccess/vnc/

code: select all

sudo su cd /etc/init.d/ nano vncboot

enter following:

code: select all

### begin init info # provides: vncboot # required-start: $remote_fs $syslog # required-stop: $remote_fs $syslog # default-start: 2 3 4 5 # default-stop: 0 1 6 # short-description: start vnc server @ boot time # description: start vnc server @ boot time. ### end init info  #! /bin/sh # /etc/init.d/vncboot  user=pi home=/home/pi  export user home  case "$1" in  start)   echo "starting vnc server"   #insert favoured settings vnc session   su - pi -c "/usr/bin/vncserver :0 -geometry 1280x800 -depth 16 -pixelformat rgb565"   ;;   stop)   echo "stopping vnc server"   /usr/bin/vncserver -kill :0   ;;   *)   echo "usage: /etc/init.d/vncboot {start|stop}"   exit 1   ;; esac  exit 0

save file vncboot , exit nano

code: select all

chmod 755 vncboot #because error with: update-rc.d: update-rc.d /etc/init.d/vncboot defaults use:  update-rc.d vncboot defaults  reboot

after usual dialog screen blank, tightvncserver running x0 , accessable. ssh working.

if ctrl/alt f2 can log in pi , start desktop using startx.

have had happen once before , put down updating using rpi-update or multiple reboots causing file corruption. however, time know have not made updates means , have rebooted when necessary point. in addition, pi band new , has never had sd card in until now.

have installed tightvnc on other pi's many times , never had problem.

can answer or suggestion why install of tightvncserver causes blank screen on boot?

just out of curiosity, sure want "tightvncserver" , not "x11vnc"?

99 times out of 100, people want "x11vnc", , trace following general pattern:

1. install tightvncserver.
2. wonder why doesn't expect. , wonder why ever program odd functionality tightvncserver implements.
3. start thread on forum asking why doesn't expect.
4. told use "x11vnc" instead.
5. go away happy (still scratching heads though, why other functionality ever coded up).

raspberrypi