When I launch applications with flatpak, "journalctl -f" shows the following:
Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: Failed to add PIDs to scope's control group: Permission denied
Jan 11 22:44:13 localhost systemd[1244]: Failed to start flatpak-org.kde.krita-8134.scope.
Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: Unit entered failed state.
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.
There it was suggested to try the following command:
$ systemd-run --user --scope echo hello
Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and "journalctl -xe" for details.
When I launch applications with flatpak, "journalctl -f" shows the following:
Jan 11 22:44:13 localhost systemd[1244]: flatpak- org.kde. krita-8134. scope: Failed to add PIDs to scope's control group: Permission denied org.kde. krita-8134. scope. org.kde. krita-8134. scope: Unit entered failed state.
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:/ /github. com/flatpak/ flatpak/ issues/ 1216
There it was suggested to try the following command:
$ systemd-run --user --scope echo hello 8a4c5e919acbbc3 de0b29c. scope failed. 8a4c5e919acbbc3 de0b29c. scope" and "journalctl -xe" for details.
Job for run-r150c7437bf
See "systemctl status run-r150c7437bf
...and this one also fails.