chromium-browser is refusing to start

[Chris Guiver]

Ubuntu jammy box.

I woke my box this morning & resumed it (from suspend; LXQt session) & everything was normal (many apps including chromium-browser visible on displays). I can't say when I last logged in (many days no doubt!), but I shutdown session to use box for QA-test & comment on bug report.

After normal reboot & logging in though I tried opening `chromium` many times but nothing happened (from dock in GNOME). As most of what I do is in `firefox` I ignored it... It's been like that several hours with occasional tries & no exploration as to issue.

On opening a terminal to try and open `chromium-browser` I get the following

--
guiverc@d960-ubu2:~$ chromium-browser
internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/771 finished with result failed
--

In `journalctl` I notice

--
Feb 23 17:53:01 d960-ubu2 sudo[74762]: guiverc : TTY=pts/0 ; PWD=/home/guiverc ; USER=root ; COMMAND=/usr/bin/journalctl
Feb 23 17:53:01 d960-ubu2 sudo[74762]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Couldn't move process 74970 to requested cgrou>
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed to add PIDs to scope's control group: P>
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed with result 'resources'.
Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope.
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Couldn't move process 74994 to requested c>
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed to add PIDs to scope's control grou>
Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed with result 'resources'.
Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope.
Feb 23 17:53:07 d960-ubu2 polkitd(authority=local)[48397]: Registered Authentication Agent for unix-process:74411:1109253 (system bus name :1.183 [pkttyage>
Feb 23 17:53:11 d960-ubu2 polkit-agent-helper-1[75023]: pam_ecryptfs: pam_sm_authenticate: /home/guiverc is already mounted
Feb 23 17:53:11 d960-ubu2 polkitd(authority=local)[48397]: Operator of unix-session:10 successfully authenticated as unix-user:guiverc to gain ONE-SHOT aut>
Feb 23 17:53:11 d960-ubu2 pkexec[75020]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Feb 23 17:53:11 d960-ubu2 pkexec[75020]: guiverc: Executing command [USER=root] [TTY=/dev/pts/1] [CWD=/home/guiverc] [COMMAND=/usr/bin/dmesg]
--

I see a snap-confine error in `dmesg` but I don't think its related (nothing else is even close)

[ 9697.594155] audit: type=1400 audit(1645597770.987:130): apparmor="DENIED" operation="capable" profile="/snap/core/12725/usr/lib/snapd/snap-confine" pid=73276 comm="snap-confine" capability=4 capname="fsetid"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DRM.card0-DVI-I-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAeAAAA/QA3TB5SEQAKICAgICAgAAAA/ABLQUxFRDI0TU9OQ0EKAJo=
 modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
DRM.card0-DVI-I-2:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAEchMBz9ogAhYUAQOAMx14KsKFpFZNnCUSUFSzDABxT4EAgYCVALMA0cABAQEBAjqAGHE4LUBYLEUA/h8RAAAeAAAA/QA4Sx5TEQAKICAgICAgAAAA/ABBY2VyIEcyMzVICiAgAAAA/wBMSkswVzAxNjQzMjAKAIg=
 modes: 1920x1080 1680x1050 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
Date: Wed Feb 23 17:52:47 2022
DiskUsage:
 Filesystem Type Size Used Avail Use% Mounted on
 /dev/sda4 xfs 32G 31G 1.1G 97% /home
 tmpfs tmpfs 3.9G 4.0K 3.9G 1% /dev/shm
 /home/guiverc/.Private ecryptfs 32G 31G 1.1G 97% /home/guiverc
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-16 (1560 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. OptiPlex 960
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
Snap.Changes: no changes found
Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: error: transient scope could not be started, job /org/freedesktop/systemd1/job/779 finished with result failed
Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: error: transient scope could not be started, job /org/freedesktop/systemd1/job/775 finished with result failed
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2011
dmi.bios.release: 10.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0F428D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 1701283234
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/05/2011:br10.0:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr:sku:
dmi.product.name: OptiPlex 960
dmi.sys.vendor: Dell Inc.

[Chris Guiver (guiverc)]

i have disk space (1.1GB /home & 1.5 /)

i logged out of GNOME desktop & into Lubuntu/LXQt and same error

I also noted `telegram` wasn't running, in fact it appears to be an issue with all snaps

guiverc@d960-ubu2:~$ chromium-browser
internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1729 finished with result failed

guiverc@d960-ubu2:~$ telegram-desktop
internal error, please report: running "telegram-desktop" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1733 finished with result failed
guiverc@d960-ubu2:~$

guiverc@d960-ubu2:~$ wethr
internal error, please report: running "wethr" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1737 finished with result failed

[Ian Johnson (anonymouse67)]

Hi, can you paste the full journalctl output with --no-pager? The output you posted above is cut off right where I would like to see what systemd says.

[Chris Guiver (guiverc)]

I've added the requested detail; the file was too big so I've limited it a 'little'.

journalctl --no-pager --since "2022-02-21" >blah

NOTE HOWEVER, I rebooted the system a little while ago & snaps are loading again.. eg.

guiverc@d960-ubu2:~$ wethr
Melbourne, Australia: 24.14C ☁☁

& I have `chromium` working now which is what told me you requested the extra detail.

I don't know the issue, but it appears resolved.

[Maciej Borzecki (maciek-borzecki)]

If this happens again try running `SNAPD_DEBUG=1 snap run telegram-desktop` and collect the log. Since 22.04 is using unified hierarchy, we try to ask your session's systemd to create a transient scope for it. In your case, the log indicates that this operation failed. Looking at the log:

Feb 23 15:17:04 d960-ubu2 featherpad[66733]: Failed to load module "appmenu-gtk-module"
Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Couldn't move process 66754 to requested cgroup '/user.slice/user-1000.slice/[e-mail]/app.slice/snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope' (directly or via the system bus): Input/output error
Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Failed to add PIDs to scope's control group: Permission denied
Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Failed with result 'resources'.
Feb 23 15:17:19 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope.
Feb 23 15:17:19 d960-ubu2 chromium_chromium.desktop[66754]: internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/724 finished with result failed
Feb 23 15:17:32 d960-ubu2 systemd[1]: systemd-timedated.service: Deactivated successfully.
Feb 23 15:17:45 d960-ubu2 rtkit-daemon[56123]: Supervising 3 threads of 2 processes of 1 users.

Specifically this one is worrying:

systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Couldn't move process 66754 to requested cgroup '/user.slice/user-1000.slice/[e-mail]/app.slice/snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope' (directly or via the system bus): Input/output error

I'm afraid there's nothing snapd can do about that. I'm adding systemd to the bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christoph Singer (wasinger)]

Same here, Chromium does not start anymore.
System: Kubuntu 21.10 with latest updates as of today

chris@kubuntu:~$ LANG=C SNAPD_DEBUG=1 snap run chromium
2022/03/23 12:09:12.183829 tool_linux.go:204: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
2022/03/23 12:09:12.201553 cmd_run.go:1026: DEBUG: executing snap-confine from /snap/core/12821/usr/lib/snapd/snap-confine
2022/03/23 12:09:12.201954 cmd_run.go:433: DEBUG: SELinux not enabled
2022/03/23 12:09:12.202219 tracking.go:46: DEBUG: creating transient scope snap.chromium.chromium
2022/03/23 12:09:12.202980 tracking.go:186: DEBUG: using session bus
2022/03/23 12:09:12.204386 tracking.go:319: DEBUG: create transient scope job: /org/freedesktop/systemd1/job/561
2022/03/23 12:09:12.205375 tracking.go:419: DEBUG: job result is "failed"
error: transient scope could not be started, job /org/freedesktop/systemd1/job/561 finished with result failed

[Nick Rosbrook (enr0n)]

Based on comment #4 it sounds like there is nothing left to do for now.

[Chris Guiver (guiverc)]

Ubuntu 21.10 (along with flavors like Kubuntu; comment #7) is EOL - https://fridge.ubuntu.com/2022/07/19/ubuntu-21-10-impish-indri-end-of-life-reached-on-july-14-2022/

(though the comment was written year+ ago)

I concur with comment #8... My then d960 box stopped having this issue and I continued using that box/install until the PSU died (late 2022) & it was replaced with the box I'm using now

I'm not experiencing this issue now.

[Launchpad Janitor (janitor)]

[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]