@Akkana. My suspicion from digging around is that the problem happens during login, not session start. Certain steps in the sessiond login process need to be invoked for the session bus to work correctly. You will see from other reports that this issue is with the dbus session bus not being set up correctly. The report about cgroups is a consequence of that. The workarounds prove this. When I looked into the session start up process, the problem occurred before session start. systemd has documentation on what the login needs to do, and I don't think this is being followed when this problem occurs. I therefore think this is not about the sessions, but the login process. It's why I wondered if you were using a modern login manager (such as gdm3) because gdm3 is compliant with systemd's requirements. You could dp
echo $DBUS_SESSION_BUS_ADDRESS from your console before you do startx, and see if it is valid. I'm going to guess that it is not. When I spent some time looking at this a few months ago, I had the impression that this variable needs to be set correctly before the gui session starts. On Sun, 23 Oct 2022 at 07:40, Akkana Peck <1951...@bugs.launchpad.net> wrote: > Tim Richardson: I'm not using a login manager, I'm logging in on the > console then running startx. > > This is clearly not an openbox-specific bug since people have seen it in > many different environments, and besides, it only happens on Ubuntu with > Ubuntu snaps. The problem seems to be that snap has started to require > [some unknown system service or configuration] that it didn't need > before, which some desktop environments start and others don't. If we > knew what it was looking for, then people who need to run snaps could > make sure it was configured in their environments. > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
