[winswitch] xpra shadow works, but start-desktop just shows a black screen

Antoine Martin antoine at nagafix.co.uk
Thu Apr 18 02:33:45 BST 2019

Your MUA has completely mashed this email thread.
Can you make it not do that? Or switch to something better?

> Here's an xpra at .service I created under /etc/systemd/system:
> [Unit]
> Description=Xpra Remote Desktop
> After=syslog.target network.target nfs-home.mount
> [Service]
> Type=simple
> User=%i
> EnvironmentFile=/etc/conf.d/xpra
> ExecStart=/usr/bin/xpra --no-daemon start-desktop --start=startxfce4
> ${%i}
> [Install]
> WantedBy=multi-user.target
> And the /etc/conf.d/xpra:
> myusername=:2
> I enabled the service by using 'systemctl enable
> xpra at myusername.service<mailto:xpra at myusername.service>'
> Still not working, but I do see the xpra process running after logging into my Linux box locally. Just cannot attach to it. Reports that it doesn't detect any live xpra sessions.
> myuserna+  2554  1.4  0.6 466784 110644 ?       SLs  16:15   0:04 /usr/bin/python2 /usr/bin/xpra --no-daemon start-desktop --start=startxfce4 :2
> myuserna+  2794  1.1  1.2 1104644 197308 ?      Ssl  16:15   0:03 /usr/lib/xorg/Xorg-for-Xpra-:2 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/myusername/.Xauthority -logfile /tmp/Xorg.:2.log -configdir /run/user/10345/xpra/xorg.conf.d/2554 -config /etc/xpra/xorg.conf -depth 24 :2
> The Xorg.:2.log shows a couple of errors that occurred when it started as a service.
> [    51.003] (EE) Unable to locate/open config directory: "/run/user/10345/xpra/xorg.conf.d/2554"
That's harmless.
> [    51.487] (EE) systemd-logind: failed to get session: PID 2794 does not belong to any known session
Probably harmless, you can get rid of this problem by starting via the
system-wide proxy server.

> Thanks for any advice on how to debug this issue.
You should post the xpra server log output found in the journal.

If the process is running by can't be found with "xpra list" then maybe
its sockets were not created, or not in the right place.
You could always try to bind it to a TCP port and see if you can connect
to it that way.


> Ben

More information about the shifter-users mailing list