[Bug 1961898] Re: chromium-browser is refusing to start
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
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/user@1000.service/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/user@1000.service/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. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
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. ** Attachment added: "journalctl --no-pager --since "2022-02-21" >blah" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+attachment/5563271/+files/blah -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
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. ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
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 ** Package changed: chromium-browser (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
