Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
if by non graphical shell you mean a shell you arrive at via a local login,
I would not expect the bug to be present. The bug, as I understand it,
happens when the login process (not the UI) skips some step.
I can't imagine you would encounter this in any "official" login, such as
to a virtual terminal, or via ssh. Because I think the bug happens in the
login process and not the session start process, I have to predict that
using wayland vs xorg sessions would make no difference. \
It is interesting that xrdp works. I don't know how xrdp works as far as
starting sessions goes. But it is actively maintained unlike x2go so it
seems likely to me that it has "modern" log in methods so it may be fine.
I use nomachine workstation server and the most recent version release
notes specifically mention changes to the login process with respect to PAM
handling.
The systemd experts who have looked at this bug, including correspondence
I've had with them outside of this bug report, indicate that the problem
with x2go and nomachine look like a missing PAM step in the login process.
I will upgrade my server soon to check it out
regards
TIm
On Tue, 7 Nov 2023 at 05:16, Richard Brooksby <1951...@bugs.launchpad.net>
wrote:
> Thank you for the clarifications, Tim. For what it's worth, my Ubuntu
> 22 non-graphical shell *does* have DBUS_SESSION_BUS_ADDRESS to the same
> value that appears in a Wayland session
> ("unix:path=/run/user/1000/bus"). So the bug you mention being exposed
> does not occur for me.
>
> It is also set correctly for an RDP (remote desktop) login to a headless
> Ubuntu 22 machine with xrdp installed to provide the session. The
> Firefox snap starts happily in that session.
>
> A local X session started with `startx` also produces a session in which
> the Firefox snap will run.
>
> The only session that breaks Firefox for me is starting Wayland using
> `XDG_SESSION_TYPE=wayland dbus-run-session gnome-session`. I have not
> found any other way to get a Wayland session from the command line.
>
> It's possible this is all evidence of this bug being fixed in Ubuntu 22,
> and all I have is a problem with starting Wayland correctly.
>
> --
> 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 Xpra Terminal Server:
New
Status in snapd package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Incomplete
Status in x2goserver package in Ubuntu:
Confirmed
Status in snapd package in Debian:
New
Status in snapd package in Fedora:
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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
it is more that systemd is not setup properly rather than snaps, but snaps assume systemd cgroup is set up when other applications are not so fussy. systemd-oomd also relies on cgroups and I wonder if it is broken too. Anyway, the root cause of this is not snaps, but rather, snaps expose a bug which has occurred before the graphical session even starts. The DBUS_SESSION_BUS_ADDRESS is supposed to be set in the login process, way before the graphical session starts,,so my own amateur investigations agree with yours. There is a promise relating to the systemd "pam" login steps which do this, and I guess our broken logins skip this, but there are so many scripts involved that it hard to work out. It seems plausible that this is relatively recent change to the login process which old tools with custom login approaches have not been adapted to This is why I concluded that the problem that people are having is related to the way the login is done by their remote access tool, be it nomachine in my case or x2go or the vnc connections that first spawn a login (some types of remote access simply connect to an existing session and these would be immune from our problem). However, I'm just repeating myself, and likewise I will no doubt get more angry replies from people who believe this is a snap bug and are frustrated about the snap developers ignoring it. On Sun, 5 Nov 2023 at 09:55, Richard Brooksby <1951...@bugs.launchpad.net> wrote: > Some clues: > > If I start Ubuntu 22 with kernel argument `systemd.unit=multi- > user.target` (i.e. non-graphical) then start Wayland with > `XDG_SESSION_TYPE=wayland dbus-run-session gnome-session` then > DBUS_SESSION_BUS_ADDRESS gets set to something like > "DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus- > mcSf5L11K8,guid=b86aac9a59f39dddad072fc86546c3f8" and the Firefox snap > errors with "/user.slice/user-1000.slice/session-1.scope is not a snap > cgroup". > > But Firefox launched with > `DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus" firefox` from > a Terminal will run. > > Note that DBUS_SESSION_BUS_ADDRESS is already set in the non-graphical > shell before starting the Wayland session. It is overriden by dbus-run- > session (as documented in the man page). > > I don't understand these systems, but it would seem to me that the > Firefox snap is assuming that it's being run from a top-level session. > If a Wayland is started by a user with dbus-run-session then it can't > talk to it because it's assuming the top level D-bus. > > This might also be a clue as to why things don't work for remote > sessions. Perhaps snaps assume (indirectly) that they're only being run > in a top-level local session. A "standard session" if you like. > > Incidentally, the Firefox is happy if I use `startx` to get a session. > > -- > 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 Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: 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)
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Hi, if you connect with VNC, then you are starting the session with the VNC scripts, and this is actually an instance of the bug as I understand it, a non-standard login. If this is how you reproduce it, you are simply repeating what is common to the reports already here. There is something wrong with the login process missing some part of the systemd setup. This means it is not an Ubuntu or gnome or snapd or systemd problem, which is why no one from this packages is interested in fixing it. It is not a snap problem because snap is perfectly allowed to assume cgroups v2 are working in our sessions. On Sat, 21 Oct 2023 at 20:46, Andy Ruddock <1951...@bugs.launchpad.net> wrote: > Install VNC on a remote box (or VM), connect using VNC client, try to run > firefox. > Stop telling users it's their fault for having mis-configured machines or > using "non-standard logins" (whatever one of those is). > Jeez, I've been a fan of Ubuntu over the years, but this piece of > functionality is simply broken for certain use-cases. > > -- > 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 Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
If you find a way to reproduce it, for example installing into a VM in such a way that you can trigger it, then it would be helpful. The point is that there are millions of standard Ubuntu installs involving a few different kernel versions and the only reports of it are a couple here. If a developer can't reproduce it, they can't fix it. On Wed, 18 Oct 2023 at 20:47, mtu <1951...@bugs.launchpad.net> wrote: > As noted in #57, this bug _does_ occur on standard desktop installs, > such as mine (updated from 21.10 to 22.04, thus taking firefox from .deb > to snap). > > -- > 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 Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I doubt the kernel but a standard desktop install should have given you the hwe kernel so something isn't right. There is no way you should get this problem running Firefox in a standard desktop install. The bug is mostly due to non standard logins and certainly a standard Ubuntu install delivers snaps that work. On Wed, 18 Oct 2023, 04:15 Janus Kobain, <1951...@bugs.launchpad.net> wrote: > Tim, this is a desktop installation of 22.04 LTS, I simply followed > where package updates led me. > > After installing linux-generic-hwe-22.04-edge package: > $ snap --version > snap2.60.4 > snapd 2.60.4 > series 16 > ubuntu 22.04 > kernel 6.2.0-36-generic > > $ firefox; chromium-browser > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope > is not a snap cgroup > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope > is not a snap cgroup > > Is the problem still in the kernel version? > > -- > 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 > > -- 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 Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Janus, your kernel is old and does not match a desktop (HWE) kernel for 22.04.3, so I guess this is a server install of Ubuntu. How are you connecting to it? On Tue, 17 Oct 2023 at 13:21, Janus Kobain <1951...@bugs.launchpad.net> wrote: > In GNOME Terminal: > $ chromium > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-404feab7-2748-4d47-ad69-3cceb67db014.scope > is not a snap cgroup > > In xterm: > $ chromium > /user.slice/user-1000.slice/session-2.scope is not a snap cgroup > > > $ lsb_release -a; uname -a > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 22.04.3 LTS > Release:22.04 > Codename: jammy > Linux panama 5.15.0-85-generic #95-Ubuntu SMP Fri Sep 1 15:02:17 UTC 2023 > x86_64 x86_64 x86_64 GNU/Linux > > Started happening out of nowhere several hours ago, now I'm afraid to > restart Firefox. > > -- > 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 Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
unconfinded snaps don't have thie problem (that is, --classic snaps), these bypass all the snap sandboxing and I guess this means they bypass the controls and restrictions of cgroups. If you want this fixed, you have to get x2go fixed. Report the bug there. On Sun, 6 Nov 2022 at 21:05, Luigi Caiazza <1951...@bugs.launchpad.net> wrote: > Same issue here. > > My configuration is a fresh install of Ubuntu Mate 22.04 LTS, meant to > be used both locally and remotely (via X2GO). > > From local sessions, I have no anomalies for each application installed > via snap, so I am sure that the system works like a charm under some > conditions. In contrast, if I log in from a remote session and I try to > start almost all applications installed via snap (e.g., Firefox, Brave, > Arduino IDE), I fall into: > > /user.slice/user-1000.slice/session-14.scope is not a snap cgroup > > The "strange" thing is that I found an application that works pretty well > even through remote sessions: Visual Studio Code, installed using this > command: > sudo snap install code --classic > > I have not yet understood what can make the difference here, but to have > a full working system I prefer to rely on a sort of bugfixing, rather > than (permanently) apply some workaround that distorts the behaviour of > the system. > > I am curious to know why Visual Studio Code works (maybe the classic > confinement?). Please, inform us if you get the point. > > Thank you. > > -- > 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
@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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
@mtu and make sure that systemd is properly installed, how you check this I don't know. On Fri, 21 Oct 2022 at 08:13, Tim Richardson wrote: > hi @mtu, in that case no confined snaps will work for you, which you are > probably noticing. Something is wrong with your installation, I think. At a > wild guess, try installing gdm3 and making it default. Or reinstall. > Speaking from my own experience, I have not seen this once in any upgrades > or installs (from a sample size including VMs which is > 10, one of which > is kubuntu 22.04 -> 22.10) > > On Thu, 20 Oct 2022 at 19:51, mtu <1951...@bugs.launchpad.net> wrote: > >> I'd like to re-interate that I use a regular Kubuntu installation, >> freshly installed as 21.10 and later upgraded to 22.04 (a few months >> after 22.04 was released). During the upgrade to 22.04, the dpkg firefox >> was replaced by the snap firefox. That's when the problem appeared. >> >> -- >> 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 > -- 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
hi @mtu, in that case no confined snaps will work for you, which you are probably noticing. Something is wrong with your installation, I think. At a wild guess, try installing gdm3 and making it default. Or reinstall. Speaking from my own experience, I have not seen this once in any upgrades or installs (from a sample size including VMs which is > 10, one of which is kubuntu 22.04 -> 22.10) On Thu, 20 Oct 2022 at 19:51, mtu <1951...@bugs.launchpad.net> wrote: > I'd like to re-interate that I use a regular Kubuntu installation, > freshly installed as 21.10 and later upgraded to 22.04 (a few months > after 22.04 was released). During the upgrade to 22.04, the dpkg firefox > was replaced by the snap firefox. That's when the problem appeared. > > -- > 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Akkana, what login manager are you using with openbox? On Thu, 20 Oct 2022 at 14:57, Tim Richardson wrote: > The problem was identified as the session not being established correctly > in some instances, and those instances were 100% involved in non-mainstream > session starts (nomachine or other remote session starts such as X2Go). > The fixes apart from disabling cgroups v2 involve simulating one aspect of > a successful login. > > It seems that the login process of these sessions skips something that > systemd now requires. X2Go for instance is old and it is not surprising > perhaps. I think the problem is happening at login not when the gui shell > is started. > I don't know openbox, but if you consistently get this problem, may be > that is the reason. So the common element is not remote desktop as such, > but old and non-compliant login process (I hypothesize). I hope you report > this back to openbox and they have people interesting in investigating it. > Nomachine is a blackbox (non open source) and I don't think X2Go has > development effort. > > Obviously a standard gnome, plasma or xfce session does not get the > problem, because if Ubuntu, Kubuntu and Xubuntu users couldn't use the > default browser, we would know about it. All the complaining about slow > start times would be nothing to the browser not actually starting. > > There are some reports here of people using gnome and encountering the > problem. I can not explain that, except that there may be another root > cause, or those systems may be strangely misconfigured. Also, it is not a > snap bug and if snap needs to run in a v2 cgroup and the session can't > enable this, what do you propose that snapd do about it? > > > On Thu, 20 Oct 2022 at 08:20, Akkana Peck <1951...@bugs.launchpad.net> > wrote: > >> Tim, I'm not sure where you got that impression about remote desktops >> (re #55), but I'm the original reporter and I reported the problem on a >> local openbox session (see comment #6). My impression was that most of >> the people chiming in were similar to me, running local sessions with >> various window managers other than gnome or kde. >> >> -- >> 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 > -- 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
The problem was identified as the session not being established correctly in some instances, and those instances were 100% involved in non-mainstream session starts (nomachine or other remote session starts such as X2Go). The fixes apart from disabling cgroups v2 involve simulating one aspect of a successful login. It seems that the login process of these sessions skips something that systemd now requires. X2Go for instance is old and it is not surprising perhaps. I think the problem is happening at login not when the gui shell is started. I don't know openbox, but if you consistently get this problem, may be that is the reason. So the common element is not remote desktop as such, but old and non-compliant login process (I hypothesize). I hope you report this back to openbox and they have people interesting in investigating it. Nomachine is a blackbox (non open source) and I don't think X2Go has development effort. Obviously a standard gnome, plasma or xfce session does not get the problem, because if Ubuntu, Kubuntu and Xubuntu users couldn't use the default browser, we would know about it. All the complaining about slow start times would be nothing to the browser not actually starting. There are some reports here of people using gnome and encountering the problem. I can not explain that, except that there may be another root cause, or those systems may be strangely misconfigured. Also, it is not a snap bug and if snap needs to run in a v2 cgroup and the session can't enable this, what do you propose that snapd do about it? On Thu, 20 Oct 2022 at 08:20, Akkana Peck <1951...@bugs.launchpad.net> wrote: > Tim, I'm not sure where you got that impression about remote desktops > (re #55), but I'm the original reporter and I reported the problem on a > local openbox session (see comment #6). My impression was that most of > the people chiming in were similar to me, running local sessions with > various window managers other than gnome or kde. > > -- > 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
This is not a snap problem. I don't think it is a problem with standard Linux desktops either. The problem seems to be entirely reported for remote desktop sessions,.somehow they have missed something modern systemd sets up at login. On Mon, 17 Oct 2022, 13:40 Daniel van Vugt, <1951...@bugs.launchpad.net> wrote: > IMHO it's not reasonable for any software to absolutely require an > environment variable that's not already set in a default console login. > We all need to build better software that still works without > environment variables. > > Also changing multiple desktop environments now and into the future > doesn't scale. > > -- > 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 > > -- 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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
It is (much) better to use the more sophisticated workaround that does not disable cgroups v2. On Tue, 2 Aug 2022 at 07:32, mtu <1951...@bugs.launchpad.net> wrote: > > I see the same as Stephen in c46: snap-Firefox fails to start locally, > _sometimes_ – the error is not readily reproducable. > > When it happens, the following errors appear in ~/.xsession-errors: > > /user.slice/user-1000.slice/user@1000.service/app.slice/app-firefox_firefox-0403ae5e70f94aa6ace2ebfdfb404e54.scope > is not a snap cgroup > qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2201, > resource id: 104858919, major code: 18 (ChangeProperty), minor code: 0 > file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: > Unable to assign [undefined] to QString > > Usually, launching firefox from a terminal still works as expected. > > -- > 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: Confirmed 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
