as a doc reference, the way i install and use Mir Kiosk and Chromium under 18.04 Server.
At first install mir-kiosk: sudo snap install mir-kiosk
Then chromium-mir-kiosk, please note to add the “devmode” flas, otherwise the screen will remain black: sudo snap install chromium-mir-kiosk --beta --devmode
At last, don’t forget to daemonize mir-kiosk to start after boot: sudo snap set mir-kiosk daemon=true
To customize the startup url for chromium use: sudo snap set chromium-mir-kiosk url="https://yoururl.com"
@alessio I have tested the kiosk following this post. I meet an error. My website can display in the screen but it is not click and any other operation.
First, my setup a ubuntu 18.04 server with vmware fusion. Then I ssh my machine and execute some commands which look like below:
At here, everything is good. But when I try to click or scroll the page, the screen goes into black. I have collect the mir-kiosk and chromium-mir-kiosk log:
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: (EE)
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: Fatal server error:
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@8.create_pool
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: (EE)
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: [8343:8343:1212/094725.269117:ERROR:x11_util.cc(103)] X IO error received (X server probably went away)
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: i3: Cannot open display
2019-12-12T09:47:25Z chromium-mir-kiosk.chromium-mir-kiosk[8133]: [8317:8317:1212/094725.283921:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away)
This looks like the problem addressed by https://github.com/snapcore/snapd/pull/7409 which is odd as you’re running chromium-mir-kiosk as a daemon, and that shouldn’t hit the same problem.
Can you check dmsg?
dmesg | grep mir-kiosk
You’re looking for an apparmor="DENIED" for a file associated with chromium-mir-kiosk. It might be something like /run/user/0/snap.chromium-mir-kiosk/xwayland-shared-*.
If that is what is happening, you can temporarily work around this by reinstalling mir-kiosk with --devmode but for a permanent fix we would need to update snapd.
Alternately, try using wpe-webkit-mir-kiosk as chromium-mir-kiosk is unsupported.
Hello @alan_g
I am new to Mir-Kiosk and find it very appealing for my kind of project. I am also taking this route of installing it on Ubuntu Server 18.04. Please, is it possible to run my custom portable Qt5 WebEngine app packaged with AppImage on Mir-Kiosk?
That depends on your app: does it have a Wayland backend? The first few steps of this tutorial show how to test this: Make a Wayland-native Kiosk snap.
In theory, mir-kiosk can run any Wayland app. In practice though, the specific approach described in this thread runs the mir-kiosk and app “daemons” as root. That isn’t a concern when they are confined snaps, but you may not consider this to be a good idea with AppImage.
(You don’t have to follow this specific approach to use mir-kiosk, and the first thing to determine is whether your app works with Mir.)
I followed your post. The chrome kiosk is work on Ubuntu core. I have one issue. The screen restarts by it self once a while. Its like some kind of schedule. I checked the pid, chrome-browser ids did not change. Do you have any idea why this happens?
