** Tags removed: rls-nn-incoming
--
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
Thanks for the bug report, unfortunately this has become quite
convoluted and I've identified at least 3 different strands of
discussion in here that are not related.
Some stuff, like "runuser" in a cron job is clearly never going to work,
but I don't know how the other two instances - sessions
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Tags added: rls-nn-incoming
--
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
Encountered this problem while attempting to run a confined snap from a
cronjob.
All that is wrong actually is that the systemd user session has not been
properly setup.
I had to install dbus-user-session and then make sure the
/run/user/../bus was initialized by for example runuser -u user
I maintain TurboVNC, a modern Xvnc implementation derived originally
from TightVNC and TigerVNC, and users have reported this problem both
with the Firefox snap on Ubuntu 22.04 and with Podman on Fedora. I
wanted to add some clarifying remarks:
- The reason why Linux remote desktop solutions
I've encountered similar issue, and my installation is Ubuntu Mate
22.04. After some tinkering I found a workaround that works for me. On
my Ubuntu Mate, there is a file /etc/X11/Xsession.d/80mate-environment
containing a command to unset DBUS_SESSION_BUS_ADDRESS, this seems cause
the subsequnt
Also had this issue on Ubuntu Serverusing crons and chromedriver, as
well as with newly added user
cron.service is not a snapd cgroup.
Were able to fix it by `loginctl enable-linger ubuntu`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: impish
** Tags added: mantic
--
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
I have similar problem with telegram-desktop on Kubuntu 23.10. Before
the dist upgrade this snap used to work fine and could be launched from
the application launcher. After the upgrade, the snap stopped working
and no amount or remove or purge would make it work. I see this in
syslog
>
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
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
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
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
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
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
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
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 a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
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
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
>
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;
I'm using VNC to access a desktop and experiencing just this issue. Using the
"export DBUS_SESSION_BUS_ADDRESS" allows me to get a firefox window. I can't
open file load/save dialogs from that session though, so can't import/export
certificates & websites with file upload pages that use the
Thanks for your comments and workarounds, I was using nomachine at a
headless server with run target set to multi-user instead of graphical,
and Firefox had this problem in the xsession created by nomachine.
My workaround is to edit the Firefox script itself, handily,
/usr/bin/Firefox is a script
I may be mistaken in thinking that the Firefox I was using under 20.04
was not a snap.
All the same, launching new Firefox windows with the same session on
different workspaces was a normal part of my day-to-day workflow until I
upgraded to 22.04 a couple of weeks ago. I now get an error when I
# I have this problem on a fresh install:
Xubuntu 22.04
Firefox 113.0.2 (snap)
# When I try to launch Firefox from the command line with a profile that
is already running, I get an error reported to mu GUI:
"Firefox is already running, but is not responding. To use Firefox, you
must first close
For me installing `dbus-user-session` fixed this issue
--
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
Another affected user. Here using VNC through Apache Guacamole with
XFCE4 as a desktop manager. Similar errors to others:
$ firefox
2023/03/30 14:56:04.261227 cmd_run.go:1055: WARNING: cannot start document
portal: Can't mount path /home/student/.cache/doc
For those of us who are using Xubuntu, X2Go and experiencing this
problem, I have a work-around:
I had already switched firefox to the apt repository version, so I
installed the chromium snap to test with. As expected, it failed to
launch with the same issue mentioned at the top of this thread:
unfortunately my problem still lingers.
Though for some reason, it only affects users with a non-standard $HOME
location.
For instance, I have created a few users on the directory
/storage/home/ and voilà the problem shows up whenever I try to
run a snap.
The problem does not affect users
** Also affects: snapd (Fedora)
Importance: Undecided
Status: New
--
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:
@Steve Fatula I resolved my issue with:
sudo loginctl enable-linger
I'm not sure this is really the correct way to go about it, but it
ensures that everything is there for the user when the cron process
spawns.
--
You received this bug notification because you are a member of Ubuntu
Touch
The error described in comment 78 is due to the way the session is
established.
When connecting directly, it works:
$ ssh philippe@myserver
$ chromium -v # Works
Whereas using sudo su generates an error:
$ ssh anotheruser@myserver
$ sud su philippe
$ chromium -v # not a snap cgroup
I think
IF that can help, I can reproduce the issue, with the snap working with
a user and failing with another one.
Setup a fresh Ubuntu Server 22 in a VirtualBox hosted on Windows (but I
also reproduce the issue on a dedicated server). No extra packages apart
from an SSH server.
Once Ubuntu is
Yeah, I know my answer dont solve this issue. But, if you cant wait for
a fix, like me, you can try install chrome without snap. In my case I
thought it was impossible, cause I was running ubuntu 22.04 in a ARM
instance. But after remove the snap version and install a deb version I
found peace and
** Also affects: xts
Importance: Undecided
Status: New
--
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
I'm running xpra from vanilla 22.04 (wayland) to vanialla 22.04 (X).
Firefox works fine directly on the server, but won't run over xpra. The
`export DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus"` works
for me.
--
You received this bug notification because you are a member of Ubuntu
--
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
Have the same issue as Ron Simpkin in c56. "I'm attempting to run
automated testing from cron running chromium on X/vfb (headless server).
The cron job works so long as the user is logged in, the tests also run
successfully directly from the command line (in an ssh session). I've
tried the
Another datapoint. Just upgraded a laptop from 20.04 to 22.04.
1 - the laptop itself has no problem running Chromium or Firefox. When
run from a terminal, DBUS_SESSION_BUS_ADDRESS is
'unix:path=/run/user/1000/bus'
2 - When connecting over vnc, using the 'normal' xstartup (which must
have been on
Hi, any update on this bug, we are facing this issue in OpenStack CI
jobs. For error, logs see here [1]. let me know if more info. is
required.
I have opened a new bug in openstack/horizon as well to track it and
added more details there [2].
[1]
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
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
You can disregard my issue. It was caused by the limited environment
supplied by cron.
--
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:
@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
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
After a lot of digging, it seems that I have an unexpected, but simple
work-around for getting firefox to work under x2go on ubuntu 22.04:
Add to ~/.bashrc:
unset DBUS_SESSION_BUS_ADDRESS
I tried putting this unset command in xinitrc right before xfce4-session
is run. No luck.
I tried the
This happened to me on a fresh install of Xubuntu 22.04 when using X2Go.
Local sessions don't have this problem. I can work around it by setting
the environment variable (as specified in message 31)
DBUS_SESSION_BUS_ADDRESS before running firefox.
I'd like to get this fixed as we use X2go
@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
>
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
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
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
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
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
just to add some extra context:
dbus-daemon[26236]: [session uid=1001 pid=26236] Activating service
name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1001 pid=26249
comm="/snap/bin/chromium.chromedriver --port=9515 " label="unconfined")
dbus-daemon[26236]: [session uid=1001
Unfortunately, I must disagree with Tim in #55: This problem affects me
on a standard desktop, with absolutely no remote access involved. I'm
running 22.04, which I updated from 21.10 with KDE Plasma, and firefox
intermittently(!) will not start, spouting the "not a snap cgroup" error
message
Just thought I'd add a 'me too' although my situation is slightly
different in that I'm attempting to run automated testing from cron
running chromium on X/vfb (headless server). The cron job works so long
as the user is logged in, the tests also run successfully directly from
the command line (in
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,
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
I think the issue here is that snaps (with cgroupsv2) require a systemd
user session and some desktop environments do not set this up? It's not
clear to me what needs to change here -- should snapd be more tolerant
of this situation or should the other desktop environments change to set
the
I am experiencing this problem too. using VNC (tigervnc-standalone-server).
I read the entire thread. I tried damn near all of the workarounds. None worked.
The symptom is that I can't start Firefox in my xfce4 session .
madbrain@u22041:~/Desktop$ firefox
/system.slice/vncserver.service is not a
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.
>
>
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:
I have firefox working. To get it to work I had to disable cgroup. To do
this I followed Tim Richardson's instructions at c25. When launched it
outputs many permission denied errors which are attached.
I do not know what to do about these errors. Before I can use the
installation these have to be
I have recently discovered:
1)The global variable XDG_RUNTIME_DIR is not set to anything.
2) There is only one user on this newly installed Ubuntu 22.04 OS. It
would be expected the user number for it is 1000. This is verified by
the global $UID being set to that number as expected. But
** Attachment removed: "Jira 1951491 Attachment 2022-07-13.zip"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5603023/+files/Jira%201951491%20Attachment%202022-07-13.zip
** Attachment added: "Jira 1951491 Attachment 2022-07-16.zip"
I too have a very similar error. Only when I attempt to launch firefox
remotely by SSH I get this:
/system.slice/ssh.service is not a snap cgroup
And this when I attempt launch firefox directly on my target computer:
WARNING: cannot start document portal: Expected portal at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: x2goserver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Now I think we should file upstream bug reports with x2go (which I don't
use) and nomachine and get some clarity on whether they are doing the
login in compliance with up-to-date
https://www.freedesktop.org/software/systemd/man/systemd-
logind.service.html
--
You received this bug notification
Tim Richardson, I recognize your effort and contribution to solve the
problem, but without my comment in #33, where I must say I were not very
nice, you would not have clarified that cgroups v2 was enabled again.
Maybe you stated that with nomachine community, but not here.
Not stated before my
I have been reading a bit more. I'm starting to form the impression that
this problem may originate from the way our various remote solutions are
logging in. They may not be doing it the proper modern login-systemd
way. This would mean that nomachine, x2go are both wrong.
--
You received this
And let us hope that someone who can fix it steps up and fixes it
properly because right now, ubuntu 22.04 and derivatives are unfit for
remote desktop deployments.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I'm just an ordinary user trying to get this working and volunteering what I
learn, so bear that in mind. I have no real clue about what the problem is and
I still don't understand where in the session start process
DBUS_SESSION_BUS_ADDRESS is set and why we get a wrong value when starting
Tim, yes it works adding the environment variable, but you wrote "I
should have been clearer" in comment 35, but that is wrong, you should
at least had mentioned that you did enabled the cgroupsv2, and from
comment 27 to comment 32, there are no mention about reverting
Tim,
Two "Thank-you"s for you:
1. "spamming" elsewhere and here. Indeed, I got redirected here after I saw
your comments at snapcraft forum
2. Correctly specifying the bus address for the session by setting
DBUS_SESSION_BUS_ADDRESS. This worked like magic! My Ubuntu 22.04 running KDE
PS I do not think this is a bug in snap. It is a bug with the way the
session is being setup. I don't know what the bug is, I have spend some
hours trawling through bug reports and following clues (I tried to be
useful). My "spam" on the snapcraft bug was a helpful note directing
readers here,
I do not have cgroups disabled, I reverted that earlier change. My fix
works with cgroupsv2, at least for my xfce4 session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I've commented before, but if your desktop session is correctly set up,
the systemd --user instance should be available, then a transient scope
can be created for snap and proper device access filtering can be set up
in that cgroup, thus completing the sandbox. Cgroup v1 works
differently, in that
Tim Richardson Thank you so much, but NO, no and again NO.
I will not disable cgroups v2 because "at least blah blah blah".
I came from a configuration in which cgroups v2 was disabled, and snapd
worked. So thank you, but please stop spamming.
The point is that I need cgroups v2 and snapd has a
I added that to my ~/.profile and confined snap apps run now.
--
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
for me and my xfce4 login, in a terminal this lets me launch snaps:
tim@ubuntu ~ $ export DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus"
tim@ubuntu ~ $ firefox
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is what I get in journalctl when trying to start firefox:
Jun 15 13:09:30 ubuntu dbus-daemon[7531]: [session uid=1000 pid=7528]
Activating service name='org.freedesktop.systemd1' requested by ':1.60'
(uid=1000 pid=8624 comm="/snap/bin/firefox " label="unconfined")
Jun 15 13:09:30 ubuntu
... running systemd --user in a terminal window first, and then starting
the snap-store worked.
--
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
I ran into this again, this time in a virt-man virtual ubuntu 22.04
guest connected to via virt-viewer --attach.
tim@ubuntu-virtio:~$ snap-store
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-b5b3e096-ebb3-4eca-b9d1-d07ca7028b22.scope/init.scope
is
Yes, based on your link this 'work around' disables new cgroups.
: "If for some reason you need to keep the legacy cgroup v1 hierarchy, you
can select it via a kernel parameter at boot time:
systemd.unified_cgroup_hierarchy=0"
however, it at least allows a working session.
on another point:
@tim-ruchardson unified_cgroup_hierarchy=1 is exactly what I want to
enable, and I reported the problem in #1956942, where there is a
reference to https://lists.ubuntu.com/archives/ubuntu-
devel/2021-August/041598.html
the default is hierarchy=unified.
Also, in my configuration docker is using
Please note that nomachine technical support provided me with a
workaround. It works, but I don't understand the implications. This
fixed the problem with xubuntu 22.04. The support notes says it works
for ubuntu 22. 04 as well
In my case I added the kernel setting to GRUB_CMDLINE_LINUX which was
I have this problem connecting with nomachine to a virtual xubuntu desktop.
I hoped that the solution here might have helped:
https://askubuntu.com/a/1310739/152287
but this script does not fix the problem, although it is active for me
(the new environment variables are present in my session, for
Confirm issue is in latest LTS Xubuntu setup running x2go desktop
environment.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename: jammy
--
You received this bug notification because you are a member of
I All,
I can confirm same problem with Ubuntu MATE 22.04 running Xtightvnc
session.
--
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:
It has been reported also for Debian 11
https://forum.snapcraft.io/t/non-classic-snaps-fail-to-load-due-to-
cgroup-apparmor-issue/28756
looking at `tail -f /var/log/syslog` I see almost the same message
May 13 08:31:15 iltoshibo dbus-daemon[15558]: [session uid=1000 pid=15556]
Activating
Same problem with both 22.04 Server and Ubuntu Mate 22.04.
All the confined GUI snaps have this problem and thus can't run.
First, I encountered running MATE desktop via X2Go Server.
Then I tried to see if using xRDP would work. No still problem persists whether
I use xRDP or X2Go
Left unable to
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Same problem in 21.10 with Firefox, Chromium, and Waterfox Classic. All
have suddenly stopped working with error
/user.slice/user-1000.slice/session-30.scope is not a snap cgroup
I'm running MATE inside X2Go
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
FWIW systemd --user is expected to have been started as part of your
session. This is supposed to be fully automatic. I don't think you can
start it yourself, as it's up to systemd/logind to properly start the
process and move it to the right cgroup. I've added systemd to the bug
report, so maybe
94 matches
Mail list logo
