You are very likely on to something with your investigation, I think: The
Apparmor error is quite weird, as
% grep /maps /var/lib/snapd/apparmor/profiles/snap-update-ns.chromium
owner @{PROC}/@{pid}/maps r,
The core24 snap still exists in --channel stable/core24-lp2072395 and install
as I may it, I don't hit the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2072395
Title:
[snap] Chromium with core24 base won't start: desktop-launch not found
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
Today I was prompted to update my chromium snap, so I closed it down
and the auto-refresh happened. When I tried to launch it, it did not
come up. Running `chromium` from the command line resulted in the
following error:
$ chromium
Content snap command-chain for
/snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found:
ensure slot is connected
Browsing the internet, I found people saying that gnome needed to be
connected. Running `sudo snap connect chromium:gnome-46-2404
gnome-46-2404:gnome-46-2404` did not fix the problem.
I'm not sure it matters for a snap, but this is (very recently
updated) ubuntu 22.04 running KDE on x86_64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
