Failed to add PIDs to scope's control group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
[impact]
systemd-run --user --scope fails
[test case]
$ systemd-run --user --scope echo hello
Job for run-r150c7437bf
See "systemctl status run-r150c7437bf
[regression potential]
large. this is fixed upstream by a large sequence of patches, and would need careful attention applying them all to make sure no regressions were introduced.
If I, or anyone else, attempts this backport, they definitely need to add more detail to this section.
[scope]
This is fixed upstream by this large PR:
https:/
That's included starting in systemd v238, so just missed the Bionic version. This is fixed already in all releases after Bionic, and needed only for Bionic.
[original description]
When I launch applications with flatpak, "journalctl -f" shows the following:
Jan 11 22:44:13 localhost systemd[1244]: flatpak-
Jan 11 22:44:13 localhost systemd[1244]: Failed to start flatpak-
Jan 11 22:44:13 localhost systemd[1244]: flatpak-
I explicitly mentioned "Kubuntu" in the summary, because I experience this only under Kubuntu (17.10 and 18.04), NOT under the regular Gnome-based Ubuntu Desktop (17.10). At first this error message seemed harmless, because it looked like it had no effect. But now I noticed that with certain flatpak apps, the file open dialog would not pop up. And I too experienced this only under Kubuntu, not Ubuntu or Fedora (all tested). So there might be a connection.
I first reported this to flatpak:
https:/
There it was suggested to try the following command:
$ systemd-run --user --scope echo hello
Job for run-r150c7437bf
See "systemctl status run-r150c7437bf
...and this one also fails.
description: | updated |
Changed in systemd: | |
status: | Unknown → Fix Released |
I tested it again with the regular Gnome-based Ubuntu desktop, and it exhibits the same bug, so i changed the title accordingly. It seems there is no connection to the flatpak problem.