When the computer boots the Ubuntu login screen is displayed for 10 seconds before the limited user account is automatically logged in and the kiosk application is automatically launched.

The problem with this process is that during this 10 second window someone could change the login session from the default ( I normally use blackbox ) to something else by using the little “options” button in the bottom left corner. ( or at least it’s in the bottom left corner of the default Ubuntu login theme ‘human’ ).

If you want to lock down or even just customize the login screen to suit your needs an easy way to do this is to edit the XML file which defines and places the elements on the login window. You can edit the main file for the default human theme with gedit.

cd /usr/share/gdm/themes/Humansudo cp Human.xml Human.xml.backupsudo gedit Human.xml

In my file I just commented out the <item> element which defined the option button. Voila ! No more option button.

1) Monitoring the computer services and network
2) Monitoring FireFox performance

Monitoring the computer services and network

Because our Kiosk computer is an Ubuntu server and running apache/php/mysql locally there are several open source network and service monitoring programs. The one I found most suitable for my solution is called Monit and I found a very good post at Ubuntu Geek describing how to install monit on ubuntu and configure it. I basically followed the Ubuntu Geek tutorial but made some modifications to the config file. My revised process is below.

1. Install Monit

   sudo apt-get install monit

2. Configure Monit. Open /etc/monit/monitrc in your favorite text editor. Below is an example of how I set up my own configuration file. It should be pretty self explanatory.

   ## Start monit in background (run as daemon) and check the services at 2-minute## intervals.set daemon  120
   
   ## Set syslog logging with the 'daemon' facility.set logfile syslog facility log_daemon
   
   ## Set list of mailservers for alert delivery.## I use my ISP's SMTP server for better reliability and means## I don't need an smtp server running on my Kioskset mailserver mail.shawcable.com
   
   ## Use event queue if mailserver unavailableset eventqueuebasedir /var/monit  # set the base directory where events will be storedslots 100           # optionaly limit the queue size
   
   ## You can set the alert recipient hereset alert someone@domain.com
   
   # Monitor Apachecheck process apache2 with pidfile /var/run/apache2.pid
   
   # Action to be taken when apache failsstart program = "/etc/init.d/apache2 start"stop program = "/etc/init.d/apache2 start"# Admin will notify by mail if below the condition satisfied belowif cpu is greater than 60% for 2 cycles then alertif cpu > 60% for 5 cycles then restartif children > 10 then alertif children > 50 then restartif loadavg(5min) greater than 10 for 8 cycles then stopif 3 restarts within 5 cycles then timeoutgroup servers
   
   # Monitor MySQLcheck process mysql with pidfile /var/run/mysqld/mysqld.pidgroup databasestart program = "/etc/init.d/mysql start"stop program = "/etc/init.d/mysql stop"if failed host 127.0.0.1 port 3306 then restartif failed host 127.0.0.1 port 3306 then alertif 5 restarts within 5 cycles then timeout
   
   # Monitor SSH Servicecheck process sshd with pidfile /var/run/sshd.pidstart program = "/etc/init.d/ssh start"stop program = "/etc/init.d/ssh stop"if failed port 22 protocol ssh then restartif failed port 22 protocol ssh then alertif 5 restarts within 5 cycles then timeoutgroup programs
   
   # Check servicescheck system localhostif loadavg (1min) > 4 then alertif loadavg (5min) > 2 then alertif memory usage > 75% then alertif cpu usage (user) > 70% then alertif cpu usage (system) > 80% then alertif cpu usage (wait) > 20% then alert

3. Set Monit to start automagically. Open the file /etc/default/monit and change the startup value to 1. You can now start monit with the following command.

   sudo /etc/init.d/monit start

If you want to be able to access Monit’s web based interface remotely then check out the Ubuntu Geek tutorial for more information. I am not enabling this ability in my kiosk at present.

Monitoring FireFox performance

By using Monit we are able to get good alerts regarding the overall health of our Kiosk. But Monit doesn’t tell us is how our Kiosk client (Firefox) is behaving. If Firefox starts to eat up a percentage of your kiosk’s available memory or CPU power you should be notified early.

I myself am not that great at building BASH scripts so I opted to create a PHP script which tests a few conditions and sends an email if Firefox isn’t running or is using too many resources. This script can be run as a cron job every few minutes. My PHP script requires the open source class PHPMailer which makes sending email from PHP a snap.

Here is my php script.

 /*** This script gets the CPU and MEM usage of Firefox*/$cpu = 0;$mem = 0;$failed = false;

// Get the PID of firefox$pid = exec('pidof firefox-bin');

// If firefox is running get memoryif ( $pid ){$status_str = exec('ps aux | grep "'. $pid .'" | grep -v grep');$status = explode( ' ', $status_str );// Strip blanksforeach( $status as $k=>$v ){  if ( trim($v) == '' ) unset($status[$k]);}$status = array_values($status);

$cpu = $status[2];$mem = $status[3];

if ( $cpu >= 60 || $mem >= 60 ){   $failed = true;   $message = "Firefox is using $cpu% of CPU and $mem% of MEM";}

} else {

// Firefox is not running$failed = true;$message = "Firefox is NOT running";

}

if ( $failed ){$body = date('l jS of F Y h:i:s A',time() )."nn";$body .= $message;

// Create and Send Emailrequire_once( "/class/phpmailer/class.phpmailer.php");

$mail = new PHPMailer();$mail->From     = ' firefox@mykiosk ';$mail->FromName = " Firefox Status ";$mail->Host     = 'mail.shawcable.com';$mail->Mailer   = "smtp";

$mail->Subject = "Firefox Issue on ArtTouch";$mail->AddAddress(" someone@domain.com ");

$mail->IsHtml(0);$mail->Body    = $body;

// LOG RESULTSif(! $mail->Send() ) {   error_log("There was an error ending Firefox Performance Alert " . $mail->ErrorInfo );}}

If anyone wants to turn this into a bash script instead of PHP and share it that would be great.

The easiest way to build a kiosk application is to customize a web page to serve as the kiosk interface. Launch the web page in a browser and set the browser to run in full screen mode and voila, instant kiosk. To turn it into a touch screen kiosk all you need to do is buy an LCD touch screen monitor and your all set.

This basic solution might work fine if you’re always standing next to the computer and can enable full screen mode every time it reboots and also stop anyone from mucking around with your computer should the browser crash and they get access to the desktop.

Setting up a kiosk which can run in a public space and have reasonable enough security to prevent someone from mucking around with it should the browser crash or computer crash takes a little more thought.

I’ve addressed the overall solution in two parts.

1) The server/host computer
2) The browser

1) The Server / Host Computer

The computer used to host a touch screen application needs some thoughtful consideration. You want something that will offer good reliable performance and also prevent anyone who might be feeling a little malicious from causing the computer or your application any harm. My touch screen system does NOT have a keyboard attached to it which certainly helps in providing a certain level of security but I still need to take steps to make sure the user cannot get access to the desktop, general file system or any application other than the Firefox browser.

For my solution I decided to run Ubuntu 7.10 and use Blackbox as the default desktop environment. Ubuntu allows me to run an apache http server as well as mysql locally. This keeps the application running very fast, provides me with dynamic data and requires no internet connection. Your kiosk application could be simple straight HTML running locally or running off a remote web server whatever suits your needs. Using Ubuntu (or really any flavor of linux you’re comfortable with) keeps your kiosk highly customizable.

Using the Blackbox windows manager instead of the default Gnome or KDE desktop environment allows me to lockout the user from accessing anything other than Firefox and keeps your kiosk as a light weight, fast computer with a single focus.

How to set up the server/host computer

1. Download and install Ubuntu 7.10
   A default install is fine. The main user you will create during install will be considered a super user. You’ll later create a user account specifically for accessing the touch screen application. Click here to get Ubuntu

2. Install Apache, PHP5 and MySQL (Optional)
   My specific application uses dynamic data and requires both Apache and PHP. Using an Ubuntu computer makes it easy to run these services locally and means my computer doesn’t require a dedicated internet connection. Although having one makes remote administration and updates easier. To install these on the computer just reference the UbuntuGuide.org wiki

3. Create a limited user account
   While your touch screen application is running you’ll want to have a limited user account logged into the computer.

   To create this account log into Ubuntu using the account you created during install and select :

   System > Administration > Users and Groups

   From the User settings window select:

   Add User
   
   From the New User Account window fill in the Basic Settings for your user. For the purpose of this example we will use the username: touchuser. After you’ve provided a user name and and password select the User Privileges tab. Unselect all options which are not a requirement of your touch screen application. For my application I blocked access to all external hard drives, cdroms, floppies and log monitors.

4. Install Blackbox Window Manager
   Blackbox is a fast, lightweight and minimal windows manager for the X Window System. You can learn more about it here. Blackbox will be setup as the default desktop for our host computer. I use Blackbox because it helps prevent the touch screen user from having access to any applications unless they are specifically enabled via Blackbox.

   To install blackbox open up the terminal and type the following command.

   sudo apt-get install blackbox blackbox-themes

   Next we need to create a .blackboxrc file and a .blackbox directory. These will be used to define our configuration settings for our desktop and define what applications touchuser has access to. Note: we are going to do this in the home directory of the touchuser account not the account we are logged in as. After we create the file and directory we set permissions on them.

   sudo mkdir /home/touchuser/.blackboxsudo touch /home/touchuser/.blackboxrcsudo chown touchuser /home/touchuser/.blackboxsudo chown touchuser /home/touchuser/.blackboxrcsudo chgrp touchuser /home/touchuser/.blackboxsudo chgrp touchuser /home/touchuser/.blackboxrc

5. Define the .blackboxrc File
   Using your favorite text editor add the following definitions to the .blackboxrc file. Note the reference to /home/touchuser/.blackbox/menu. This file will be created in the next step.

session.styleFile: /usr/share/blackbox/styles/Graysession.menuFile: /home/touchuser/.blackbox/menusession.screen0.workspaces: 1session.screen0.workspaceNames: My Touch Screensession.fullMaximization: True

NOTE: If you decide to run Blackbox now you may find yourself unable to complete the rest of the steps in this tutorial. All the steps for setting up the host computer assume you are logged into Ubuntu using the user created during install and running a Gnome session. If you’re logged into Blackbox press CTRL + ALT + BACKSPACE to return to the Ubuntu login screen. You can select the ‘options’ button to change what windows manager is used when you log in.

6. Create the Blackbox menu file
   By default the Blackbox desktop provides no icons. To launch a program the user needs to right-click on the desktop to see a menu of available applications. We want to provide our own menu settings so that the only application available to our user is Firefox. This is really only of limited use as right-clicking on a touch screen is impossible as far as I know, but in case someone figures out how to do it we don’t want them to have access to anything other than the browser.

   Enter the following commands into the terminal to create the menu file and set appropriate permissions.

   sudo touch /home/touchuser/.blackbox/menusudo chgrp touchuser /home/touchuser/.blackbox/menusudo chown touchuser /home/touchuser/.blackbox/menu

   To limit our menu to only provide access to Firefox open up the menu file and add the following.

   [begin] (ArtTouch)[exec] (firefox) {firefox}[end]

   For more details on configuring blackbox and creating menus see the blackbox wiki
   

7. Install iDesk
   Blackbox doesn’t by default support desktop icons which is okay since we are building a minimal system. Well what if the Firefox browser crashes and the touch screen user is left starting at an empty desktop with no ability to right-click and relaunch the browser. To provide a solution to this problem we are going to install iDesk which adds icon support to minimal window managers such as Blackbox.

   To install iDesk open a terminal and provide the following command

   sudo apt-get install idesk

   Once iDesk is installed we need to create an .ideskrc file for configuration settings and create an .idesktop folder where we can define our icons.

   sudo touch /home/touchuser/.ideskrcsudo mkdir /home/touchuser/.idesktopsudo chgrp touchuser /home/touchuser/.ideskrcsudo chgrp touchuser /home/touchuser/.idesktopsudo chown touchuser /home/touchuser/.ideskrcsudo chown touchuser /home/touchuser/.idesktop

   Next open up the .ideskrc file and add the following

   table ConfigBackground.Color: #C2CCFFendtable ActionsExecute[0]: left singleClkend

   This is a very minimal use of iDesk configuration options for more see the iDesk Usage Wiki
   

8. Create an Icon and define icon commands
   Next we need to create an icon for our desktop. You could use the standard Firefox icon but you’re probably best to create a PNG specifically for your touch screen application. Create a PNG file (for example touchicon.png) and stick it in the .idesktop directory. To add the icon to the desktop we need to create a file with a .lnk extension and place it in the .desktop directory also.

   sudo touch /home/touchuser/.idesktop/touchicon.lnksudo chown touchuser /home/touchuser/.idesktop/touchicon.lnksudo chgrp touchuser /home/touchuser/.idesktop/touchicon.lnk

   Open the touchicon.lnk file and add the following. Adjust ‘caption’, ‘tooltip’, ‘width’, ‘height’ and ‘x/y’ coordinates to suit your needs.

   table IconCaption: Touch ApplicationToolTip.Caption: Touch Me To LaunchCommand: firefoxIcon: /home/touchuser/.idesktop/touchicon.pngWidth: 400Height: 275X: 100Y: 100end

9. Create Blackbox startup script
   Now that we have a minimal desktop and we also have an icon for our desktop we need to make sure that iDesk is automatically run when Blackbox runs (by default it doesn’t). To do this we are going to create a startup script for Blackbox.

   Create a file called .bbstartup.sh in your touchuser’s home directory

   sudo touch /home/touchuser/.bbstartup.shsudo chgrp touchuser /home/touchuser/.bbstartup.shsudo chown touchuser /home/touchuser/.bbstartup.shsudo chmod x+ /home/touchuser/.bbstartup.sh

   Add the following to the .bbstartup.sh file

   #!/bin/shidesk &exec blackbox

   Now we need to change the path of exec blackbox in /usr/share/xsessions/blackbox.desktop. Start by making a backup

   sudo cp /usr/share/xsessions/blackbox.desktop /usr/share/xsessions/blackbox.desktop_backup

   Edit /usr/share/xsessions/blackbox.desktop and make the following changes to Exec and TryExec definitions

   [Desktop Entry]Encoding=UTF-8Name=BlackBoxComment=Highly configurable and low resource X11 Window managerExec=/home/touchuser/.bbstartup.shTerminal=FalseTryExec=/home/touchuser/.bbstartup.shType=Application

10. Set Auto-login and define Blackbox as default window manager
    The final step in configuring our server/host computer is to set up Ubuntu to automatically log into our touchuser profile and to use Blackbox as the default windows manager. This ensures that if the computer crashes or reboots that it immediately goes into kiosk mode. (note we’ll further improve this by making the browser automatically launch later).

    Open the Login Window Preferences by selecting:

    System > Administration > Login Window

    Under the General tab select ‘Blackbox’ for default session.
    Under the Security tab select ‘Enable automatic login’ and select the user ‘touchuser’

Hopefully after all that you should now have a basic set up to run a kiosk. When the computer boots it should load directly to a Blackbox desktop that allows the user to launch Firefox and only Firefox. In the next step of the process we are going to modify a few settings in Firefox to make sure it loads our touch screen application as it’s homepage and automatically launches in full screen mode when the computer boots up.

NOTE: If the computer is running in kiosk mode and you want to be able to login as your super user and get back to a fully functional Gnome desktop all you need to do is plug in a keyboard and press CTRL + ALT + BACKSPACE. This will kill the Blackbox session and bring you to the Ubuntu login screen.

2) The Browser

Now that we have our host computer set up and running we’ll want to make a few small changes to the preferences of our Firefox browser so that it performs well as a kiosk client.

1. Set the Home Page
   This should be pretty obvious. When the browser launches we want it to automatically load our Kiosk application. For my solution I have the Kiosk application running locally as a Flex/PHP application. Your kiosk doesn’t have to be Flex, it could be a Flash or simple HTML web page and it could be running remotely or locally. Whatever the case may be you’ll want to set the URL location of your application as the homepage for Firefox.

2. Disabling session restore
   When Firefox crashes or the computer is shutdown before closing the browser, Firefox will by default ask if you want to restore your previous session or start a new one the next time it launches. This is kind of a pointless feature for the kiosk as you’ll likely always want it to start a new session. You can disable this feature by logging into your kiosk as ‘touchuser’ launching Firefox and entering ‘about:config’ in address bar.

   Find the preference settings for browser.sessionstore.resume_from_crash and browser.sessionstore.resume_session_once and set their values to false.

3. Getting the browser to automatically launch in fullscreen mode.
   When the browser is launched in order to provide a true kiosk type environment we want it to load in full screen mode giving the user no access to the navigation bar and locked out of most shortcuts. The easiest way to do this is to install one of the many ‘Full Screen‘ extensions available for Firefox.

   The one I recommend is R-Kiosk. For the pure purpose of running a web based Kiosk it does a very good job. While logged in as ‘touchuser’ Visit this link in Firefox and click the ‘Add To Firefox‘ button.

   NOTE: After this component is added to Firefox you’ll be unable to make any preference or configuration changes to Firefox unless you launch it in safe mode. For information on how to run Firefox in safe mode, visit this link.

4. Setting the browser to automatically launch after boot
   When our kiosk system is booted it will automatically login as with the touchuser profile and load our Blackbox desktop. Now we also want Firefox to automatically launch so that after the system boots the user is presented with our Kiosk application running in all it’s full screen glory.

   This is very simple to accomplish by adding one line to the Blackbox startup script we created in step 9 when setting up the host computer. You’ll need to log into Ubuntu as the user you defined during install for this step.

   Open /user/touchuser/.bbstartup and add the following line

   #!/bin/shidesk &/usr/bin/firefox &exec blackbox

If everything has gone as I hope, you should have a fully functioning kiosk system. The only thing left to do is buy yourself a fancy touchscreen LCD monitor and plug it in.

References for this setup can be found at the following links.
HOWTO: A Blackbox Guide
Blackbox Wiki
iDesk Wiki