I've tried multiple ways to stop this from happening:
1) upgrading the snapd snap to version 2.60.4 before starting the upgrade
2) modifying the upgrader so that firmware-updater is installed after gtk-common-themes
Neither of those resolved the issue and in my experience the error message changes occassionally.
Below is one message I've seen:
Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware-updater:icon-themes" "gtk-common-themes:icon-themes"} failed: snap "gtk-common-themes" has no slot named "icon-themes")
Another:
- Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware-updater:gnome-42-2204" "gnome-42-2204:gnome-42-2204"} failed: snap "gnome-42-2204" has no slot named "gnome-42-2204")
Also running `snap info snapd` I noticed that snapd is broken before rebooting after the upgrade.
I've tried multiple ways to stop this from happening:
1) upgrading the snapd snap to version 2.60.4 before starting the upgrade
2) modifying the upgrader so that firmware-updater is installed after gtk-common-themes
Neither of those resolved the issue and in my experience the error message changes occassionally.
Below is one message I've seen:
Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware- updater: icon-themes" "gtk-common- themes: icon-themes" } failed: snap "gtk-common-themes" has no slot named "icon-themes")
Another:
- Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware- updater: gnome-42- 2204" "gnome- 42-2204: gnome-42- 2204"} failed: snap "gnome-42-2204" has no slot named "gnome-42-2204")
Also running `snap info snapd` I noticed that snapd is broken before rebooting after the upgrade.