I've run into this bug today as well. The workflow was: Firefox (via
snap) was working as expected, I ran Virtualbox, the OOM killer
terminated my open Firefox and Librewolf (via apt/dpkg) instances,
finished using the VM, went to open back up Firefox and Librewolf.
Librewolf opened back up as normal, but Firefox won't launch. When
running `firefox` in the terminal, I get this output:

`/user.slice/user-1000.slice/session-1239.scope is not a snap cgroup`

At no point was I logged out of my session. The output of `snap list`
shows my system has the youtube-dl snap installed, and now running that
gives the same error on launch as above. Interestingly, the `codium`
snap does not have this issue, and launches normally as expected.

I see some mention of VNC in the conversation above; my
`xtightvncviewer` functionality is not affected by any of this. Also
mentioned above seems to be comments about login being "done by their
remote access tool": I'm affected by this bug and am not using any form
of a remote access tool for logging in. Login/display manager appears to
be SDDM.

I'm using the Lubuntu flavor of Ubuntu, customized with WindowMaker
installed as the window manager. Display server is X11. This issue
occurred in an active session, where after login programs were
functional for multiple days, and during the session suddenly the error
appeared.

I don't get any new log output from `journalctl --user` after running
`firefox`.

My system info and command outputs:

```
tom@tom:~$ uptime
 13:01:35 up 20 days, 13:55, 22 users,  load average: 0.63, 0.81, 0.81

tom@tom:~$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.5 LTS
Release:        22.04
Codename:       jammy
Linux tom 5.15.0-156-generic #166-Ubuntu SMP Sat Aug 9 00:02:46 UTC 2025 x86_64 
x86_64 x86_64 GNU/Linux

tom@tom:~$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

tom@tom:~$ ls -l /run/user/1000/bus
srw-rw-rw- 1 tom tom 0 Oct  9 10:58 /run/user/1000/bus

tom@tom:~$ systemctl --user
Failed to connect to bus: Connection refused

tom@tom:~$ systemd --user
Failed to create /user.slice/user-1000.slice/session-1239.scope/init.scope 
control group: Permission denied
Failed to allocate manager object: Permission denied
```

Happy to provide other command outputs or full logs at request, hope
this helps to further document this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to