Dear Maintainer,
xpra in debian buster does not work anymore. The error messages when
trying to start it from another host with xpra start are:

$ xpra start ssh:remotehost:10 --encoding=vp9 --min-quality=50 --start=konsole

2018-09-01 00:16:30,119 Xpra gtk2 client version 0.17.6-r14322
2018-09-01 00:16:30,120  running on Linux debian 9.5
Warning: failed to import GStreamer:
 GStreamer 1.0: Namespace Gst not available
 GStreamer 0.10: could not import gobject (could not find _PyGObject_API object)
2018-09-01 00:16:30,419 Error: failed to query sound subsystem:
2018-09-01 00:16:30,419  query did not return any data
2018-09-01 00:16:30,772 PyOpenGL warning: missing accelerate module
2018-09-01 00:16:38,282  detected keyboard: rules=evdev, model=pc101, layout=de
2018-09-01 00:16:38,283  desktop size is 1920x1080 with 1 screen:
2018-09-01 00:16:38,284   :0.0 (508x285 mm - DPI: 96x96) workarea: 1920x1020
2018-09-01 00:16:38,284     monitor 1 (309x174 mm - DPI: 157x157)

(Then SSH connects)

Warning: failed to write script file in '/run/user/1000/xpra':
 [Errno 2] No such file or directory: '/run/user/1000/xpra'
 ($XDG_RUNTIME_DIR has not been created?)
Warning: cannot use the system proxy for 'start' subcommand,
 failed to connect to '/run/xpra/system':
 [Errno 2] No such file or directory
 more information may be available in your system log
2018-09-01 00:17:07,417 Warning: failed to write script file in '/run/user/1000/xpra':
2018-09-01 00:17:07,417  [Errno 2] No such file or directory: '/run/user/1000/xpra'
2018-09-01 00:17:07,418  ($XDG_RUNTIME_DIR has not been created?)
Entering daemon mode; any further errors will be reported to:
  /home/allo/.xpra/:10.log
xpra initialization error:
 failed to identify the new server display!
bash: /xpra/run-xpra: Datei oder Verzeichnis nicht gefunden
Warning: cannot use the system proxy for 'start' subcommand,
 failed to connect to '/run/xpra/system':
 [Errno 2] No such file or directory
 more information may be available in your system log
2018-09-01 00:17:29,904 Warning: failed to write script file in '/run/user/1000/xpra':
2018-09-01 00:17:29,904  [Errno 2] No such file or directory: '/run/user/1000/xpra'
2018-09-01 00:17:29,905  ($XDG_RUNTIME_DIR has not been created?)
Entering daemon mode; any further errors will be reported to:
  /home/allo/.xpra/:10.log
xpra initialization error:
 failed to identify the new server display!
2018-09-01 00:17:30,787 The SSH process has terminated with exit code 0
2018-09-01 00:17:30,788  the command line used was:
2018-09-01 00:17:30,788  ssh -x -T neptune xpra initenv;~/.xpra/run-xpra _proxy_start :10 "--start=konsole" --encoding=vp9 || $XDG_RUNTIME_DIR/xpra/run-xpra _proxy_start :10 "--start=konsole" --encoding=vp9 || xpra _proxy_start :10 "--start=konsole" --encoding=vp9

After that, xpra terminates.

with kind regards,
Alex

Does it work with "--systemd-run=no"?

---

No person, no idea, and no religion deserves to be illegal to insult,
not even the Church of Emacs.
        -- Richard Stallman

Hi.
It seems to work, but still logs an error about the directory to stdout:

Warning: cannot use the system proxy for 'start' subcommand,
 failed to connect to '/run/xpra/system':
 [Errno 2] No such file or directory
 more information may be available in your system log
2018-09-22 00:08:12,217 Warning: failed to write script file in
'/run/user/1000/xpra':
2018-09-22 00:08:12,217  [Errno 2] No such file or directory:
'/run/user/1000/xpra'
2018-09-22 00:08:12,217  ($XDG_RUNTIME_DIR has not been created?)
Entering daemon mode; any further errors will be reported to:
  /home/allo/.xpra/:10.log

Alex

I seem to get good results by modifying script /usr/bin/xpra as below.

Cheers, Paul

--- /usr/bin/xpra.bak   2019-01-20 17:23:10.000000000 +1100
+++ /usr/bin/xpra       2019-12-26 11:17:42.455901905 +1100
@@ -1,5 +1,14 @@
 #! /usr/bin/python2

+# PSz 26 Dec 2019
+# Avoid error like:
+#   Warning: failed to create script directory '/run/user/1001/xpra':
+#    [Errno 2] No such file or directory: '/run/user/1001/xpra'
+#    ($XDG_RUNTIME_DIR has not been created?)
+# We do not have /run/user/UID directories.
+import os
+os.environ["XDG_RUNTIME_DIR"] = os.environ["HOME"] + "/.xpra"
+
 import sys
 try:
     import xpra

Is this still necessary with the latest release from backports?

Which reproducer command exhibits this problem?

Thanks.

---

A man does what he must - in spite of personal consequences, in spite of
obstacles and dangers and pressures - and that is the basis of all human
morality.
        -- Winston Churchill

Dear Dmitry,

I just upgraded from stretch to buster, using xpra version 2.4.3+dfsg1-1
(in buster, not backports). The issue did not seem to be present at
stretch, was "new" at buster. I start xpra "normally": on my home PC
(running some Ubuntu version), use

  xpra start ssh/psz@work --no-speaker --start-child=xterm

connecting to my work server running Debian buster; the error is shown
by the work server.

Cheers, Paul

Thanks. I can not reproduce on 3.x from buster-backports so I reckon the
problem is already fixed in a newer release.

---

Morality is doing what is right, no matter what you are told. Religion
is doing what you are told, no matter what is right.
        -- H. L. Mencken, 1925