I have documented how I resolved this issue on my blog:
http://brtknr.com/2017/03/15/permission-issues-with-xpra-on-ubuntu-16-04-when-tunnelling-through-SSH/
Turns out that the version of xpra (0.15.x) provided with Ubuntu 16.04
is not supported anymore and updating to 2.0.x resolved the issue.
Do you have a set of parent/child processes like this? Note the middle
2 are running on tty63.
ps -f 748 750 926 1089
UID PID PPID C STIME TTY STATTIME CMD
root748 1 0 20:45 ? Ss 0:00 /bin/openvt -c 63 -f -v
-w -- /usr/bin/sudo --user user --login /u
Fixed that Xauthority stuff. It was caused by me having `ForwardX11 yes`
in `.ssh/config` for that host. Now I still get the following in
/home/sehe/.xpra/:90.log:
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
2016-10-31 00:45:25,027
2016-10-31 00:45:25,027 Xvfb comm
@G Carl (h-lauc9pad-k) thanks for that. The openvt trick looks very
promising.
I've created the systemd service and the server appears to start/stop
like a charm.
However, attempts to run X clients on the xpra server still result in
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run
I've gotten Xpra to work with Xdummy on lubuntu 16.04 by by starting
Xpra on a virtual console. This may not support your use case but it
works for mine.
INSTALLATION
sudo apt-get install xpra
apt list xpra
xpra/xenial,now 0.15.8+dfsg-1 amd64 [installed]
sudo usermod -aG tty
USE FROM DE
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589447
Title:
Xdummy cannot be used in Xenial
To manage notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158
After some investigation, the problem seems to be in the Xorg.wrap
wrapper that is way too picky.
1) Without the wrapper Xdummy cannot be executed because it tries to
open some virtual console and fails
2) With the wrapper Xdummy cannot be executed either because
a) you need to modify the Xwrapp