From antoine at nagafix.co.uk  Tue Aug  1 08:09:00 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Tue, 1 Aug 2017 14:09:00 +0700
Subject: [winswitch] Windows Client: preexec_fn not supported on Windows
 platform
In-Reply-To: <CANdeXhzNKUno1e-sPwfMPTJdgvc=CfP9YgQhHk3fd-V_Zs-rKQ@mail.gmail.com>
References: <CANdeXhwYi9zUHZ3w7++TN-+P8VBE-ekLKHbj5ffcBjWD+a1_Qw@mail.gmail.com>
 <e3b906b0-3a08-d5eb-149a-5b64ab11cb09@nagafix.co.uk>
 <CANdeXhzNKUno1e-sPwfMPTJdgvc=CfP9YgQhHk3fd-V_Zs-rKQ@mail.gmail.com>
Message-ID: <98535f40-e452-d6a9-dc45-079e2896f4c4@nagafix.co.uk>

On 01/08/17 01:14, Thomas Mainka via shifter-users wrote:
> The latest version I tried is Windows 64bit v2.1 revision 16505
> "built on Win7ProDev-PC by Win7ProDev 2017-07-25 22:26."
> That was the .exe Installer directly from the homepage.
> 
> I did not use a command line, as the error message pops up in the Xpra
> launcher GUI after selecting SSH as connection method.
Thanks for the details, the bug has been fixed:
http://xpra.org/trac/changeset/16575

This only affected MS Windows clients connecting in SSH mode using the
launcher (which means there might be another harmless bug still waiting
to be fixed)

There was a Mac OS SSH fix just a few days ago, so I will make a 2.1.1
release, hopefully by the end of the week.

In the meantime, you can downgrade to 2.0.x or use the fresh 2.1.1 RC
builds found here:
http://xpra.org/beta/windows/
or for Mac OS:
http://xpra.org/beta/MacOS/

Cheers
Antoine


> 
> 
> Regards,
> Thomas
> 
> 
> On Sun, Jul 30, 2017 at 12:09 PM, Antoine Martin via shifter-users
> <shifter-users at lists.devloop.org.uk> wrote:
>> On 30/07/17 17:06, Thomas Mainka via shifter-users wrote:
>>> Hi,
>>>
>>> I've tried to update my Xpra windows client on Win 10 from 2.0.2, but
>>> somehow any newer version since that gives the error message
>>> "preexec_fn not supported on Windows platforms".
>>>
>>> Could this be a problem with a second Python runtime installed somewhere else?
>> It could be, or it could also just be a bug.
>>
>> Please specify the exact download that you've used (exe? msi? 32-bit?
>> 64-bit?) and the exact command line that you've used.
>> Please note that the 2.0.x branch is out of date, try using 2.1
>>
>> Cheers
>> Antoine
>>
>>>
>>>
>>> Regards,
>>> Thomas
>> _______________________________________________
>> shifter-users mailing list
>> shifter-users at lists.devloop.org.uk
>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> 



From esarmien at g.harvard.edu  Wed Aug  2 16:17:55 2017
From: esarmien at g.harvard.edu (Evan Sarmiento)
Date: Wed, 02 Aug 2017 11:17:55 -0400
Subject: [winswitch] x264-xpra disappeared?
Message-ID: <b1c2ca25-c69e-4d46-bac0-d040f469cb71@g.harvard.edu>

Hi Antoine,
Trying to install XPRA on CentOS 6 and I noticed it requires x264-xpra 
package, but, it is no longer in the repository:
https://www.xpra.org/dists/CentOS/6/x86_64/ 
[https://www.xpra.org/dists/CentOS/6/x86_64/]
Is this right?
---> Package xpra.x86_64 0:1.0.6-1.r15846.el6_9 will be installed

--> Processing Dependency: x264-xpra for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libswscale.so.4(LIBSWSCALE_4)(64bit) for 
package: xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavutil.so.55(LIBAVUTIL_55)(64bit) for 
package: xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavformat.so.57(LIBAVFORMAT_57)(64bit) for 
package: xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavcodec.so.57(LIBAVCODEC_57)(64bit) for 
package: xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: ffmpeg-xpra for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libx264.so.148()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libswscale.so.4()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavutil.so.55()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavformat.so.57()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libavcodec.so.57()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Running transaction check

---> Package ffmpeg-xpra.x86_64 0:3.3.3-1.el6_9 will be installed

--> Processing Dependency: libx264.so.148()(64bit) for package: 
ffmpeg-xpra-3.3.3-1.el6_9.x86_64

---> Package xpra.x86_64 0:1.0.6-1.r15846.el6_9 will be installed

--> Processing Dependency: x264-xpra for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Processing Dependency: libx264.so.148()(64bit) for package: 
xpra-1.0.6-1.r15846.el6_9.x86_64

--> Finished Dependency Resolution

Error: Package: ffmpeg-xpra-3.3.3-1.el6_9.x86_64 (xpra)

Requires: libx264.so.148()(64bit)

Error: Package: xpra-1.0.6-1.r15846.el6_9.x86_64 (xpra)

Requires: x264-xpra

Error: Package: xpra-1.0.6-1.r15846.el6_9.x86_64 (xpra)

Requires: libx264.so.148()(64bit)



Best,

Evan Sarmiento Systems Project Manager Harvard-MIT Data Center

From dougdoole at gmail.com  Wed Aug  2 16:48:57 2017
From: dougdoole at gmail.com (Douglas Doole)
Date: Wed, 02 Aug 2017 15:48:57 +0000
Subject: [winswitch] Xpra not starting
Message-ID: <CADE5jYLkLm5CQVEiXcEO9TsBPn=H65NfPvZ4G2=XPzC72Xj33w@mail.gmail.com>

I'm running xpra 1.0.6 on Ubuntu 14.04. It had been working fine, but
recently I've been unable to start the server.

I use "xpra start :10 --start-new-commands=yes" to start the server. My
:10.log file ends with:

Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(EE)
Fatal server error:
(EE) xf86OpenConsole: Cannot open virtual console 8 (Permission denied)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/home/ddoole/.xpra/Xorg-10.log" for
additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
display :10 failed:
could not connect to X server on display ':10' after 3 seconds
2017-08-02 08:30:13,194 killing xvfb with pid 168742
2017-08-02 08:30:13,194 failed to kill xvfb process with pid 168742:
2017-08-02 08:30:13,194  [Errno 3] No such process

The Xorg-10.log file ends with:

[1031398.386] (--) using VT number 8

[1031398.386] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[1031398.386] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[1031398.386] (EE)
Fatal server error:
[1031398.386] (EE) xf86OpenConsole: Cannot open virtual console 8
(Permission denied)
[1031398.386] (EE)
[1031398.386] (EE)

I haven't made any system changes recently other than regular software
updates. Since this is a work machine, it is possible that a sys admin made
a configuration change without me being aware of it though.

I tried Googling the error message and found a couple suggestions for
updating Xwrapper.config and changing permissions on /dev/tty8, but those
didn't help.

Any ideas?


From antoine at nagafix.co.uk  Thu Aug  3 08:02:34 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 3 Aug 2017 14:02:34 +0700
Subject: [winswitch] Xpra not starting
In-Reply-To: <CADE5jYLkLm5CQVEiXcEO9TsBPn=H65NfPvZ4G2=XPzC72Xj33w@mail.gmail.com>
References: <CADE5jYLkLm5CQVEiXcEO9TsBPn=H65NfPvZ4G2=XPzC72Xj33w@mail.gmail.com>
Message-ID: <f113c56c-e06e-f772-77ed-c6350af5773a@nagafix.co.uk>

On 02/08/17 22:48, Douglas Doole via shifter-users wrote:
> I'm running xpra 1.0.6 on Ubuntu 14.04. It had been working fine, but
> recently I've been unable to start the server.
> 
> I use "xpra start :10 --start-new-commands=yes" to start the server. My
> :10.log file ends with:
(..)
> Fatal server error:
> (EE) xf86OpenConsole: Cannot open virtual console 8 (Permission denied)
(..)
> [1031398.386] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
> [1031398.386] (WW) xf86OpenConsole: setsid failed: Operation not permitted
> [1031398.386] (EE)
> Fatal server error:
> [1031398.386] (EE) xf86OpenConsole: Cannot open virtual console 8
> (Permission denied)
(..)
> I haven't made any system changes recently other than regular software
> updates. Since this is a work machine, it is possible that a sys admin made
> a configuration change without me being aware of it though.
Looks like your installation is trying to use Xdummy instead of Xvfb,
but the default xpra 1.x on Ubuntu 14.04 should be using Xvfb.
Did you modify your system to try to switch to Xdummy?

You can verify the current xvfb settings with:
xpra showconfig | grep Xvfb

I've just tested a default installation and Xvfb started without problems.

> I tried Googling the error message and found a couple suggestions for
> updating Xwrapper.config and changing permissions on /dev/tty8, but those
> didn't help.
Make sure you revert those before trying something else.

Cheers
Antoine


> 
> Any ideas?
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> 



From antoine at nagafix.co.uk  Thu Aug  3 08:04:33 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 3 Aug 2017 14:04:33 +0700
Subject: [winswitch] Xpra not starting
In-Reply-To: <f113c56c-e06e-f772-77ed-c6350af5773a@nagafix.co.uk>
References: <CADE5jYLkLm5CQVEiXcEO9TsBPn=H65NfPvZ4G2=XPzC72Xj33w@mail.gmail.com>
 <f113c56c-e06e-f772-77ed-c6350af5773a@nagafix.co.uk>
Message-ID: <9dd9daee-c1ca-5d64-678a-0d1f0fbfed6c@nagafix.co.uk>

Just a typo (lowercase required):

> You can verify the current xvfb settings with:
> xpra showconfig | grep Xvfb

xpra showconfig | grep xvfb


From antoine at nagafix.co.uk  Thu Aug  3 08:06:30 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 3 Aug 2017 14:06:30 +0700
Subject: [winswitch] x264-xpra disappeared?
In-Reply-To: <b1c2ca25-c69e-4d46-bac0-d040f469cb71@g.harvard.edu>
References: <b1c2ca25-c69e-4d46-bac0-d040f469cb71@g.harvard.edu>
Message-ID: <2aa54960-fa12-b2cd-01c3-a904d6f125c6@nagafix.co.uk>

On 02/08/17 22:17, Evan Sarmiento via shifter-users wrote:
> Hi Antoine,
> Trying to install XPRA on CentOS 6 and I noticed it requires x264-xpra
> package, but, it is no longer in the repository:
> https://www.xpra.org/dists/CentOS/6/x86_64/
> Is this right?
> ---> Package xpra.x86_64 0:1.0.6-1.r15846.el6_9 will be installed
(...)
> Error: Package: xpra-1.0.6-1.r15846.el6_9.x86_64 (xpra)
> Requires: x264-xpra
> Error: Package: xpra-1.0.6-1.r15846.el6_9.x86_64 (xpra)
> Requires: libx264.so.148()(64bit)
Sorry about that, I was meant to push new x264 packages and forgot.

(and I didn't notice because upgrades continue to work.. only CentOS 6.9
is missing the package and "CentOS/6/" is now pointing to "CentOS/6.9/")

Try now, the updated packages are there.

Cheers
Antoine


From antoine at nagafix.co.uk  Thu Aug  3 13:29:08 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 3 Aug 2017 19:29:08 +0700
Subject: [winswitch] Stuck with automatic picture encoding while trying
 to connect with HTML5
In-Reply-To: <026c7412-15ed-2755-94fc-1cb221703409@nagafix.co.uk>
References: <864540a4c8f47845a28913171211f8c5@webmail.grammatico.me>
 <026c7412-15ed-2755-94fc-1cb221703409@nagafix.co.uk>
Message-ID: <98915abc-0ba6-d142-0e3d-8a62a5f4792a@nagafix.co.uk>

>> How can I have better performance with HTML2 ?
> Please file a ticket with enough details.
Turns out that the performance is really bad if you use an external
proxy process - don't do that. That's why we moved the websocket proxy
in-process for the 1.0 release. More details here:
http://xpra.org/trac/ticket/1604#comment:4

Cheers
Antoine


From dougdoole at gmail.com  Thu Aug  3 17:20:39 2017
From: dougdoole at gmail.com (Douglas Doole)
Date: Thu, 03 Aug 2017 16:20:39 +0000
Subject: [winswitch] Xpra not starting
In-Reply-To: <9dd9daee-c1ca-5d64-678a-0d1f0fbfed6c@nagafix.co.uk>
References: <CADE5jYLkLm5CQVEiXcEO9TsBPn=H65NfPvZ4G2=XPzC72Xj33w@mail.gmail.com>
 <f113c56c-e06e-f772-77ed-c6350af5773a@nagafix.co.uk>
 <9dd9daee-c1ca-5d64-678a-0d1f0fbfed6c@nagafix.co.uk>
Message-ID: <CADE5jY+o+Asd61kpx1fVXVF54kY4Dvwqg3qkJ0QHeCRZXMHmiw@mail.gmail.com>

Sorry, forgot to include that detail. I am.using Xdummy and have been using
it for ages. My xpra.conf contains:

xvfb=Xorg -noreset -nolisten tcp +extension GLX \
    -config ${HOME}/xorg.conf \
    +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg-10.log

None of this changed between the last time I successfully used xpra and
when it started failing.

That said, falling back to Xvfb does let Xpra start. I'd still like to
figure out why my Xdummy setup stopped working though.

On Thu, Aug 3, 2017 at 12:04 AM Antoine Martin via shifter-users <
shifter-users at lists.devloop.org.uk> wrote:

> Just a typo (lowercase required):
>
> > You can verify the current xvfb settings with:
> > xpra showconfig | grep Xvfb
>
> xpra showconfig | grep xvfb
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>


From antoine at nagafix.co.uk  Tue Aug  8 08:10:45 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Tue, 8 Aug 2017 14:10:45 +0700
Subject: [winswitch] [ANNOUNCE] Xpra 2.1.1 : important SSH fixes
Message-ID: <6f916fab-7932-1680-dfb3-1a25c95d4f91@nagafix.co.uk>

Hi,

There aren't too many fixes in this update: the two fixes for SSH
connection regressions are important, but everything else is fairly minor.


Release notes:
* fix SSH connections from the launcher on MS Windows
* fix remote session start via SSH
* fix full quality refresh control command
* fix HTML5 client clipboard access
* fix client SHELL when starting via system wide proxy (on some distros)
* fix clipboard sanitization workaround (clipboard stopped)
* fix regression introduced by previous DPI fix
* fix Mac OS vertical wheel value accumulator
* fix misleading log error message (confusing uid with gid)
* fix invalid packet error message logging
* fix MS Windows client exit on signal (control-C)
* fix invalid mmap path warnings on MS Windows servers
* fix OpenGL context creation failure message
* fix duplicate button click events (causing triple clicks with MS
Windows shadow servers)
* fix error when a shadow server is shut down without being used
* honour window ids with control channel speed and quality adjustments
* ignore dead sockets when enumerating possible X11 displays
* add missing mdns tool icon
* add missing "meta" modifier to keyboard tools

The source:
https://xpra.org/src/
Binaries/repositories:
https://winswitch.org/downloads/
Direct binary downloads:
https://xpra.org/dists/
Beta:
https://xpra.org/beta/

Cheers
Antoine


From titusiforum at gmail.com  Wed Aug  9 00:19:48 2017
From: titusiforum at gmail.com (Titusi Forum)
Date: Tue, 8 Aug 2017 16:19:48 -0700
Subject: [winswitch] XPRA Server on MS Win 7
Message-ID: <CAFFxQ40izx_E1MGrazWGPnas61Pmd5D15=ZZYFwkqFeYT6b1=A@mail.gmail.com>

Hi:

I have a quick question out of curiosity. Please pardon me, I have not
explored MS windows documentation on your site. I use XPRA on Linux and I
am very happy with its capabilities.

I would like to start xpra server on a MS win7 and then connect to it using
HTML5 client. But, just like my Linux experience, I don't want to expose
entire win7 desktop. I like to send graphics from only chosen select
applications to the xpra server display channel for remote viewer on
browser. Is this something possible?


From antoine at nagafix.co.uk  Wed Aug  9 07:45:35 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Wed, 9 Aug 2017 13:45:35 +0700
Subject: [winswitch] XPRA Server on MS Win 7
In-Reply-To: <CAFFxQ40izx_E1MGrazWGPnas61Pmd5D15=ZZYFwkqFeYT6b1=A@mail.gmail.com>
References: <CAFFxQ40izx_E1MGrazWGPnas61Pmd5D15=ZZYFwkqFeYT6b1=A@mail.gmail.com>
Message-ID: <2f7c949b-f21e-3ac0-952b-c4368111127a@nagafix.co.uk>

On 09/08/17 06:19, Titusi Forum via shifter-users wrote:
> Hi:
> 
> I have a quick question out of curiosity. Please pardon me, I have not
> explored MS windows documentation on your site. I use XPRA on Linux and I
> am very happy with its capabilities.
> 
> I would like to start xpra server on a MS win7 and then connect to it using
> HTML5 client. But, just like my Linux experience, I don't want to expose
> entire win7 desktop. I like to send graphics from only chosen select
> applications to the xpra server display channel for remote viewer on
> browser. Is this something possible?
No, sorry.
Adding this functionality would require a significant amount of work.

Cheers
Antoine


From titusiforum at gmail.com  Wed Aug  9 23:05:55 2017
From: titusiforum at gmail.com (Titusi Forum)
Date: Wed, 9 Aug 2017 15:05:55 -0700
Subject: [winswitch] XPRA Server on MS Win 7
In-Reply-To: <1A49EC8E-2F60-4E09-829D-F2A068A737C1@gmail.com>
References: <CAFFxQ40izx_E1MGrazWGPnas61Pmd5D15=ZZYFwkqFeYT6b1=A@mail.gmail.com>
 <1A49EC8E-2F60-4E09-829D-F2A068A737C1@gmail.com>
Message-ID: <CAFFxQ42azYUtXaF6EVii-FhyG4nBS-4wLYN6GOqPonsDis+pMA@mail.gmail.com>

I did not know that, thanks for the information.
Do you know if this RemoteApp or (MS RDP in general) also comes with an
HTML5 client?
If I could show selected app windows on a client browser window then that
would solve my problems.

On Tue, Aug 8, 2017 at 8:26 PM, Abdulaziz Aldarrab <adarrab at gmail.com>
wrote:

> Hi,
>
> Checkout Remoteapp available with Windows Server 2012/2016 does exactly
> that.
>
> I don't think it is available with Xpra, though it would be nice,
>
> Best regards,
>
> On Aug 9, 2017, at 2:19 AM, Titusi Forum via shifter-users <
> shifter-users at lists.devloop.org.uk> wrote:
>
> Hi:
>
> I have a quick question out of curiosity. Please pardon me, I have not
> explored MS windows documentation on your site. I use XPRA on Linux and I
> am very happy with its capabilities.
>
> I would like to start xpra server on a MS win7 and then connect to it using
> HTML5 client. But, just like my Linux experience, I don't want to expose
> entire win7 desktop. I like to send graphics from only chosen select
> applications to the xpra server display channel for remote viewer on
> browser. Is this something possible?
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>
>


From adarrab at gmail.com  Thu Aug 10 15:37:36 2017
From: adarrab at gmail.com (Abdulaziz Aldarrab)
Date: Thu, 10 Aug 2017 17:37:36 +0300
Subject: [winswitch] XPRA Server on MS Win 7
In-Reply-To: <CAFFxQ42azYUtXaF6EVii-FhyG4nBS-4wLYN6GOqPonsDis+pMA@mail.gmail.com>
References: <CAFFxQ40izx_E1MGrazWGPnas61Pmd5D15=ZZYFwkqFeYT6b1=A@mail.gmail.com>
 <1A49EC8E-2F60-4E09-829D-F2A068A737C1@gmail.com>
 <CAFFxQ42azYUtXaF6EVii-FhyG4nBS-4wLYN6GOqPonsDis+pMA@mail.gmail.com>
Message-ID: <8F2FE15A-401B-4121-9A1D-4D2DED02F599@gmail.com>

It does have a web portal, and applications do launch individually (not full desktop) seamlessly as other native desktop applications (almost) without any special software, at least on windows clients.

One advantage of MS Server 2016 is the support for 3D acceleration (DirectX & OpenGL v4.4), i.e. does the rendering on the server, if that is something you need.

Best regards,

> On Aug 10, 2017, at 1:05 AM, Titusi Forum <titusiforum at gmail.com> wrote:
> 
> I did not know that, thanks for the information.
> Do you know if this RemoteApp or (MS RDP in general) also comes with an HTML5 client?
> If I could show selected app windows on a client browser window then that would solve my problems.
> 
>> On Tue, Aug 8, 2017 at 8:26 PM, Abdulaziz Aldarrab <adarrab at gmail.com> wrote:
>> Hi,
>> 
>> Checkout Remoteapp available with Windows Server 2012/2016 does exactly that. 
>> 
>> I don't think it is available with Xpra, though it would be nice, 
>> 
>> Best regards,
>> 
>>> On Aug 9, 2017, at 2:19 AM, Titusi Forum via shifter-users <shifter-users at lists.devloop.org.uk> wrote:
>>> 
>>> Hi:
>>> 
>>> I have a quick question out of curiosity. Please pardon me, I have not
>>> explored MS windows documentation on your site. I use XPRA on Linux and I
>>> am very happy with its capabilities.
>>> 
>>> I would like to start xpra server on a MS win7 and then connect to it using
>>> HTML5 client. But, just like my Linux experience, I don't want to expose
>>> entire win7 desktop. I like to send graphics from only chosen select
>>> applications to the xpra server display channel for remote viewer on
>>> browser. Is this something possible?
>>> _______________________________________________
>>> shifter-users mailing list
>>> shifter-users at lists.devloop.org.uk
>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> 


From anto.trande at gmail.com  Sun Aug 13 13:41:20 2017
From: anto.trande at gmail.com (Antonio Trande)
Date: Sun, 13 Aug 2017 14:41:20 +0200
Subject: [winswitch] Xpra 2.1.1 : xpra.socket
In-Reply-To: <041c6bee-3a59-4d8b-4260-a12623e46362@gmail.com>
References: <041c6bee-3a59-4d8b-4260-a12623e46362@gmail.com>
Message-ID: <f878d5bc-bf7d-8f68-d9d6-d575767c88b3@fedoraproject.org>

Hi all.

Since this release (2.1.1) provides a 'xpra.socket' file, i need some
info about before including it in a new RPM release for Fedora:

* Does the service require post-installation configuration in order to
be useful (for example, does it need manual edits to a configuration file)?

* Does the service listen on a network socket for connections
originating on a separate physical or virtual machine?

* Is the service non-persistent (i.e. run once at startup and exit)?


Hope to get help from someone.

-- 
--
Antonio Trande
sagitter AT fedoraproject dot org


From antoine at nagafix.co.uk  Sun Aug 13 13:48:15 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Sun, 13 Aug 2017 19:48:15 +0700
Subject: [winswitch] Xpra 2.1.1 : xpra.socket
In-Reply-To: <f878d5bc-bf7d-8f68-d9d6-d575767c88b3@fedoraproject.org>
References: <041c6bee-3a59-4d8b-4260-a12623e46362@gmail.com>
 <f878d5bc-bf7d-8f68-d9d6-d575767c88b3@fedoraproject.org>
Message-ID: <94b7bf77-bbbe-e17b-6d3b-c0f34d00f6c5@nagafix.co.uk>

On 13/08/17 19:41, Antonio Trande via shifter-users wrote:
> Hi all.
> 
> Since this release (2.1.1) provides a 'xpra.socket' file, i need some
> info about before including it in a new RPM release for Fedora:
To be exact, the systemd socket activation is new in 2.1.0
The proxy server it starts has been available for a while, but was not
usually started by default.
> * Does the service require post-installation configuration in order to
> be useful (for example, does it need manual edits to a configuration file)?
No.

> * Does the service listen on a network socket for connections
> originating on a separate physical or virtual machine?
It listens on the xpra port (14500) on all interfaces, as per the socket
file.

> * Is the service non-persistent (i.e. run once at startup and exit)?
No.

More information here:
https://xpra.org/trac/ticket/1521
https://xpra.org/trac/ticket/1105
https://xpra.org/trac/ticket/1521

Cheers
Antoine

> 
> 
> Hope to get help from someone.
> 



From antoine at nagafix.co.uk  Mon Aug 14 18:48:55 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Tue, 15 Aug 2017 00:48:55 +0700
Subject: [winswitch] [ANNOUNCE] Xpra 1.0.7 LTS : many minor fixes
Message-ID: <5a060343-0669-8ee9-ccd7-cde4544f9ff0@nagafix.co.uk>

Hi,

This update contains a large number of fixes but they are mostly
cosmetic issues or build and platform quirks, the only true bug fixes
affected DPI, XSettings and a rare clipboard crash.

There is no urgency to update if your were not affected by those issues.

Warning: the 1.x branch is only really meant to be used by those who are
unable to upgrade because they are stuck on an outdated operating system
like CentOS 6.x, Mac OS < 10.10, Windows XP, etc.
The 1.x binaries for Mac OS and MS Windows are known to contain a number
of security vulnerabilities. This is only going to get worse with time.
Use at your own risk.
The situation is marginally better when running on Linux distributions
as long as the vendors continue to provide security updates.


Release notes:
* fix authentication with unencrypted xor mode
* fix potential symlink attacks when running the proxy server as root
* fix packet handling errors with AES encryption enabled
* fix RPM build errors due to incompatible build and install switches
* fix Debian Stretch x264 package dependency
* fix Debian deprecated package name for Python Pillow
* fix window aspect ratio handling in client
* fix compatibility with Fedora 26: disable broken systemd-run
* fix RPM build dependency: the test phase needs rencode
* fix build prefix stripping with newer Debian versions
* fix proxy server errors with scroll encoded packets
* fix errors during launcher cleanup
* fix Mac OS corrupted build patch
* fix crashes accessing some xsettings
* fix systray logging on posix OS
* fix Cython runtime warnings in keyboard definition parsing
* fix compilation with Cython 0.26b0
* fix sample configuration file line endings on MS Windows
* fix Mac OS build failures with python3 installed
* fix Mac OS errors with clipboard disabled on server
* fix XSettings error preventing server from starting
* fix server startup error in the window icon capture code
* fix window repaint after change in border paint status
* fix icon error on resume from suspended state
* fix error message for missing shadow X11 display
* fix DPI miscalculation in case of platform API error
* fix handling of shadow server screen resizing
* fix window geometry feature flag wrongly removed
* fix missing window filter for raise packets
* fix command error when stopping a local server via TCP or SSL
* fix crashes due to a GTK clipboard bug
* fix NVENC complete system lockups
* fix invalid packet error message logging
* fix OpenGL context creation failure message
* fix duplicate button click events
 (causing triple clicks with MS Windows servers)
* fix X11 timetstamp overflow
* fix DoS with invalid connections
* full quality refresh control command
* honour window ids with the control channel to adjust speed and quality
* ignore dead sockets when enumerating possible X11 displays
* add runtime warning: the GTK3 client should not be used
* add missing man page entries
* add missing "meta" modifier to keyboard tools
* use a smaller initial display size with desktop mode


Source:
https://xpra.org/trac/wiki/Source
Downloads:
https://xpra.org/trac/wiki/Download

Cheers
Antoine


From mailinglist__shifter-users at compeuphoria.com  Mon Aug 14 21:32:55 2017
From: mailinglist__shifter-users at compeuphoria.com (mailinglist__shifter-users at compeuphoria.com)
Date: Mon, 14 Aug 2017 16:32:55 -0400
Subject: [winswitch] Various mountpoints (both /dev/sd* and NFSv4) readonly
 after xpra session created
Message-ID: <001c01d3153c$829ec2a0$87dc47e0$@compeuphoria.com>

Hello there;

First-off, let me preface this by admitting I cannot tell if this a
strictly-xpra issue, strictly-Fedora 26 issue, silliness in Systemd,
operator-stupidity on my part, or some combination of the above.  I've gone
back through 2-1/2 years of the mailing-list archives, and googled every
pertinent term I could think of, but I haven't had much luck.

Environment Details
-------------------
  Host OS:      Fedora 26 (x86_84)
  xpra Server:	2.2-0.20170811r16688.fc26 (from WinSwitch beta repo)
  Client OS:	Windows 10 (yuck!)
  xpra client:	Xpra 2.2 (64-bit) revision 16657 (2017-08-08)

I'm using the repo-supplied 'xpra.service' unit file to start xpra on the
host.  This works, properly bringing up an xpra proxy, and I can
successfully create a session through it from my client (with an existing
non-root account).

However, I have found that many of my filesystem mounts are (both /dev/sd*
and NFSv4 mounts) are read-only.  This happens both in terminals (tested in
xterm and gnome-terminal), and with other apps (e.g. Calibre, brasero,
devedeng, etc.).  If I directly ssh into the host from my client PC with
that same non-root account then the filesystems appear properly as
read-write.  Same is true if I ssh from xterm (inside the xpra session) to
user at localhost - mounts are now read-write.

Also within that xterm, I can do things like "sudo mount -o remount,rw
<mountpoint>" successfully.  However this won't work for non-terminal apps
without writing wrappers, etc.  It also doesn't address whatever my
root-cause is.

I suspect this has something to do with how the user-session environment is
being set up, but I'm enough of a Systemd noob that I have no idea how to
troubleshoot the problem.



For what it's worth, here's 'ps -ef' output showing both the xpra proxy
process started by the Systemd unit file, and the processes that are spawned
when I start up the actual xpra session:

root      8105     1  0 16:05 ?        00:00:00 /usr/bin/python2
/usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=allow
--ssl-cert=/etc/letsencrypt/live/example.com/cert.pem --bind=none
--auth=allow --socket-dirs=/run/xpra --socket-permissions=666
--log-dir=/var/log --pidfile=/run/xpra.pid --debug=
testuser  8156     1  2 16:05 ?        00:00:15 /usr/bin/python2
/usr/bin/xpra start --csc-modules=all --attach=no --start-via-proxy=no
--packet-encoders=rencode, bencode, yaml --video-decoders=all
--encodings=all --compressors=lz4, lzo, zlib --video-encoders=all
--env=XPRA_PROXY_START_UUID=f42ee27577b24606a04bf6dc3feeb251 --daemon=yes
--systemd-run=no --uid=1000 --gid=1000 --displayfd=17
testuser  8157  8156  0 16:05 ?        00:00:05
/usr/libexec/Xorg-for-Xpra-S8152 -noreset -novtswitch -nolisten tcp
+extension GLX +extension RANDR +extension RENDER -auth /root/.Xauthority
-logfile /run/user/1000/xpra/Xorg.S8152.log -configdir
/run/user/1000/xpra/xorg.conf.d/8156 -config /etc/xpra/xorg.conf -depth 24
-displayfd 8
testuser  8255  8105  1 16:06 ?        00:00:10 /usr/bin/python2
/usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=allow
--ssl-cert=/etc/letsencrypt/live/example.com/cert.pem --bind=none
--auth=allow --socket-dirs=/run/xpra --socket-permissions=666
--log-dir=/var/log --pidfile=/run/xpra.pid --debug=
testuser  8317  8156  3 16:06 ?        00:00:22 /usr/bin/python2
/usr/bin/xpra _sound_record - - pulsesrc device=Xpra-Speaker.monitor
opus+ogg  1.0
testuser  9872  8441  0 16:17 pts/4    00:00:00 grep --color=auto xpra

I cannot find anything seemingly related to this in the xpra logs, but I can
provide if requested.

Any suggestions, or tips on how to better troubleshoot this, would be
very-greatly appreciated.

Thank you



From antoine at nagafix.co.uk  Tue Aug 15 09:33:50 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Tue, 15 Aug 2017 15:33:50 +0700
Subject: [winswitch] Various mountpoints (both /dev/sd* and NFSv4)
 readonly after xpra session created
In-Reply-To: <001c01d3153c$829ec2a0$87dc47e0$@compeuphoria.com>
References: <001c01d3153c$829ec2a0$87dc47e0$@compeuphoria.com>
Message-ID: <e337bf74-7db7-df91-ba69-570bf5c34196@nagafix.co.uk>

Hi,

The problem you describe is very likely to be caused by the
"ProtectSystem" systemd exec option, see:
https://www.freedesktop.org/software/systemd/man/systemd.exec.html

We set it to "strict", which may be too strict.. Your options are:
* change from "strict" to "full", or even "off".
* add paths to "ReadWritePaths" as needed
* start xpra with "start-via-proxy=no" (you will lose session management
integration)

Which option is best for you depends on your requirements in terms of
ease of maintenance, security, etc..
We could change the default from "strict" to "full" if this causes too
many problems.

Cheers
Antoine

PS: the file you are looking for is:
/usr/lib/systemd/system/xpra.service
But you should not edit that file directly, instead use:
systemctl edit xpra.service
Or create the file by hand in:
/etc/systemd/system/xpra.service


On 15/08/17 03:32, WireRydr via shifter-users wrote:
> Hello there;
> 
> First-off, let me preface this by admitting I cannot tell if this a
> strictly-xpra issue, strictly-Fedora 26 issue, silliness in Systemd,
> operator-stupidity on my part, or some combination of the above.  I've gone
> back through 2-1/2 years of the mailing-list archives, and googled every
> pertinent term I could think of, but I haven't had much luck.
> 
> Environment Details
> -------------------
>   Host OS:      Fedora 26 (x86_84)
>   xpra Server:	2.2-0.20170811r16688.fc26 (from WinSwitch beta repo)
>   Client OS:	Windows 10 (yuck!)
>   xpra client:	Xpra 2.2 (64-bit) revision 16657 (2017-08-08)
> 
> I'm using the repo-supplied 'xpra.service' unit file to start xpra on the
> host.  This works, properly bringing up an xpra proxy, and I can
> successfully create a session through it from my client (with an existing
> non-root account).
> 
> However, I have found that many of my filesystem mounts are (both /dev/sd*
> and NFSv4 mounts) are read-only.  This happens both in terminals (tested in
> xterm and gnome-terminal), and with other apps (e.g. Calibre, brasero,
> devedeng, etc.).  If I directly ssh into the host from my client PC with
> that same non-root account then the filesystems appear properly as
> read-write.  Same is true if I ssh from xterm (inside the xpra session) to
> user at localhost - mounts are now read-write.
> 
> Also within that xterm, I can do things like "sudo mount -o remount,rw
> <mountpoint>" successfully.  However this won't work for non-terminal apps
> without writing wrappers, etc.  It also doesn't address whatever my
> root-cause is.
> 
> I suspect this has something to do with how the user-session environment is
> being set up, but I'm enough of a Systemd noob that I have no idea how to
> troubleshoot the problem.
> 
> 
> 
> For what it's worth, here's 'ps -ef' output showing both the xpra proxy
> process started by the Systemd unit file, and the processes that are spawned
> when I start up the actual xpra session:
> 
> root      8105     1  0 16:05 ?        00:00:00 /usr/bin/python2
> /usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=allow
> --ssl-cert=/etc/letsencrypt/live/example.com/cert.pem --bind=none
> --auth=allow --socket-dirs=/run/xpra --socket-permissions=666
> --log-dir=/var/log --pidfile=/run/xpra.pid --debug=
> testuser  8156     1  2 16:05 ?        00:00:15 /usr/bin/python2
> /usr/bin/xpra start --csc-modules=all --attach=no --start-via-proxy=no
> --packet-encoders=rencode, bencode, yaml --video-decoders=all
> --encodings=all --compressors=lz4, lzo, zlib --video-encoders=all
> --env=XPRA_PROXY_START_UUID=f42ee27577b24606a04bf6dc3feeb251 --daemon=yes
> --systemd-run=no --uid=1000 --gid=1000 --displayfd=17
> testuser  8157  8156  0 16:05 ?        00:00:05
> /usr/libexec/Xorg-for-Xpra-S8152 -noreset -novtswitch -nolisten tcp
> +extension GLX +extension RANDR +extension RENDER -auth /root/.Xauthority
> -logfile /run/user/1000/xpra/Xorg.S8152.log -configdir
> /run/user/1000/xpra/xorg.conf.d/8156 -config /etc/xpra/xorg.conf -depth 24
> -displayfd 8
> testuser  8255  8105  1 16:06 ?        00:00:10 /usr/bin/python2
> /usr/bin/xpra proxy :14500 --daemon=no --tcp-auth=allow
> --ssl-cert=/etc/letsencrypt/live/example.com/cert.pem --bind=none
> --auth=allow --socket-dirs=/run/xpra --socket-permissions=666
> --log-dir=/var/log --pidfile=/run/xpra.pid --debug=
> testuser  8317  8156  3 16:06 ?        00:00:22 /usr/bin/python2
> /usr/bin/xpra _sound_record - - pulsesrc device=Xpra-Speaker.monitor
> opus+ogg  1.0
> testuser  9872  8441  0 16:17 pts/4    00:00:00 grep --color=auto xpra
> 
> I cannot find anything seemingly related to this in the xpra logs, but I can
> provide if requested.
> 
> Any suggestions, or tips on how to better troubleshoot this, would be
> very-greatly appreciated.
> 
> Thank you
> 
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> 



From daniel.deus at icen.ufpa.br  Tue Aug 15 13:46:15 2017
From: daniel.deus at icen.ufpa.br (daniel.deus at icen.ufpa.br)
Date: Tue, 15 Aug 2017 13:46:15 +0100 (BST)
Subject: [winswitch] How to split up .h264 encoded to feed up broadway and
 aurora?
Message-ID: <2c7f6fd4013985aa26bde65f48d5950a@icen.ufpa.br>

Hi, 

I was only looking for you html5 client that merges broadway.js to
decode NAL unit and aurora.js to decode the audio received. 

So, I'd like to build a browser client which merge this components that
is feeded by a MSWindows server mine. But I have a bunch of questions: 

First, in my MS server I capture and encode a application, by the result
a I get a .h264 encoded. What I konw is that .h264 is different from a
h.264 NAL and that broadwayjs only decode .h264 NAL. 

 So, how to split up this .h264 in NAL unit in order that a I'd have
video and audio separeted to feed broadway and aurora each one? 

Thanks, 

Daniel F.

From yattamax at gmail.com  Sat Aug 19 21:04:11 2017
From: yattamax at gmail.com (Massimiliano Dal Cero)
Date: Sat, 19 Aug 2017 22:04:11 +0200
Subject: [winswitch] I need to video record session
Message-ID: <CAKb1gc78Vw1ZKqTquh21krx6u9jCQjxSbhwo0VDt21e+c0oVcw@mail.gmail.com>

Hi :)
I'm new here, so I can repeat something that you've read in the past
? about XPRA?
(but I do not find anything about this).

I need to execute an application and access it via a browser session (so I
use the --html5 option).

Ok, this work without a problem, but I have another need: record session on
a video file.

I tried with ffmpeg but I can only see the mouse, but the window of my app
is an black box :(

So i tried with "shadow + xvfb" options and the video now is ok, but with
this option I lose some funtionality in html5 (ie: stretch area to full
browser tab).
So, the question is:
Exist a solution for recording video without using shadow + xvfb and use
native mode?

thanks and best regards :)


?Max?




-- 
Ridentem dicere verum: quid vetat?


>_<


From antoine at nagafix.co.uk  Sun Aug 20 05:16:15 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Sun, 20 Aug 2017 11:16:15 +0700
Subject: [winswitch] I need to video record session
In-Reply-To: <CAKb1gc78Vw1ZKqTquh21krx6u9jCQjxSbhwo0VDt21e+c0oVcw@mail.gmail.com>
References: <CAKb1gc78Vw1ZKqTquh21krx6u9jCQjxSbhwo0VDt21e+c0oVcw@mail.gmail.com>
Message-ID: <2d31f8f9-c598-3a4e-3798-cd2ee3b2165a@nagafix.co.uk>

On 20/08/17 03:04, Massimiliano Dal Cero via shifter-users wrote:
> Hi :)
> I'm new here, so I can repeat something that you've read in the past
> ? about XPRA?
> (but I do not find anything about this).
> 
> I need to execute an application and access it via a browser session (so I
> use the --html5 option).
> 
> Ok, this work without a problem, but I have another need: record session on
> a video file.
> 
> I tried with ffmpeg but I can only see the mouse, but the window of my app
> is an black box :(
Xpra is a compositing window manager that happens to composite the
windows on the client (ie: HTML5 client), so the windows are never
actually painted on the server's vfb.

> So i tried with "shadow + xvfb" options and the video now is ok, but with
> this option I lose some funtionality in html5 (ie: stretch area to full
> browser tab).
> So, the question is:
> Exist a solution for recording video without using shadow + xvfb and use
> native mode?
Yes, use "--sync-xvfb=DELAY", see:
https://www.xpra.org/trac/ticket/988

Cheers
Antoine


> 
> thanks and best regards :)
> 
> 
> ?Max?
> 
> 
> 
> 



From yattamax at gmail.com  Sun Aug 20 07:42:39 2017
From: yattamax at gmail.com (Massimiliano Dal Cero)
Date: Sun, 20 Aug 2017 08:42:39 +0200
Subject: [winswitch] I need to video record session
In-Reply-To: <2d31f8f9-c598-3a4e-3798-cd2ee3b2165a@nagafix.co.uk>
References: <CAKb1gc78Vw1ZKqTquh21krx6u9jCQjxSbhwo0VDt21e+c0oVcw@mail.gmail.com>
 <2d31f8f9-c598-3a4e-3798-cd2ee3b2165a@nagafix.co.uk>
Message-ID: <CAKb1gc78WgUWr3K_559awxG5+6hKagiZOJVAGuwd+0AVpcFDoA@mail.gmail.com>

Thank you Martin :)
you response has solved my problem.

Sorry if my question can be sound trivial.


Massimiliano


= Mail sent via Smartphone =


On Aug 20, 2017 06:16, "Antoine Martin via shifter-users" <
shifter-users at lists.devloop.org.uk> wrote:

> On 20/08/17 03:04, Massimiliano Dal Cero via shifter-users wrote:
> > Hi :)
> > I'm new here, so I can repeat something that you've read in the past
> > ? about XPRA?
> > (but I do not find anything about this).
> >
> > I need to execute an application and access it via a browser session (so
> I
> > use the --html5 option).
> >
> > Ok, this work without a problem, but I have another need: record session
> on
> > a video file.
> >
> > I tried with ffmpeg but I can only see the mouse, but the window of my
> app
> > is an black box :(
> Xpra is a compositing window manager that happens to composite the
> windows on the client (ie: HTML5 client), so the windows are never
> actually painted on the server's vfb.
>
> > So i tried with "shadow + xvfb" options and the video now is ok, but with
> > this option I lose some funtionality in html5 (ie: stretch area to full
> > browser tab).
> > So, the question is:
> > Exist a solution for recording video without using shadow + xvfb and use
> > native mode?
> Yes, use "--sync-xvfb=DELAY", see:
> https://www.xpra.org/trac/ticket/988
>
> Cheers
> Antoine
>
>
> >
> > thanks and best regards :)
> >
> >
> > ?Max?
> >
> >
> >
> >
>
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users


From massimiliano.dalcero at gmail.com  Tue Aug 22 17:33:25 2017
From: massimiliano.dalcero at gmail.com (Dr. Massimiliano Dal Cero)
Date: Tue, 22 Aug 2017 18:33:25 +0200
Subject: [winswitch] XPRA: keyboard problem on Linux + Chromium Browser and
 derivates
Message-ID: <CAKb1gc5DSBVEX_08W7nP1jb6vUq--nqNryLUD3D=9M4wG815KQ@mail.gmail.com>

Hi to all,
I have a problem with XPRA (via html) and chrome browser (on Ubuntu 17.04)
and keyboard events.

When using another program like firefox or xterm, I do not have any
problems, but when using chromium (or an app made with "electron" also
chromium based) the keyboard does not work.

In debug mode I can see the input of my keyboard typing, but in the browser
nothing is happening (note: all ok with mouse event).


The problem goes out if I use XPRA in "shadow" mode and run xvfb separately
(but I need to use XPRA without xvfb :()


Someone knows why it happens this :(

Thanks and best regards
Massimiliano





-- 

Dott. Massimiliano Dal Cero
Consulente e sviluppatore informatico
Via Albornoz 19/F - Bologna
Mobile +39 3388207123 - Skype:  massimiliano.dalcero
http://www.yattaweb.it/


From vfclists at gmail.com  Thu Aug 24 07:23:25 2017
From: vfclists at gmail.com (vfclists .)
Date: Thu, 24 Aug 2017 07:23:25 +0100
Subject: [winswitch] Which command option sets the compression method to be
 used with an rgb encoding?
Message-ID: <CAE3mkNC+c3TJc67Dr6P8rgSo76MRZjB=xKeb0hqD2FsMqNCKqg@mail.gmail.com>

According to the docs rgb encoding can be compressed with lzo, lz4 or zlib.

Which command option sets the compression method to be used with an rgb
encoding?

-- 
Frank Church

=======================
http://devblog.brahmancreations.com


From antoine at nagafix.co.uk  Thu Aug 24 14:08:05 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 24 Aug 2017 20:08:05 +0700
Subject: [winswitch] Which command option sets the compression method to
 be used with an rgb encoding?
In-Reply-To: <CAE3mkNC+c3TJc67Dr6P8rgSo76MRZjB=xKeb0hqD2FsMqNCKqg@mail.gmail.com>
References: <CAE3mkNC+c3TJc67Dr6P8rgSo76MRZjB=xKeb0hqD2FsMqNCKqg@mail.gmail.com>
Message-ID: <45b2104c-a855-00ed-963d-ab9abf2f0eed@nagafix.co.uk>

On 24/08/17 13:23, vfclists . via shifter-users wrote:
> According to the docs rgb encoding can be compressed with lzo, lz4 or zlib.
> 
> Which command option sets the compression method to be used with an rgb
> encoding?
There isn't one. Xpra will use the best one available, which is lz4 if
present.
It doesn't compress very well, but it is very very fast.

If you want any more compression than that, use a proper picture
compression format (jpeg or png), but in most cases you are better off
letting xpra choose automatically for you. (and potentially adjusting
speed and quality settings to suit your needs)

Cheers
Antoine


From antoine at nagafix.co.uk  Thu Aug 24 14:27:14 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Thu, 24 Aug 2017 20:27:14 +0700
Subject: [winswitch] XPRA: keyboard problem on Linux + Chromium Browser
 and derivates
In-Reply-To: <CAKb1gc5DSBVEX_08W7nP1jb6vUq--nqNryLUD3D=9M4wG815KQ@mail.gmail.com>
References: <CAKb1gc5DSBVEX_08W7nP1jb6vUq--nqNryLUD3D=9M4wG815KQ@mail.gmail.com>
Message-ID: <f1a63675-4250-4f97-fb2b-8bd637f0320b@nagafix.co.uk>

On 22/08/17 23:33, Dr. Massimiliano Dal Cero via shifter-users wrote:
> Hi to all,
> I have a problem with XPRA (via html) and chrome browser (on Ubuntu 17.04)
> and keyboard events.
> 
> When using another program like firefox or xterm, I do not have any
> problems, but when using chromium (or an app made with "electron" also
> chromium based) the keyboard does not work.
This sound like an xpra focus bug.
Does this only occur with the HTML5 client?

> In debug mode I can see the input of my keyboard typing, but in the browser
> nothing is happening (note: all ok with mouse event).
Then the events are being sent, but may not be received correctly by the
application

> The problem goes out if I use XPRA in "shadow" mode and run xvfb separately
> (but I need to use XPRA without xvfb :()
The "shadow" mode uses the same mechanism for injecting mouse and
keyboard events (XTest in versions before 2.2), so the only difference
would be the focus events.

> Someone knows why it happens this :(
Sounds like you may want to file a ticket with enough details for us to
reproduce the problem with a minimal example.
(and include "--debug focus")

Cheers
Antoine

> 
> Thanks and best regards
> Massimiliano
> 
> 
> 
> 
> 



From philip at tidepool.ca  Thu Aug 24 17:18:21 2017
From: philip at tidepool.ca (Philip Loewen)
Date: Thu, 24 Aug 2017 09:18:21 -0700
Subject: [winswitch] XPRA - installation on Orange PI Plus 2E
Message-ID: <7d1ea067-4ba9-9b4c-7173-80982fa2fa99@tidepool.ca>

Hello,

I have succeeded in getting XPRA to work on an ARM-based single-board 
computer. In the hope that this might interest someone else, I recorded 
the commands I used in the form of a shell-script that I successfully 
ran as 'root'. These commands make xpra available to all users on the 
system. The script is provided here below my signature.

This note provides a snapshot of my experience, after removing the sad 
parts -- hours of trial-and-error, etc. Please set (low) expectations 
accordingly.

The board is an Orange PI Plus 2E. The monitor is my HDTV with 720i 
format. Network connection comes through wired ethernet.

My first step was to install a suitable Ubuntu-based desktop OS on the 
Orange PI. This came from https://www.armbian.com; the download was named
   Armbian_5.30_Orangepiplus2e_Ubuntu_xenial_default_3.4.113.7z
Getting Armbian started on the board required some tuning of the file 
system, my location, the video parameters, keyboard, etc., and 
rebooting. All the usual stuff associated with installing a new OS.

I went on to create a sudo-capable user account for myself, named 
'philip'. This shows up in the last command in the script.

On a freshly-rebooted OrangePI, I said "sudo su -" to get root, then ran 
the script shown below. About 2 hours later, I had a working XPRA setup 
on the little device. (Of these 2 hours, about 80 minutes were spent 
doing other constructive tasks while ffmpeg compiled.)

Please note that the script requires frequent user interaction: one has 
to consent to each of the "apt-get install" commands. This allows one to 
see what's working, assess the speed of the system, and notice if 
something breaks.

I use XPRA daily, but only to forward silent X-windows. This now works 
for me, and I'm satisfied. I have not pursued the many other exciting 
things XPRA can do -- e.g., sound, video, and print-forwarding. But I 
can report that X-window forwarding works nicely as both client and 
server. Many thanks to Antoine for this nice cross-platform(!) system.

Sincerely,
Philip

#####################################################################
# 2017-08-18: Commands to install xpra on armbian (Orange PI Plus 2E)

# Run all these as root. Or, prefix each one with "sudo -H ".

# Clean up potentially conflicting packages
apt-get purge xpra cython

# Get a bunch of system tools. Check that the file vpx.pc actually arrived.
apt-get install libx11-dev libxtst-dev libxcomposite-dev libxdamage-dev
apt-get install libxkbfile-dev libx264-dev libvpx-dev libswscale-dev
apt-get install libavformat-dev libavcodec-dev
apt-get install xvfb xauth x11-xkb-utils
apt-get install zlib1g zlib1g-dev liblzo2-2 liblzo2-dev
echo +++++ /usr/lib/pkgconfig/vpx.pc +++++
cat /usr/lib/pkgconfig/vpx.pc
echo +++++++++++++++++++++++++++++++++++++

# Get a bunch more system tools based on Python.
apt-get install python-all-dev python-gobject-dev python-gtk2-dev cython
apt-get install python-netifaces dbus-x11 python-dbus python-rencode
apt-get install hicolor-icon-theme python-avahi python-numpy
apt-get install gstreamer1.0-x gstreamer1.0-tools
apt-get install python-pil python-lzo python-setuptools python-wheel

# Some system-supplied Python tools are just too old.
# Get new ones directly from the world of Python.
apt-get install python-pip
pip install --upgrade pip
pip install lz4

# System version of ffmpeg is too old. Compile new one from source.
# Note the suggested LDPATH and PIC flag in configuration step.
# (Found this online at some stage - forgot source - sorry.)
# Compilation took about 80 minutes.
git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
cd ffmpeg
LDPATH=/usr/lib/arm-linux-gnueabihf ./configure --enable-pic
time make
make install

# Note that version number 2.1 below might increase in future.
# Used LDPATH from above just in case it helps.
wget https://www.xpra.org/src/xpra-2.1.tar.xz
unxz xpra-2.1.tar.xz
tar xvf xpra-2.1.tar
cd xpra-2.1
LDPATH=/usr/lib/arm-linux-gnueabihf ./setup.py install

# xpra wants to have a group, and xpra users should belong.
addgroup xpra
adduser philip xpra

# DONE!



From juan at elsotanillo.net  Fri Aug 25 07:45:54 2017
From: juan at elsotanillo.net (Juan Sierra Pons)
Date: Fri, 25 Aug 2017 08:45:54 +0200
Subject: [winswitch] XPRA - installation on Orange PI Plus 2E
In-Reply-To: <7d1ea067-4ba9-9b4c-7173-80982fa2fa99@tidepool.ca>
References: <7d1ea067-4ba9-9b4c-7173-80982fa2fa99@tidepool.ca>
Message-ID: <CABS=y9suNqgdzAz4A7ijJQQ3-MTAu85VVwqsrsACzUA=bU2poQ@mail.gmail.com>

Hi,

You should create a public repository (on github, bitbucket, etc) and
upload your code. This way it will be easier to track changes, fork
your code to adapt to others PI flavors ,etc

Thanks for sharing

Best regards
--------------------------------------------------------------------------------------
Juan Sierra Pons                                 juan at elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--------------------------------------------------------------------------------------


2017-08-24 18:18 GMT+02:00 Philip Loewen via shifter-users
<shifter-users at lists.devloop.org.uk>:
> Hello,
>
> I have succeeded in getting XPRA to work on an ARM-based single-board
> computer. In the hope that this might interest someone else, I recorded the
> commands I used in the form of a shell-script that I successfully ran as
> 'root'. These commands make xpra available to all users on the system. The
> script is provided here below my signature.
>
> This note provides a snapshot of my experience, after removing the sad parts
> -- hours of trial-and-error, etc. Please set (low) expectations accordingly.
>
> The board is an Orange PI Plus 2E. The monitor is my HDTV with 720i format.
> Network connection comes through wired ethernet.
>
> My first step was to install a suitable Ubuntu-based desktop OS on the
> Orange PI. This came from https://www.armbian.com; the download was named
>   Armbian_5.30_Orangepiplus2e_Ubuntu_xenial_default_3.4.113.7z
> Getting Armbian started on the board required some tuning of the file
> system, my location, the video parameters, keyboard, etc., and rebooting.
> All the usual stuff associated with installing a new OS.
>
> I went on to create a sudo-capable user account for myself, named 'philip'.
> This shows up in the last command in the script.
>
> On a freshly-rebooted OrangePI, I said "sudo su -" to get root, then ran the
> script shown below. About 2 hours later, I had a working XPRA setup on the
> little device. (Of these 2 hours, about 80 minutes were spent doing other
> constructive tasks while ffmpeg compiled.)
>
> Please note that the script requires frequent user interaction: one has to
> consent to each of the "apt-get install" commands. This allows one to see
> what's working, assess the speed of the system, and notice if something
> breaks.
>
> I use XPRA daily, but only to forward silent X-windows. This now works for
> me, and I'm satisfied. I have not pursued the many other exciting things
> XPRA can do -- e.g., sound, video, and print-forwarding. But I can report
> that X-window forwarding works nicely as both client and server. Many thanks
> to Antoine for this nice cross-platform(!) system.
>
> Sincerely,
> Philip
>
> #####################################################################
> # 2017-08-18: Commands to install xpra on armbian (Orange PI Plus 2E)
>
> # Run all these as root. Or, prefix each one with "sudo -H ".
>
> # Clean up potentially conflicting packages
> apt-get purge xpra cython
>
> # Get a bunch of system tools. Check that the file vpx.pc actually arrived.
> apt-get install libx11-dev libxtst-dev libxcomposite-dev libxdamage-dev
> apt-get install libxkbfile-dev libx264-dev libvpx-dev libswscale-dev
> apt-get install libavformat-dev libavcodec-dev
> apt-get install xvfb xauth x11-xkb-utils
> apt-get install zlib1g zlib1g-dev liblzo2-2 liblzo2-dev
> echo +++++ /usr/lib/pkgconfig/vpx.pc +++++
> cat /usr/lib/pkgconfig/vpx.pc
> echo +++++++++++++++++++++++++++++++++++++
>
> # Get a bunch more system tools based on Python.
> apt-get install python-all-dev python-gobject-dev python-gtk2-dev cython
> apt-get install python-netifaces dbus-x11 python-dbus python-rencode
> apt-get install hicolor-icon-theme python-avahi python-numpy
> apt-get install gstreamer1.0-x gstreamer1.0-tools
> apt-get install python-pil python-lzo python-setuptools python-wheel
>
> # Some system-supplied Python tools are just too old.
> # Get new ones directly from the world of Python.
> apt-get install python-pip
> pip install --upgrade pip
> pip install lz4
>
> # System version of ffmpeg is too old. Compile new one from source.
> # Note the suggested LDPATH and PIC flag in configuration step.
> # (Found this online at some stage - forgot source - sorry.)
> # Compilation took about 80 minutes.
> git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
> cd ffmpeg
> LDPATH=/usr/lib/arm-linux-gnueabihf ./configure --enable-pic
> time make
> make install
>
> # Note that version number 2.1 below might increase in future.
> # Used LDPATH from above just in case it helps.
> wget https://www.xpra.org/src/xpra-2.1.tar.xz
> unxz xpra-2.1.tar.xz
> tar xvf xpra-2.1.tar
> cd xpra-2.1
> LDPATH=/usr/lib/arm-linux-gnueabihf ./setup.py install
>
> # xpra wants to have a group, and xpra users should belong.
> addgroup xpra
> adduser philip xpra
>
> # DONE!
>
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users


From antoine at nagafix.co.uk  Fri Aug 25 16:58:43 2017
From: antoine at nagafix.co.uk (Antoine Martin)
Date: Fri, 25 Aug 2017 22:58:43 +0700
Subject: [winswitch] XPRA - installation on Orange PI Plus 2E
In-Reply-To: <7d1ea067-4ba9-9b4c-7173-80982fa2fa99@tidepool.ca>
References: <7d1ea067-4ba9-9b4c-7173-80982fa2fa99@tidepool.ca>
Message-ID: <350a350e-c374-f3ea-2a80-588d8af766af@nagafix.co.uk>

On 24/08/17 23:18, Philip Loewen via shifter-users wrote:
> Hello,
> 
> I have succeeded in getting XPRA to work on an ARM-based single-board
> computer. In the hope that this might interest someone else, I recorded
> the commands I used in the form of a shell-script that I successfully
> ran as 'root'. These commands make xpra available to all users on the
> system. The script is provided here below my signature.
> 
> This note provides a snapshot of my experience, after removing the sad
> parts -- hours of trial-and-error, etc. Please set (low) expectations
> accordingly.
> 
> The board is an Orange PI Plus 2E. The monitor is my HDTV with 720i
> format. Network connection comes through wired ethernet.
> 
> My first step was to install a suitable Ubuntu-based desktop OS on the
> Orange PI. This came from https://www.armbian.com; the download was named
>   Armbian_5.30_Orangepiplus2e_Ubuntu_xenial_default_3.4.113.7z
> Getting Armbian started on the board required some tuning of the file
> system, my location, the video parameters, keyboard, etc., and
> rebooting. All the usual stuff associated with installing a new OS.
> 
> I went on to create a sudo-capable user account for myself, named
> 'philip'. This shows up in the last command in the script.
> 
> On a freshly-rebooted OrangePI, I said "sudo su -" to get root, then ran
> the script shown below. About 2 hours later, I had a working XPRA setup
> on the little device. (Of these 2 hours, about 80 minutes were spent
> doing other constructive tasks while ffmpeg compiled.)
Thanks. I have added a wiki page based on these instructions:
http://xpra.org/trac/wiki/Building/OrangePI

With the following changes:
* less hand-holding: users should be able to figure out that using
apt-get requires root - if not, they probably won't go very far anyway
* try to distinguish build time dependencies and runtime extra features
* I don't think python-wheel is needed, is it?
* ffmpeg compilation from a released version rather than straight from
git (more reliable) and using only the components actually needed by xpra.
* removed the unix group creation, this should be optional

> Please note that the script requires frequent user interaction: one has
> to consent to each of the "apt-get install" commands. This allows one to
> see what's working, assess the speed of the system, and notice if
> something breaks.
> 
> I use XPRA daily, but only to forward silent X-windows. This now works
> for me, and I'm satisfied. I have not pursued the many other exciting
> things XPRA can do -- e.g., sound, video, and print-forwarding. But I
> can report that X-window forwarding works nicely as both client and
> server. Many thanks to Antoine for this nice cross-platform(!) system.
Since I don't have the hardware to test - I haven't added any
instructions for audio/video/printing, but this is a wiki so anyone can
add the information once verified:
* printer forwarding: only requires cups + python-cups
* audio: some gstreamer plugins, and pulseaudio for the server
* video: should be enabled already: that's what ffmpeg is for. But I'm
not sure those ARM boards are powerful enough to handle video in software...

Cheers
Antoine

> 
> Sincerely,
> Philip
> 
> #####################################################################
> # 2017-08-18: Commands to install xpra on armbian (Orange PI Plus 2E)
> 
> # Run all these as root. Or, prefix each one with "sudo -H ".
> 
> # Clean up potentially conflicting packages
> apt-get purge xpra cython
> 
> # Get a bunch of system tools. Check that the file vpx.pc actually arrived.
> apt-get install libx11-dev libxtst-dev libxcomposite-dev libxdamage-dev
> apt-get install libxkbfile-dev libx264-dev libvpx-dev libswscale-dev
> apt-get install libavformat-dev libavcodec-dev
> apt-get install xvfb xauth x11-xkb-utils
> apt-get install zlib1g zlib1g-dev liblzo2-2 liblzo2-dev
> echo +++++ /usr/lib/pkgconfig/vpx.pc +++++
> cat /usr/lib/pkgconfig/vpx.pc
> echo +++++++++++++++++++++++++++++++++++++
> 
> # Get a bunch more system tools based on Python.
> apt-get install python-all-dev python-gobject-dev python-gtk2-dev cython
> apt-get install python-netifaces dbus-x11 python-dbus python-rencode
> apt-get install hicolor-icon-theme python-avahi python-numpy
> apt-get install gstreamer1.0-x gstreamer1.0-tools
> apt-get install python-pil python-lzo python-setuptools python-wheel
> 
> # Some system-supplied Python tools are just too old.
> # Get new ones directly from the world of Python.
> apt-get install python-pip
> pip install --upgrade pip
> pip install lz4
> 
> # System version of ffmpeg is too old. Compile new one from source.
> # Note the suggested LDPATH and PIC flag in configuration step.
> # (Found this online at some stage - forgot source - sorry.)
> # Compilation took about 80 minutes.
> git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
> cd ffmpeg
> LDPATH=/usr/lib/arm-linux-gnueabihf ./configure --enable-pic
> time make
> make install
> 
> # Note that version number 2.1 below might increase in future.
> # Used LDPATH from above just in case it helps.
> wget https://www.xpra.org/src/xpra-2.1.tar.xz
> unxz xpra-2.1.tar.xz
> tar xvf xpra-2.1.tar
> cd xpra-2.1
> LDPATH=/usr/lib/arm-linux-gnueabihf ./setup.py install
> 
> # xpra wants to have a group, and xpra users should belong.
> addgroup xpra
> adduser philip xpra
> 
> # DONE!
> 
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users