From yogata at jscom.co.jp Mon Mar 2 01:19:29 2020 From: yogata at jscom.co.jp (=?iso-2022-jp?B?GyRCSHg3QRsoQiAbJEJNNDUqGyhC?=) Date: Mon, 02 Mar 2020 10:19:29 +0900 (JST) Subject: [winswitch] About clipboard-filter-file option Message-ID: <1583111969.30643.yogata@jscom.co.jp> Hello It?s a pretty rudimentary question, I want to exclude png and jpeg format data from the contents of the clipboard. Is it OK if the contents of the file specified in the --clipboard-filter-file option are as follows? .*\.(png|jpeg)$ Thanks in advance From mike at cchtml.com Mon Mar 2 23:34:16 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Mon, 2 Mar 2020 17:34:16 -0600 Subject: [winswitch] multiple users with html5 Message-ID: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> Hi, Is there an existing product or workflow that someone has created to handle multiple users logging in through the HTML5 interface? I would like to have each user logging in to their own Xpra instance. The only way I see to do it now is start up Xpra for each user, but this seems wasteful and hard to maintain. Thanks, Michael From antoine at nagafix.co.uk Mon Mar 9 11:50:09 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 9 Mar 2020 18:50:09 +0700 Subject: [winswitch] About clipboard-filter-file option In-Reply-To: <1583111969.30643.yogata@jscom.co.jp> References: <1583111969.30643.yogata@jscom.co.jp> Message-ID: <7e3b7163-d50b-627b-b26b-c54e7d9f01fb@nagafix.co.uk> On 02/03/2020 08:19, ?? ?? via shifter-users wrote: > Hello > > It?s a pretty rudimentary question, > I want to exclude png and jpeg format data from the contents of the clipboard. > Is it OK if the contents of the file specified in the --clipboard-filter-file option are as follows? > > .*\.(png|jpeg)$ Probably not. The filter applies to clipboard data not clipboard content type names. And the PNG file header contains 'PNG' in uppercase, the JPEG header is even harder to identify. In any case, this is probably not the way to go about it: you would also prevent copying of any plain text data containing those two strings. Also, it would not stop the copying of image data in other formats. (ie: webp) A better solution would be to tell the clipboard code to ignore all image content-types. You may be able to achieve this with: XPRA_DISCARD_TARGET=^image/.* xpra start ... Note that this would not completely prevent image data exfiltration, only make it more difficult. Cheers, Antoine > > Thanks in advance From antoine at nagafix.co.uk Mon Mar 9 12:00:13 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 9 Mar 2020 19:00:13 +0700 Subject: [winswitch] Xpra session cloning In-Reply-To: References: Message-ID: <239ad65d-61f2-78ea-5cab-19c27e2f035b@nagafix.co.uk> On 01/03/2020 04:18, Mark Knittel via shifter-users wrote: > Antoine: thanks for your response below. I'll answer the question in-line. Your MUA (office365?) is making it really hard to see who said what in this thread. > Mark Knittel > 360-441-2126 > > > On 15/02/2020 08:35, Mark Knittel via shifter-users wrote: >> Greetings. I am trying to use Xpra on a (local) Apache server to access single desktop applications via browser links on a webpage. >> I need to have multiple users use the same web page link to open a new > version of the application, and then close the session when the window > is closed by the user. > Start your servers with: --exit-with-client=yes > >> That means that I need to prevent one user from taking over the > session from an existing user, and I need to make sure I don't end up > with an excess of open/unused sessions that will consume RAM. >> Is there a realistic way to accomplish this with either: >> >> - Connection strings in the xpra start commands? >> >> - A script that is launched when the URL is clicked? > I don't think there are enough details to give you a clear answer. > How are your users identified? Is this done by apache authentication? > Do you have a straightforward mapping between apache users and unix users? > etc.. > > **** Let me add a little more background. We're attempting to user XPRA on an Apache/Linux system that is being used to serve educational content to schools in remote villages in eastern Africa. The server preloaded with content and is entirely offline - no internet connection, and all users/students connect via wireless devices (notebooks, tablets, phones) using a browser interface. We do not require/need user login, as there is no built in tracking, etc. So we don't have an easy way to identify individual users. We now need to connect users to individual desktop applications, but would like to keep things as simple as possible by continueing to use a browser interface, avoiding an user side XPRA, VNC, etc. client. Hence the reason for XPRA and HTML access. We are testing with the proxy server as well. The challenge we're having is knowing how to format a generic URL/link that will: > > - Start a server to access a specific application when clicked from a browser, and then You could just tweak the standard "connect.html" page and remove all the options you don't need, then instead of a free text input field for the "start command" you could replace it with a drop down menu with your custom list of applications. If you don't care about authentication, you could run all your sessions as a single unprivileged user. Just start the proxy and let each new connection start a new instance as needed. > > - Stop the server when the user closes the application tab in the browser. That's the exit-with-client option. You probably want exit-with-children too. > Any help you can provide would be appreciated. Sorry for the slow reply. Cheers, Antoine > > Mark K From antoine at nagafix.co.uk Mon Mar 9 12:06:21 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 9 Mar 2020 19:06:21 +0700 Subject: [winswitch] multiple users with html5 In-Reply-To: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> Message-ID: On 03/03/2020 06:34, Michael Cronenworth via shifter-users wrote: > Hi, > > Is there an existing product or workflow that someone has created to > handle multiple users logging in through the HTML5 interface? I would > like to have each user logging in to their own Xpra instance. This seems to be a common request, but often with slightly different requirements. We're still trying to figure out what those are to provide the most versatile solution to this problem. > The only way I see to do it now is start up Xpra for each user, but this > seems wasteful and hard to maintain. If those users are not expected to have dedicated user accounts on the server, you can use the sqlite authentication backend (which supersedes the 'multifile' backend) to maintain a list of authentication username + password pairs. There are other ways of doing the same thing (ie: with pam configurations) but this is probably the easiest. Do you want them to be able to start new sessions or only connect to existing ones? Cheers Antoine > > Thanks, > Michael From antoine at nagafix.co.uk Tue Mar 10 06:29:28 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 10 Mar 2020 13:29:28 +0700 Subject: [winswitch] Xpra session cloning In-Reply-To: References: <239ad65d-61f2-78ea-5cab-19c27e2f035b@nagafix.co.uk> Message-ID: Please keep the list CCed. On 10/03/2020 12:47, Mark Knittel wrote: > *** > It is Office 365. I can preface/finish my comments with *** going forward. > > I appreciate the response. I think we can easily do what you are suggesting. However, it would help to know what format to use to pass the connect strings to the xpra proxy server in a URL?. Is there some general format rules that we can follow? We're probably missing something simple, but we've started looking at the code, logs, etc. but not there yet. If not, we'll try modifying connect.html. The parameters you can specify on the connection URI are not documented, unfortunately. But you can easily figure out what parameters are allowed by looking at the "connect.html" form: almost all form fields are allowed as URL attributes. So in your case, something like this should work: http://HOST:PORT/?username=USERNAME&password=PASSWORD&exit_with_children=1&exit_with_client=1&start=xterm&action=start Connecting to a proxy started with: xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=allow Cheers, Antoine > > Thanks, > > Mark Knittel > 360-441-2126 > *** > > -----Original Message----- > From: shifter-users On Behalf Of Antoine Martin via shifter-users > Sent: Monday, March 9, 2020 5:00 AM > To: shifter-users at lists.devloop.org.uk > Subject: Re: [winswitch] Xpra session cloning > > On 01/03/2020 04:18, Mark Knittel via shifter-users wrote: >> Antoine: thanks for your response below. I'll answer the question in-line. > Your MUA (office365?) is making it really hard to see who said what in this thread. > >> Mark Knittel >> 360-441-2126 >> >> >> On 15/02/2020 08:35, Mark Knittel via shifter-users wrote: >>> Greetings. I am trying to use Xpra on a (local) Apache server to access single desktop applications via browser links on a webpage. >>> I need to have multiple users use the same web page link to open a >>> new >> version of the application, and then close the session when the window >> is closed by the user. >> Start your servers with: --exit-with-client=yes >> >>> That means that I need to prevent one user from taking over the >> session from an existing user, and I need to make sure I don't end up >> with an excess of open/unused sessions that will consume RAM. >>> Is there a realistic way to accomplish this with either: >>> >>> - Connection strings in the xpra start commands? >>> >>> - A script that is launched when the URL is clicked? >> I don't think there are enough details to give you a clear answer. >> How are your users identified? Is this done by apache authentication? >> Do you have a straightforward mapping between apache users and unix users? >> etc.. >> >> **** Let me add a little more background. We're attempting to user XPRA on an Apache/Linux system that is being used to serve educational content to schools in remote villages in eastern Africa. The server preloaded with content and is entirely offline - no internet connection, and all users/students connect via wireless devices (notebooks, tablets, phones) using a browser interface. We do not require/need user login, as there is no built in tracking, etc. So we don't have an easy way to identify individual users. We now need to connect users to individual desktop applications, but would like to keep things as simple as possible by continueing to use a browser interface, avoiding an user side XPRA, VNC, etc. client. Hence the reason for XPRA and HTML access. We are testing with the proxy server as well. The challenge we're having is knowing how to format a generic URL/link that will: >> >> - Start a server to access a specific application when clicked from a browser, and then > You could just tweak the standard "connect.html" page and remove all the options you don't need, then instead of a free text input field for the "start command" you could replace it with a drop down menu with your custom list of applications. > > If you don't care about authentication, you could run all your sessions as a single unprivileged user. > Just start the proxy and let each new connection start a new instance as needed. >> >> - Stop the server when the user closes the application tab in the browser. > That's the exit-with-client option. > You probably want exit-with-children too. > >> Any help you can provide would be appreciated. > Sorry for the slow reply. > > Cheers, > Antoine > >> >> Mark K > _______________________________________________ > shifter-users mailing list > mailto:shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From mike at cchtml.com Tue Mar 10 13:05:25 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Tue, 10 Mar 2020 08:05:25 -0500 Subject: [winswitch] multiple users with html5 In-Reply-To: References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> Message-ID: <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> On 3/9/20 7:06 AM, Antoine Martin via shifter-users wrote: > Do you want them to be able to start new sessions or only connect to > existing ones? They need to start their own sessions. Currently a single Xpra session starts under a single user so things like gnome-terminal or IDEs start in the home directory of the Xpra user and not the logging in user. Sounds like the only solution at the moment is Xpra per-user. For VNC / noVNC I can setup XDCMP and have GDM control multiple users and X servers are started for each user that logs into that specific user. From antoine at nagafix.co.uk Wed Mar 11 04:05:31 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Mar 2020 11:05:31 +0700 Subject: [winswitch] multiple users with html5 In-Reply-To: <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> Message-ID: <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> On 10/03/2020 20:05, Michael Cronenworth wrote: > On 3/9/20 7:06 AM, Antoine Martin via shifter-users wrote: >> Do you want them to be able to start new sessions or only connect to >> existing ones? > > They need to start their own sessions. Currently a single Xpra session > starts under a single user so things like gnome-terminal or IDEs start > in the home directory of the Xpra user and not the logging in user. > > Sounds like the only solution at the moment is Xpra per-user. There are different ways of doing that too. You can manage the sessions yourself or use the proxy to do it. > For VNC / noVNC I can setup XDCMP and have GDM control multiple users > and X servers are started for each user that logs into that specific user. The xpra proxy can do pretty much the same thing. ie as root: xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=sys Then you can authenticate as individual unix users on that proxy and request a new sessions. Cheers, Antoine From berserker.troll at yandex.com Wed Mar 11 04:34:38 2020 From: berserker.troll at yandex.com (Troll Berserker) Date: Wed, 11 Mar 2020 07:34:38 +0300 Subject: [winswitch] multiple users with html5 In-Reply-To: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> Message-ID: <32e792df-0ec6-e2f1-2f07-982053a0f9a6@yandex.com> On 03/03/2020 02:34, Michael Cronenworth via shifter-users wrote: > Hi, > > Is there an existing product or workflow that someone has created to handle multiple users logging in through the HTML5 interface? I would like to have each user logging in to their own Xpra instance. Hi, I was playing with putting Xpra behind JupyterHub (does authentication, spawning of user-sessions and protects access to them). > The only way I see to do it now is start up Xpra for each user, but this seems wasteful and hard to maintain. > > Thanks, > Michael > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From mike at cchtml.com Wed Mar 11 14:11:01 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Wed, 11 Mar 2020 09:11:01 -0500 Subject: [winswitch] multiple users with html5 In-Reply-To: <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> Message-ID: <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> On 3/10/20 11:05 PM, Antoine Martin wrote: > The xpra proxy can do pretty much the same thing. ie as root: > xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=sys > > Then you can authenticate as individual unix users on that proxy and > request a new sessions. Thanks! This is what I was looking for. It's working but with a caveat. When I try to use '--tcp-auth=sys' I cannot login. Xpra outputs: Error: PAM authentication check failed: ?No module named 'xpra.server.pam' I'm using Xpra 3.0.6 on RHEL 7. When I use 'tcp-auth=allow' it works, but obviously I need pam instead. Am I missing something else? Thanks, Michael From MarkK at mjkservices.net Wed Mar 11 16:32:16 2020 From: MarkK at mjkservices.net (Mark Knittel) Date: Wed, 11 Mar 2020 16:32:16 +0000 Subject: [winswitch] Xpra session cloning In-Reply-To: References: <239ad65d-61f2-78ea-5cab-19c27e2f035b@nagafix.co.uk> Message-ID: Antoine: I wanted to let you know that the URL parameters you sent me worked perfectly. We are now able to dynamically open/close single application sessions with a single user ID from a web page link. For what it's worth - it might help a lot of folks to document this on the Xpra Tracker site - it could be very useful to a lot of users. We now have the same functionality as NoMachine Terminal Server - which is very expensive. Thanks! Mark Knittel 360-441-2126 -----Original Message----- From: Antoine Martin Sent: Monday, March 9, 2020 11:29 PM To: Mark Knittel ; Xpra and Winswitch ML Subject: Re: [winswitch] Xpra session cloning Please keep the list CCed. On 10/03/2020 12:47, Mark Knittel wrote: > *** > It is Office 365. I can preface/finish my comments with *** going forward. > > I appreciate the response. I think we can easily do what you are suggesting. However, it would help to know what format to use to pass the connect strings to the xpra proxy server in a URL?. Is there some general format rules that we can follow? We're probably missing something simple, but we've started looking at the code, logs, etc. but not there yet. If not, we'll try modifying connect.html. The parameters you can specify on the connection URI are not documented, unfortunately. But you can easily figure out what parameters are allowed by looking at the "connect.html" form: almost all form fields are allowed as URL attributes. So in your case, something like this should work: http://HOST:PORT/?username=USERNAME&password=PASSWORD&exit_with_children=1&exit_with_client=1&start=xterm&action=start Connecting to a proxy started with: xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=allow Cheers, Antoine > > Thanks, > > Mark Knittel > 360-441-2126 > *** > > -----Original Message----- > From: shifter-users On > Behalf Of Antoine Martin via shifter-users > Sent: Monday, March 9, 2020 5:00 AM > To: shifter-users at lists.devloop.org.uk > Subject: Re: [winswitch] Xpra session cloning > > On 01/03/2020 04:18, Mark Knittel via shifter-users wrote: >> Antoine: thanks for your response below. I'll answer the question in-line. > Your MUA (office365?) is making it really hard to see who said what in this thread. > >> Mark Knittel >> 360-441-2126 >> >> >> On 15/02/2020 08:35, Mark Knittel via shifter-users wrote: >>> Greetings. I am trying to use Xpra on a (local) Apache server to access single desktop applications via browser links on a webpage. >>> I need to have multiple users use the same web page link to open a >>> new >> version of the application, and then close the session when the >> window is closed by the user. >> Start your servers with: --exit-with-client=yes >> >>> That means that I need to prevent one user from taking over the >> session from an existing user, and I need to make sure I don't end up >> with an excess of open/unused sessions that will consume RAM. >>> Is there a realistic way to accomplish this with either: >>> >>> - Connection strings in the xpra start commands? >>> >>> - A script that is launched when the URL is clicked? >> I don't think there are enough details to give you a clear answer. >> How are your users identified? Is this done by apache authentication? >> Do you have a straightforward mapping between apache users and unix users? >> etc.. >> >> **** Let me add a little more background. We're attempting to user XPRA on an Apache/Linux system that is being used to serve educational content to schools in remote villages in eastern Africa. The server preloaded with content and is entirely offline - no internet connection, and all users/students connect via wireless devices (notebooks, tablets, phones) using a browser interface. We do not require/need user login, as there is no built in tracking, etc. So we don't have an easy way to identify individual users. We now need to connect users to individual desktop applications, but would like to keep things as simple as possible by continueing to use a browser interface, avoiding an user side XPRA, VNC, etc. client. Hence the reason for XPRA and HTML access. We are testing with the proxy server as well. The challenge we're having is knowing how to format a generic URL/link that will: >> >> - Start a server to access a specific application when clicked from a browser, and then > You could just tweak the standard "connect.html" page and remove all the options you don't need, then instead of a free text input field for the "start command" you could replace it with a drop down menu with your custom list of applications. > > If you don't care about authentication, you could run all your sessions as a single unprivileged user. > Just start the proxy and let each new connection start a new instance as needed. >> >> - Stop the server when the user closes the application tab in the browser. > That's the exit-with-client option. > You probably want exit-with-children too. > >> Any help you can provide would be appreciated. > Sorry for the slow reply. > > Cheers, > Antoine > >> >> Mark K > _______________________________________________ > shifter-users mailing list > mailto:shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Thu Mar 12 04:02:31 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Mar 2020 11:02:31 +0700 Subject: [winswitch] multiple users with html5 In-Reply-To: <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> Message-ID: On 11/03/2020 21:11, Michael Cronenworth wrote: > On 3/10/20 11:05 PM, Antoine Martin wrote: >> The xpra proxy can do pretty much the same thing. ie as root: >> xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=sys >> >> Then you can authenticate as individual unix users on that proxy and >> request a new sessions. > > Thanks! This is what I was looking for. It's working but with a caveat. > > When I try to use '--tcp-auth=sys' I cannot login. Xpra outputs: > > Error: PAM authentication check failed: > ?No module named 'xpra.server.pam' That's odd, the module is present with a default 64-bit CentOS 7 installation of python2-xpra-server-3.0.6-0.r25195: ls -la /usr/lib64/python2.7/site-packages/xpra/server/pam.so You can test that it imports successfully with: python -c "from xpra.server import pam" Maybe one of the libraries pam needs is not installed? ie: yum install pam Otherwise you'll have to figure out what is missing with: ldd /usr/lib64/python2.7/site-packages/xpra/server/pam.so > I'm using Xpra 3.0.6 on RHEL 7. When I use 'tcp-auth=allow' it works, > but obviously I need pam instead. Yes, if your users all have system accounts then it's easier. Otherwise, you can try another backend (ie: sqlite) FYI: you can run your server with "-d auth" to get more authentication debugging output. Cheers, Antoine > > Am I missing something else? > > Thanks, > Michael From antoine at nagafix.co.uk Thu Mar 12 04:05:44 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Mar 2020 11:05:44 +0700 Subject: [winswitch] Xpra session cloning In-Reply-To: References: <239ad65d-61f2-78ea-5cab-19c27e2f035b@nagafix.co.uk> Message-ID: <6b45e577-f5ac-d182-d4b7-ef99afffe7c8@nagafix.co.uk> On 11/03/2020 23:32, Mark Knittel wrote: > Antoine: I wanted to let you know that the URL parameters you sent me worked perfectly. We are now able to dynamically open/close single application sessions with a single user ID from a web page link. > > For what it's worth - it might help a lot of folks to document this on the Xpra Tracker site - it could be very useful to a lot of users. It would be, if only I had the time to do even half the things on my ever growing TODO list.. The wiki is free to edit, so anyone can help with that. Cheers Antoine > We now have the same functionality as NoMachine Terminal Server - which is very expensive. > > Thanks! > > Mark Knittel > 360-441-2126 > > > -----Original Message----- > From: Antoine Martin > Sent: Monday, March 9, 2020 11:29 PM > To: Mark Knittel ; Xpra and Winswitch ML > Subject: Re: [winswitch] Xpra session cloning > > Please keep the list CCed. > > On 10/03/2020 12:47, Mark Knittel wrote: >> *** >> It is Office 365. I can preface/finish my comments with *** going forward. >> >> I appreciate the response. I think we can easily do what you are suggesting. However, it would help to know what format to use to pass the connect strings to the xpra proxy server in a URL?. Is there some general format rules that we can follow? We're probably missing something simple, but we've started looking at the code, logs, etc. but not there yet. If not, we'll try modifying connect.html. > The parameters you can specify on the connection URI are not documented, unfortunately. > But you can easily figure out what parameters are allowed by looking at the "connect.html" form: almost all form fields are allowed as URL attributes. > > So in your case, something like this should work: > http://HOST:PORT/?username=USERNAME&password=PASSWORD&exit_with_children=1&exit_with_client=1&start=xterm&action=start > > Connecting to a proxy started with: > xpra proxy --bind-tcp=0.0.0.0:10000 --tcp-auth=allow > > Cheers, > Antoine > > >> >> Thanks, >> >> Mark Knittel >> 360-441-2126 >> *** >> >> -----Original Message----- >> From: shifter-users On >> Behalf Of Antoine Martin via shifter-users >> Sent: Monday, March 9, 2020 5:00 AM >> To: shifter-users at lists.devloop.org.uk >> Subject: Re: [winswitch] Xpra session cloning >> >> On 01/03/2020 04:18, Mark Knittel via shifter-users wrote: >>> Antoine: thanks for your response below. I'll answer the question in-line. >> Your MUA (office365?) is making it really hard to see who said what in this thread. >> >>> Mark Knittel >>> 360-441-2126 >>> >>> >>> On 15/02/2020 08:35, Mark Knittel via shifter-users wrote: >>>> Greetings. I am trying to use Xpra on a (local) Apache server to access single desktop applications via browser links on a webpage. >>>> I need to have multiple users use the same web page link to open a >>>> new >>> version of the application, and then close the session when the >>> window is closed by the user. >>> Start your servers with: --exit-with-client=yes >>> >>>> That means that I need to prevent one user from taking over the >>> session from an existing user, and I need to make sure I don't end up >>> with an excess of open/unused sessions that will consume RAM. >>>> Is there a realistic way to accomplish this with either: >>>> >>>> - Connection strings in the xpra start commands? >>>> >>>> - A script that is launched when the URL is clicked? >>> I don't think there are enough details to give you a clear answer. >>> How are your users identified? Is this done by apache authentication? >>> Do you have a straightforward mapping between apache users and unix users? >>> etc.. >>> >>> **** Let me add a little more background. We're attempting to user XPRA on an Apache/Linux system that is being used to serve educational content to schools in remote villages in eastern Africa. The server preloaded with content and is entirely offline - no internet connection, and all users/students connect via wireless devices (notebooks, tablets, phones) using a browser interface. We do not require/need user login, as there is no built in tracking, etc. So we don't have an easy way to identify individual users. We now need to connect users to individual desktop applications, but would like to keep things as simple as possible by continueing to use a browser interface, avoiding an user side XPRA, VNC, etc. client. Hence the reason for XPRA and HTML access. We are testing with the proxy server as well. The challenge we're having is knowing how to format a generic URL/link that will: >>> >>> - Start a server to access a specific application when clicked from a browser, and then >> You could just tweak the standard "connect.html" page and remove all the options you don't need, then instead of a free text input field for the "start command" you could replace it with a drop down menu with your custom list of applications. >> >> If you don't care about authentication, you could run all your sessions as a single unprivileged user. >> Just start the proxy and let each new connection start a new instance as needed. >>> >>> - Stop the server when the user closes the application tab in the browser. >> That's the exit-with-client option. >> You probably want exit-with-children too. >> >>> Any help you can provide would be appreciated. >> Sorry for the slow reply. >> >> Cheers, >> Antoine >> >>> >>> Mark K >> _______________________________________________ >> shifter-users mailing list >> mailto:shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > From mike at cchtml.com Thu Mar 12 13:27:54 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Thu, 12 Mar 2020 08:27:54 -0500 Subject: [winswitch] multiple users with html5 In-Reply-To: References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> Message-ID: <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> On 3/11/20 11:02 PM, Antoine Martin wrote: > That's odd, the module is present with a default 64-bit CentOS 7 > installation of python2-xpra-server-3.0.6-0.r25195: > ls -la /usr/lib64/python2.7/site-packages/xpra/server/pam.so > > You can test that it imports successfully with: > python -c "from xpra.server import pam" > > Maybe one of the libraries pam needs is not installed? ie: > yum install pam > > Otherwise you'll have to figure out what is missing with: > ldd /usr/lib64/python2.7/site-packages/xpra/server/pam.so > >> I'm using Xpra 3.0.6 on RHEL 7. When I use 'tcp-auth=allow' it works, >> but obviously I need pam instead. > Yes, if your users all have system accounts then it's easier. > Otherwise, you can try another backend (ie: sqlite) > > FYI: you can run your server with "-d auth" to get more authentication > debugging output. Thanks for the pointers. I was using the Fedora package rebuilt for RHEL 7. The Fedora package was not shipping the PAM binary module. After a rebuild with PAM enabled auth is working. I'll inform the maintainer. One final issue: Sessions are not closing when the user disconnects. I am using 'xpra proxy --bind-tcp=0.0.0.0:port --html=on --tcp-auth=pam --exit-with-client=yes --terminate-children=yes --exit-with-children=yes' and after a user disconnects the 'xpra start', X server, and pulseaudio are left running. I would have expected the session to fully exit. Am I wrong or am I doing something wrong? Thanks, Michael From antoine at nagafix.co.uk Thu Mar 12 14:32:18 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Mar 2020 21:32:18 +0700 Subject: [winswitch] multiple users with html5 In-Reply-To: <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> Message-ID: <844a649f-2424-972c-317d-f76e3498b55b@nagafix.co.uk> (..) > Thanks for the pointers. I was using the Fedora package rebuilt for RHEL > 7. The Fedora package was not shipping the PAM binary module. After a > rebuild with PAM enabled auth is working. I'll inform the maintainer. Third party packages are plagued with these sorts of issues. And if you are going to be rebuilding packages yourself, please make sure to mention that fact, it will save us all time. > One final issue: Sessions are not closing when the user disconnects. > > I am using 'xpra proxy --bind-tcp=0.0.0.0:port --html=on --tcp-auth=pam > --exit-with-client=yes --terminate-children=yes "exit-with-client" is not honoured by the proxy server, otherwise it would be impossible to use it more than once. What you want is to enable "exit-with-client" for the new session you are starting. (and you're not specifying how you're doing that - so I can't really help with that) > --exit-with-children=yes' and after a user disconnects the 'xpra start', > X server, and pulseaudio are left running. I would have expected the > session to fully exit. Am I wrong or am I doing something wrong? They should all be terminated with the xpra server if you use "exit-with-client". Cheers, Antoine > > Thanks, > Michael From mike at cchtml.com Thu Mar 12 15:13:05 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Thu, 12 Mar 2020 10:13:05 -0500 Subject: [winswitch] multiple users with html5 In-Reply-To: <844a649f-2424-972c-317d-f76e3498b55b@nagafix.co.uk> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> <844a649f-2424-972c-317d-f76e3498b55b@nagafix.co.uk> Message-ID: <694b6c33-d6d9-42c0-4a7c-ba82a8a1b5c6@cchtml.com> On 3/12/20 9:32 AM, Antoine Martin wrote: >> One final issue: Sessions are not closing when the user disconnects. >> >> I am using 'xpra proxy --bind-tcp=0.0.0.0:port --html=on --tcp-auth=pam >> --exit-with-client=yes --terminate-children=yes > "exit-with-client" is not honoured by the proxy server, otherwise it > would be impossible to use it more than once. > > What you want is to enable "exit-with-client" for the new session you > are starting. (and you're not specifying how you're doing that - so I > can't really help with that) It's in the $SUBJECT. I'm only using the HTML5 client (connect.html). > >> --exit-with-children=yes' and after a user disconnects the 'xpra start', >> X server, and pulseaudio are left running. I would have expected the >> session to fully exit. Am I wrong or am I doing something wrong? > They should all be terminated with the xpra server if you use > "exit-with-client". They are not terminating with the HTML5 client. The checkboxes for "Terminate server..." are grey, but checked. From antoine at nagafix.co.uk Thu Mar 12 15:34:50 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Mar 2020 22:34:50 +0700 Subject: [winswitch] multiple users with html5 In-Reply-To: <694b6c33-d6d9-42c0-4a7c-ba82a8a1b5c6@cchtml.com> References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> <844a649f-2424-972c-317d-f76e3498b55b@nagafix.co.uk> <694b6c33-d6d9-42c0-4a7c-ba82a8a1b5c6@cchtml.com> Message-ID: On 12/03/2020 22:13, Michael Cronenworth wrote: > On 3/12/20 9:32 AM, Antoine Martin wrote: >>> One final issue: Sessions are not closing when the user disconnects. >>> >>> I am using 'xpra proxy --bind-tcp=0.0.0.0:port --html=on --tcp-auth=pam >>> --exit-with-client=yes --terminate-children=yes >> "exit-with-client" is not honoured by the proxy server, otherwise it >> would be impossible to use it more than once. >> >> What you want is to enable "exit-with-client" for the new session you >> are starting. (and you're not specifying how you're doing that - so I >> can't really help with that) > > It's in the $SUBJECT. I'm only using the HTML5 client (connect.html). So, you're using the connect.html form, but with what options? >>> --exit-with-children=yes' and after a user disconnects the 'xpra start', >>> X server, and pulseaudio are left running. I would have expected the >>> session to fully exit. Am I wrong or am I doing something wrong? >> They should all be terminated with the xpra server if you use >> "exit-with-client". > > They are not terminating with the HTML5 client. The checkboxes for > "Terminate server..." are grey, but checked. (maybe they should not be checked) The "terminate .." options are only greyed out if you use "Connect" mode, they should be available with "Start", "Start Desktop" and "Shadow". You cannot modify the command line options of a server once it is started and you just connect to it. Cheers, Antoine From mike at cchtml.com Thu Mar 12 17:38:35 2020 From: mike at cchtml.com (Michael Cronenworth) Date: Thu, 12 Mar 2020 12:38:35 -0500 Subject: [winswitch] multiple users with html5 In-Reply-To: References: <875cb3b0-357b-88fc-1352-e07da94a1221@cchtml.com> <4ad2783c-f4b2-e2ff-dfcf-b6169bfe2d94@cchtml.com> <2dd48dd3-936f-1390-50e9-346f5689811f@nagafix.co.uk> <1c5f1959-0a2b-42fd-2848-84514dbf49aa@cchtml.com> <99fddf17-b632-d971-7a0a-9cdee02f777d@cchtml.com> <844a649f-2424-972c-317d-f76e3498b55b@nagafix.co.uk> <694b6c33-d6d9-42c0-4a7c-ba82a8a1b5c6@cchtml.com> Message-ID: On 3/12/20 10:34 AM, Antoine Martin wrote: > So, you're using the connect.html form, but with what options? > >> They are not terminating with the HTML5 client. The checkboxes for >> "Terminate server..." are grey, but checked. > (maybe they should not be checked) > The "terminate .." options are only greyed out if you use "Connect" > mode, they should be available with "Start", "Start Desktop" and "Shadow". > > You cannot modify the command line options of a server once it is > started and you just connect to it. Thanks. The "Connect" option is the default and it Just Worked(tm) so I didn't try the other options. Using "Start Desktop" with the terminate option does terminate when the user disconnects. From antoine at devloop.org.uk Fri Mar 13 17:36:21 2020 From: antoine at devloop.org.uk (Antoine Martin) Date: Sat, 14 Mar 2020 00:36:21 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 3.0.7: many fixes, one important Message-ID: Hi, There's a large number of bug fixes in this release, including a fix for a very old bug which can cause client crashes when decoding H264 streams. There is also the usual set of clipboard and keyboard fixes, and a smattering of platform and other minor issues (transparency, etc). Updating is strongly recommended. Release notes: * fix avcodec2 race condition crash * fix errors when re-initializing windows (ie: toggling OpenGL) * fix deiconification error when there are system trays forwarded * fix missing alpha channel when some windows are first shown * fix systemd-run errors: verify it does work before trying to use it * fix debug builds compilation error on MS Windows * fix server crashes on SIGINT: shutdown cleanly * fix proxy server client connection setup error hanlder * fix file authentication handler using a default password filename * fix directshow errors on local mingw installations * fix opengl properties missing from server hello packet * fix HTML5 sound-control errors when speaker forwarding is disabled * fix HTML5 "Terminate" options wrongly enabled in "Connect" mode * fix clipboard sharing with the MacOS shadow server * fix MS Windows clipboard access denied errors * fix X11 clipboard error handling: continue processing * fix unit tests failures (clipboard, etc) * fix bug report clipboard copy and screnshots * fix clipboard timeouts when a client disconnects * fix mdns cleanup done twice on server exit, causing errors * fix malformed XSettings due to invalid color data format * fix FreeBSD builds * fix MS Windows packaging missing a codec DLL, Plink DLL * fix HMAC hashes exposed, keep only valid options * fix 'showconfig' output for boolean values set to 'auto' * fix parsing of client display information in legacy format * fix validation of size-hints * fix cursor saving debug code with GTK3 * fix keyboard layout group not getting reset on client exit * fix some empty keyboard layout group strings parsed as non-empty * fix keyboard-sync mode not being honoured by servers * fix keyboard raw mode * fix missing 'perispomeni' key mapping with Python 2 servers * add missing debug logging to keyboard mapping * more reliable lookup of keycodes when translating (non-X11 clients) * add missing dependency for printer forwarding on Debian * packaging for Ubuntu Focal Fossa * skip bundling some external test modules with binary installers * more correct code for locating the 'Downloads' folder on MS Windows * avoid spurious background worker warnings on exit * make unavoidable comtypes error less scary * add 'libreoffice' to the text mode whitelist * library updates: Python 3.8.2, etc * packaging workarounds for setuptools breakage Cheers, Antoine From markus.mohr at icloud.com Sun Mar 15 11:25:28 2020 From: markus.mohr at icloud.com (Markus Mohr) Date: Sun, 15 Mar 2020 12:25:28 +0100 Subject: [winswitch] Headless raspi & macOS Message-ID: Hi, I?m new to Xpra and I?m not sure if it can solve my problem. I have a headless Pi with Raspian and I need to continously run a X11 program on it. I?d like to connect and disconnect from this program from macOS and Windows10. Is this possible with Xpra? Thanks From antoine at nagafix.co.uk Sun Mar 15 11:59:23 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 15 Mar 2020 18:59:23 +0700 Subject: [winswitch] Headless raspi & macOS In-Reply-To: References: Message-ID: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> On 15/03/2020 18:25, Markus Mohr via shifter-users wrote: > Hi, > > I?m new to Xpra and I?m not sure if it can solve my problem. > I have a headless Pi with Raspian and I need to continously run a X11 program on it. > I?d like to connect and disconnect from this program from macOS and Windows10. > > Is this possible with Xpra? Yes. ie: assuming you want to connect via ssh: xpra start --start=xterm ssh://user at rpi/ Then re-attach with: xpra attach ssh://user at rpi/ There's also a GUI for connecting more easily. Just beware that the version in raspbian is well out of date.. Cheers, Antoine > > > Thanks > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From markus at johalla.de Sun Mar 15 12:24:02 2020 From: markus at johalla.de (Markus Mohr) Date: Sun, 15 Mar 2020 13:24:02 +0100 Subject: [winswitch] Headless raspi & macOS In-Reply-To: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> References: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> Message-ID: <66E9939A-BF8A-4EED-B261-C636F121EC71@johalla.de> > > ie: assuming you want to connect via ssh: > xpra start --start=xterm ssh://user at rpi/ > Then re-attach with: > xpra attach ssh://user at rpi/ I?ve tried this but I get a lot of error messages: Nelson:~ markus$ xpra start --start=xterm ssh://pi at ra 2020-03-15 13:03:39,671 Xpra GTK3 client version 3.0.7-r25628 64-bit 2020-03-15 13:03:39,715 running on Mac OS X 10.15.3 2020-03-15 13:03:41,143 GStreamer version 1.14.4 for Python 3.8.0 64-bit 2020-03-15 13:03:41,535 OpenGL_accelerate module loaded 2020-03-15 13:03:41,615 Using accelerated ArrayDatatype 2020-03-15 13:03:42,565 Warning: vendor 'Intel Inc.' is greylisted, 2020-03-15 13:03:42,565 you may want to turn off OpenGL if you encounter bugs /Applications/Xpra.app/Contents/Resources/lib/python/numpy/ma/core.py:4466: SyntaxWarning: "is" with a literal. Did you mean "=="? if self.shape is (): /Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/gl/gtk3/nativegl_client_window.py:13: Warning: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed return GLContext().check_support(force_enable) #pylint: disable=not-callable /Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/gl/gtk3/nativegl_client_window.py:13: Warning: g_object_set_qdata_full: assertion 'G_IS_OBJECT (object)' failed return GLContext().check_support(force_enable) #pylint: disable=not-callable /Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/gl/gtk3/nativegl_client_window.py:13: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed return GLContext().check_support(force_enable) #pylint: disable=not-callable 2020-03-15 13:03:43,727 OpenGL enabled with Intel(R) HD Graphics 6000 2020-03-15 13:03:43,792 Connected (version 2.0, client OpenSSH_7.9p1) 2020-03-15 13:03:44,034 Warning: private key '/Users/markus/.ssh/id_rsa' 2020-03-15 13:03:44,034 this file seems to be using OpenSSH's own format 2020-03-15 13:03:44,034 please convert it to something more standard (ie: PEM) 2020-03-15 13:03:44,035 so it can be used with the paramiko backend 2020-03-15 13:03:44,035 or switch to the OpenSSH backend with '--ssh=ssh' 2020-03-15 13:03:44,039 loaded RSA private key from '/Users/markus/.ssh/id_rsa' 2020-03-15 13:03:44,085 Authentication (publickey) successful! 2020-03-15 13:03:44,796 keyboard settings: layout=de 2020-03-15 13:03:44,801 Warning: invalid screen size 7256x8170mm 2020-03-15 13:03:44,802 using 285x178 mm 2020-03-15 13:03:44,810 desktop size is 1440x900 with 1 screen: 2020-03-15 13:03:44,811 nelson-9.local (285x178 mm - DPI: 128x128) workarea: 1440x877 at 0x23 2020-03-15 13:03:44,811 monitor 2 /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/osx_tray.py:91: Warning: invalid cast from 'GtkMenuBar' to 'GtkWindow' self.macapp.set_menu_bar(self.menu) (Xpra:64778): Gtk-CRITICAL **: 13:03:45.004: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed 2020-03-15 13:05:26,528 Error: failed to receive anything, not an xpra server? 2020-03-15 13:05:26,528 could also be the wrong protocol, username, password or port 2020-03-15 13:05:26,529 or the session was not found 2020-03-15 13:05:26,529 Connection lost Then I wanted to make sure the Xpra service is running. Now its a bit weird: I can start and stop the service but status throws errors (and the same one no matter if Xpra has been started or not): root at ra:/home/pi# /etc/init.d/xpra stop [ ok ] Stopping xpra (via systemctl): xpra.service. root at ra:/home/pi# /etc/init.d/xpra start [ ok ] Starting xpra (via systemctl): xpra.service. root at ra:/home/pi# /etc/init.d/xpra stop [ ok ] Stopping xpra (via systemctl): xpra.service. root at ra:/home/pi# /etc/init.d/xpra status ? xpra.service - Xpra System Server Loaded: loaded (/lib/systemd/system/xpra.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-03-15 13:17:49 CET; 31s ago Docs: https://xpra.org/trac/wiki/Service man:xpra Process: 31757 ExecStart=/usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=${TCP_AUTH} --ssl-cert=/etc/xpra/ssl-cert.pem --ssl=on --bind=none --auth=${AUTH} --socket-dirs=/run/xpra --socket-permissions=666 --log-dir=/var/log --pidfile=/run/xpra.pid --debug=${DEBUG} (code=exited, status=1/FAILURE) Main PID: 31757 (code=exited, status=1/FAILURE) M?r 15 13:17:46 ra systemd[1]: Started Xpra System Server. M?r 15 13:17:49 ra xpra[31757]: wrote pid 31757 to '/run/xpra.pid' M?r 15 13:17:49 ra xpra[31757]: xpra initialization error: M?r 15 13:17:49 ra xpra[31757]: cannot create SSL socket, check your certificate paths ('/etc/xpra/ssl-cert.pem'): [Errno 2] No such file or directory M?r 15 13:17:49 ra systemd[1]: xpra.service: Main process exited, code=exited, status=1/FAILURE M?r 15 13:17:49 ra systemd[1]: xpra.service: Failed with result 'exit-code'. > > There's also a GUI for connecting more easily. > Just beware that the version in raspbian is well out of date.. > root at ra:/home/pi# xpra --version xpra v2.4.3-r21350M Maybe this the root of my problems? Is there a current Debian package somewhere or do I have to build it myself (I can, just asking)? Thanks Markus From antoine at nagafix.co.uk Sun Mar 15 13:01:30 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 15 Mar 2020 20:01:30 +0700 Subject: [winswitch] Headless raspi & macOS In-Reply-To: <66E9939A-BF8A-4EED-B261-C636F121EC71@johalla.de> References: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> <66E9939A-BF8A-4EED-B261-C636F121EC71@johalla.de> Message-ID: On 15/03/2020 19:24, Markus Mohr via shifter-users wrote: > >> >> ie: assuming you want to connect via ssh: >> xpra start --start=xterm ssh://user at rpi/ >> Then re-attach with: >> xpra attach ssh://user at rpi/ > > I?ve tried this but I get a lot of error messages: > > Nelson:~ markus$ xpra start --start=xterm ssh://pi at ra (..) > (Xpra:64778): Gtk-CRITICAL **: 13:03:45.004: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed > 2020-03-15 13:05:26,528 Error: failed to receive anything, not an xpra server? > 2020-03-15 13:05:26,528 could also be the wrong protocol, username, password or port > 2020-03-15 13:05:26,529 or the session was not found > 2020-03-15 13:05:26,529 Connection lost FYI: usually, this happens when xpra is not installed on the server, or when you have more than one session already running. On a pi, it is likely to be because the server is taking too long to start up and / or running out of RAM. (this will vary depending on what model you have) > Then I wanted to make sure the Xpra service is running. Now its a bit weird: I can start and stop the service but status throws errors (and the same one no matter if Xpra has been started or not): > > root at ra:/home/pi# /etc/init.d/xpra stop > [ ok ] Stopping xpra (via systemctl): xpra.service. > root at ra:/home/pi# /etc/init.d/xpra start > [ ok ] Starting xpra (via systemctl): xpra.service. > root at ra:/home/pi# /etc/init.d/xpra stop > [ ok ] Stopping xpra (via systemctl): xpra.service. > root at ra:/home/pi# /etc/init.d/xpra status > ? xpra.service - Xpra System Server > Loaded: loaded (/lib/systemd/system/xpra.service; disabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Sun 2020-03-15 13:17:49 CET; 31s ago > Docs: https://xpra.org/trac/wiki/Service > man:xpra > Process: 31757 ExecStart=/usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=${TCP_AUTH} --ssl-cert=/etc/xpra/ssl-cert.pem --ssl=on --bind=none --auth=${AUTH} --socket-dirs=/run/xpra --socket-permissions=666 --log-dir=/var/log --pidfile=/run/xpra.pid --debug=${DEBUG} (code=exited, status=1/FAILURE) > Main PID: 31757 (code=exited, status=1/FAILURE) > > M?r 15 13:17:46 ra systemd[1]: Started Xpra System Server. > M?r 15 13:17:49 ra xpra[31757]: wrote pid 31757 to '/run/xpra.pid' > M?r 15 13:17:49 ra xpra[31757]: xpra initialization error: > M?r 15 13:17:49 ra xpra[31757]: cannot create SSL socket, check your certificate paths ('/etc/xpra/ssl-cert.pem'): [Errno 2] No such file or directory > M?r 15 13:17:49 ra systemd[1]: xpra.service: Main process exited, code=exited, status=1/FAILURE > M?r 15 13:17:49 ra systemd[1]: xpra.service: Failed with result 'exit-code'. You don't need to have the service running. It is optional and on a pi it will just consume extra RAM, which is already scarce. >> There's also a GUI for connecting more easily. >> Just beware that the version in raspbian is well out of date.. >> > > root at ra:/home/pi# xpra --version > xpra v2.4.3-r21350M > > Maybe this the root of my problems? It doesn't help, but no, I have a working setup with 2.4.3 on a pi3. The first problem is that they should have used Xvfb instead of Xdummy on the pi, as the pi isn't powerful enough to load the Xdummy server. To fix it: apt-get install xvfb Then edit /etc/xpra/conf.d/55_server_x11.conf, comment out the last line which has xvfb=/usr/lib/xorg/Xorg and uncomment the line which has xvfb=Xvfb... Another problem is that the client times out because the pi still takes so long to spin up a server. So you may want to start your session via ssh before connecting. ssh to the pi and then: xpra start --start=xterm (and keep an eye on the xpra server log for failures) The pi is OK as a client, but dreadfully slow as a server. > Is there a current Debian package somewhere or do I have to build it myself (I can, just asking)? There are no official packages from xpra.org at this point. You could build from source easily enough though, if you wanted to. Just make sure to build "--without-Xdummy". Cheers, Antoine > > > Thanks > Markus From markus at johalla.de Sun Mar 15 14:01:10 2020 From: markus at johalla.de (Markus Mohr) Date: Sun, 15 Mar 2020 15:01:10 +0100 Subject: [winswitch] Headless raspi & macOS In-Reply-To: References: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> <66E9939A-BF8A-4EED-B261-C636F121EC71@johalla.de> Message-ID: <30E725C4-2117-4D80-BC77-A3191732F924@johalla.de> > On a pi, it is likely to be because the server is taking too long to > start up and / or running out of RAM. > (this will vary depending on what model you have) Its a Pi3 with 1Gb of memory. About two thirds are free. > You don't need to have the service running. > It is optional and on a pi it will just consume extra RAM, which is > already scarce. Ok, stopped it. > apt-get install xvfb > Then edit /etc/xpra/conf.d/55_server_x11.conf, comment out the last line > which has xvfb=/usr/lib/xorg/Xorg and uncomment the line which has > xvfb=Xvfb... Did that and uncommented this line: # - Old Xvfb option (required on Ubuntu where Xorg is broken): xvfb = Xvfb -nolisten tcp -noreset \ +extension GLX +extension Composite \ -auth $XAUTHORITY \ -screen 0 5760x2560x24+32 And commented in this: #xvfb = /usr/lib/xorg/Xorg -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth $XAUTHORITY -logfile ${XPRA_LOG_DIR}/Xorg.${DISPLAY}.log -configdir ${XDG_RUNTIME_DIR}/xpra/xorg.conf.d/$PID -config /etc/xpra/xorg.conf > Another problem is that the client times out because the pi still takes > so long to spin up a server. So you may want to start your session via > ssh before connecting. ssh to the pi and then: > xpra start --start=xterm > (and keep an eye on the xpra server log for failures) That was the problem. Now it works - many thanks! Is there a way to extend the timeout? Because on the first try it didn?t work and it looked like it needed just a few extra seconds. Regards, Markus From antoine at nagafix.co.uk Sun Mar 15 16:00:52 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 15 Mar 2020 23:00:52 +0700 Subject: [winswitch] Headless raspi & macOS In-Reply-To: <30E725C4-2117-4D80-BC77-A3191732F924@johalla.de> References: <2dc786a5-dbed-69f4-d198-16814dc58b99@nagafix.co.uk> <66E9939A-BF8A-4EED-B261-C636F121EC71@johalla.de> <30E725C4-2117-4D80-BC77-A3191732F924@johalla.de> Message-ID: On 15/03/2020 21:01, Markus Mohr via shifter-users wrote: > >> On a pi, it is likely to be because the server is taking too long to >> start up and / or running out of RAM. >> (this will vary depending on what model you have) > > Its a Pi3 with 1Gb of memory. About two thirds are free. This should be enough, but my pi3 with just 512MB of RAM is struggling. >> You don't need to have the service running. >> It is optional and on a pi it will just consume extra RAM, which is >> already scarce. > Ok, stopped it. > >> apt-get install xvfb >> Then edit /etc/xpra/conf.d/55_server_x11.conf, comment out the last line >> which has xvfb=/usr/lib/xorg/Xorg and uncomment the line which has >> xvfb=Xvfb... > Did that and uncommented this line: > > # - Old Xvfb option (required on Ubuntu where Xorg is broken): > xvfb = Xvfb -nolisten tcp -noreset \ > +extension GLX +extension Composite \ > -auth $XAUTHORITY \ > -screen 0 5760x2560x24+32 > > And commented in this: > > #xvfb = /usr/lib/xorg/Xorg -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth $XAUTHORITY -logfile ${XPRA_LOG_DIR}/Xorg.${DISPLAY}.log -configdir ${XDG_RUNTIME_DIR}/xpra/xorg.conf.d/$PID -config /etc/xpra/xorg.conf > > >> Another problem is that the client times out because the pi still takes >> so long to spin up a server. So you may want to start your session via >> ssh before connecting. ssh to the pi and then: >> xpra start --start=xterm >> (and keep an eye on the xpra server log for failures) > > That was the problem. Now it works - many thanks! I have now changed the default to use Xvfb on arm: http://xpra.org/trac/changeset/25652/xpra > Is there a way to extend the timeout? Because on the first try it didn?t work and it looked like it needed just a few extra seconds. I'm not entirely sure which timeout is firing, you can try: XPRA_CONNECT_TIMEOUT=60 xpra start ssh://pi/10 As long as you specify the display on the URI (the "/10" part) Because otherwise you will be hitting the displayfd timeout: XPRA_DISPLAY_FD_TIMEOUT=60 xpra start But this one is server side, so you can't easily override it when you launch directly from the client via ssh. (or you could patch the source) Cheers, Antoine > > Regards, > Markus > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at devloop.org.uk Mon Mar 16 16:05:20 2020 From: antoine at devloop.org.uk (Antoine Martin) Date: Mon, 16 Mar 2020 23:05:20 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 3.0.7: many fixes, one important In-Reply-To: References: Message-ID: <162eaedd-b267-c735-97ba-ef04cb944717@devloop.org.uk> For anyone experiencing keyboard mapping problems with non-X11 clients, in particular keys accessed using the AltGr modifier key, please see: https://xpra.org/trac/ticket/2648#comment:8 This fix will be included in 3.0.8 Cheers, Antoine On 14/03/2020 00:36, Antoine Martin wrote: > Hi, > > There's a large number of bug fixes in this release, including a fix for > a very old bug which can cause client crashes when decoding H264 > streams. There is also the usual set of clipboard and keyboard fixes, > and a smattering of platform and other minor issues (transparency, etc). > > Updating is strongly recommended. > > Release notes: > * fix avcodec2 race condition crash > * fix errors when re-initializing windows (ie: toggling OpenGL) > * fix deiconification error when there are system trays forwarded > * fix missing alpha channel when some windows are first shown > * fix systemd-run errors: verify it does work before trying to use it > * fix debug builds compilation error on MS Windows > * fix server crashes on SIGINT: shutdown cleanly > * fix proxy server client connection setup error hanlder > * fix file authentication handler using a default password filename > * fix directshow errors on local mingw installations > * fix opengl properties missing from server hello packet > * fix HTML5 sound-control errors when speaker forwarding is disabled > * fix HTML5 "Terminate" options wrongly enabled in "Connect" mode > * fix clipboard sharing with the MacOS shadow server > * fix MS Windows clipboard access denied errors > * fix X11 clipboard error handling: continue processing > * fix unit tests failures (clipboard, etc) > * fix bug report clipboard copy and screnshots > * fix clipboard timeouts when a client disconnects > * fix mdns cleanup done twice on server exit, causing errors > * fix malformed XSettings due to invalid color data format > * fix FreeBSD builds > * fix MS Windows packaging missing a codec DLL, Plink DLL > * fix HMAC hashes exposed, keep only valid options > * fix 'showconfig' output for boolean values set to 'auto' > * fix parsing of client display information in legacy format > * fix validation of size-hints > * fix cursor saving debug code with GTK3 > * fix keyboard layout group not getting reset on client exit > * fix some empty keyboard layout group strings parsed as non-empty > * fix keyboard-sync mode not being honoured by servers > * fix keyboard raw mode > * fix missing 'perispomeni' key mapping with Python 2 servers > * add missing debug logging to keyboard mapping > * more reliable lookup of keycodes when translating (non-X11 clients) > * add missing dependency for printer forwarding on Debian > * packaging for Ubuntu Focal Fossa > * skip bundling some external test modules with binary installers > * more correct code for locating the 'Downloads' folder on MS Windows > * avoid spurious background worker warnings on exit > * make unavoidable comtypes error less scary > * add 'libreoffice' to the text mode whitelist > * library updates: Python 3.8.2, etc > * packaging workarounds for setuptools breakage > > > Cheers, > Antoine > From johnsons at google.com Thu Mar 26 22:35:32 2020 From: johnsons at google.com (Scott Johnson) Date: Thu, 26 Mar 2020 15:35:32 -0700 Subject: [winswitch] Xpra-x86_64.pkg cannot be installed on my mac running catalina Message-ID: I get a pop-up window saying "*Xpra-x86_64.pkg? can?t be opened because Apple cannot check it for malicious software.* Apparently the binary has not been signed by Apple. Is there anything that can be done about this issue? From antoine at nagafix.co.uk Fri Mar 27 03:16:53 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 27 Mar 2020 10:16:53 +0700 Subject: [winswitch] Xpra-x86_64.pkg cannot be installed on my mac running catalina In-Reply-To: References: Message-ID: On 27/03/2020 05:35, Scott Johnson via shifter-users wrote: > I get a pop-up window saying "*Xpra-x86_64.pkg? can?t be opened because > Apple cannot check it for malicious software.* Apparently the binary has > not been signed by Apple. Is there anything that can be done about this > issue? Please see: https://xpra.org/trac/ticket/2639 From crl.langlois at gmail.com Fri Mar 27 13:50:57 2020 From: crl.langlois at gmail.com (carl langlois) Date: Fri, 27 Mar 2020 09:50:57 -0400 Subject: [winswitch] profile.d not load Message-ID: Hi, I am currently having trouble getting some global variable to be load when start xpra. I am using this command to start xpra from the client xpra start ssh:user at server Xpra does start correctly on the server and i can attach to it. But some of the variable defined in the profile.d are not present. This is probably something related to interactive vs non-interactive shell... How can i make Xpra start with full login shell? Thanks Regards cl From alexander.berg at atos.net Mon Mar 30 09:18:41 2020 From: alexander.berg at atos.net (Berg, Alexander) Date: Mon, 30 Mar 2020 08:18:41 +0000 Subject: [winswitch] profile.d not load In-Reply-To: References: Message-ID: Hi Carl, I'm solving this by --start-child="xterm -ls" This starts an xterm with a login shell. You could also use a desktop-session like xpra start-desktop ssh:user at server --start-child="startxfce4" --exit-with-children Maybe there is a better workaround? With kind regards, Alex -----Urspr?ngliche Nachricht----- Von: shifter-users Im Auftrag von carl langlois via shifter-users Gesendet: Freitag, 27. M?rz 2020 14:51 An: Xpra and Winswitch ML Betreff: [winswitch] profile.d not load Hi, I am currently having trouble getting some global variable to be load when start xpra. I am using this command to start xpra from the client xpra start ssh:user at server Xpra does start correctly on the server and i can attach to it. But some of the variable defined in the profile.d are not present. This is probably something related to interactive vs non-interactive shell... How can i make Xpra start with full login shell? Thanks Regards cl _______________________________________________ shifter-users mailing list shifter-users at lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users From crl.langlois at gmail.com Mon Mar 30 13:45:27 2020 From: crl.langlois at gmail.com (carl langlois) Date: Mon, 30 Mar 2020 08:45:27 -0400 Subject: [winswitch] profile.d not load In-Reply-To: References: Message-ID: Hi Alex, Thanks for the suggestions. I have tried your suggestions and here is what i can see. 1- with --start-child="xterm -ls" What i see is that only the xterm get the environment variable from profile.d . All other application from the Xpra menu does does get those variables. So does not work for me. 2- with --start-desktop This work but i dont't need and want the full desktop. In our infrastructure(Ovirt) some people use full desktop over Spice protocol(virt-viewer). and the others used Xpra for seamless integration. The only way i was able to make this work is to remote execute a ssh command like this "bash -l -c xpra start :display". For what i understand this work because the xpra server is started with a login shell and child process will get all the variables from profile.d. The only weird thing is that in Centos7 i never had this kind of problem. Not sure why Ubuntu have a different behavior. Thanks & Regards. cl On Mon, Mar 30, 2020 at 4:18 AM Berg, Alexander wrote: > Hi Carl, > > I'm solving this by > --start-child="xterm -ls" > This starts an xterm with a login shell. > > You could also use a desktop-session like > xpra start-desktop ssh:user at server --start-child="startxfce4" > --exit-with-children > > Maybe there is a better workaround? > > With kind regards, > Alex > > -----Urspr?ngliche Nachricht----- > Von: shifter-users Im > Auftrag von carl langlois via shifter-users > Gesendet: Freitag, 27. M?rz 2020 14:51 > An: Xpra and Winswitch ML > Betreff: [winswitch] profile.d not load > > Hi, > > I am currently having trouble getting some global variable to be load when > start xpra. > > I am using this command to start xpra from the client > > xpra start ssh:user at server > > Xpra does start correctly on the server and i can attach to it. But some of > the variable defined in the profile.d are not present. > > This is probably something related to interactive vs non-interactive > shell... > How can i make Xpra start with full login shell? > > Thanks > Regards > cl > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From crl.langlois at gmail.com Tue Mar 31 01:50:26 2020 From: crl.langlois at gmail.com (carl langlois) Date: Mon, 30 Mar 2020 20:50:26 -0400 Subject: [winswitch] Nautilus, gedit, gnome-terminal minimize problem. Message-ID: Hi, I am having a really weird behavior with nautilus, gedit and gnome-terminal. When I have only nautilus open I am able to minimize de windows but when I have a gnome-terminal open a the same time I am not able to minimize the nautilus windows. I have the same behavior with gedit+gnome-terminal. The server is run on Ubuntu 19:10 and running latest 3.0 Xpra client en windows 10. The server is start with all default value over ssh xpra start ssh:user at server Any suggestions on what to look for. Thanks and regards. cl From antoine at nagafix.co.uk Tue Mar 31 10:18:27 2020 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 31 Mar 2020 16:18:27 +0700 Subject: [winswitch] profile.d not load In-Reply-To: References: Message-ID: <70df7c65-262a-276e-a554-5bb83931dfa7@nagafix.co.uk> On 30/03/2020 19:45, carl langlois via shifter-users wrote: > Hi Alex, > > Thanks for the suggestions. I have tried your suggestions and here is what > i can see. > > 1- with --start-child="xterm -ls" > What i see is that only the xterm get the environment variable from > profile.d . All other application from the Xpra menu does does get those > variables. So does not work for me. > 2- with --start-desktop > This work but i dont't need and want the full desktop. In our > infrastructure(Ovirt) some people use full desktop over Spice > protocol(virt-viewer). and the others used Xpra for seamless integration. > > The only way i was able to make this work is to remote execute a ssh > command like this "bash -l -c xpra start :display". For what i understand > this work because the xpra server is started with a login shell and > child process will get all the variables from profile.d. There is now a better solution to this problem: http://xpra.org/trac/ticket/2688#comment:1 This will be available in v4, which is due quite soon. Cheers, Antoine > The only weird thing is that in Centos7 i never had this kind of problem. > Not sure why Ubuntu have a different behavior. > > Thanks & Regards. > > cl > > > On Mon, Mar 30, 2020 at 4:18 AM Berg, Alexander > wrote: > >> Hi Carl, >> >> I'm solving this by >> --start-child="xterm -ls" >> This starts an xterm with a login shell. >> >> You could also use a desktop-session like >> xpra start-desktop ssh:user at server --start-child="startxfce4" >> --exit-with-children >> >> Maybe there is a better workaround? >> >> With kind regards, >> Alex >> >> -----Urspr?ngliche Nachricht----- >> Von: shifter-users Im >> Auftrag von carl langlois via shifter-users >> Gesendet: Freitag, 27. M?rz 2020 14:51 >> An: Xpra and Winswitch ML >> Betreff: [winswitch] profile.d not load >> >> Hi, >> >> I am currently having trouble getting some global variable to be load when >> start xpra. >> >> I am using this command to start xpra from the client >> >> xpra start ssh:user at server >> >> Xpra does start correctly on the server and i can attach to it. But some of >> the variable defined in the profile.d are not present. >> >> This is probably something related to interactive vs non-interactive >> shell... >> How can i make Xpra start with full login shell? >> >> Thanks >> Regards >> cl >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From crl.langlois at gmail.com Tue Mar 31 11:46:04 2020 From: crl.langlois at gmail.com (carl langlois) Date: Tue, 31 Mar 2020 06:46:04 -0400 Subject: [winswitch] profile.d not load In-Reply-To: <70df7c65-262a-276e-a554-5bb83931dfa7@nagafix.co.uk> References: <70df7c65-262a-276e-a554-5bb83931dfa7@nagafix.co.uk> Message-ID: Hi, That's the Xpra way I like it. Cl Le mar. 31 mars 2020 05 h 18, Antoine Martin via shifter-users < shifter-users at lists.devloop.org.uk> a ?crit : > On 30/03/2020 19:45, carl langlois via shifter-users wrote: > > Hi Alex, > > > > Thanks for the suggestions. I have tried your suggestions and here is > what > > i can see. > > > > 1- with --start-child="xterm -ls" > > What i see is that only the xterm get the environment variable from > > profile.d . All other application from the Xpra menu does does get those > > variables. So does not work for me. > > 2- with --start-desktop > > This work but i dont't need and want the full desktop. In our > > infrastructure(Ovirt) some people use full desktop over Spice > > protocol(virt-viewer). and the others used Xpra for seamless integration. > > > > The only way i was able to make this work is to remote execute a ssh > > command like this "bash -l -c xpra start :display". For what i understand > > this work because the xpra server is started with a login shell and > > child process will get all the variables from profile.d. > There is now a better solution to this problem: > http://xpra.org/trac/ticket/2688#comment:1 > This will be available in v4, which is due quite soon. > > Cheers, > Antoine > > > > The only weird thing is that in Centos7 i never had this kind of problem. > > Not sure why Ubuntu have a different behavior. > > > > Thanks & Regards. > > > > cl > > > > > > On Mon, Mar 30, 2020 at 4:18 AM Berg, Alexander > > > wrote: > > > >> Hi Carl, > >> > >> I'm solving this by > >> --start-child="xterm -ls" > >> This starts an xterm with a login shell. > >> > >> You could also use a desktop-session like > >> xpra start-desktop ssh:user at server --start-child="startxfce4" > >> --exit-with-children > >> > >> Maybe there is a better workaround? > >> > >> With kind regards, > >> Alex > >> > >> -----Urspr?ngliche Nachricht----- > >> Von: shifter-users Im > >> Auftrag von carl langlois via shifter-users > >> Gesendet: Freitag, 27. M?rz 2020 14:51 > >> An: Xpra and Winswitch ML > >> Betreff: [winswitch] profile.d not load > >> > >> Hi, > >> > >> I am currently having trouble getting some global variable to be load > when > >> start xpra. > >> > >> I am using this command to start xpra from the client > >> > >> xpra start ssh:user at server > >> > >> Xpra does start correctly on the server and i can attach to it. But > some of > >> the variable defined in the profile.d are not present. > >> > >> This is probably something related to interactive vs non-interactive > >> shell... > >> How can i make Xpra start with full login shell? > >> > >> Thanks > >> Regards > >> cl > >> _______________________________________________ > >> shifter-users mailing list > >> shifter-users at lists.devloop.org.uk > >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users > >> > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at devloop.org.uk Tue Mar 31 12:40:49 2020 From: antoine at devloop.org.uk (Antoine Martin) Date: Tue, 31 Mar 2020 18:40:49 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 3.0.8: nothing major Message-ID: Hi, There's a fair number of bug fixes in this release, but none of them are critical. The clipboard and keyboard (AltGr) handling are the most important ones in there, the rest is all fairly minor stuff. (platforms, warnings, etc) Release notes: * handling of dpi command line switch (correctly this time?) * bug report window not getting focus on MacOS * spurious ssh key warnings with newer versions of paramiko * AltGr mode with non-X11 clients, layout-group changes * rare unexpected client exit on MS Windows * MS Windows clipboard: update failures convert CRLF line endings * Clipboard: fix selection not shown as active in menus (MS Windows and MacOS) fix spurious warnings when sharing a session fix clipboard reset with python2 builds selection translation for outbound data support client applications that don't use TARGETS (ie: Motif) reject invalid targets * 'xpra upgrade' wrongly updating non-xpra displays * logging error in client geometry debugging output * pulseaudio start command with Ubuntu Xenial * spurious de-iconifications * handling of server control commands with python3 clients * UDP backport bug sending control packets * vfb getting killed on upgrade failure * proxy server cleanup: force forwarders to terminate * session info errors during client exit * printer cleanup errors with invalid UTF8 printer names * transient-for popup window workaround * missing libyuv csc module on MacOS * unicode errors saving xpra runner shell script with python3 * try to prevent conflicts with Fedora's packages * better detection of Wayland environments * use python3 (if installed) by default on Ubuntu Xenial * don't use Xdummy on arm, too slow * don't show 'Download' button that we can't honour * show all pressed keys according to X11 server in 'xpra info' * try harder not to use video for tiny areas Cheers, Antoine