xpra icon
Bug tracker and wiki

Opened 2 weeks ago

Last modified 2 weeks ago

#1654 new defect

xpra start with proxy fails / xvfb error

Reported by: mviereck Owned by: Antoine Martin
Priority: major Milestone: 2.2
Component: server Version: 2.1.x
Keywords: start proxy xvfb Cc:

Description

System: debian 9 with xpra v2.1.2-r16903
A regular start of xpra fails. Disabling the proxy mode with --start-via-proxy=no works fine.

$ xpra start :30
2017-10-01 23:12:33,925 server failure: disconnected before the session could be established
2017-10-01 23:12:33,926 server requested disconnect: server error (failed to start a new session)
Warning: cannot use the system proxy for 'start' subcommand,
 FAILURE
Entering daemon mode; any further errors will be reported to:
  /run/user/1000/xpra/:30.log
$ cat   /run/user/1000/xpra/:30.log
2017-10-01 23:12:34,931 Warning: xpra start from an existing 'xfce' desktop session
2017-10-01 23:12:34,931  pulseaudio forwarding may not work
2017-10-01 23:12:34,932  try using a clean environment, a dedicated user,
2017-10-01 23:12:34,932  or disable xpra's "pulseaudio" option
(EE) 
Fatal server error:
(EE) Server is already active for display 30
	If this server is no longer running, remove /tmp/.X30-lock
	and start again.
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) 
2017-10-01 23:12:34,956 
2017-10-01 23:12:34,957 Xvfb command has terminated! xpra cannot continue
2017-10-01 23:12:34,957  if the display is already running, try a different one,
2017-10-01 23:12:34,957  or use the --use-display flag
2017-10-01 23:12:34,957 
2017-10-01 23:12:34,958 killing xvfb with pid 6704
2017-10-01 23:12:34,958 failed to kill xvfb process with pid 6704:
2017-10-01 23:12:34,958  [Errno 3] No such process
# systemctl status xpra
● xpra.service - Xpra System Server
   Loaded: loaded (/lib/systemd/system/xpra.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2017-10-01 15:38:52 CEST; 7h ago
     Docs: https://xpra.org/trac/wiki/Service
           man:xpra
 Main PID: 613 (xpra)
    Tasks: 1 (limit: 4915)
   Memory: 118.4M
      CPU: 18.407s
   CGroup: /system.slice/xpra.service
           └─613 /usr/bin/python /usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=sys --ssl=on --ssl-cert=/etc/xpra/ssl-cert.pem --bind=none --auth=peercred --socket-dirs=/run/xpra --socket-permissions=666 --log-

Okt 01 16:54:37 debian9 xpra[613]:  display :5 is already active!
Okt 01 23:12:18 debian9 xpra[613]: New unix-domain connection received on /run/xpra/system
Okt 01 23:12:19 debian9 python[6457]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
Okt 01 23:12:19 debian9 python[6457]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
Okt 01 23:12:19 debian9 python[6457]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
Okt 01 23:12:19 debian9 python[6457]: PAM _pam_load_conf_file: unable to open /etc/pam.d/postlogin
Okt 01 23:12:19 debian9 xpra[613]: Entering daemon mode; any further errors will be reported to:
Okt 01 23:12:19 debian9 xpra[613]:   /run/user/1000/xpra/:30.log
Okt 01 23:12:33 debian9 xpra[613]: Error: failed to start server subprocess:
Okt 01 23:12:33 debian9 xpra[613]:  failed to identify the new server display!

If I try the same display number afterwards, xpra start :30 --start-via-proxy=no fails, the display number is already in use. xpra start :31 --start-via-proxy=no works fine.

Change History (1)

comment:1 Changed 2 weeks ago by mviereck

As a strange side effect, I can not start X applications on display :0 afterwards. No protocol specified. XAUTHORITY is set and the file still contains a cookie. Maybe xpra changed and damaged the cookie?

Note: See TracTickets for help on using tickets.