Failed to add PIDs to scope's control group: Permission denied

[Ramiro]

I am on the server side, an Ubuntu 18.04, with xpra version 2.1.3.

When I try:

[email protected]:~$ PATH="/usr/lib/xorg:$PATH" xpra start --bind-tcp=0.0.0.0:14500 --html=on --start=xterm

I get:

using systemd-run to wrap 'start' server command
'systemd-run' '--description' 'xpra-start' '--scope' '--user' '/usr/bin/xpra' 'start' '--bind-tcp=0.0.0.0:14500' '--html=on' '--start=xterm' '--systemd-run=no'
Job for run-rc4c6fd6f0a8445b08d9bfb1da717308c.scope failed.
See "systemctl status run-rc4c6fd6f0a8445b08d9bfb1da717308c.scope" and "journalctl -xe" for details.

then journalctl -xe shows me:

Nov 16 07:35:28 r2d2 systemd[26686]: run-rb32e0e35376249e1b0d77b784c1beffb.scope: Failed to add PIDs to scope's control group: Permission denied
Nov 16 07:35:28 r2d2 systemd[26686]: run-rb32e0e35376249e1b0d77b784c1beffb.scope: Failed with result 'resources'.
Nov 16 07:35:28 r2d2 systemd[26686]: Failed to start xpra-start.

[Antoine Martin]

Is this from an SSH session? This works fine from a regular terminal in my Ubuntu 18.04 VM.

That said, I'm using a supported version (2.4.1) and you are not (2.1.3).
Please do not use the version provided by the Ubuntu repositories which is fundamentally broken and insecure (more details here: wiki/Packaging/DistributionPackages)

[Ramiro]

Could you please instruct me on how to install version 2.4.1 under Ubuntu 18.04?

And yes, I am trying to run that command from an SSH session.

BTW: How to check xpra version?

[Ramiro]

connect.html error msg

[Antoine Martin]

Could you please instruct me on how to install version 2.4.1 under Ubuntu 18.04?

See wiki/Download.

And yes, I am trying to run that command from an SSH session.

This can cause problems under some circumstances.
If you still encounter issues after upgrading, start your sessions first, then connect over ssh - rather than doing all in one.

BTW: How to check xpra version?

xpra --version

[snhirsch]

I suddenly started seeing exactly the same symptoms on my Ubuntu 18.04 system when running from a standard Xterm (NOT ssh session). Was working fine until several days ago when, I suspect, a Ubuntu update broke it.

I followed the directions to install directly from your repository, but apparently the Ubuntu package is newer and nothing was brought down.

xpra --version yields: xpra v2.5-r21174

[snhirsch]

More information: The root cause of this problem is related to cgroup permissions. If I hack ownership with this script things start working again.

#!/usr/bin/env bash

set -euo pipefail

file=/sys/fs/cgroup/unified/user.slice/user-$(id -u).slice/cgroup.procs

sudo chown $(whoami):root $file
sudo chmod g+w            $file

[Antoine Martin]

I followed the directions to install directly from your repository, but apparently the Ubuntu package is newer and nothing was brought down.
xpra --version yields: xpra v2.5-r21174

Looks like you're using the beta channel.

Try the stable 2.4.3, which has this fix: r21227
Otherwise, I'll try to make new beta builds shortly.

You can also do:

echo "systemd-run=no" >> ~/.xpra/xpra.conf

[snhirsch]

I am not using the beta channel. My winswitch.list file contains:

deb ​http://winswitch.org/ bionic main

There are no other references to winswitch anywhere in the apt configuration tree.

[Antoine Martin]

I am not using the beta channel.

There are no 2.5 builds in the stable repository.
I have no idea how it landed on your system.

Maybe try:

apt-get update
apt-get remove -y xpra
apt-get install -y xpra