What is snap list? It seems that you also have mir-kiosk installed?
1 Like
For what it’s worth if you install Ubuntu Core, then the ScummVM snap works fine with mir-kiosk. I was testing this with Ubuntu Core and it installed fine for me.
Also, the message about multiple candidates found seems to be harmless because on a successful (arm64) install on Ubuntu 20.10, I see the same message but things still install successfully.
I think that the issue really is with the install-snap change in progress error message, it seems that some hook is trying to start/stop the snap and snapd thinks that this task conflicts with installing the snap.
I think I did install mir-kiosk at some point, but it was just a blank screen that didn’t work. When I get in I will share the snap-list results.
that is exactly what mir-kiosk is supposed to show 
its a display server, nothig more (it should also show a mouse pointer if you have a mouse attached)
Haha, goes to show I have no idea what its intended function was. Forgive my noobishness
I’m excited to learn more about Linux, I’ve done IT and networking most of my life but have been in the safespace of x86 and Windows. If anyone have any books or beginner projects I’d be down for recommendations! Getting the Rpi and working within bash I’ve already learned a lot, but at least once a week I have to yell “I’d have done this 20 times already if it was Windows, hell even Dos!” but I recognize that my ignorance is the problem and not the platform, lol.
1 Like
Okay, had a chance to try again tonight. 100% fresh install of RpiOS, all I did was update:
sudo apt update
sudo apt full-upgrade
then install snap:
sudo apt update
sudo apt install snapd
then rebooted:
sudo reboot
Then tried to install the scummvm snap:
sudo snap install scummvm
2020-12-02T21:54:27-07:00 INFO snap “scummvm” has bad plugs or slots: audio-playback (unknown interface “audio-playback”)
error: cannot perform the following tasks:
- restart of [scummvm.daemon] (# systemctl restart snap.scummvm.daemon.service
Job for snap.scummvm.daemon.service failed.
See “systemctl status snap.scummvm.daemon.service” and “journalctl -xe” for details.
)- restart of [scummvm.daemon] (exit status 1)
It looks like I’m getting a different audio playback error now? I saw a different forum post about this particular issue here: Trouble with Snap ScummVM on Raspian
systemctl output:
"pi@raspberrypi:~ $ systemctl
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p1.device loaded active plugged /sys/dev
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p2.device loaded active plugged /sys/dev
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0.device loaded active plugged /sys/devices/platf
sys-devices-platform-scb-fd500000.pcie-pci0000:00-0000:00:00.0-0000:01:00.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card1.device loaded
sys-devices-platform-scb-fd580000.ethernet-net-eth0.device loaded active plugged /sys/devices/platform/scb
sys-devices-platform-soc-fe00b840.mailbox-bcm2835_audio-sound-card0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0-hci0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe300000.mmcnr-mmc_host-mmc1-mmc1:0001-mmc1:0001:1-net-wlan0.device loaded active plugged /sys/devices/pl
sys-devices-virtual-block-loop0.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-loop1.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-loop2.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram0.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram1.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram10.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram11.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram12.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram13.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram14.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram15.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram2.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram3.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram4.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram5.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram6.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram7.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram8.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram9.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-misc-rfkill.device loaded active plugged /sys/devices/virtual/misc
sys-devices-virtual-tty-ttyprintk.device loaded active plugged /sys/devices/virtual/tty/
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-module-fuse.device loaded active plugged /sys/module/fuse
sys-subsystem-bluetooth-devices-hci0.device loaded active plugged /sys/subsystem/bluetooth/
sys-subsystem-net-devices-eth0.device loaded active plugged /sys/subsystem/net/device
lines 1-36
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p1.device loaded active plugged /sys/devices/platform/emm
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p2.device loaded active plugged /sys/devices/platform/emm
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0.device loaded active plugged /sys/devices/platform/emm
sys-devices-platform-scb-fd500000.pcie-pci0000:00-0000:00:00.0-0000:01:00.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card1.device loaded active plugged Audio Adapter (
sys-devices-platform-scb-fd580000.ethernet-net-eth0.device loaded active plugged /sys/devices/platform/scb
sys-devices-platform-soc-fe00b840.mailbox-bcm2835_audio-sound-card0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0-hci0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0.device loaded active plugged /sys/devices/platform/soc
sys-devices-platform-soc-fe300000.mmcnr-mmc_host-mmc1-mmc1:0001-mmc1:0001:1-net-wlan0.device loaded active plugged /sys/devices/platform/soc
sys-devices-virtual-block-loop0.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-loop1.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-loop2.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram0.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram1.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram10.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram11.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram12.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram13.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram14.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram15.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram2.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram3.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram4.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram5.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram6.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram7.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram8.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-block-ram9.device loaded active plugged /sys/devices/virtual/bloc
sys-devices-virtual-misc-rfkill.device loaded active plugged /sys/devices/virtual/misc
sys-devices-virtual-tty-ttyprintk.device loaded active plugged /sys/devices/virtual/tty/
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-module-fuse.device loaded active plugged /sys/module/fuse
sys-subsystem-bluetooth-devices-hci0.device loaded active plugged /sys/subsystem/bluetooth/
sys-subsystem-net-devices-eth0.device loaded active plugged /sys/subsystem/net/device
"
and finally journalctl -xe output:
pi@raspberrypi:~ $ journalctl -xe
Dec 02 21:54:34 raspberrypi systemd[1]: Failed to start Service for snap application scummvm.daemon.
Subject: A start job for unit snap.scummvm.daemon.service has failed
Defined-By: systemd
Support: xhttps://www.debian.org/supportA start job for unit snap.scummvm.daemon.service has finished with a failure.
The job identifier is 1347 and the job result is failed.
Dec 02 21:54:35 raspberrypi systemd[734]: run-snapd-ns-scummvm.mnt.mount: Succeeded.
Subject: Unit succeeded
Defined-By: systemd
Support: xhttps://www.debian.org/supportThe unit UNIT has successfully entered the ‘dead’ state.
Dec 02 21:54:35 raspberrypi systemd[1]: run-snapd-ns-scummvm.mnt.mount: Succeeded.
Subject: Unit succeeded
Defined-By: systemd
Support: xhttps://www.debian.org/supportThe unit run-snapd-ns-scummvm.mnt.mount has successfully entered the ‘dead’ state.
Dec 02 21:54:35 raspberrypi systemd[1]: Reloading.
Dec 02 21:54:36 raspberrypi systemd[734]: snap-scummvm-4462.mount: Succeeded.
Subject: Unit succeeded
Defined-By: systemd
Support: xhttps://www.debian.org/supportThe unit UNIT has successfully entered the ‘dead’ state.
Dec 02 21:54:36 raspberrypi systemd[1]: snap-scummvm-4462.mount: Succeeded.
Subject: Unit succeeded
Defined-By: systemd
Support: xhttps://www.debian.org/supportThe unit snap-scummvm-4462.mount has successfully entered the ‘dead’ state.
Dec 02 21:54:36 raspberrypi systemd[1]: Reloading.
Dec 02 21:54:37 raspberrypi snapd[1104]: handlers.go:394: Reported install problem for “scummvm” as Crash report successfully submitted.
Dec 02 21:54:38 raspberrypi sudo[1096]: pam_unix(sudo:session): session closed for user root
i’m trying to install pulse audio and see what happens, it appears maybe this is a dependancy for ScummVM?
sudo apt-get install pulseaudio sudo reboot sudo sudo snap install scummvm
2020-12-02T22:13:51-07:00 INFO snap “scummvm” has bad plugs or slots: audio-playback (unknown interface “audio-playback”) error: cannot perform the following tasks:
- restart of [scummvm.daemon] (# systemctl restart snap.scummvm.daemon.service Job for snap.scummvm.daemon.service failed. See “systemctl status snap.scummvm.daemon.service” and “journalctl -xe” for details. )
- restart of [scummvm.daemon] (exit status 1)
still no dice 
I think Raspbian ships with a version of snapd that is so old it doesn’t correctly self-refresh to the current release when installing some snaps. You may have better luck if you run sudo snap install core before installing scummvm.
You can check what snapd version you’re running by typing snap version.
1 Like
I ran the sudo snap install core, rebooted, and tried again.
sudo snap install scummvm
error: cannot perform the following tasks:
- restart of [scummvm.daemon] (# systemctl restart snap.scummvm.daemon.service
Job for snap.scummvm.daemon.service failed.
See “systemctl status snap.scummvm.daemon.service” and “journalctl -xe” for details.
version confirmation:
pi@raspberrypi:~ $ snap version
snap 2.48
snapd 2.48
series 16
raspbian 10
kernel 5.4.72-v7l+
HI there, ScummVM dev here.
Unfortunately, I don’t have a Pi4/400 to test with, so I can only guess what went wrong here.
I wonder if this issue is related to snapd on Raspbian/Raspberry Pi OS. Could you please try to sudo snap install hello-world and run the hello world command afterwards to check if Snaps are working in general?
Another great test would be to check if you can run the ScummVM snap with Ubuntu Desktop 20.10 on your Pi (via https://ubuntu.com/download/raspberry-pi), so if you have a spare SD card…
1 Like
Hey @ lotharsm, thanks for the reply and helping bring ScummVM to more computers. I’d love to help out with troubleshooting this bug.
Here are my results:
pi@raspberrypi:~ $ sudo snap install hello-world
hello-world 6.4 from Canonical✓ installed
pi@raspberrypi:~ $ hello-world
ERROR: ld.so: object ‘/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so’ from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Hello World!
I will try the Ubuntu Desktop 20.10 tomorrow. Hopefully this information is useful.
@lotharsm, I have Ubuntu Desktop 20.10 up.
Snap Installed:
pi@pi-desktop:~$ sudo snap install hello-world
hello-world 6.4 from Canonical✓ installed
pi@pi-desktop:~$ hello-world
Hello World!
Installed ScummVM:
pi@pi-desktop:~$ sudo snap install scummvm
error: cannot perform the following tasks:
- Download snap “scummvm” (4461) from channel “stable” (context canceled)
- Download snap “gnome-3-28-1804” (147) from channel “stable” (context canceled)
I also noticed this from “snap info scummvm”, did you update this today?
snap-id: wXpsTyUtxXJ6aqnqhWRi0d3WwqzrD1Yv
channels:
latest/stable: 2.2.0 2020-11-19 (4461) 486MB -
latest/candidate: ↑
latest/beta: ↑
latest/edge: 2.2.0 2020-12-05 (4514) 589MB -
Snap Changes output:
pi@pi-desktop:~$ snap changes
ID Status Spawn Ready Summary
1 Done 44 days ago, at 07:17 MST today at 11:32 MST Initialize system state
2 Done today at 11:32 MST today at 11:32 MST Initialize device
3 Done today at 11:43 MST today at 11:43 MST Install “hello-world” snap
4 Error today at 11:46 MST today at 11:46 MST Install “scummvm” snap
systemctl output:
pi@pi-desktop:~$ systemctl
UNIT LOAD ACTIVE SUB >
proc-sys-fs-binfmt_misc.automount loaded active waiting >
dev-loop0.device loaded activating tentative >
dev-loop1.device loaded activating tentative >
dev-loop2.device loaded activating tentative >
dev-loop3.device loaded activating tentative >
dev-loop4.device loaded activating tentative >
dev-loop5.device loaded activating tentative >
dev-loop6.device loaded activating tentative >
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p1.device loaded active plugged >
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0-mmcblk0p2.device loaded active plugged >
sys-devices-platform-emmc2bus-fe340000.emmc2-mmc_host-mmc0-mmc0:59b4-block-mmcblk0.device loaded active plugged >
sys-devices-platform-scb-fd500000.pcie-pci0000:00-0000:00:00.0-0000:01:00.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card1.device loaded active plugged >
sys-devices-platform-scb-fd580000.ethernet-net-eth0.device loaded active plugged >
sys-devices-platform-soc-fe00b840.mailbox-bcm2835_audio-sound-card0.device loaded active plugged >
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0-hci0.device loaded active plugged >
sys-devices-platform-soc-fe201000.serial-tty-ttyAMA0.device loaded active plugged >
sys-devices-platform-soc-fe300000.mmcnr-mmc_host-mmc1-mmc1:0001-mmc1:0001:1-net-wlan0.device loaded active plugged >
sys-devices-virtual-misc-rfkill.device loaded active plugged >
sys-devices-virtual-tty-ttya0.device loaded active plugged >
sys-devices-virtual-tty-ttya1.device loaded active plugged >
sys-devices-virtual-tty-ttya2.device loaded active plugged >
sys-devices-virtual-tty-ttya3.device loaded active plugged >
sys-devices-virtual-tty-ttya4.device loaded active plugged >
sys-devices-virtual-tty-ttya5.device loaded active plugged >
sys-devices-virtual-tty-ttya6.device loaded active plugged >
sys-devices-virtual-tty-ttya7.device loaded active plugged >
sys-devices-virtual-tty-ttya8.device loaded active plugged >
sys-devices-virtual-tty-ttya9.device loaded active plugged >
sys-devices-virtual-tty-ttyaa.device loaded active plugged >
sys-devices-virtual-tty-ttyab.device loaded active plugged >
sys-devices-virtual-tty-ttyac.device loaded active plugged >
sys-devices-virtual-tty-ttyad.device loaded active plugged >
sys-devices-virtual-tty-ttyae.device loaded active plugged >
sys-devices-virtual-tty-ttyaf.device loaded active plugged >
sys-devices-virtual-tty-ttyb0.device loaded active plugged >
journalctl --no-pager -u snap.scummvm.daemon.service output (seems to be nothing):
pi@pi-desktop:~$ journalctl --no-pager -u snap.scummvm.daemon.service
– Logs begin at Thu 2020-09-24 12:27:11 MST, end at Sat 2020-12-05 11:47:53 MST. –
– No entries –
journalctl -xe:
pi@pi-desktop:~$ journalctl -xe
░░
░░ The job identifier is 502.
Dec 05 11:43:58 pi-desktop systemd[1]: tmp-snap.rootfs_lY2dsC.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit tmp-snap.rootfs_lY2dsC.mount has successfully entered the ‘dead’ state.
Dec 05 11:43:58 pi-desktop audit[45155]: AVC apparmor=“DENIED” operation=“capable” profile="/usr/lib/snapd/snap-confine" pid=45155 comm=“snap-confine” capability=>
Dec 05 11:43:58 pi-desktop kernel: audit: type=1400 audit(1607193838.375:72): apparmor=“DENIED” operation=“capable” profile="/usr/lib/snapd/snap-confine" pid=4515>
Dec 05 11:43:58 pi-desktop systemd[40203]: tmp-snap.rootfs_lY2dsC.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has successfully entered the ‘dead’ state.
Dec 05 11:44:29 pi-desktop tracker-store[45168]: OK
Dec 05 11:44:29 pi-desktop systemd[40203]: tracker-store.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has successfully entered the ‘dead’ state.
Dec 05 11:46:14 pi-desktop sudo[45200]: pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/snap install scummvm
Dec 05 11:46:14 pi-desktop sudo[45200]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Dec 05 11:46:14 pi-desktop snapd[44502]: api.go:1007: Installing snap “scummvm” revision unset
Dec 05 11:46:53 pi-desktop snapd[44502]: taskrunner.go:271: [change 4 “Download snap “gnome-3-28-1804” (147) from channel “stable”” task] failed: context canc>
Dec 05 11:46:53 pi-desktop snapd[44502]: taskrunner.go:271: [change 4 “Download snap “scummvm” (4461) from channel “stable”” task] failed: context canceled
Dec 05 11:46:53 pi-desktop sudo[45200]: pam_unix(sudo:session): session closed for user root
Dec 05 11:47:53 pi-desktop PackageKit[43814]: daemon quit
Dec 05 11:47:53 pi-desktop systemd[1]: packagekit.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit packagekit.service has successfully entered the ‘dead’ state.
I didn’t update it today, the new builds in the edge channel are due to Snapcrafts autobuild feature.
Could you please check if snap install scummvm --edge changes something?
I don’t really have an idea why it’s failing at the moment, but I can only test on AMD64 right now and not on any ARM based devices - maybe some weird things are going on on the snapd side of things.
However, I’m a bit worried because of the AppArmor denials and
Dec 05 11:46:53 pi-desktop snapd[44502]: taskrunner.go:271: [change 4 “Download snap “gnome-3-28-1804” (147) from channel “stable”” task] failed: context canc>
Dec 05 11:46:53 pi-desktop snapd[44502]: taskrunner.go:271: [change 4 “Download snap “scummvm” (4461) from channel “stable”” task] failed: context canceled
which at least from my point of view indicates a deeper issue with snapd.
1 Like
It’s looking good, this is still on the Ubuntu OS:
pi@pi-desktop:~$ sudo snap install scummvm --edge
scummvm (edge) 2.2.0 from Snapcrafters installed
Hey, it ran! I’m going to check it on the RaspberryPi OS now…
Unfortunately, did not work on RPiOS
pi@raspberrypi:~ $ sudo snap install scummvm --edge
error: cannot perform the following tasks:
- restart of [scummvm.daemon] (# systemctl restart snap.scummvm.daemon.service
Job for snap.scummvm.daemon.service failed.
See “systemctl status snap.scummvm.daemon.service” and “journalctl -xe” for deta ils.
)- restart of [scummvm.daemon] (exit status 1)
What I don’t get is why RPiOS is trying to start the snap in the daemonized mode, this should only happen on Ubuntu Core so get some sort of “Kiosk” experience.
@alan_g any idea what’s going on here? 
is there a flag I can set to fix this issue? is it perhaps because I installed the kiosk? I had to switch back to a previous iteration of my RpiOS, if there is something I need to make sure isn’t there I can try to uninstall it…
Please ignore the kiosk stuff for know, it’s not unlikely I’m mixing things up here. Another way to rule out would be to start from scratch with a fresh RPiOS installation to check if it’s something specific to your installation - then we know if we need to look after potential issues with your installation or if we have to deal with a general problem here.
I can go back to a vanilla RPiOS build and give it a try. The only things I am doing on this build are, enabling composite video output from the boot variables, turning on ssh, and updating everything. I haven’t really had time to muck with anything else at all, lol. But for sake of certainty, I will make a clean install with no flags and try installing snap / scummvm. Thanks for your help, I’m happy to fight through troubleshooting to help find the bug and to get ScummVM vis Snap working on RPiOS