Adguard Home: no slot named "desktop" install error

Hi all,

I’m hoping someone can help me out. I’m new to snaps and am running across an error that a lot of googling has been unable to solve for me.

I’m trying to install the snap for Adguard Home. When I first tried installing it, it gave me errors with apparmor. Once I figured out what that was, I had to install the apparmor utils then restart apparmor. That let me get further in the process. Now I’m getting the below error:

$ sudo snap install adguard-home
error: cannot perform the following tasks:

  • Automatically connect eligible plugs and slots of snap “adguard-home” (internal error: auto-connect of &{“adguard-home:desktop” “snapd:desktop”} failed: snap “snapd” has no slot named “desktop”)

I have no idea what this error is telling me, so I don’t know how to fix whatever needs fixing. I’m running Kubuntu 20.04 LTS and have run the latest apt-get upgrade.

Any help would be very much appreciated! Thank you.

Edit: I had previously installed another snap and it’s running fine, and I can install and remove hello-world without issues. It’s only Adguard Home so far that gives me this error.

To help diagnosing the problem please paste the output of the snap version command from a terminal.

I’ve run apt-get update and apt-get upgrade so I assume it’s all at the latest version. Here’s the output you requested, thanks!

$ snap version
snap 2.46.1+20.04
snapd 2.46.1+20.04
series 16
ubuntu 20.04
kernel 5.4.0-42-generic

Hi, what’s snap changes and then for the change that is listed in Error for installing adguard, what is snap tasks <change-number> ?

Also the output of journalctl --no-pager -u snapd would be helpful.

1 Like

Thanks for the suggestions, I’m documenting this for the future. The last time I used Linux was over 10 years ago. Things have changed a lot in the last 10 years! :slight_smile:

$ snap changes ID Status Spawn Ready Summary 23 Error yesterday at 18:25 EDT yesterday at 18:25 EDT Install “adguard-home” snap from “beta” channel 24 Error yesterday at 18:29 EDT yesterday at 18:30 EDT Install “adguard-home” snap 25 Done yesterday at 18:31 EDT yesterday at 18:31 EDT Refresh all snaps: no updates 26 Error yesterday at 18:41 EDT yesterday at 18:41 EDT Install “adguard-home” snap 27 Error yesterday at 19:09 EDT yesterday at 19:09 EDT Install “adguard-home” snap 28 Error yesterday at 19:11 EDT yesterday at 19:11 EDT Install “adguard-home” snap 29 Error yesterday at 19:13 EDT yesterday at 19:13 EDT Install “adguard-home” snap 30 Error yesterday at 19:15 EDT yesterday at 19:15 EDT Install “adguard-home” snap 31 Error yesterday at 19:22 EDT yesterday at 19:22 EDT Install “adguard-home” snap 32 Error yesterday at 19:34 EDT yesterday at 19:34 EDT Install “adguard-home” snap 33 Error yesterday at 19:35 EDT yesterday at 19:35 EDT Install “adguard-home” snap 34 Done yesterday at 21:04 EDT yesterday at 21:04 EDT Install “hello-world” snap 35 Done yesterday at 21:05 EDT yesterday at 21:05 EDT Remove “hello-world” snap

$ snap tasks 30 Status Spawn Ready Summary Done yesterday at 19:15 EDT yesterday at 19:15 EDT Ensure prerequisites for “adguard-home” are available Undone yesterday at 19:15 EDT yesterday at 19:15 EDT Download snap “adguard-home” (606) from channel “stable” Done yesterday at 19:15 EDT yesterday at 19:15 EDT Fetch and check assertions for snap “adguard-home” (606) Undone yesterday at 19:15 EDT yesterday at 19:15 EDT Mount snap “adguard-home” (606) Undone yesterday at 19:15 EDT yesterday at 19:15 EDT Copy snap “adguard-home” data Undone yesterday at 19:15 EDT yesterday at 19:15 EDT Setup snap “adguard-home” (606) security profiles Undone yesterday at 19:15 EDT yesterday at 19:15 EDT Make snap “adguard-home” (606) available to the system Error yesterday at 19:15 EDT yesterday at 19:15 EDT Automatically connect eligible plugs and slots of snap “adguard-home” Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Set automatic aliases for snap “adguard-home” Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Setup snap “adguard-home” aliases Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Run install hook of “adguard-home” snap if present Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Start snap “adguard-home” (606) services Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Run configure hook of “adguard-home” snap if present Hold yesterday at 19:15 EDT yesterday at 19:15 EDT Run health check of “adguard-home” snap

… Automatically connect eligible plugs and slots of snap “adguard-home”

2020-09-30T19:15:53-04:00 ERROR internal error: auto-connect of &{“adguard-home:desktop” “snapd:desktop”} failed: snap “snapd” has no slot named “desktop”

I tried installing the snap again just now and then ran this command as asked:

$journalctl --no-pager -u snapd Oct 01 12:15:37 Radar snapd[665]: api.go:997: Installing snap “adguard-home” revision unset Oct 01 12:15:37 Radar snapd[665]: snapmgr.go:303: cannot read snap info of snap “snapd” at revision 9279: cannot find installed snap “snapd” at revision 9279: missing file /snap/snapd/9279/meta/snap.yaml Oct 01 12:15:37 Radar snapd[665]: snapmgr.go:303: cannot read snap info of snap “code” at revision 45: cannot find installed snap “code” at revision 45: missing file /snap/code/45/meta/snap.yaml Oct 01 12:15:37 Radar snapd[665]: snapmgr.go:303: cannot read snap info of snap “core” at revision 9993: cannot find installed snap “core” at revision 9993: missing file /snap/core/9993/meta/snap.yaml Oct 01 12:15:37 Radar snapd[665]: snapmgr.go:303: cannot read snap info of snap “core18” at revision 1885: cannot find installed snap “core18” at revision 1885: missing file /snap/core18/1885/meta/snap.yaml Oct 01 12:15:40 Radar snapd[665]: link.go:124: cannot update fontconfig cache: cannot get fc-cache-v6 from core: open /snap/snapd/current/bin/fc-cache-v6: no such file or directory Oct 01 12:15:40 Radar snapd[665]: snapmgr.go:303: cannot read snap info of snap “snapd” at revision 9279: cannot find installed snap “snapd” at revision 9279: missing file /snap/snapd/9279/meta/snap.yaml Oct 01 12:15:40 Radar snapd[665]: taskrunner.go:271: [change 36 “Automatically connect eligible plugs and slots of snap “adguard-home”” task] failed: internal error: auto-connect of &{“adguard-home:desktop” “snapd:desktop”} failed: snap “snapd” has no slot named “desktop” Oct 01 12:15:42 Radar snapd[665]: handlers.go:495: Reported install problem for “adguard-home” as already-reported

What is

systemctl status snap*.mount

?

Also the output of

cat /proc/self/mountinfo

would be helpful

1 Like

I’ve copied the results below. It says core20 failed to attach, so I tried looking up the error and reading up on core20, but didn’t find much info so don’t know if it’s contributing to my snap install error or not.

$ systemctl status snap*.mount
● snap-core20-634.mount - Mount unit for core20, revision 634
Loaded: loaded (/proc/self/mountinfo; enabled; vendor preset: enabled)
Active: active (mounted) since Sun 2020-09-27 20:25:48 EDT; 3 days ago
Where: /snap/core20/634
What: /dev/loop0
CGroup: /system.slice/snap-core20-634.mount

Sep 27 20:25:48 Radar systemd[1]: Mounting Mount unit for core20, revision 634…
Sep 27 20:25:48 Radar systemd[19872]: Failed to attach 19872 to compat systemd cgroup /system.slice/snap-core20-634.mount: No such file or directory
Sep 27 20:25:48 Radar systemd[1]: Mounted Mount unit for core20, revision 634.

● snap-tautulli-98.mount - Mount unit for tautulli, revision 98
Loaded: loaded (/proc/self/mountinfo; enabled; vendor preset: enabled)
Active: active (mounted) since Sat 2020-09-26 13:17:39 EDT; 5 days ago
Where: /snap/tautulli/98
What: /dev/loop7
CGroup: /system.slice/snap-tautulli-98.mount

Sep 26 13:17:39 Radar systemd[1]: Mounted Mount unit for tautulli, revision 98.

$ cat /proc/self/mountinfo
24 31 0:22 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
25 31 0:5 / /proc rw,nosuid,nodev,noexec,relatime shared:15 - proc proc rw
26 31 0:6 / /dev rw,nosuid,noexec,relatime shared:2 - devtmpfs udev rw,size=7942884k,nr_inodes=1985721,mode=755
27 26 0:23 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
28 31 0:24 / /run rw,nosuid,nodev,noexec,relatime shared:5 - tmpfs tmpfs rw,size=1597208k,mode=755
31 1 8:2 / / rw,relatime shared:1 - ext4 /dev/sda2 rw,errors=remount-ro
35 24 0:29 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:9 - tmpfs tmpfs ro,mode=755
36 35 0:30 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:10 - cgroup2 cgroup2 rw,nsdelegate
57 28 0:48 / /run/rpc_pipefs rw,relatime shared:32 - rpc_pipefs sunrpc rw
158 31 7:7 / /snap/tautulli/98 ro,nodev,relatime shared:89 - squashfs /dev/loop7 ro
620 28 0:57 / /run/user/1000 rw,nosuid,nodev,relatime shared:575 - tmpfs tmpfs rw,size=1597204k,mode=700,uid=1000,gid=1000
32 31 8:1 / /boot/efi rw,relatime shared:4 - vfat /dev/sda1 rw,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
58 31 0:28 / /mnt/smb/bay1 rw,relatime shared:22 - cifs //10.168.2.10/bay1 rw,vers=1.0,sec=ntlm,cache=strict,username=****,uid=0,noforceuid,gid=0,noforcegid,addr=10.168.2.10,file_mode=0777,dir_mode=0777,soft,nounix,serverino,mapposix,rsize=61440,wsize=65536,bsize=1048576,echo_interval=60,actimeo=1
88 31 7:0 / /snap/core20/634 ro,nodev,relatime shared:33 - squashfs /dev/loop0 ro
171 24 0:7 / /sys/kernel/security rw,relatime shared:91 - securityfs securityfs rw

What does snap list say ?

1 Like

$ snap list
Name Version Rev Tracking Publisher Notes
code 45 latest/stable vscode✓ broken
core 9993 latest/stable canonical✓ broken
core18 1885 latest/stable canonical✓ broken
core20 20 634 latest/stable canonical✓ base
snapd 9279 latest/stable canonical✓ broken
tautulli v2.5.5 98 latest/stable capruro-s -

somehow that sounds related to:

1 Like

Woohoo! That got me there! I ran through that thread you linked and had a good read. The OP there said he ran apt upgrade, rebooted and everything worked. I had been using “apt-get upgrade” like I always did in the past, and everything was up to date. Apparently you can use just “apt upgrade” now, and it upgrades more than apt-get will, since there was an additional 360MB to be updated. I did that, rebooted, and the snaps showing “broken” no longer do, and I can install the snap for AdGuard Home properly! I guess that’s what I get for stepping away from Linux for well over 10 years, things have changed a lot and my lack of knowledge bit me in the backside.

Thanks to both of you for the help, I really appreciate it!

1 Like

I’m glad you got it working, if you could attach your apt logs as referenced on that other thread however that would be good to know as we don’t want more folks to run into this issue and it’s still unclear to us what causes this to happen.

2 Likes

Looking at the other thread, it looks like you wanted the info from /var/log/apt/term.log as well as /var/log/apt/history.log so I’ve pasted it below. Before I ran “apt upgrade” and rebooted, both those files were 0 bytes. If I misunderstood and you wanted something different, please let me know.

$ cat /var/log/apt/term.log

Log started: 2020-10-01 18:03:42
Selecting previously unselected package linux-modules-5.4.0-48-generic.
(Reading database … 188459 files and directories currently installed.)
Preparing to unpack …/0-linux-modules-5.4.0-48-generic_5.4.0-48.52_amd64.deb …
Unpacking linux-modules-5.4.0-48-generic (5.4.0-48.52) …
Selecting previously unselected package linux-image-5.4.0-48-generic.
Preparing to unpack …/1-linux-image-5.4.0-48-generic_5.4.0-48.52_amd64.deb …
Unpacking linux-image-5.4.0-48-generic (5.4.0-48.52) …
Selecting previously unselected package linux-modules-extra-5.4.0-48-generic.
Preparing to unpack …/2-linux-modules-extra-5.4.0-48-generic_5.4.0-48.52_amd64.deb …
Unpacking linux-modules-extra-5.4.0-48-generic (5.4.0-48.52) …
Preparing to unpack …/3-linux-generic_5.4.0.48.51_amd64.deb …
Unpacking linux-generic (5.4.0.48.51) over (5.4.0.42.46) …
Preparing to unpack …/4-linux-image-generic_5.4.0.48.51_amd64.deb …
Unpacking linux-image-generic (5.4.0.48.51) over (5.4.0.42.46) …
Selecting previously unselected package linux-headers-5.4.0-48.
Preparing to unpack …/5-linux-headers-5.4.0-48_5.4.0-48.52_all.deb …
Unpacking linux-headers-5.4.0-48 (5.4.0-48.52) …
Selecting previously unselected package linux-headers-5.4.0-48-generic.
Preparing to unpack …/6-linux-headers-5.4.0-48-generic_5.4.0-48.52_amd64.deb …
Unpacking linux-headers-5.4.0-48-generic (5.4.0-48.52) …
Preparing to unpack …/7-linux-headers-generic_5.4.0.48.51_amd64.deb …
Unpacking linux-headers-generic (5.4.0.48.51) over (5.4.0.42.46) …
Setting up linux-headers-5.4.0-48 (5.4.0-48.52) …
Setting up linux-modules-5.4.0-48-generic (5.4.0-48.52) …
Setting up linux-image-5.4.0-48-generic (5.4.0-48.52) …
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-42-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-48-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-48-generic
Setting up linux-modules-extra-5.4.0-48-generic (5.4.0-48.52) …
Setting up linux-image-generic (5.4.0.48.51) …
Setting up linux-headers-5.4.0-48-generic (5.4.0-48.52) …
Setting up linux-headers-generic (5.4.0.48.51) …
Setting up linux-generic (5.4.0.48.51) …
Processing triggers for linux-image-5.4.0-48-generic (5.4.0-48.52) …
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-48-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file /etc/default/grub' Sourcing file /etc/default/grub.d/init-select.cfg’
Generating grub configuration file …
Found linux image: /boot/vmlinuz-5.4.0-48-generic
Found initrd image: /boot/initrd.img-5.4.0-48-generic
Found linux image: /boot/vmlinuz-5.4.0-42-generic
Found initrd image: /boot/initrd.img-5.4.0-42-generic
Adding boot menu entry for UEFI Firmware Settings
done
Log ended: 2020-10-01 18:04:40

$ cat /var/log/apt/history.log

Start-Date: 2020-10-01 18:03:42
Commandline: apt upgrade
Requested-By: loner (1000)
Install: linux-headers-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-modules-extra-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-modules-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-headers-5.4.0-48:amd64 (5.4.0-48.52, automatic), linux-image-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic)
Upgrade: linux-headers-generic:amd64 (5.4.0.42.46, 5.4.0.48.51), linux-image-generic:amd64 (5.4.0.42.46, 5.4.0.48.51), linux-generic:amd64 (5.4.0.42.46, 5.4.0.48.51)
End-Date: 2020-10-01 18:04:40