xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 3 of Ticket #2746


Ignore:
Timestamp:
04/28/20 13:38:50 (17 months ago)
Author:
Antoine Martin
Comment:

Use:

xpra start :123 --use-display=yes

In v4, this is automatic, even over ssh: ticket:2523#comment:8.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2746

    • Property Status changed from new to closed
    • Property Resolution changed from to invalid
    • Property Component changed from android to server
  • Ticket #2746 – Description

    initial v3  
    44
    55What I see then on xpra server host is this:
     6{{{
    67[ ~]$ xpra list
    78Found the following xpra sessions:
     
    1011Re-probing unknown sessions in: /run/user/3035/xpra
    1112        UNKNOWN session at :123 (cleaned up)
    12 
     13}}}
    1314I can still see that Xorg is up as well as apps I have been running:
    14 
     15{{{
    15162230560 /usr/libexec/Xorg -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/mj/.Xauthority -logfile /run/user/3035/xpra/Xorg.:123.log -configdir /run/user/3035/xpra/xorg.conf.d/2230559 -config /etc/xpra/xorg.conf -depth 24 :123
    16 
     17}}}
    1718So if only xpra server could be restarted, find the existing Xorg session and reconnect to it, then it would mitigate problems with xpra stability.