command-chain ... not found

[udippel]

(I'm not familiar with snap, was migrated to it by *buntu for chromium-browser)

Received the usual, well-know notification of having to snap refresh, some time given ...
Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with

$ chromium-browser
Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected

Using Firefox, after some Google I found and tried
$ sudo apt install snap --reinstall
...
The following NEW packages will be installed:
  snap

And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it.

[udippel (udippel)]

Sorry, forgot the last line: After $ sudo apt install snap --reinstall chromium did work again. I didn't have to reinstall the snap apps; contrary to what was written in the web page that Google had found for me.

[Nathan Teodosio (nteodosio)]

I think you had removed the gnome-42-2204 and this caused the interface not to connect.

> sudo apt install snap --reinstall

> sudo apt install snap --reinstall chromium

You conflated snap[1] and snapd[2] in those instances. If your intention was to reinstall Chromium (and not snapd), then you could have used either of

apt install --reinstall chromium
snap remove chromium && snap install chromium

[1] https://packages.ubuntu.com/mantic/snap
[2] https://packages.ubuntu.com/mantic/snapd

[udippel (udippel)]

No. As I wrote, since this is my main laptop, I didn't do anything. I don't know anything about snap nor snapd. I had no 'intention'.

I do a
apt update && apt upgrade && snap refresh
(One after the other!) on a daily base. That's all.

grep "remove " /var/log/dpkg.log
shows nothing. The file was started on July 1st.

My mistake, eventually, to fail to make clear that I did not want install/reinstall chromium; and I issued only one single additional command: the one given by ricsipontaz in
https://forum.snapcraft.io/t/snap-problem-on-ubuntu-20-10-21-04-dev/21512/7
on how to solve this problem.
I did not have to reinstall the apps, contrary to him.

[Kakadu (kakadout)]

> I think you had removed the gnome-42-2204 and this caused the interface not to connect.

I had the same issue, but `sudo snap install gnome-42-2204` had fixed it. Many thanks!

I'm wondering, how could I guess by myself which exactly dependency is missing...

[Nathan Teodosio (nteodosio)]

That is currently a Snap shortcoming, there is no dependency enforcement
like in Apt. So in general you'd really have to ask. :/

[udippel (udippel)]

Once again, no, I didn't remove anything, neither manually nor automatically.

I checked a bit closer, watching the logs of my 'daily routine' as mentioned above, and today I saw this line in snap refresh:
gnome-3-38-2004 0+git.efb213a from Canonical✓ refreshed

What the heck is this?? I never installed gnome; and surely not with snap. I used snap reluctantly because it was shoved down my throat by *buntu. (Something I thought would be impossible in FOSS; but that's not the topic at this moment in time.)

So maybe someone with more insight than myself can draw a line from my report to this gnome update?

[Nathan Teodosio (nteodosio)]

 > I never installed gnome; and surely not with snap.

That snap is just poorly named, it doesn't have only Gnome stuff, but
also other snaps' dependencies, including e.g. Chromium.

There is nothing surprising in the fact that it was refreshed though and
as such gives no insight into the original problem.

[Stephen Gutknecht (roundsparrow)]

This happened to me in recent days. I did routine updates to Ubuntu 22.04 and shut down my system. The next time I went to boot the system chromium was not working. the icon was still on the launcher bar, but it would just spin loading for 15 or so seconds and do nothing. I started "chromium-browser" from a terminal shell and saw the error described in this incident. "Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected"

I never did any add/remove of snap or anything that should have triggered this. 3 gigabytes of free storage, so disk full during upgrade didn't happen. Anyway, to fix it: I followed what was mentioned in this thread `sudo snap install gnome-42-2204` and all back to normal, including my chromium profile still having the previous content.

I think I did the apt update / apt upgrade on June 30. Maybe there was a short period where routine updates triggered this problem? No idea. Thank you for reporting it, as I would never have known about the gnome-42-2204 snap without this bug report.

[udippel (udippel)]

The --reinstall did the trick here. Without, it said, it was there, blabla, nothing happening.
I guess the --reinstall drew in the necessary dependencies in order to not just being happy.

Thanks for the comment; it feels good to know that I wasn't fantasizing stuff.

[Nathan Teodosio (nteodosio)]

If it still shows up in "snap changes" (which at this point is unfortunately unlikely), please get the ID for the refresh and share the output of `snap change {ID}`.

[udippel (udippel)]

Sorry, was too fast. 'changes' only show yesterday's "no updates".