I use vnc to access graphic interface from my PC to cubieboard that runs on lubuntu. I have chosen tightvncserver and spent some time to configure and run it. Also to my surprise it took me a while to set it up correctly. This guide was the most helpful how-to but I needed to make some changes so I’ve written this post.
To check if you have any version of VNC installed type:
dpkg --get-selections | grep vnc
If you don’t have it then install tightvncserver:
apt-get install tightvncserver
Run the command vncpasswd to define a vncpasswd as depicted bellow.
Configure ~/.vnc/xstartup file as:
#!/bin/sh xsetroot -solid grey export XKL_XMODMAP_DISABLE=1 #autocutsel -fork openbox & /usr/bin/lxsession -s Lubuntu &
Start vnc again with tightvncserver :1 and get the TCP port from the log file.
My VNC was opened at TCP port 5901 so this port has to be used if I want to connect from VNC viewer. I have installed vncviewer on my win7 PC:
TightVNC server is up and running on Lubuntu and connection from VNC client is established.
Autostart tightvnc server
One simple way to autostart tightvncserver is to configure user autologin and start vnc server in lxsession autostart script (I used autologin in my previous post). The only needed configuration to enable autologin of the unix user (user linaro in my case) is to update the /etc/lightdm/lightdm.conf file with the following lines:
[SeatDefaults] autologin-user=linaro autologin-user-timeout=0 greeter-session=lightdm-gtk-greeter user-session=Lubuntu
Once the user autologin is configured, add the line @/usr/bin/tightvncserver :1 to autostart VNC in lubuntu autostart file:
sudo mcedit /etc/xdg/lxsession/Lubuntu/autostart
VNC is now available also after the reboot. 😎
Whereas most VNC servers share your desktop, tightvnc creates a completely new desktop, not attached to any actual screen. This makes it much less useful for some things (like remote help), but much more useful for others (like creating a public area for collaboration). If you decide for x11vnc you can try another guide, that I found after I spent the time with tightvncserver described in this post. There are many types of vnc server that you can check.
CHECK if the file ~/.cache/lxsession/Lubuntu/run.log is not increasing in size. My file was increasing ~100MB a day.
This message was added to the run.log file quite often:
** Message: app.vala:59: Launching /usr/bin/tightvncserver :1 (null) A VNC server is already running as :1 ** Message: app.vala:73: /usr/bin/tightvncserver exit with this type of exit: 25088 ** Message: app.vala:91: Exit not normal, reload
In my original post I had ~/.vnc/xstartup file this line: /usr/bin/lxsession -s Lubuntu -e LXDE &
I removed “-e LXDE” and the ~/.cache/lxsession/Lubuntu/run.log file is not increasing now. This is now stated as confirmed bug of not rotating logs of lxsession in ubuntu: bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1376380
The new config line is:
/usr/bin/lxsession -s Lubuntu &
Other useful posts with lubuntu topic:
- apache and php as web server on cubieboard
- minidlna – media server on cubieboard
- creating disk in memory
- using cubieboard as a honeypot (to detect and track hackers)
- seeting timezone and NTP
Posts with cubieboard2 tips:
- Turn off/on blue/green LED
- extendind NAND partition from 2GB to 4GB
- enable UART to connect with my arduino
Mini solar projects posts: