You can't install Google Chrome, but you can install Chromium. As other people have posted, Chromium is the code base out of which Google Chrome is compiled. Chromium is an open-source version of this browser. Simply type the following.
$ sudo apt-get install chromium-browser
If you receive any errors running this command, try running
$ sudo ...
I have a Raspberry Pi 2 running Raspbian Jessie with Chromium 45 installed. I found that you need to copy the existing autostart file to your local:
mkdir -p /home/pi/.config/lxsession/LXDE-pi/
cp /etc/xdg/lxsession/LXDE-pi/autostart /home/pi/.config/lxsession/LXDE-pi/autostart
So edit this local version:
You can enter the following three xset commands
xset s off # don't activate screensaver
xset -dpms # disable DPMS (Energy Star) features.
xset s noblank # don't blank the video device
file (You should insert these after the first line).
I had the same issue. At raspberry pi forum I found this:
You need to edit your script that's starting X. In the default build with lightdm the file to edit is
in the SeatDefaults section it gives the command for starting the X server which I modified to get it to turn off the screen saver as well as dpms
It appears there is now a different autostart file to use located in /etc/xdg/lxsession/LXDE-pi/autostart
To get Chromium to autostart follow these instructions
sudo nano /etc/xdg/lxsession/LXDE-pi/autostart"
Add the following line:
/usr/bin/chromium --kiosk --ignore-certificate-errors --disable-restore-session-state "http://www.domain.com"
For Raspbian (Jessie), this solution worked for me:
Create a new .desktop file in ~/.config/autostart/, e.g.
sudo nano ~/.config/autostart/autoChromium.desktop
Then add the following:
Exec=/usr/bin/chromium-browser --noerrdialogs --disable-session-crashed-bubble --disable-infobars --kiosk http://www.website.com
This answer is outdated and should no more be followed. See https://raspberrypi.stackexchange.com/a/56231/42933 for—since October 2016—the most appropriate answer.
As already shown in the previous answer, the general idea is to use Chromium builds from Ubuntu. Using their staging repository for Chromium security updates is probably not the only way, but not ...
You can apply hildred's suggestion permanently by creating a ~/.xinitrc file:
exec chromium --kiosk
This will then be applied if you are using a graphical login, so that you do not have to boot to console. To test it from the console, try startx with no arguments.
As far as I know Google does not (yet) distribute Chrome binaries for Linux/ARM. (The only ARM binaries are for Android and these will not be compatible.)
You might be able to cross-compile Chromium for Linux/armel (I have not tried but I am willing to bet that the RasPi itself is not powerful enough to compile it.)
Also keep in mind that if you were able ...
Edit this file
sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
And add this:
@xset s off
@xset s noblank
@chromium-browser --kiosk http://google.com/ # load chromium after boot and open the website in full screen mode
Then reboot. Chromium should automatically launch in fullscreen mode after the desktop has loaded.
Doable, but if chromium is minimised, you will still see a window manager/background.
I would recommend using a lightweight window manager, like openbox with an empty menu file ~/.openbox/config/menu.xml, so a user cannot active any programs.
Install a window manager
Configure window manager settings (blank config so no other programs can be ...
Use these commands to install chromium-browser on Jessie (not Wheezy):
OpenELEC appears to be an intentionally confined, minimal operating system. I assume it is simple to use, partially because you cannot do much with it beyond Kodi.
Part of this is that it does not have much of a "package management" system. You cannot install a vast range of software the way you could on Raspbian; you are limited to the various "add-ons". ...
Axel Beckert is correct in his answer, however any version of Chromium after 48 wont run on armhf (which is what Raspberry Pi 2 & 3 use) because of this bug: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184
To correct this I modified DolbyOver's answer as follows:
Okay so I found a solution here: https://www.raspberrypi.org/forums/viewtopic.php?t=191087
use raspi-config to enable OpenGL (Full KMS)
remove "--disable-gpu-compositing'' from /etc/chromium-browser/customizations/00-rpi-var
is all you need to do to get the https://get.webgl.org cube spinning.
Works for me!
There is currently no easy way to get a recent Chromium build on the rpib+.
If you just want chromecast you could try some projects that don't use Chromium because the rpib+ is RAM limited (limiting Chromium functionality) and has a less popular CPU architecture (limiting your install options).
If you really want a recent version of ...
Raspbian Jessie Chromium boot to fullscreen:
*Loaded Chromium-browser for Raspbian Jessie based on this site:
*And got the Chromium "boot to fullscreen" from this guidance:
Create a file called ...
By default the Pi the auto-logon X environment is done with credentials of the pi user. The config setting's of the Xserver environment of this user is in /home/pi/.config/lxsession/LXDE-pi/autostart, NOT in /etc/xdg/lxsession/LXDE-pi/autostart (this is the environment for the root user).
1) I dunno why --disable-infobars didn't work for you. This works well for me:
chromium-browser --kiosk --disable-infobars \
2) A better way to refresh the browser (contents) would be to sent it Control-R?
e.g. in your browser startup script, do:
(while sleep 200; do xdotool key ctrl+R; done) &
(I also send ...
A segmentation fault will occur, for example, if a program attempts to access memory that does not belong to it; then the kernel brings a hammer down. This is the result of a programming error.
It should absolutely unequivocally not be possible for you to force an end-user tool to do this, regardless of how you have used it. So that would be a bonefide ...