Hi,
I suppose you already fixed it by disabling and enabling the snap, so
it's not possible to recover the system state from the moment where the
problem occurred.
However, in case anyone else hits the same problem and finds this bug
report, make sure do the following (and collect outputs):
- run: snap version
- run: snap list
- run: snap connections <failing-snap>
- actually confirm that the relevant slot is connected (none of the fixes we
landed will establish the connection if it isn't there)
- if not, then run: snap connect <slot> <plug>
- run: snap changes - identify which ones mention either the slot snap or the
failing app snap
- for those, run: snap change <id>
- check whether /run/snapd/ns/<failing-snap>.mnt exists
- if it does, run: /usr/lib/snapd/snap-discard-ns <failing-snap>
- does the app work now? --> most likely issue with mounts, let us know
- doesn't work --> could be mounts related, but not necessarily, let us know
> Firefox updated on startup, before I had time to start it - it usually
> upgrades with a current instance open
Can you clarify what 'upgrades with a current instance open' means? This
should not be possible, snapd should complain when you try to refresh a
snap and its apps are running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146960
Title:
Firefox fails to start with Content snap command-chain for
/snap/firefox/8054/gpu-2404/bin/gpu-2404-provider-wrapper not found:
ensure slot is connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2146960/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
