xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #2585


Ignore:
Timestamp:
02/11/20 04:51:21 (14 months ago)
Author:
Antoine Martin
Comment:

Job for run-rfff30b9e85394e8198e446d53091aa64.scope failed.

Just tried it on Ubuntu Bionic and the problem did not occur. Maybe you're running on Linux Mint instead?

The cause of the error:

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

See #2042, #1536, #1105.

First I make sure that firefox or whatever the initial program is, isn't running (though it would be nice if this didn't have to happen).

This is a "feature" of Firefox and most browsers. They have no intention of fixing it and there's absolutely nothing we can do in xpra.

I found in a previous systemd ticket ...

Same as ticket:2042?#comment:6.

I have merged a workaround (r25206) based on this solution: facebook/flow : disable cgroups under broken versions of systemd.

Backport to v3 in r25207. Until this fix lands in a stable release, you can:

  • use the beta channel (new builds will land shortly)
  • apply the patch by hand
  • disable systemd-run: --systemd-run=no (or edit /etc/xpra/conf.d/60_server.conf)
  • start your sessions from an ssh login (already disables systemd-run)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2585

    • Property Owner changed from Antoine Martin to Tmanok
    • Property Milestone changed from 3.1 to 4.0
  • Ticket #2585 – Description

    initial v1  
    11Hello XPRA Devs,
    22
    3 '''You all make a most excellent application''', I use it daily as of this past month and used to use it long ago. There was a bug that plagued XPRA for about 2 years it seemed and it related to systemd changes. This month I have noticed this problem on every fresh install (from your APT repository) on over 10 devices just this week alone. My platforms are Ubuntu, Debian, LinuxMint, (and HeliumBL actually). My installation process is simple:
     3'''You all make a most excellent application''', I use it daily as of this past month and used to use it long ago. There was a bug that plagued XPRA for about 2 years it seemed and it related to systemd changes. This month I have noticed this problem on every fresh install (from your APT repository) on over 10 devices just this week alone. My platforms are Ubuntu, Debian, !LinuxMint, (and HeliumBL actually). My installation process is simple:
    44
    5 1. sudo apt update ; sudo apt install apt-transport-https
    6 2. wget -q https://xpra.org/gpg.asc -O- | sudo apt-key add -
    7 3. sudo add-apt-repository "deb https://xpra.org/ bionic main"
    8 4. sudo apt update ; sudo apt install xpra
    9 5. xpra --version
     51. {{{sudo apt update ; sudo apt install apt-transport-https}}}
     62. {{{wget -q https://xpra.org/gpg.asc -O- | sudo apt-key add -}}}
     73. {{{sudo add-apt-repository "deb https://xpra.org/ bionic main"}}}
     84. {{{sudo apt update ; sudo apt install xpra}}}
     95. {{{xpra --version}}}
    1010(Should be 3.0.5 or greater in 2020.)
    11 6. xpra start :100 --start=/usr/bin/firefox
     116. {{{xpra start :100 --start=/usr/bin/firefox}}}
    1212
    1313But then this happens:
    14 "
    15 
    1614{{{
    1715using systemd-run to wrap 'start' server command
     
    2119}}}
    2220
    23 "
    24 ... 7. journalctl -xe
    25 "
    26 
     217. {{{journalctl -xe}}}
    2722{{{
    2823-- Unit xpra.socket has finished starting up.
     
    4540}}}
    4641
    47 "
    48 
    4942----
    5043
    5144So how do I resolve it? First I make sure that firefox or whatever the initial program is, isn't running (though it would be nice if this didn't have to happen).
    52 "
    5345
    5446{{{
     
    5749}}}
    5850
    59 "
    60 
    61 If that doesn't prove to yield anything as shown above, I then borrow the following information I found in a previous systemd ticket on GitHub and apply the "fix", though this is most certainly not from my understanding a very good solution and should only be done to personal machine and not within production environments...
    62 
    63 "
     51If that doesn't prove to yield anything as shown above, I then borrow the following information I found in a previous systemd ticket on !GitHub and apply the "fix", though this is most certainly not from my understanding a very good solution and should only be done to personal machine and not within production environments...
    6452
    6553{{{
     
    7462}}}
    7563
    76 "
    77 
    7864Thanks, let me know if there's a missing dependency or something you want me to test though I really feel like this is an XPRA bug as many of the systems I've tried this on were fresh installations and still encountered this bug.