Chromium fails to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This morning, I was running chromium and I received the usual, well-known pop-up notification of having to do a snap refresh. Closed chromium, clicked on the pop-up. A few minutes later, I was informed that chromium was updated.
Clicked on chromium menu item and... nothing. No response. Tried from a terminal and received
xyz@optiplex:~$ env BAMF_DESKTOP_
Content snap command-chain for /snap/chromium/
xyz@optiplex:~$ chromium
Content snap command-chain for /snap/chromium/
Using synaptic package manager, I checked that I was running the newest version (1:85.0.
Checked snap info command
xya@optiplex:~$ snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical**
store-url: https:/
contact: https:/
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
commands:
- chromium.
- chromium
snap-id: XKEcBqPM06H1Z7z
tracking: latest/stable
refresh-date: today at 06:32 CDT
channels:
latest/stable: 126.0.6478.126 2024-07-04 (2905) 174MB -
latest/candidate: 126.0.6478.126 2024-07-03 (2905) 174MB -
latest/beta: 127.0.6533.26 2024-06-28 (2904) 179MB -
latest/edge: 128.0.6555.2 2024-06-26 (2898) 180MB -
installed: 126.0.6478.126 (2905) 174MB -
I've checked my version of snapd. It is 2.63+22.04 which is the latest stable version.
My Xubuntu version is
xxx@optiplex:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
What do I do?
Update: I usually turn off (power down) my computer at night. After turning on the computer this morning, I tried to start chromium and it worked.
All it took was a (cleansing) reboot?
Also I have to think that given the error I saw ("snap command-chain for /snap/. ../desktop- launch not found") this is probably more a snapd issue than chromium(-package) issue. I'm going to check there.