From antoine at nagafix.co.uk Mon Apr 2 15:54:48 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 2 Apr 2018 21:54:48 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.2.6: important fixes Message-ID: Hi, This update fixes a number of serious issues, in particular some X11 server crashes and auto-refresh loops. Updating is strongly recommended. Release notes: * fix support for encryption key environment variable * fix html-disabled option not honoured when ssl upgrades used * fix MS Windows SSL server timeouts * fix refresh loop with video region * fix auto-refresh of transparent windows (was losing transparency) * fix default printing information collection method * fix OpenGL backend validation not honoured * fix swapped colour channels in OpenGL client with transparent windows encoded as PNG * fix webp paint errors with OpenGL disabled * fix NVENC codec compatibility with Cython 0.28 * fix png/P encoding wrongly used in some exceedingly rare cases * fix padding issues with very large passwords or challenge packets * fix missing window contents when switching tabs (HTML5 client) * fix MS Windows comtypes packaging: webcam device detection issues * fix unmanaged X11 calls causing GTK crashes * fix clipboard handler wrongly answering requests when disabled * fix unlikely errors during connection cleanup * remove outdated option from the man page, fix missing paragraphs * disable VP9 decoding via ffmpeg on MS Windows (crashy) Links: https://xpra.org/trac/wiki/Source https://xpra.org/trac/wiki/Download Cheers Antoine From stdedos at gmail.com Tue Apr 3 16:12:29 2018 From: stdedos at gmail.com (=?UTF-8?B?zp3PhM6tzr3PhM6/z4IgzqPPhM6xz43Pgc6/z4I=?=) Date: Tue, 3 Apr 2018 18:12:29 +0300 Subject: [winswitch] Physical Displays to different windows (under the same Xpra process?) Message-ID: Hello there! I am trying to `xpra shadow` my Ubuntu 16.04.3 working environment when I am using my laptop (Windows 10). Environment is 3 screens wide. I'd prefer if this was 3 windows instead of one window of ~5k x 1080 p. I fail to think how that'd be possible. I think that fakexinerama could be useful here, but I have no actual clue. Tried irc, channel was dead at my time. I grep'ped the whole mail archive, I failed to find something related Ntentos Stavros From antoine at nagafix.co.uk Tue Apr 3 19:24:36 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 4 Apr 2018 01:24:36 +0700 Subject: [winswitch] Physical Displays to different windows (under the same Xpra process?) In-Reply-To: References: Message-ID: On 03/04/18 22:12, ??????? ??????? via shifter-users wrote: > Hello there! I am trying to `xpra shadow` my Ubuntu 16.04.3 working > environment when I am using my laptop (Windows 10). Environment is 3 > screens wide. > > I'd prefer if this was 3 windows instead of one window of ~5k x 1080 p. > I fail to think how that'd be possible. I think that fakexinerama could be > useful here, but I have no actual clue. Please create a ticket for this, it shouldn't be too hard to implement. > Tried irc, channel was dead at my time. We're not all on the same timezones. > I grep'ped the whole mail archive, I failed to find something related That's because no-one has ever requested this feature. It sounds very useful though, we should be doing this. Cheers Antoine > > Ntentos Stavros > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Mon Apr 9 12:26:10 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 9 Apr 2018 18:26:10 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 1.0.11: important fixes Message-ID: Hi, This update to the LTS branch fixes two serious issues: X11 server crashes and auto-refresh loops. The other fixes are minor. Updating is recommended for those stuck on this branch. (ie: CentOS 6.x) Release notes: * fix refresh loop with video region * fix NVENC codec compatibility with Cython 0.28 * fix unmanaged X11 calls causing GTK crashes * fix padding issues with large passwords * fix webp paint errors with OpenGL disabled * disable ffmpeg encoder (compatibility issues) * remove duplicated declarations in Cython files * log password file loading failure details * remove outdated option from the man page, fix missing paragraphs * disable VP9 decoding via ffmpeg on MS Windows Links: https://xpra.org/trac/wiki/Source https://xpra.org/trac/wiki/Download Cheers Antoine From pxd at tuta.io Sun Apr 29 19:59:20 2018 From: pxd at tuta.io (pxd at tuta.io) Date: Sun, 29 Apr 2018 20:59:20 +0200 (CEST) Subject: [winswitch] Xpra "can't open display" error Message-ID: Hi, Using Xpra 2.3-r19058 from the Xpra Debian buster repo (on client and server), I can't get the display to get sent over ssh from a headless VM to the VM's host machine. >From the client machine, if I run: xpra start ssh:hostname:102 --start-via-proxy=no I get: xpra initialization error: ?failed to identify the new server display Error: failed to receive anything, not an xpra server? ? could also be the wrong protocol, username, password, or port Connection lost But `xpra list` on the host machine shows that display :102 was successfully started and live. (If I do the above without `--start-via-proxy=no`, I get the same errors and can see? the xpra command running with `ps aux`, but I can't connect to it, there are no xpra sessions found with `xpra list` and I have to manually kill the xpra process.) I can attach to the session without any client side errors with `xpra attach ssh:hostname:102`, but can't get any windows sent over the connection. On the server, if I run `DISPLAY=:102 xterm`, I get "No protocol specified" and "xterm: Xt error: Can't open display: :102". Firefox similarly gives me "No protocol specified / Unable to init server: Could not connect: Connection refused / Error: cannot open display: :102". I can start xterm through an ssh session with X-forwarding, so X is somehow working. The full xpra start and Xorg commands as shown in ps aux are: /usr/bin/python2 /usr/bin/xpra start :102 --start-via-proxy=no --env=XPRA_PROXY_START_UUID=(some long uuid) --daemon=yes --systemd-run=no /usr/lib/bin/xorg/Xorg-for-Xpra-:102 -noreset -novtswitch -nolisten tcp +extension GLX +extension XRANDR +extension RENDER -auth /run/user/1000/xpra/Xauthority-102 -logfile /run/user/1000/xpra/Xorg.:102.log -configdir /run/user/1000/xpra/xorg.conf.d/9075 -config /etc/xpra/xorg.conf -depth 24 :102 Errors in Xorg.:102.log are: (EE) Unable to open config directory: "/run/user/1000/xpra/xorg.conf.d/9075" (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted (EE) AIGLX: reverting to software rendering and a bunch of (EE) Failed to load module something (module does not exist, 0), where "something" is mouse, kbd, libinput Errors in :102.log are: /bin/sh: 1: dbus-launch: not found dbus-launch failed to start using command 'dbus-launch --close-stderr': ?exit code is 127 (but later there is the message "D-Bus notification forwarding is available") And the log ends with "xpra is ready / printer forwarding enabled.... / 3.9GB of system memory" The VM running the Xpra server is a fresh Debian Buster install (without any graphical desktop environment) where I just `apt-get install xpra`ed. Interestingly, on a fresh Debian Buster + Gnome 3 install, I get a similar issue with `xpra start` apparently failing but still starting the display and letting me connect with `xpra attach`. On that VM, I can get a window sent over if I add the flags ` --start-via-proxy=no --xvfb="/usr/bin/Xwayland -rootless -noreset` to the start command to use Gnome's Xwayland X server. Any ideas of where to poke to get more information on what's going wrong? Thanks! Persimmon From antoine at nagafix.co.uk Mon Apr 30 08:43:29 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 30 Apr 2018 14:43:29 +0700 Subject: [winswitch] Xpra "can't open display" error In-Reply-To: References: Message-ID: On 30/04/18 01:59, pxd--- via shifter-users wrote: > Hi, > Using Xpra 2.3-r19058 from the Xpra Debian buster repo (on client and server), I can't get the display to get sent over ssh from a headless VM to the VM's host machine. > > From the client machine, if I run: > xpra start ssh:hostname:102 --start-via-proxy=no > > I get: > xpra initialization error: > ?failed to identify the new server display > Error: failed to receive anything, not an xpra server? > ? could also be the wrong protocol, username, password, or port > Connection lost That's usually an ssh connection problem, or maybe the server took too long to start. Try starting the server in advance from a server shell then run "attach" from the client. > But `xpra list` on the host machine shows that display :102 was successfully started and live. (If I do the above without `--start-via-proxy=no`, I get the same errors and can see? the xpra command running with `ps aux`, but I can't connect to it, there are no xpra sessions found with `xpra list` and I have to manually kill the xpra process.) > > I can attach to the session without any client side errors with `xpra attach ssh:hostname:102`, but can't get any windows sent over the connection. > > On the server, if I run `DISPLAY=:102 xterm`, This should be avoided. If possible, always use "--start=xterm" instead, this will use the correct environment settings to run the command. > I get "No protocol specified" and "xterm: Xt error: Can't open display: :102". Firefox similarly gives me "No protocol specified / Unable to init server: Could not connect: Connection refused / Error: cannot open display: :102". Details can be found in: http://xpra.org/trac/ticket/1776 xpra 2.3 will not use "private XAUTHORITY files" by default to avoid this sort of confusion, but this behaviour can be changed using the XPRA_PRIVATE_XAUTH environment variable. > I can start xterm through an ssh session with X-forwarding, so X is somehow working. > > The full xpra start and Xorg commands as shown in ps aux are: > /usr/bin/python2 /usr/bin/xpra start :102 --start-via-proxy=no --env=XPRA_PROXY_START_UUID=(some long uuid) --daemon=yes --systemd-run=no > /usr/lib/bin/xorg/Xorg-for-Xpra-:102 -noreset -novtswitch -nolisten tcp +extension GLX +extension XRANDR +extension RENDER -auth /run/user/1000/xpra/Xauthority-102 -logfile /run/user/1000/xpra/Xorg.:102.log -configdir /run/user/1000/xpra/xorg.conf.d/9075 -config /etc/xpra/xorg.conf -depth 24 :102 > > Errors in Xorg.:102.log are: > (EE) Unable to open config directory: "/run/user/1000/xpra/xorg.conf.d/9075" > (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted > (EE) AIGLX: reverting to software rendering > and a bunch of (EE) Failed to load module something (module does not exist, 0), where "something" is mouse, kbd, libinput All of those can be safely ignored. > Errors in :102.log are: > /bin/sh: 1: dbus-launch: not found > dbus-launch failed to start using command 'dbus-launch --close-stderr': > ?exit code is 127 Not sure why dbus-launch would fail here, is it installed correctly? > (but later there is the message "D-Bus notification forwarding is available") > And the log ends with "xpra is ready / printer forwarding enabled.... / 3.9GB of system memory" > > The VM running the Xpra server is a fresh Debian Buster install (without any graphical desktop environment) where I just `apt-get install xpra`ed. Interestingly, on a fresh Debian Buster + Gnome 3 install, I get a similar issue with `xpra start` apparently failing but still starting the display and letting me connect with `xpra attach`. On that VM, I can get a window sent over if I add the flags ` --start-via-proxy=no --xvfb="/usr/bin/Xwayland -rootless -noreset` to the start command to use Gnome's Xwayland X server. Please file a ticket. Debian Buster is not a high priority at the moment as it is still pretty far from its release date, but this should eventually be fixed. Cheers Antoine > > Any ideas of where to poke to get more information on what's going wrong? > > Thanks! > > Persimmon > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users >