#1738 closed defect (worksforme)
starting via system proxy fails
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | blocker | Milestone: | 2.3 |
Component: | server | Version: | 2.2.x |
Keywords: | system proxy | Cc: |
Description
For just a simple xpra start --start=xterm
with or without ssh (first reported for an ssh start via IRC).
The xpra early startup log is full of:
No protocol specified
As we try to open the vfb display to verify that it has started OK.
I'm pretty sure this used to work fine not so long ago.
It may be related to XAUTHORITY
.
root used to be able to access the display, maybe not any more?
To make it easier to debug, I tested with start-via-proxy=yes
so we don't retry without the proxy and clobber the log files.
SSH start is worse, because we take so long to timeout that we may not have time to try without the system proxy before the client gives up.
Links:
- No protocol specified - cannot open display: :0.0
- some suggestions of turning off authentication with "
-ac
" to verify that the problem is authentication related
Change History (3)
comment:1 Changed 3 years ago by
comment:2 Changed 3 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:3 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1738
Note: See
TracTickets for help on using
tickets.
Fix is in r17960. For older branches, use r17963.
Something must have changed with the xauth handling to cause this breakage. (our code was wrong but was succeeding anyway!)
@shimm: does that work for you?