Custom Query (2683 matches)

I think there is an issue with the socket dir handling. This is Ubuntu 18.04 with the latest stable xpra. I tried to establish xpra as a systemd service, run as an unpriviliged user. The service does not create the environment variables (i.e. XDG_RUNTIME_DIR, XAUTHORITY), as does sudo -u, when called without -E. xpra complains:

Apr 19 12:26:07 cp1sdy sudo[1239]: 2020-04-19 12:26:07,433 Warning: failed to create socket directory '/run/user/1001/xpra'
Apr 19 12:26:07 cp1sdy sudo[1239]: 2020-04-19 12:26:07,433  [Errno 2] No such file or directory: '/run/user/1001/xpra'
Apr 19 12:26:07 cp1sdy sudo[1239]: 2020-04-19 12:26:07,433 Warning: cannot create socket '/run/user/1001/xpra/cp1sdy-17106':
Apr 19 12:26:07 cp1sdy sudo[1239]: 2020-04-19 12:26:07,433  [Errno 2] No such file or directory
Apr 19 12:26:07 cp1sdy sudo[1239]: 2020-04-19 12:26:07,433  ($XDG_RUNTIME_DIR has not been created?)

which is legitimate, because these dirs don't exist. Then I tried to set --socket-dir=/tmp, which had no effect, basically. Then I tried to set XDG_RUNTIME_DIR=/tmp, which had no effect, the error messages persisted and xpra still accessed /run/user, which failed. Only when I explicitely create /run/user/1001 directories, the errors disappear and indicate that indeed now /tmp has been used. I believe there is some preconditional directory check with hard coded /run/user/ directories existent.

I hope you don't need further logs ;-) The above should be reproducible with /usr/bin/sudo -u test1 /usr/bin/env bash xpra_start.sh

Fedora, CentOS, and Red Hat systems are very nearly identical. The attached patch adds RedHat? to Fedora and CentOS when /usr/libexec is needed. It also fixes a bug for is_RedHat() function in the xpra.os_utils module.

Details here: ​New Chrome 0-day Bug Under Active Attacks – Update Your Browser Now!: the other resides in the PDFium (​CVE-2019-13721) library