In this article we will show how to setup a browser or RDP kiosk, based on Ubuntu server 18.04 LTS. Because we are using the server edition the kiosk system will have a very small footprint and way less packets installed when we compare it to a stripped down desktop kiosk.<\/p>\n
First we need to install a fresh Ubuntu 18.04 LTS system. After the installation is complete, make sure to install any available updates by executing the following commands:<\/p>\n
sudo apt-get update\r\nsudo apt-get upgrade -y\r\nsudo reboot<\/pre>\nKiosk purpose<\/strong><\/p>\n
Before we start configuring the kiosk, we first need to think what we want to show on the kiosk unit. Different content types require different applications and configurations. in this article we will show how to install and use a chrome based kiosk and a Remmina (RDP) based kiosk. Other applications\/types of content are also possible but might require additional research.<\/p>\n
The kiosk can only serve one type of content at the time.<\/p>\n
To go with the web content kiosk, install chrome using the following command:<\/p>\n
sudo apt-get install --no-install-recommends chromium-browser<\/pre>\nTo go with the remote desktop kiosk, install Remmina using the following command:<\/p>\n
sudo apt-get install remmina -y<\/pre>\nAutomatic logon<\/strong><\/p>\n
Our kiosk needs to log on automatically, to achieve this we will overwrite the getty service configuration to change the way TTY1 is started (TTY1 is the default console output on most Linux based servers). To overwrite a part of the getty configuration we need to execute the following command:<\/p>\n
sudo systemctl edit getty@tty1<\/pre>\nThe above command will create an overwrite file for the getty configuration. paste the following text in this file to enable automatic login (replace <username> with a local account on the Ubuntu server):<\/p>\n
[Service]\r\nExecStart=\r\nExecStart=-\/sbin\/agetty -a <username> --noclear %I $TERM<\/pre>\nBecause the user configured in the above file will automatically logon to the system at boot, it is recommended to make sure the user can not access sensitive documents (which should not be stored on a kiosk system in any case). the selected user may be in the sudoers file, this will not present a security problem because sudo alway’s requires a password. For more information about auto logon: Muru, a user on askubuntu.com<\/a> has written a very interesting answer about auto logon<\/a>.<\/p>\n
Graphical user interface<\/strong><\/p>\n
Ubuntu server has no X server and Window manager installed by default, its text only. Our kiosk needs a both a X server and a window manger to display any graphical applications.<\/p>\n
Use the following command to install the X server (X.org) and windows manager (Openbox):<\/p>\n
sudo apt-get install --no-install-recommends xserver-xorg x11-xserver-utils xinit openbox -y<\/pre>\nwith the GUI installed, we need to configure it. X.org will work out of the box, but openbox requires some minor configuration changes to start our kiosk application.<\/p>\n
The Openbox configuration file is located at “\/etc\/xdg\/openbox\/autostart”. We can open it for editing with the following command:<\/p>\n
sudo nano \/etc\/xdg\/openbox\/autostart<\/pre>\nReplace the contents of the Openbox configuration file with one of the below ones, depending on witch packet you installed earlier.<\/p>\n
Web content\/Chrome (replace <http:\/\/your-url-here> with your desired url:<\/p>\n
# Disable any form of screen saver \/ screen blanking \/ power management\r\nxset s off\r\nxset s noblank\r\nxset -dpms\r\n\r\n# Allow quitting the X server with CTRL-ATL-Backspace\r\nsetxkbmap -option terminate:ctrl_alt_bksp\r\n\r\n# Start Chromium in kiosk mode\r\nsed -i 's\/\"exited_cleanly\":false\/\"exited_cleanly\":true\/' ~\/.config\/chromium\/'Local State'\r\nsed -i 's\/\"exited_cleanly\":false\/\"exited_cleanly\":true\/; s\/\"exit_type\":\"[^\"]\\+\"\/\"exit_type\":\"Normal\"\/' ~\/.config\/chromium\/Default\/Preferences\r\nchromium-browser --disable-infobars --kiosk '<http:\/\/your-url-here>'<\/pre>\nRemote Desktop\/Remmina (change <path to remmina file> to the actual path to the desired remmina file):<\/p>\n
# Disable any form of screen saver \/ screen blanking \/ power management\r\nxset s off\r\nxset s noblank\r\nxset -dpms\r\n\r\n# Allow quitting the X server with CTRL-ATL-Backspace\r\nsetxkbmap -option terminate:ctrl_alt_bksp\r\n\r\n# Start Remmina in kiosk mode\r\nremmina -c <path to remmina file>\r\n\r\n#start remmina in normal mode (for configuration purposes)\r\n#remmina<\/pre>\nIf you don’t have a .remmina file, comment out row 10 and uncomment row 13, now when the xserver is started Remmina will start in normal mode.<\/p>\n
The main part of the configuration is done. To start the GUI simply type “startx” in the console, the GUI can be closed by pressing ctr+alt+backspace.<\/p>\n
Autostart Graphical user interface<\/strong><\/p>\n
We can not call a system a kiosk if we need to manually type “startx” after every reboot. So lets make sure we wont have to.<\/p>\n
We can accomplish this by configuring the “.bash_profile” file for the auto login user. Assuming we are alredy logged on as the auto logon user, use the following commands to create or open the “.bash_profile” file for editing:<\/p>\n
cd\r\nsudo nano .bash_profile<\/pre>\nnow append the following line to the file:<\/p>\n
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && startx<\/pre>\n<\/p>\n
Reboot and enjoy your kiosk \ud83d\ude42<\/p>\n
<\/p>\n