From antoine at nagafix.co.uk Sat Mar 1 03:32:20 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 01 Mar 2014 10:32:20 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.11.4 (important bug fixes) Message-ID: <531154C4.9000708@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This update fixes 6 bugs, some important fixes and some compatibility issues for older clients: * fix NVENC GPU memory leak * fix video compatibility with ancient clients * fix vpx decoding in ffmpeg decoders * fix transparent system tray image with RGB encoding * fix client crashes with system tray forwarding * fix webp codec loader error handler Now, for the usual links: 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMRVMAACgkQGK2zHPGK1rsUTwCdFxmbwtKKjq6cdweU4OepeDhw YqcAnjvzSKD6S57OjLxlGtVBm5p6bafP =9EKl -----END PGP SIGNATURE----- From adresatt at gmail.com Tue Mar 4 15:01:10 2014 From: adresatt at gmail.com (Sergey Malkin) Date: Tue, 04 Mar 2014 19:01:10 +0400 Subject: [winswitch] How to connect to linux server with non-standart SSH port using Xpra on Windows? Message-ID: <5315EAB6.7000005@gmail.com> Hello! I have a linux server with Xpra started without binding to TCP port. SSH on server is listening on port 41. When connecting from another linux machine I can specify the SSH port in user's ssh config and connect to server typing just "xpra attach ssh:servername:$DISPLAY". But I can't use the same method on Windows because there is no SSH config. How to specify the SSH port for Xpra to use in that case? From antoine at nagafix.co.uk Wed Mar 5 03:04:47 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 05 Mar 2014 10:04:47 +0700 Subject: [winswitch] How to connect to linux server with non-standart SSH port using Xpra on Windows? In-Reply-To: <5315EAB6.7000005@gmail.com> References: <5315EAB6.7000005@gmail.com> Message-ID: <5316944F.1080205@nagafix.co.uk> On 04/03/14 22:01, Sergey Malkin wrote: > Hello! > I have a linux server with Xpra started without binding to TCP port. > SSH on server is listening on port 41. When connecting from another > linux machine I can specify the SSH port in user's ssh config and > connect to server typing just "xpra attach ssh:servername:$DISPLAY". > But I can't use the same method on Windows because there is no SSH > config. How to specify the SSH port for Xpra to use in that case? The easiest way to use a non-standard SSH port is to use the latest version 0.12 beta, which you can find here: http://xpra.org/beta/ It includes the ability to specify the SSH server port as part of the connection string, ie: ssh/username:password at servername:port/DISPLAY (username and password are optional, though the username is often necessary as MS Windows usernames tend to be different from the Unix server usernames) Alternatively, you should be able to specify the port using the --ssh switch, which uses plink.exe on win32 (untested): xpra_cmd.exe attach --ssh="C:\Program Files\Xpra\Plink.exe -P 41" ... Cheers Antoine From wens at unav.es Wed Mar 5 16:58:43 2014 From: wens at unav.es (=?ISO-8859-1?Q?Wenceslao_Gonz=E1lez-Vi=F1as?=) Date: Wed, 05 Mar 2014 17:58:43 +0100 Subject: [winswitch] xpra through a ssh tunnel Message-ID: <531757C3.10909@unav.es> Dear all, First my apologies if this question is answered elsewhere .. I'd like to do an xpra ssh:remotehostatwork:port but the problem is that remotehostatwork is not available directly. The only possibility is go through the serveratwork. Usually I do ssh serveratwork and there ssh remotehostatwork .... but I need to to the same with xpra ... (xpra is not installed at serveratwork, BTW) Thank you all for your help. Best, W From antoine at nagafix.co.uk Thu Mar 6 04:32:40 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 06 Mar 2014 11:32:40 +0700 Subject: [winswitch] xpra through a ssh tunnel In-Reply-To: <531757C3.10909@unav.es> References: <531757C3.10909@unav.es> Message-ID: <5317FA68.90700@nagafix.co.uk> On 05/03/14 23:58, Wenceslao Gonz?lez-Vi?as wrote: > Dear all, > > First my apologies if this question is answered elsewhere .. I'd like > to do an xpra ssh:remotehostatwork:port but the problem is that > remotehostatwork is not available directly. The only possibility is go > through the serveratwork. Usually I do ssh serveratwork and there ssh > remotehostatwork .... but I need to to the same with xpra ... (xpra is > not installed at serveratwork, BTW) You can find a discussion on this subject and a patch, which was never applied, in this ticket: https://www.xpra.org/trac/ticket/17 Summary: you should be able to do what you want with (untested): xpra --ssh 'ProxyCommand ...' ssh:.. Cheers Antoine > > Thank you all for your help. > > Best, > > W From fshahriar at gmail.com Thu Mar 6 05:02:31 2014 From: fshahriar at gmail.com (Fazlul Shahriar) Date: Thu, 6 Mar 2014 00:02:31 -0500 Subject: [winswitch] xpra through a ssh tunnel In-Reply-To: <531757C3.10909@unav.es> References: <531757C3.10909@unav.es> Message-ID: This is what I do: 1) Set up a persistent ssh tunnel: autossh -M 20000 -f -N -L 2222:remotehostatwork:22 serveratwork 2) Add this in .ssh/config Host remotehosttunnel HostName localhost Port 2222 3) Assuming you have xpra running on display :100 on remotehostatwork, you can run: xpra attach ssh:remotehosttunnel:100 This has been working well for me. Hope that helps, fhs On Wed, Mar 5, 2014 at 11:58 AM, Wenceslao Gonz?lez-Vi?as wrote: > Dear all, > > First my apologies if this question is answered elsewhere .. I'd like to > do an xpra ssh:remotehostatwork:port but the problem is that > remotehostatwork is not available directly. The only possibility is go > through the serveratwork. Usually I do ssh serveratwork and there ssh > remotehostatwork .... but I need to to the same with xpra ... (xpra is not > installed at serveratwork, BTW) > > Thank you all for your help. > > Best, > > W > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From wens at unav.es Thu Mar 6 14:56:08 2014 From: wens at unav.es (=?ISO-8859-1?Q?Wenceslao_Gonz=E1lez-Vi=F1as?=) Date: Thu, 06 Mar 2014 15:56:08 +0100 Subject: [winswitch] xpra through a ssh tunnel In-Reply-To: <5317FA68.90700@nagafix.co.uk> References: <531757C3.10909@unav.es> <5317FA68.90700@nagafix.co.uk> Message-ID: <53188C88.9060708@unav.es> How can I apply a patch easily? my box is debian jessie. Do I have to apply on the server side or on the client or on both? Thanks and best regards, Wenceslao On 03/06/2014 05:32 AM, Antoine Martin wrote: > On 05/03/14 23:58, Wenceslao Gonz?lez-Vi?as wrote: >> Dear all, >> >> First my apologies if this question is answered elsewhere .. I'd like >> to do an xpra ssh:remotehostatwork:port but the problem is that >> remotehostatwork is not available directly. The only possibility is go >> through the serveratwork. Usually I do ssh serveratwork and there ssh >> remotehostatwork .... but I need to to the same with xpra ... (xpra is >> not installed at serveratwork, BTW) > You can find a discussion on this subject and a patch, which was never > applied, in this ticket: > https://www.xpra.org/trac/ticket/17 > > Summary: you should be able to do what you want with (untested): > xpra --ssh 'ProxyCommand ...' ssh:.. > > Cheers > Antoine > >> Thank you all for your help. >> >> Best, >> >> W > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From wens at unav.es Thu Mar 6 14:58:45 2014 From: wens at unav.es (=?ISO-8859-1?Q?Wenceslao_Gonz=E1lez-Vi=F1as?=) Date: Thu, 06 Mar 2014 15:58:45 +0100 Subject: [winswitch] xpra through a ssh tunnel In-Reply-To: References: <531757C3.10909@unav.es> Message-ID: <53188D25.8000807@unav.es> I did and almost it works! except that I get a message of 'segmentation fault' like in ticket #244 ... Is there any problem in the jessie version 0.11.2-dfsg2-1 ? I have this version on both sides .. Thanks again!! Wenceslao On 03/06/2014 06:02 AM, Fazlul Shahriar wrote: > This is what I do: > > 1) Set up a persistent ssh tunnel: > autossh -M 20000 -f -N -L 2222:remotehostatwork:22 serveratwork > > 2) Add this in .ssh/config > > Host remotehosttunnel > HostName localhost > Port 2222 > > 3) Assuming you have xpra running on display :100 on remotehostatwork, > you can run: > > xpra attach ssh:remotehosttunnel:100 > > This has been working well for me. > > Hope that helps, > fhs > > > > > On Wed, Mar 5, 2014 at 11:58 AM, Wenceslao Gonz?lez-Vi?as > > wrote: > > Dear all, > > First my apologies if this question is answered elsewhere .. I'd > like to do an xpra ssh:remotehostatwork:port but the problem is > that remotehostatwork is not available directly. The only > possibility is go through the serveratwork. Usually I do ssh > serveratwork and there ssh remotehostatwork .... but I need to to > the same with xpra ... (xpra is not installed at serveratwork, BTW) > > Thank you all for your help. > > Best, > > W > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > From wens at unav.es Thu Mar 6 19:38:29 2014 From: wens at unav.es (=?ISO-8859-1?Q?Wenceslao_Gonz=E1lez-Vi=F1as?=) Date: Thu, 06 Mar 2014 20:38:29 +0100 Subject: [winswitch] Fwd: Re: xpra through a ssh tunnel In-Reply-To: <53188D25.8000807@unav.es> References: <53188D25.8000807@unav.es> Message-ID: <5318CEB5.80605@unav.es> BTW, the beta version (from web) doesn't have this problem .... -------- Original Message -------- Subject: Re: [winswitch] xpra through a ssh tunnel Date: Thu, 06 Mar 2014 15:58:45 +0100 From: Wenceslao Gonz?lez-Vi?as Organization: University of Navarra To: Fazlul Shahriar CC: shifter-users at lists.devloop.org.uk I did and almost it works! except that I get a message of 'segmentation fault' like in ticket #244 ... Is there any problem in the jessie version 0.11.2-dfsg2-1 ? I have this version on both sides .. Thanks again!! Wenceslao On 03/06/2014 06:02 AM, Fazlul Shahriar wrote: > This is what I do: > > 1) Set up a persistent ssh tunnel: > autossh -M 20000 -f -N -L 2222:remotehostatwork:22 serveratwork > > 2) Add this in .ssh/config > > Host remotehosttunnel > HostName localhost > Port 2222 > > 3) Assuming you have xpra running on display :100 on remotehostatwork, > you can run: > > xpra attach ssh:remotehosttunnel:100 > > This has been working well for me. > > Hope that helps, > fhs > > > > > On Wed, Mar 5, 2014 at 11:58 AM, Wenceslao Gonz?lez-Vi?as > > wrote: > > Dear all, > > First my apologies if this question is answered elsewhere .. I'd > like to do an xpra ssh:remotehostatwork:port but the problem is > that remotehostatwork is not available directly. The only > possibility is go through the serveratwork. Usually I do ssh > serveratwork and there ssh remotehostatwork .... but I need to to > the same with xpra ... (xpra is not installed at serveratwork, BTW) > > Thank you all for your help. > > Best, > > W > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > -- ________________________________________ Wenceslao Gonz?lez-Vi?as e-mail: wens at unav.es http://fisica.unav.es/gmm/ FAX:+34 948.425.740 phn:+34 948.425.600 ext: 806500 / 806603 Depto. F?sica y Matem?tica Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea 1 E-31008 Pamplona, Navarra, Spain ________________________________________ From antoine at nagafix.co.uk Fri Mar 7 07:24:28 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 07 Mar 2014 14:24:28 +0700 Subject: [winswitch] Fwd: Re: xpra through a ssh tunnel In-Reply-To: <5318CEB5.80605@unav.es> References: <53188D25.8000807@unav.es> <5318CEB5.80605@unav.es> Message-ID: <5319742C.8060401@nagafix.co.uk> On 07/03/14 02:38, Wenceslao Gonz?lez-Vi?as wrote: > BTW, the beta version (from web) doesn't have this problem .... Can you be a bit more specific? Which version would that be? (exact filename and "xpra --version" string) > (snip) > > I did and almost it works! except that I get a message of > 'segmentation fault' like in ticket #244 ... Is there any problem in > the jessie version 0.11.2-dfsg2-1 ? I have this version on both sides .. Try changing the encoding to "png" or "jpeg" instead of one of the video encodings "h264" or "vp8". If that solves your problem then this is once again a libav related issue, as always. Note: 0.11.2 is out of date, but I very much doubt that 0.11.4 will have fixed this problem. Cheers Antoine From wens at unav.es Fri Mar 7 08:57:15 2014 From: wens at unav.es (=?ISO-8859-1?Q?Wenceslao_Gonz=E1lez-Vi=F1as?=) Date: Fri, 07 Mar 2014 09:57:15 +0100 Subject: [winswitch] Fwd: Re: xpra through a ssh tunnel In-Reply-To: <5319742C.8060401@nagafix.co.uk> References: <53188D25.8000807@unav.es> <5318CEB5.80605@unav.es> <5319742C.8060401@nagafix.co.uk> Message-ID: <531989EB.8000501@unav.es> More specific, it worked old 0.11.2 version (server) with new one (client). Now I have rebooted system and with same server and client (xpra v0.12.0) it doesn't work giving 'Segmentation fault' when I type 'xpra attach :20' (even locally !) without giving any other output If I use " xpra attach :20 --encoding='jpeg' " instead, also it is not working Thanks in advance for helping. Best regards, Wenceslao On 07/03/14 08:24, Antoine Martin wrote: > On 07/03/14 02:38, Wenceslao Gonz?lez-Vi?as wrote: >> BTW, the beta version (from web) doesn't have this problem .... > Can you be a bit more specific? > Which version would that be? (exact filename and "xpra --version" string) >> (snip) >> >> I did and almost it works! except that I get a message of >> 'segmentation fault' like in ticket #244 ... Is there any problem in >> the jessie version 0.11.2-dfsg2-1 ? I have this version on both sides .. > Try changing the encoding to "png" or "jpeg" instead of one of the video > encodings "h264" or "vp8". > If that solves your problem then this is once again a libav related > issue, as always. > > Note: 0.11.2 is out of date, but I very much doubt that 0.11.4 will have > fixed this problem. > > Cheers > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users -- ________________________________________ Wenceslao Gonz?lez-Vi?as e-mail: wens at unav.es http://fisica.unav.es/gmm/ FAX:+34 948.425.740 phn:+34 948.425.600 ext: 806500 / 806603 Depto. F?sica y Matem?tica Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea 1 E-31008 Pamplona, Navarra, Spain ________________________________________ From antoine at nagafix.co.uk Fri Mar 7 10:27:44 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 07 Mar 2014 17:27:44 +0700 Subject: [winswitch] Fwd: Re: xpra through a ssh tunnel In-Reply-To: <531989EB.8000501@unav.es> References: <53188D25.8000807@unav.es> <5318CEB5.80605@unav.es> <5319742C.8060401@nagafix.co.uk> <531989EB.8000501@unav.es> Message-ID: <53199F20.5040801@nagafix.co.uk> On 07/03/14 15:57, Wenceslao Gonz?lez-Vi?as wrote: > More specific, it worked old 0.11.2 version (server) with new one > (client). Now I have rebooted system and with same server and client > (xpra v0.12.0) it doesn't work giving 'Segmentation fault' when I type > 'xpra attach :20' (even locally !) without giving any other output I am still confused by this talk of "new one" and "old". > If I use " xpra attach :20 --encoding='jpeg' " instead, also it is not > working It sounds to me like the beta builds for jessie may well have a big problem. So go back to 0.11.4 stable and try again with different encodings. If you still have problems, file a bug: http://xpra.org/trac/wiki/ReportingBugs Antoine > > Thanks in advance for helping. Best regards, > > Wenceslao > > On 07/03/14 08:24, Antoine Martin wrote: >> On 07/03/14 02:38, Wenceslao Gonz?lez-Vi?as wrote: >>> BTW, the beta version (from web) doesn't have this problem .... >> Can you be a bit more specific? >> Which version would that be? (exact filename and "xpra --version" >> string) >>> (snip) >>> >>> I did and almost it works! except that I get a message of >>> 'segmentation fault' like in ticket #244 ... Is there any problem in >>> the jessie version 0.11.2-dfsg2-1 ? I have this version on both >>> sides .. >> Try changing the encoding to "png" or "jpeg" instead of one of the video >> encodings "h264" or "vp8". >> If that solves your problem then this is once again a libav related >> issue, as always. >> >> Note: 0.11.2 is out of date, but I very much doubt that 0.11.4 will have >> fixed this problem. >> >> Cheers >> Antoine >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From thejunk.b at gmail.com Sun Mar 9 17:59:37 2014 From: thejunk.b at gmail.com (Randy) Date: Sun, 09 Mar 2014 13:59:37 -0400 Subject: [winswitch] resize xpra-copy desktop Message-ID: <3869208.QArxPcHrNM@bumblebee> My desktop has a 1280x1024 display when I export it via xpra-copy it is too large for my laptop display at 1366x768 and there are no scroll bars. I have tried the vnc-copy but it fails with: VNC Failed to connect: More information may be in the log files. The connection end point was 0.0.0.0:16087 (via an ssh tunnel) Both systems are running Debian Jessie (testing) fully patched using the versions of winswitch 0.12.20+dfsg-1 and xpra 0'11.4+dfsg-1 that are in the repos. Is there anyway to simply add scroll bars to the xpra-copy window? I use kde on my machines it that matters in this case. -- If it ain't broke tweek it From antoine at nagafix.co.uk Mon Mar 10 04:14:23 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 10 Mar 2014 11:14:23 +0700 Subject: [winswitch] resize xpra-copy desktop In-Reply-To: <3869208.QArxPcHrNM@bumblebee> References: <3869208.QArxPcHrNM@bumblebee> Message-ID: <531D3C1F.70405@nagafix.co.uk> On 10/03/14 00:59, Randy wrote: > My desktop has a 1280x1024 display when I export it via xpra-copy it is > too large for my laptop display at 1366x768 and there are no scroll > bars. I have tried the vnc-copy but it fails with: > > VNC Failed to connect: > More information may be in the log files. The connection end point was > 0.0.0.0:16087 (via an ssh tunnel) This usually happens when the server end failed to setup the "x0vncserver", for whatever reason. As per the message, there may well be more information in the winswitch server log file. > Both systems are running Debian Jessie (testing) fully patched using > the versions of winswitch 0.12.20+dfsg-1 and xpra 0'11.4+dfsg-1 that > are in the repos. > > Is there anyway to simply add scroll bars to the xpra-copy window? "Simply", no. I have created a ticket for this feature: http://xpra.org/trac/ticket/530 Feel free to comment and subscribe to it. > I use kde on my machines it that matters in this case. It probably doesn't, but thanks for providing as much detail as possible. Cheers Antoine From antoine at nagafix.co.uk Tue Mar 18 05:37:03 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 18 Mar 2014 12:37:03 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.11.5 (minor bug fixes) Message-ID: <5327DB7F.9040109@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This update fixes a few minor issues, there is no urgency to update if you were not affected by them: * fix "xpra info" with bencoder * ensure we re-sanitize window size hints when they change * workaround applications with nonsensical size hints (ie: handbrake) * fix 32-bit painting with GTK pixbuf loader (when PIL is not installed or disabled) * fix system tray forwarding geometry issues * fix workspace restore * fix compilation warning * remove spurious cursor warnings This should be the last update to the v0.11.x branch as version 0.12 is just about ready to be released. Now, for the usual links: 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMn23sACgkQGK2zHPGK1ruBAwCfbFExNhpbO7WnG6YMlVw3zmjw g64An3cA2bqxnjE7GPBjR7O3AZglaJzb =6aQX -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Tue Mar 18 10:37:43 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 18 Mar 2014 17:37:43 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.11.6 (system tray regression introduced in 0.11.5) Message-ID: <532821F7.3030507@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The 0.11.5 release earlier today was meant to fix system tray forwarding on some platforms (amongst other things), and instead it broke it on most. Sorry about that. 0.11.6 fixes this. (MS Windows clients were not affected) 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMoIfYACgkQGK2zHPGK1ruMfQCcD9LLtZ8kp0hecIo/8DJSRVrc 12sAnAxt79XLThiAsfk8VfadaHc9x7Ch =hZyv -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Sun Mar 23 15:05:18 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 23 Mar 2014 22:05:18 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.12.0 (new major release) Message-ID: <532EF82E.3040806@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The 0.12.0 release is now available for download. You can find the full release notes in the latest entry of the news section of the wiki, including links to all the related tickets: http://xpra.org/trac/wiki/News Here are some of the most noteworthy improvements: * NVENC high quality encoding (YUV444) with proxy encoding support. This means that you can get both very low latency and very high quality with this hardware encoder. The proxy support means that you can use this hardware encoder even if the xpra server does not have access to the hardware: the proxy can encode streams for many servers as they pass through it. (and since v0.11.0, all through a single TCP port if needed) Also: * improved support for window grabs, fullscreen, resizing * improved automatic bandwidth allocation * faster network code * cleaner code, prettier output, and better debugging tools, etc 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMu+CoACgkQGK2zHPGK1rt3MACfRXQHKrnzWJc2rEXYQYJBLdxJ ttsAn2L6JNeV6INSNuXc1N6jUnP4Pcbz =dqkR -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Thu Mar 27 15:39:15 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 27 Mar 2014 22:39:15 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.12.1 (important bug fixes) Message-ID: <53344623.8000408@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes 32-bit X11 servers and also an unlikely decoding issue for client installations without python PIL or Pillow. There is no need to upgrade if you haven't experienced any issues. The OSX and MS Windows builds were unaffected, but I have updated them anyway. 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlM0Rh8ACgkQGK2zHPGK1rs9WQCfZocvt+L1qPfuC3QtkunEOROm H8gAnAm/o+cQkUpNVTD/JTV0qkGA7kpW =Z7Jq -----END PGP SIGNATURE----- From offonoffoffonoff at gmail.com Thu Mar 27 21:25:18 2014 From: offonoffoffonoff at gmail.com (...) Date: Thu, 27 Mar 2014 16:25:18 -0500 Subject: [winswitch] NVENC developer key? Message-ID: Hello, This open source project uses NVENC without requiring users to have their own developer key: https://obsproject.com/ What is the difference between OBS and xpra that xpra users must supply their own developer key to use NVENC? Thanks, Elliot From antoine at nagafix.co.uk Fri Mar 28 03:38:19 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 28 Mar 2014 10:38:19 +0700 Subject: [winswitch] NVENC developer key? In-Reply-To: References: Message-ID: <5334EEAB.7090000@nagafix.co.uk> On 28/03/14 04:25, ... wrote: > Hello, > > This open source project uses NVENC without requiring users to have their > own developer key: https://obsproject.com/ > > What is the difference between OBS and xpra that xpra users must supply > their own developer key to use NVENC? According to my magic divining skills (or google search second hit): https://twitter.com/OBSProject/status/431481382733627392 " Using NVENC just got easier - the latest @NVIDIAGeForce beta driver no longer requires a license key! http://www.geforce.com/drivers" I haven't confirmed that myself yet, and that project is for MS Windows only, so there may be some difference in the drivers too. I will update the wiki once this has been tested. Cheers Antoine From antoine at nagafix.co.uk Sun Mar 30 07:33:01 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 30 Mar 2014 13:33:01 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.12.2 (small bug fixes) Message-ID: <5337BA9D.30201@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release contains just 3 small bug fixes: * fix switching to RGB encoding via client tray * fix remote server start via SSH * fix workspace change detection causing slow screen updates There is no need to upgrade if you haven't experienced any issues. 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlM3upkACgkQGK2zHPGK1rsYLgCeOqu8c1P+Qjrt7jSBeNDDOvrB hD0AnRqc8nbTJrqOHOFS8A4Fg7gDYUUP =OxF6 -----END PGP SIGNATURE-----