From ajs1 at cam.ac.uk Wed Mar 3 21:02:11 2021 From: ajs1 at cam.ac.uk (Anthony Stone) Date: Wed, 3 Mar 2021 21:02:11 +0000 Subject: [winswitch] xpra 4.1 repeated warning Message-ID: <79905caf-c759-9967-20ea-cbf65edea7f9@cam.ac.uk> Antoine, I have encountered a tiresome niggle in the otherwise excellent xpra. I have v.4.1 of xpra installed on both server and client, both running under Ubuntu 18.04. When I started a new session, the first with the new version, I got the following warning message repeated several times a second: 2021-03-03 20:33:17,987 audio playback Warning: object of type `GstPulseSink' does not have property `processing-deadline' I can stop this by switching off the speaker in the system tray menu, and I don't use audio anyway, but it's a nuisance. I have tried setting --speaker=disabled in the config file, but xpra complains that it's an invalid option. I find that I can avoid the problem by including "--speaker=disabled" in the "xpra start" command, but I suspect that it shouldn't be necessary. Is this a bug or a feature? Regards, Anthony From antoine at nagafix.co.uk Thu Mar 4 03:41:02 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 4 Mar 2021 10:41:02 +0700 Subject: [winswitch] xpra 4.1 repeated warning In-Reply-To: <79905caf-c759-9967-20ea-cbf65edea7f9@cam.ac.uk> References: <79905caf-c759-9967-20ea-cbf65edea7f9@cam.ac.uk> Message-ID: <474515f0-93bf-ae17-dab9-c6c1eb60a331@nagafix.co.uk> On 04/03/2021 04:02, Anthony Stone via shifter-users wrote: > Antoine, > > I have encountered a tiresome niggle in the otherwise excellent xpra. > > I have v.4.1 of xpra installed on both server and client, both running > under Ubuntu 18.04. When I started a new session, the first with the new > version, I got the following warning message repeated several times a > second: > 2021-03-03 20:33:17,987 audio playback Warning: object of type > `GstPulseSink' does not have property `processing-deadline' > > I can stop this by switching off the speaker in the system tray menu, > and I don't use audio anyway, but it's a nuisance. I have tried setting > --speaker=disabled > in the config file, but xpra complains that it's an invalid option. That's the correct option but the configuration file does not accept the "--" prefix which is only used for command line options. Try this instead: echo "speaker=disabled" >> ~/.config/xpra/xpra.conf > I find that I can avoid the problem by including "--speaker=disabled" in > the "xpra start" command, but I suspect that it shouldn't be necessary. > > Is this a bug or a feature? It's a bug, one that only occurs on some distributions and so it wasn't spotted during pre-release testing. There will be a fix for it in 4.1.1 Cheers, Antoine > > Regards, > Anthony > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From luca.manganelli at comune.trento.it Fri Mar 5 11:20:39 2021 From: luca.manganelli at comune.trento.it (Luca Manganelli) Date: Fri, 5 Mar 2021 12:20:39 +0100 Subject: [winswitch] 4.1: cannot start terminal anymore Message-ID: Hello, since 4.1, using this command doesn't launch gnome-terminal anymore: xpra start ssh://user at host/ --start=gnome-terminal --dpi=120 p.s. 4.1 is installed on both client and server. The output of the command xpra start is: 2021-03-05 12:16:43,425 Authentication (password) successful! 2021-03-05 12:16:43,929 keyboard settings: rules=evdev, model=pc105, layout=it 2021-03-05 12:16:43,931 desktop size is 1920x1080 with 1 screen: 2021-03-05 12:16:43,931 :0.0 (508x285 mm - DPI: 96x96) workarea: 1920x1044 2021-03-05 12:16:43,931 ENC DP-1 (528x297 mm - DPI: 92x92) 2021-03-05 12:16:44,216 SSH: 'Entering daemon mode; any further errors will be reported to:' 2021-03-05 12:16:44,216 SSH: ' /run/user/1000/xpra/S556615.log' 2021-03-05 12:16:50,174 SSH: 'Actual display used: :3' 2021-03-05 12:16:50,175 SSH: 'Actual log file name is now: /run/user/1000/xpra/:3.log' 2021-03-05 12:16:59,260 SSH EOF on stderr of run-xpra 2021-03-05 12:16:59,267 Error: failed to receive anything, not an xpra server? 2021-03-05 12:16:59,267 could also be the wrong protocol, username, password or port 2021-03-05 12:16:59,267 or the session was not found 2021-03-05 12:16:59,267 Connection lost 2021-03-05 12:16:59,297 removing unix domain socket '/run/user/1000/xpra/clients/hp800-21912' the log "/run/user/1000/xpra/S556615.log" doesn't exist either in the server or in the client. From antoine at nagafix.co.uk Fri Mar 5 15:59:17 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 5 Mar 2021 22:59:17 +0700 Subject: [winswitch] 4.1: cannot start terminal anymore In-Reply-To: References: Message-ID: On 05/03/2021 18:20, Luca Manganelli via shifter-users wrote: > Hello, > > since 4.1, using this command doesn't launch gnome-terminal anymore: > > xpra start ssh://user at host/ --start=gnome-terminal --dpi=120 > > p.s. 4.1 is installed on both client and server. > > The output of the command xpra start is: > > 2021-03-05 12:16:43,425 Authentication (password) successful! > 2021-03-05 12:16:43,929 keyboard settings: rules=evdev, model=pc105, > layout=it > 2021-03-05 12:16:43,931 desktop size is 1920x1080 with 1 screen: > 2021-03-05 12:16:43,931 :0.0 (508x285 mm - DPI: 96x96) workarea: 1920x1044 > 2021-03-05 12:16:43,931 ENC DP-1 (528x297 mm - DPI: 92x92) > 2021-03-05 12:16:44,216 SSH: 'Entering daemon mode; any further errors > will be reported to:' > 2021-03-05 12:16:44,216 SSH: ' /run/user/1000/xpra/S556615.log' > 2021-03-05 12:16:50,174 SSH: 'Actual display used: :3' > 2021-03-05 12:16:50,175 SSH: 'Actual log file name is now: > /run/user/1000/xpra/:3.log' > 2021-03-05 12:16:59,260 SSH EOF on stderr of run-xpra > 2021-03-05 12:16:59,267 Error: failed to receive anything, not an xpra > server? > 2021-03-05 12:16:59,267 could also be the wrong protocol, username, > password or port > 2021-03-05 12:16:59,267 or the session was not found > 2021-03-05 12:16:59,267 Connection lost > 2021-03-05 12:16:59,297 removing unix domain socket > '/run/user/1000/xpra/clients/hp800-21912' > > > the log "/run/user/1000/xpra/S556615.log" doesn't exist either in the > server or in the client. Like it says 2 lines further down in your log output: "Actual log file name is now: /run/user/1000/xpra/:3.log" (this file will be on the server) I suspect that you're hitting a bug that I have managed to reproduce on some distributions with the new ffmpeg vaapi codec. It causes the server to crash and the session to fail. Until I can release 4.1.1 with the appropriate fix, you can start your servers with: --env=XPRA_VAAPI=0 Or with: --video-encoders=nvenc,x264,vpx This regression was not spotted earlier because it seems have started triggering only recently, without any changes in the xpra code. Cheers, Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From totaam at xpra.org Sun Mar 7 15:01:37 2021 From: totaam at xpra.org (Antoine Martin) Date: Sun, 7 Mar 2021 22:01:37 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 4.1.1 Message-ID: Hi, A few nagging issues evaded the final testing before the 4.1 release so I am releasing 4.1.1 rather quickly to deal with these: * server crash with the new "vaapi" hardware acceleration: this is disabled by default for now, use XPRA_VAAPI=1 to re-enable it * a bunch of "xpra top" bugs * SSH connection errors (MS Windows, trailing slash) * workaound for API breakage in newer versions of python-zeroconf * silence GStreamer warnings The more detailed release notes can be found here: https://github.com/Xpra-org/xpra/blob/v4.1.x/docs/CHANGELOG.md The source snapshots are available on github, pypi as well as the usual location: https://xpra.org/src/ Downloads: https://github.com/Xpra-org/xpra/wiki/Download Cheers Antoine From piratenteam at hotmail.com Wed Mar 24 12:51:03 2021 From: piratenteam at hotmail.com (Piratenteam SVWS) Date: Wed, 24 Mar 2021 12:51:03 +0000 Subject: [winswitch] HTML5 Server throws an Error code 400 XPRA 4.1.1 on Linux DietPi 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux Message-ID: Hi XPRA Team and Enthusiasts I love XPRA and want to have one on my own server. System: XPRA 4.1.1 on Linux DietPi 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux Debian 10 Buster as base system Command starting Xpra: xpra start :102 --start-child=xterm --exit-with-children --bind-tcp=0.0.0.0:2017 --html=on --mdns=no --webcam=no Connection using the current XPRA client from Linux or Windows works without issues. When trying to use the HTML5 server I am confronted with this error message: Server Error Error code 400. Message: this port does not support HTTP requests. Error code explanation: 400 = Bad request syntax or unsupported method. I am at a loss what to try next to solve it. Having "my session" in a browser (secured via SSH port forwarding) is a fantastic feature. Thank you for an exceptional piece of productivity enhancing software! Cheers, Georg From antoine at nagafix.co.uk Wed Mar 24 13:55:58 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 24 Mar 2021 20:55:58 +0700 Subject: [winswitch] HTML5 Server throws an Error code 400 XPRA 4.1.1 on Linux DietPi 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux In-Reply-To: References: Message-ID: <74c0ad75-b20d-ada6-5ae6-6c25558d31a9@nagafix.co.uk> On 24/03/2021 19:51, Piratenteam SVWS via shifter-users wrote: > Hi XPRA Team and Enthusiasts > > I love XPRA and want to have one on my own server. > > > System: > XPRA 4.1.1 on Linux DietPi 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux > Debian 10 Buster as base system > > Command starting Xpra: > xpra start :102 --start-child=xterm --exit-with-children --bind-tcp=0.0.0.0:2017 --html=on --mdns=no --webcam=no > > Connection using the current XPRA client from Linux or Windows works without issues. > > > > When trying to use the HTML5 server I am confronted with this error message: > > Server Error > > Error code 400. > > Message: this port does not support HTTP requests. > > Error code explanation: 400 = Bad request syntax or unsupported method. My guess is that you're using an unsupported xpra package which is missing the html5 client component. Install the official xpra.org packages or install the html5 client on top of your existing installation: https://github.com/Xpra-org/xpra-html5 If that does not solve the problem, please look at the server log. Cheers, Antoine > > > I am at a loss what to try next to solve it. > > Having "my session" in a browser (secured via SSH port forwarding) is a fantastic feature. > > > Thank you for an exceptional piece of productivity enhancing software! > > > Cheers, > > Georg From totaam at xpra.org Tue Mar 30 10:28:18 2021 From: totaam at xpra.org (Antoine Martin) Date: Tue, 30 Mar 2021 16:28:18 +0700 Subject: [winswitch] [ANNOUNCE] xpra-html5 4.1.1 Message-ID: <5c8f2a4b-b8d3-f48c-9a8a-86e87ce78d5d@xpra.org> Hi, This is the first release of the HTML5 client since it was moved to a separate github repository: https://github.com/Xpra-org/xpra-html5 It's been a fairly quiet release cycle for the HTML5 client, with just a few new features: * open print dialog * added documentation (installation, connection options, authentication, etc) * build option for platforms without any minifiers * on screen keyboard * better connection diagnostic messages * download connection files and generate connection URIs * support for rgb24 pixel encoding There was no publicized 4.1.0 release, though a git tag had been created for it. The source snapshot is at the usual location: https://xpra.org/src/ And now also on github: https://github.com/Xpra-org/xpra-html5/releases Cheers Antoine