The updated the snapcraft.yaml according to my needs. But after snapping when I installed it, it printed some logs and then got stuck and is not moving forward.
Problem fixed. I looked the logs carefully and found out that a file was missing
2021-09-03T12:20:29Z cluemaster-mediadisplay.cluemaster-mediadisplay[1560]: /snap/cluemaster-mediadisplay/42/usr/local/bin/x11_kiosk_launch: 19: bin/prepare-launch: not found
Now there is only one issue. I can’t hear the sounds when playing a video from the snap. What you have any idea as to what might be the problem. Or should I open another thread regrading the sound issue?
… and make sure the subdir it gets installed in is in your LD_LIBRARY_PATH
if you do not use any desktop launcher (i.e. from an extension or the snapcraft desktop launchers github tree) you might also need to set PULSE_SERVER to point to “$XDG_RUNTIME_DIR/…/pulse/native”
connect your snaps audio-playback interface plug to pulseaudio
thanks @ogra I will try and let you know the results. However I am facing one more issue, the snap doesn’t auto start until I connect to the core pc using ssh. Do you have any idea what might be the issue?
you log in to the device, for seeing the journal you use sudo journalctl to read the journal … there is also the systemctl command as well as snap logs <yoursnap> to see infos about errors and issues.
2021-09-05T07:03:07Z cluemaster-mediadisplay.cluemaster-mediadisplay[1438]: Watches established.
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.083398] <information> mirserver: Starting
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.289641] < - debug - > mirserver: Not using logind for session management: Failed to find active session
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.289791] < - debug - > mirserver: Not using Linux VT subsystem for session management: Failed to find the current VT
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.289812] < - debug - > mirserver: No session management supported
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.294145] <information> VT switch key handler: No VT switching support available: MinimalConsoleServices does not support VT switching
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.294376] <information> mircommon: Loading modules from: /snap/cluemaster-mediadisplay/44/usr/lib/x86_64-linux-gnu/mir/server-platform
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.294451] <information> mircommon: Loading module: /snap/cluemaster-mediadisplay/44/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-wayland.so.19
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.294499] <information> mirserver: Found graphics driver: mir:wayland (version 2.3.3) Support priority: 256
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.294618] <information> mirserver: Selected driver: mir:wayland (version 2.3.3)
Do you think it might be related to this line
2021-09-05T07:03:10Z cluemaster-mediadisplay.cluemaster-mediadisplay[1437]: [2021-09-05 07:03:10.289641] < - debug - > mirserver: Not using logind for session management: Failed to find active session
no, that just means it will not use session management, but the lines below show it started fine … the content of the journalctl output right after boot might be more interesting to see if it was even attempted to be started and if it failed with any errors to do so …
hi @ogra. Sorry, it took some time for me to generate those logs, because the auto start issue was kinda random. I noticed something strange, that is when I shutdown the PC by directly plugging off the power cord, the app auto starts on the next boot, but whenever, I use DBUS to restart or shutdown the core PC, the app does not auto starts the next time. I need to log into it using ssh and then only the app starts on the core PC.
thanks, i will add the layout to my snapcraft.yaml.
the app also doesn’t produce any sounds, did you find anything related to sound in the logs? thanks again
pulse itself seems to be starting fine, if all interfaces are connected and you use the correct version, it must be an app (or app environment) issue …