I have been using mir-kiosk to build kiosk snap. I also successfully build one and deployed it. After I tried the same configurations and setting and try to run mir-kiosk and electron kiosk snap on another system but i get the following error.
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: [2021-02-10 11:33:28.086839] < - debug - > gbm-kms: MIR_MESA_KMS_DISABLE_MODESET_PROBE is set
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: [2021-02-10 11:33:28.086851] < -warning- > gbm-kms: Failed to detect whether device /dev/dri/card0 supports KMS, but continuing anyway
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: [2021-02-10 11:33:28.086866] <information> gbm-kms: Using DRM device /dev/dri/card0
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: Failed to create /root/.cache/mesa_shader_cache for shader cache (Permission denied)---disabling.
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: ERROR: /build/mir-K7y0Z4/mir-2.2.0/src/platforms/common/server/kms-utils/drm_mode_resources.cpp(41): Throw in function mir::graphics::kms::DRMModeResUPtr {anonymous}::resources_for_drm_node(int)
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: Dynamic exception type: boost::wrapexcept<std::system_error>
2021-02-10T11:33:28Z mir-kiosk.daemon[27832]: std::exception::what: Couldn't get DRM resources: Operation not supported
2021-02-10T11:33:28Z systemd[1]: snap.mir-kiosk.daemon.service: Main process exited, code=exited, status=1/FAILURE
2021-02-10T11:33:28Z systemd[1]: snap.mir-kiosk.daemon.service: Failed with result 'exit-code'.
2021-02-10T11:33:29Z systemd[1]: Stopped Service for snap application mir-kiosk.daemon.
I am not able to see a orangish fade like before. just a black screen. Above are the logs of the same. Kindly help me on this.
Well, there is no differemce in the systems. Both uses ubuntu desktop 18.04. To add both have nvidia drivers installed for our particular tasks. But it worked on previous machine and popping up error on this new one. Can you guide to overcome this error if its related to graphics?
perhaps @alan_g has some idea about the DRM errors here, i’m also not sure why the snap tries to write to /root/.cache (it’s a daemon and should better point its home to $SNAP_DATA or $SNAP_COMMON)
Not sure what is happening here. Unfortunately the interesting part of the log messages is truncated.
From what I can see, mesa is falling back to s/w rendering because it lacks drivers to use the hardware directly. I suspect the DRM errors are related to the unsupported stack.
What hardware and OS is this running on?
I suspect it is llvmpipe that tries to use /root/.cache. (Not sure how it chooses that location but I take the point about $HOME.)
I am using ubuntu desktop 18.04 as an OS and i have nvidia drivers installed in it. Is there any workaround to solve the DRM issue?
On my previous machine with same configurations, mir-kiosk started and ran perfectly without any error.
BUT enabling DRM won’t solve all your problems as the mir-kiosk snap requires drivers that support gbm-kms. (It does not bundle the alternative “eglstream-kms” platform it would need to work with Nvidia.)
Hi @shakib1126, unfortunately due to how Nvidia drivers work (matching kernel module and userspace), we’ve not found a way to have snaps reliably work across releases:
This is a ThinkPad X61s running Ubuntu Core 16 on the bare metal, no VM. perfectly as expected (including “orange fade to black animation”) up to the point of It is just that the display on the device only shows a black screen and a The problem lies in the combination of the chromium-mir -kiosk snap and your setup.
this topic is about systems where the orange splash does not show up at all, if you see it but have a black screen afterwards, this is different … you should start a new discussion in a fresh thread instead …
Okay so I tried @alan_g reference and instructions on running mir-kiosk on nvidia drivers and thankfully mir-kiosk is running just perfect without any errors and i am able to run electron kiosk app on my ubuntu system.
Thankyou @ogra, @alan_g and @Saviq for the instant support and guidelines provided.
How can I install Mir-kiosk 2.2.0 on my system? I am facing issues in new version of mir-kiosk and previous version that is 2.2.0 seems to work seamlessly for my use case. @ogra@alan_g
Snap revert seems to only work if there is a previously installed mir-kiosk version. I want to install mir-kiosk 2.2.0 on a fresh machine . We have already ran our electron kiosk application with mir-kiosk 2.2.0 with nvidia driver version 440.59.
Specific issue I am facing with mir-kiosk 2.3.2 is the cursor gets stuck on top left corner and wherever you click any part of the screen, the click gets executed at top left corner everytime.
Note: I have already used this command - sudo snap set mir-kiosk cursor=software
As mentioned by @alan_g at Call for testing: mir-kiosk that mir-kiosk 2.3.2 has rectifications which corrects pointer sticking to the side of the screen. However, It used to work fine for my electron kiosk snap but after updating to mir-kiosk 2.3.2, the pointer seems to get stuck on top left corner everytime and also the click gets executed at top left corner.
Is there a solution for this? or if you can guide me on how can I use the previous mir-kiosk version i-e 2.2.0 on a fresh machine, or how can I build mir-kiosk 2.2.0 snap from the source code on your github. This would be highly helpful to me as mir-kiosk is one of our major part of deploying our software. @alan_g@ogra@Saviq
The change you refer to does indeed allow a client snap (such as yours) to request the cursor be locked in position. If the cursor shouldn’t be locked then, ideally, your snap not ask for it to be locked.
However, it is possible to disable the pointer confinement protocols in mir-kiosk to prevent the request being made using drop-wayland-extensions=zwp_pointer_constraints_v1:zwp_relative_pointer_manager_v1 in the configuration file described in Configuring mir-kiosk: a masterclass.
