I know this thread is a little old but I just got this working well chromium for a project at work I hope this helps others.
Requirements:
* Any Raspberry Pi 2 or 3
* Raspbian Jessie Lite image
* SD / microSD card (At least 2GB or higher.)
* Keyboard and Mouse
* Monitor
* Internet connection
Part 1 – Prep The Base
1. Download the latest Raspbian Lite image.
2. Burn Raspbian Image to SD card
3. Insert the SD / microSD card into the Pi.
4. Connect the Pi to the Internet
5. Connect your Monitor and input devices.
6. Turn on the Pi and log in. The username is pi and the password is raspberry.
7. Expand the file system, set overscan to disable and configure internationalization settings which include language, keyboard layout, and regional settings. Type in:
8. Once settings are done and file system is expanded Reboot Pi:
9. Log into the PI again and update all files. Type in:
Code: Select all
sudo apt-get update
sudo apt-get upgrade
10. Reboot the Pi by typing in:
Part 2 – Add Needed Packages
* Auto Log-in: nodm
* X command Line : xinit
* Ttf fonts for browser: ttf-mscorefonts-installer
* Auto X start: simple .xsession script
* Window Manager: matchbox
* Browser: Chromium (this will probably work with any browser)
1. Add apt-get repository just in case. Type in:
Code: Select all
sudo apt-get install –y software-properties-common python-software-properties
2. To install the packages we need, Type in:
Code: Select all
sudo apt-get install –y nodm matchbox-window-manager xinit ttf-mscorefonts-installer
3. To install Chromium on Raspbian Jessie, follow these procedures from Krusti8:
viewtopic.php?t=121195
Code: Select all
wget -qO - http://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
echo "deb http://dl.bintray.com/kusti8/chromium-rpi jessie main" | sudo tee -a /etc/apt/sources.list
sudo apt-get update
4. To proceed with the chromium install we need to make a repair to the keyring (Thanks to GhostRaider for supplying the fix)
Sometimes when doing sudo apt-get-update or some similar command, you may get an error saying:
W: GPG Error: SOMEWEBADDRESS: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY SOMENUMBER
This is a simple fix. In Terminal, type in:
Code: Select all
sudo apt-get install –y debian-keyring
5. Open Terminal as ROOT. Type in:
6. Then in the Terminal, type in:
Code: Select all
gpg --keyserver keys.gnupg.net --recv-key SOMENUMBER
gpg -a --export SOMENUMBER | sudo apt-key add –
7. Reboot the PI Type in:
8. Install Chromium Browser, Type in:
Code: Select all
sudo apt-get update
sudo apt-get install –y chromium-browser
Part 3 – Finalizing the kiosk
1. Start nodm at boot and configure the user that will log in. Type in:
2. Change settings in file to the following:
3. Create the new .xsession file in the home directory. Type in:
4. Write in the following code:
Code: Select all
#!/bin/bash
#Turn off Power saver and Screen Blanking
xset s off -dpms
#Execute window manager for full screen
exec matchbox-window-manager -use_titlebar no &
#Execute Browser with options
chromium-browser --noerrdialogs --kiosk --incognito http://www.typeinyouraddress.com
5. Configure your network settings. Type in:
Code: Select all
sudo nano /etc/dhcpcd.conf – for Ethernet
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf -for wireless
6. Add the following to the bottom:
Code: Select all
(For Ethernet)
interface eth0
static ip_address=192.168.1.101/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1
(For Wireless)
network={
ssid=”ESSID”
psk=”your_wifi_password”
}
7. Clean up for good measure Type in:
Optional from eternaltyro
1. Open /boot/cmdline.txt and do the following changes: (without the quotes of course)
* Locate the section that says “console=tty1? and make it “console=tty4“. This pushes the logs to the fourth virtual terminal
* Add a space in the end and add “loglevel=3“. This sets the severity of the logging level to “warning and above”.
* Add a space in the end of the line and add “logo.nologo“. Hides the little raspberry fruit logo.
Thanks to all contributions for helping me figure this out
https://blog.qruizelabs.com/2014/04/29/ ... hbox-uzbl/
viewtopic.php?f=66&t=133691
viewtopic.php?t=121195