I have a Pi 3 and I'd like to start Chromium with a fixed address on startup. I've read a lot of tutorials on this, but most of them are outdated and use the full Jessie with Pixel Desktop package.
I'd like to keep it slim, and just installed Jessie Lite. I've found this thread Autorun browser kiosk with Jessie Lite that addresses the exact issue I have, but unfortunately all links provided are not very helpful.
I think that I need to start some kind of x server on startup. Then Chromium should start in kiosk mode and use the window from the x server to display it's content.
My naive approach was just to fire up Chromium. Of course I haven't started a x server, so I get the following error:
pi@raspberrypi:/ $ chromium-browser [5381:5381:1216/110715:ERROR:browser_main_loop.cc(271)] Gtk: cannot open display:
I read something about
lightdm so I installed it, and tried
pi@raspberrypi:/ $ sudo lightdm
and voilà, it fires a desktop, where I can start Chromium. Unfortunately, it displays a window with an error, where I can klick
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name org.freedesktop.PolicyKit1 was not provided by any .service files
I can start Chromium, but I'm a little stuck here:
- How would I start lightdm AND Chromium on startup?
- Is lightdm the right choice for this? Or is there an easier xserver where one just starts a single application, without the whole desktop stuff?
- How can I get rid of the error when lightdm starts?
piuser there are security issues with that unless you disable its
sudopowers. There are other ways to accomplish the same thing without an autologin, since a privileged process can start X as an unprivileged user -- the one thing you do not want to do is start Chromium as root.