From antoine at nagafix.co.uk Fri Jun 7 12:52:02 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 7 Jun 2019 18:52:02 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.5.2: many fixes, none critical Message-ID: Hi, Just like the previous update, this is a collection of fixes that had accumulated for too long, updating is recommended but none of the bugs fixed are critical. Release notes: * fix mmap leak which can cause the client to stop painting * fix OpenGL crashes: don't use it when probing process has crashed * fix errors in avahi error handler * fix connection errors when loading ssh public keys * fix tests being run with the wrong python interpreter version * fix systemd-run using the wrong python interpreter version * fix start menu with python3 clients * fix x264 encoder creating incompatible stream for the html5 client * fix unnecessary xdg menu data in some subcommands * fix large xdg menu data causing initial packet size errors * fix packet size warning message format * fix start menu with python3 clients * fix html5 client connection error when xdg-menu data is missing * fix html5 client compatibility with buggy x264 encoders (as above) * fix html5 client clipboard packet format * fix session info graphs start values * fix colour channels swapped with some window icons and desktop servers * fix slower compression code path wrongly used when av-sync is disabled * fix icon type attribute (remove dot) * fix signal forwarding with python3 servers * fix system tray forwarding with python3 servers * fix socket attributes name lookup for xpra info * fix handling proxy server info requests * fix proxy server info errors trying to enumerate sessions * fix automatic MTU adjustements with UDP transport * fix NVENC compatiblity with library soname found in newer installers * fix invalid python2 DEB dependency in main meta package * fix default config value for opengl attribute * fix HTML5 client authentication bug when going through a proxy server * fix socket errors on startup with bind-ssl * fix server dbus service attribute accessor methods * fix network jitter injector * fix avahi mdns publisher test tool * fix zeroconf error when service info is not available * fix remote ssh failures with python3-only installations * fix automatic interpreter version switching when re-executing * fix start-via-proxy exit code handler * fix socket-permissions option not being honoured * fix error in the codec loader if the first codec attempted fails * fix error in the codec instantiation leak detection code * fix exit hooks not being called with 'exit-with-client' * fix RandR build errors with older versions of Cython (ie: Xenial) * fix GTK3 build of the keyboard test tool on MS Windows * fix errors parsing xresources * fix handling of xsettings with python3 servers * fix font hinting detection with python3 * fix cleanup errors if server initialization or startup had failed * fix pure python3 builds cairo headers used * updated package dependencies: recommend python-dns for sshfp support The source: https://xpra.org/src/ Downloads: https://xpra.org/trac/wiki/Download Cheers Antoine From berserker.troll at yandex.com Sun Jun 16 02:11:33 2019 From: berserker.troll at yandex.com (Troll Berserker) Date: Sun, 16 Jun 2019 04:11:33 +0300 Subject: [winswitch] Empty "Start" menu in the HTML5 client Message-ID: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> Hi, I'm running xpra GTK2 X11 version 2.5-r22138 64-bit as a server and use xpra-html5-3.0-0.20190612r22922.el7_6.noarch.rpm as a client. I'm starting the server with `start-new-commands = yes` set in configs. Starting the server with `-d menu` option shows that `.desktop` files are loaded. Here is a fragment of the log: 2019-06-16 01:05:11,023 Type=Application () 2019-06-16 01:05:11,023 VersionString= () 2019-06-16 01:05:11,023 Name=Xpra () 2019-06-16 01:05:11,023 GenericName= () 2019-06-16 01:05:11,023 NoDisplay=False () 2019-06-16 01:05:11,023 Comment=Xpra GUI () 2019-06-16 01:05:11,024 Icon=xpra () 2019-06-16 01:05:11,024 Hidden=False () 2019-06-16 01:05:11,024 OnlyShowIn=[] () 2019-06-16 01:05:11,024 NotShowIn=[] () 2019-06-16 01:05:11,024 Exec=xpra () 2019-06-16 01:05:11,025 TryExec= () 2019-06-16 01:05:11,025 Path= () 2019-06-16 01:05:11,025 Terminal=False () 2019-06-16 01:05:11,025 MimeTypes=[] () 2019-06-16 01:05:11,025 Categories=[u'Network', u'RemoteAccess'] () 2019-06-16 01:05:11,025 StartupNotify=False () 2019-06-16 01:05:11,025 StartupWMClass= () 2019-06-16 01:05:11,025 URL= () 2019-06-16 01:05:11,025 properties(Xpra)={'Comment': u'Xpra GUI', 'MimeTypes': [], 'StartupWMClass': '', 'NoDisplay': False, 'Name': u'Xpra', 'Exec': u'xpra', 'URL': '', 'TryExec': '', 'StartupNotify': False, 'OnlyShowIn': [], 'Terminal': False, 'GenericName': '', 'VersionString': '', 'Path': '', 'NotShowIn': [], 'Hidden': False, 'Type': u'Application', 'Categories': [u'Network', u'RemoteAccess'], 'Icon': u'xpra'} 2019-06-16 01:05:11,068 got icon data from '/usr/share/icons/xpra.png': 3011 bytes However, the "Start" menu in the HTML5 client is completely empty. What I'm doing wrong? From antoine at nagafix.co.uk Sun Jun 16 07:33:02 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 16 Jun 2019 13:33:02 +0700 Subject: [winswitch] Empty "Start" menu in the HTML5 client In-Reply-To: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> References: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> Message-ID: <73f947ff-ed7f-e9e7-e362-dcf9caeb55c4@nagafix.co.uk> On 16/06/2019 08:11, Troll Berserker via shifter-users wrote: > Hi, > > I'm running > xpra GTK2 X11 version 2.5-r22138 64-bit > as a server and use > xpra-html5-3.0-0.20190612r22922.el7_6.noarch.rpm > as a client. > > I'm starting the server with `start-new-commands = yes` set in configs. > Starting the server with `-d menu` option shows that `.desktop` files > are loaded. > Here is a fragment of the log: > (..) > > However, the "Start" menu in the HTML5 client is completely empty. > What I'm doing wrong? Nothing. This should work. I've just tried it and that worked for me with a v2.5.2 server and latest trunk for the html5 client. We've changed how and when this menu data is sent to the client: http://xpra.org/trac/ticket/2310 But this should be backwards compatible. Make sure that start-new-commands is enabled on the server: * in the default config: xpra showconfig | grep start-new-commands * querying a running server: xpra info | grep start-new-commands Cheers, Antoine From berserker.troll at yandex.com Sun Jun 16 14:08:40 2019 From: berserker.troll at yandex.com (Troll Berserker) Date: Sun, 16 Jun 2019 16:08:40 +0300 Subject: [winswitch] Empty "Start" menu in the HTML5 client In-Reply-To: <73f947ff-ed7f-e9e7-e362-dcf9caeb55c4@nagafix.co.uk> References: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> <73f947ff-ed7f-e9e7-e362-dcf9caeb55c4@nagafix.co.uk> Message-ID: <606f253e-61ac-fd96-90b6-97d55265f338@yandex.com> On 16/06/2019 09:33, Antoine Martin via shifter-users wrote: > On 16/06/2019 08:11, Troll Berserker via shifter-users wrote: >> Hi, >> >> I'm running >> xpra GTK2 X11 version 2.5-r22138 64-bit >> as a server and use >> xpra-html5-3.0-0.20190612r22922.el7_6.noarch.rpm >> as a client. >> >> I'm starting the server with `start-new-commands = yes` set in configs. >> Starting the server with `-d menu` option shows that `.desktop` files >> are loaded. >> Here is a fragment of the log: >> > (..) >> >> However, the "Start" menu in the HTML5 client is completely empty. >> What I'm doing wrong? > Nothing. This should work. > I've just tried it and that worked for me with a v2.5.2 server and > latest trunk for the html5 client. > > We've changed how and when this menu data is sent to the client: > http://xpra.org/trac/ticket/2310 > But this should be backwards compatible. > > Make sure that start-new-commands is enabled on the server: > * in the default config: > xpra showconfig | grep start-new-commands It says that (used) = True (default) = False > * querying a running server: > xpra info | grep start-new-commands Says: features.start-new.commands=True From antoine at nagafix.co.uk Sun Jun 16 18:23:44 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 17 Jun 2019 00:23:44 +0700 Subject: [winswitch] Empty "Start" menu in the HTML5 client In-Reply-To: <606f253e-61ac-fd96-90b6-97d55265f338@yandex.com> References: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> <73f947ff-ed7f-e9e7-e362-dcf9caeb55c4@nagafix.co.uk> <606f253e-61ac-fd96-90b6-97d55265f338@yandex.com> Message-ID: <50a68621-aa5d-63fb-d976-0e64d15fa2f3@nagafix.co.uk> >> We've changed how and when this menu data is sent to the client: >> http://xpra.org/trac/ticket/2310 >> But this should be backwards compatible. >> >> Make sure that start-new-commands is enabled on the server: >> * in the default config: >> xpra showconfig | grep start-new-commands > > It says that > (used) = True > (default) = False > >> * querying a running server: >> xpra info | grep start-new-commands > > Says: > features.start-new.commands=True Then everything is configured correctly, and I have no idea why your html5 client isn't showing you the start menu. Please create a ticket and I'll attach some patches to it that should help debug things. Cheers, Antoine From antoine at nagafix.co.uk Mon Jun 17 05:29:17 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 17 Jun 2019 11:29:17 +0700 Subject: [winswitch] Empty "Start" menu in the HTML5 client In-Reply-To: <606f253e-61ac-fd96-90b6-97d55265f338@yandex.com> References: <4d9df557-423d-ad21-9dae-36511916cb0b@yandex.com> <73f947ff-ed7f-e9e7-e362-dcf9caeb55c4@nagafix.co.uk> <606f253e-61ac-fd96-90b6-97d55265f338@yandex.com> Message-ID: >>> However, the "Start" menu in the HTML5 client is completely empty. >>> What I'm doing wrong? >> Nothing. This should work. >> I've just tried it and that worked for me with a v2.5.2 server and >> latest trunk for the html5 client. >> >> We've changed how and when this menu data is sent to the client: >> http://xpra.org/trac/ticket/2310 >> But this should be backwards compatible. >> >> Make sure that start-new-commands is enabled on the server: >> * in the default config: >> xpra showconfig | grep start-new-commands > > It says that > (used) = True > (default) = False > >> * querying a running server: >> xpra info | grep start-new-commands > > Says: > features.start-new.commands=True For the record, the detailed ticket and its resolution can be found here https://xpra.org/trac/ticket/2335#comment:1 The html5 start menu is an upcoming v3.0 feature, which can be tested by installing the beta packages of the html5 client, or directly here: http://xpra.org/html5/connect.html Cheers, Antoine From dusan at dussan.org Mon Jun 17 10:34:45 2019 From: dusan at dussan.org (=?utf-8?q?dusan=40dussan=2Eorg?=) Date: Mon, 17 Jun 2019 05:34:45 -0400 Subject: [winswitch] DATA FROM ONE SOCKET IS REDIRECTED TO ANOTHER SOCKET Message-ID: <1a7-5d075e80-b-6c4a7f00@105145663> I don't know if this a bug or not. My problem: I run two different instances of libreoffice (calculator and writer) on same machine but on the different displays and the different ports. If I connect with XPRA Html5 clients, the program (libreoffice writter) which I have to see on the second HTML client is showing on the first HTML client. If I do the same with the another program, like a xterm, this never happend. How to reproduce: run the bellow commands one the same server. xpra start :11000 --bind-tcp=0.0.0.0:11000 --tcp-auth=none --mdns=yes --start="localc" xpra start :12000 --bind-tcp=0.0.0.0:12000 --tcp-auth=none --mdns=yes --start="lowritter" Then connect with one web browser to the port 11000 and with another to the port 12000 (to the server from where you run xpra commands). You will see that libreoffice witter from the port 12000 is showing in the web client which is connected to the port 11000. I'm using latest XPRA software which is running on Debian 9. From antoine at nagafix.co.uk Mon Jun 17 11:46:11 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 17 Jun 2019 17:46:11 +0700 Subject: [winswitch] DATA FROM ONE SOCKET IS REDIRECTED TO ANOTHER SOCKET In-Reply-To: <1a7-5d075e80-b-6c4a7f00@105145663> References: <1a7-5d075e80-b-6c4a7f00@105145663> Message-ID: <4f4db44a-0f01-bced-7f4c-28d5b790bcd6@nagafix.co.uk> Please don't SHOUT, only use uppercase as necessary. On 17/06/2019 16:34, dusan at dussan.org via shifter-users wrote: > > I don't know if this a bug or not. > My problem: I run two different instances of libreoffice (calculator and writer) on same machine but on the different displays and the different ports. If I connect with XPRA Html5 clients, the program (libreoffice writter) which I have to see on the second HTML client is showing on the first HTML client. > If I do the same with the another program, like a xterm, this never happend. > > How to reproduce: run the bellow commands one the same server. > xpra start :11000 --bind-tcp=0.0.0.0:11000 --tcp-auth=none --mdns=yes --start="localc" > xpra start :12000 --bind-tcp=0.0.0.0:12000 --tcp-auth=none --mdns=yes --start="lowritter" > > Then connect with one web browser to the port 11000 and with another to the port 12000 (to the server from where you run xpra commands). You will see that libreoffice witter from the port 12000 is showing in the web client which is connected to the port 11000. That's a "feature" of the software you are using. It affects many browsers (ie: Firefox and chrome) and others (libreoffice, etc) - usually the more heavyweight variety. They have a master process and when you try to start a new instance, they go through this master process, opening the new window on the display where the master instance is running rather than the one you asked for. There is nothing xpra can do about this. You may be able to workaround the issue by: * using a different user account * modifying the environment to fool the application into thinking this is a new profile Cheers, Antoine > I'm using latest XPRA software which is running on Debian 9. Please always specify the exact version in use.