From antoine at nagafix.co.uk Sun Feb 3 19:32:13 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 04 Feb 2013 02:32:13 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.1 Message-ID: <510EBB3D.7020305@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a number of major bugs in the 0.8.0 release. Apologies for not spotting them earlier. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine Full release notes: * fix server daemonize on some platforms * fix server SSH support on platforms with old versions of glib * fix "xpra upgrade" closing applications * fix detection of almost-lossless frames with x264 * fix starting of a duplicate pulseaudio server on upgrade * fix debian packaging: lint warnings, add missing sound dependencies * fix compatibility with older versions of pulseaudio (pactl) * fix session-info window when a tray is being forwarded * remove warning on builds with limited encoding support * disable tray forwarding by default as it causes problems with some apps * rename "Quality" to "Min Quality" in tray menu * update to Cython 0.18 for binary builds * fix rpm packaging: remove unusable modules -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEOuz0ACgkQGK2zHPGK1rsRaACdGPeRzMs8V9EliKpSx4mbZdV/ XS4An2j3EmNjZknVN7qJr3irI9PlCR11 =OsBD -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Mon Feb 11 16:51:44 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 11 Feb 2013 23:51:44 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.2 Message-ID: <511921A0.2050104@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a number of bugs and finally restores the OSX client to a usable state. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine Full release notes: * fix libav uninitialized structure crash * fix warning on installations without sound libraries * fix warning when pulseaudio utils are not installed * fix delta compression race * fix the return of some ghost windows * stop pulseaudio on exit, warn if it fails to start * re-enable system tray forwarding, fix location conflicts * osx fixes: encodings wrongly grayed out * osx features: add sound and speed menus * remove spurious "too many receivers" warnings -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEZIaAACgkQGK2zHPGK1rsugACfXcG+TCicY2RsghF2Qc4YktGc 4aUAn3HxXYQm8sapSm1FrRK450ja4oWc =g1hp -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Tue Feb 12 07:17:35 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 12 Feb 2013 14:17:35 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.3 (very minor update) Message-ID: <5119EC8F.5030900@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This very minor update only fixes two small issues so there is no urgency to update and there will not be Mac OSX or MS Windows builds since those clients are not affected: * Python2.4 and old GTK versions compatibility * Missing mouse cursors The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEZ7I8ACgkQGK2zHPGK1rup1wCeKWn9mwNJRCqBvbk2mNU/AZLc taoAnRQh37U3svgOkUXb/6dgcQG9T9AM =TnQl -----END PGP SIGNATURE----- From dougdoole at gmail.com Tue Feb 12 16:09:36 2013 From: dougdoole at gmail.com (Douglas Doole) Date: Tue, 12 Feb 2013 11:09:36 -0500 Subject: [winswitch] Failed to encode packet error using xpra-0.8.3 Message-ID: I just updated my Ubuntu systems (client and server are both running Precise) to xpra-0.8.3-1. Things were working fine prior to the update. (I was using 0.8.1 on both client and server.) I upgraded the display at the server with no problems (xpra upgrade :1). When I attempt to connect, however, I get a "Failed to encode packet" error: (I pruned this a bit so it fits in the email) xpra attach ssh:reorx:1 xpra client version 0.8.3 2013-02-12 10:58:24,326 failed to encode packet: ['hello', {'bell': True, 'named_cursors': True, 'python_version': (2, 7, 3), 'gtk_version': (2, 24, 10), 'encoding': 'x264', ... 'encoding.min-speed': 0, 'dpi': 96}] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/protocol.py", line 330, in encode main_packet, proto_version = self._encoder(packet) File "/usr/lib/python2.7/dist-packages/xpra/protocol.py", line 282, in bencode return bencode(data), 0 File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 124, in bencode encode_func[type(x)](x, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 89, in encode_list encode_func[type(i)](i, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 98, in encode_dict encode_func[type(v)](v, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 89, in encode_list encode_func[type(i)](i, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 89, in encode_list encode_func[type(i)](i, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 89, in encode_list encode_func[type(i)](i, r) File "/usr/lib/python2.7/dist-packages/xpra/bencode.py", line 89, in encode_list encode_func[type(i)](i, r) KeyError: Exception in thread format: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/dist-packages/xpra/protocol.py", line 198, in _write_format_thread_loop self._add_packet_to_queue(*self._get_packet_cb()) File "/usr/lib/python2.7/dist-packages/xpra/protocol.py", line 205, in _add_packet_to_queue packets, proto_flags = self.encode(packet) File "/usr/lib/python2.7/dist-packages/xpra/protocol.py", line 338, in encode raise e KeyError: 2013-02-12 10:58:35,119 server requested disconnect: login timeout 2013-02-12 10:58:35,140 connection closed after 1 packets received (47 bytes) and 0 packets sent (0 bytes) 2013-02-12 10:58:35,142 Connection lost Any suggestions? -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Tue Feb 12 16:20:38 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 12 Feb 2013 23:20:38 +0700 Subject: [winswitch] Failed to encode packet error using xpra-0.8.3 In-Reply-To: References: Message-ID: <511A6BD6.9060601@nagafix.co.uk> On 02/12/2013 11:09 PM, Douglas Doole wrote: > I just updated my Ubuntu systems (client and server are both running > Precise) to xpra-0.8.3-1. Things were working fine prior to the update. (I > was using 0.8.1 on both client and server.) > > I upgraded the display at the server with no problems (xpra upgrade :1). > > When I attempt to connect, however, I get a "Failed to encode packet" > error: (I pruned this a bit so it fits in the email) Ouch - sorry about that! > xpra attach ssh:reorx:1 > xpra client version 0.8.3 > 2013-02-12 10:58:24,326 failed to encode packet: ['hello', {'bell': True, > 'named_cursors': True, 'python_version': (2, 7, 3), 'gtk_version': (2, 24, > 10), 'encoding': 'x264', ... 'encoding.min-speed': 0, 'dpi': 96}] (...) > KeyError: (...) Somewhere in your initial packet is a "None" value, this shouldn't happen and the encoder is failing because of that. (snip) > > Any suggestions? > If you can run with "-d all", you should see the full packet printed, and somewhere in it is going to be the value "None". If you can tell me where that is, I can fix it asap. Cheers Antoine From antoine at nagafix.co.uk Tue Feb 12 17:25:30 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 13 Feb 2013 00:25:30 +0700 Subject: [winswitch] Failed to encode packet error using xpra-0.8.3 In-Reply-To: <511A6BD6.9060601@nagafix.co.uk> References: <511A6BD6.9060601@nagafix.co.uk> Message-ID: <511A7B0A.9090602@nagafix.co.uk> (snip) > Somewhere in your initial packet is a "None" value, this shouldn't > happen and the encoder is failing because of that. > > (snip) >> >> Any suggestions? >> > If you can run with "-d all", you should see the full packet printed, > and somewhere in it is going to be the value "None". If you can tell me > where that is, I can fix it asap. Just a wild guess from the depth of the stacktrace, the "None" value might come from the "get_screen_sizes" call, so running: xpra ... -d all | grep get_screen_sizes Might gives us a clue. From antoine at nagafix.co.uk Wed Feb 13 04:29:18 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 13 Feb 2013 11:29:18 +0700 Subject: [winswitch] Failed to encode packet error using xpra-0.8.3 In-Reply-To: References: <511A6BD6.9060601@nagafix.co.uk> <511A7B0A.9090602@nagafix.co.uk> Message-ID: <511B169E.3020202@nagafix.co.uk> Please keep this on-list. On 02/13/2013 01:18 AM, Douglas Doole wrote: > This problem only occurs in 0.8.3 - 0.8.2 runs fine. Yes, the python2.4 compatibility fix in 0.8.3 undid the workaround for platforms where the "monitor plug name" is "None"... This is fixed in: https://www.xpra.org/trac/changeset/2730 Since this is a serious bug and may well affect others, I will push out 0.8.4 shortly with this bug fix. Antoine > get_screen_sizes has "None" in it: > 2013-02-12 13:10:31,491 get_screen_sizes()=[(':0.0', 3600, 1200, 709, > 242, [(None, 0, 0, 1680, 1050, -1, -1), (None, 1680, 0, 1920, 1200, -1, > -1)], 112, 0, 3488, 1200)] > > I'm running on a dual monitor configuration, configured for > side-by-side. My laptop's built-in screen is 1680x1050 and my external > monitor is 1920x1200. I'm using nVidia's twinview to merge them into a > single display of 3600x1200. > > > On Tue, Feb 12, 2013 at 12:25 PM, Antoine Martin > wrote: > > (snip) > > Somewhere in your initial packet is a "None" value, this shouldn't > > happen and the encoder is failing because of that. > > > > (snip) > >> > >> Any suggestions? > >> > > If you can run with "-d all", you should see the full packet printed, > > and somewhere in it is going to be the value "None". If you can > tell me > > where that is, I can fix it asap. > Just a wild guess from the depth of the stacktrace, the "None" value > might come from the "get_screen_sizes" call, so running: > xpra ... -d all | grep get_screen_sizes > Might gives us a clue. > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > -- > -- Doug Doole > > aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Wed Feb 13 04:57:08 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 13 Feb 2013 11:57:08 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.4 (yet another minor update..) Message-ID: <511B1D24.3040801@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This update fixes the issue which can prevent some users from connecting using the 0.8.3 client (sorry about that). The only other change makes the colours more readable again on some dialogs. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEbHSQACgkQGK2zHPGK1rvxHQCfc/zECqj2N/vVf7HIAAM6fVzp 4ekAn1bU7lC/rmwOgLEhxm9hu1+8WbJ7 =g6Ib -----END PGP SIGNATURE----- From sattler at med.uni-frankfurt.de Wed Feb 13 09:49:46 2013 From: sattler at med.uni-frankfurt.de (Thomas Sattler) Date: Wed, 13 Feb 2013 10:49:46 +0100 Subject: [winswitch] nosound binary packages Message-ID: <511B61BA.8070700@med.uni-frankfurt.de> Hi Antoine, are there any plans to additionally ship prebuild (debian) binaries that have sound disabled and therefore do not pull in gstreamer? Something like vim-nox: "This package contains a version of vim compiled with [...] but no GUI." We switched from VNC to xpra to run stuff on a re- mote linux server. As there is no need for sound, I'd prefer not to install gstreamer at all. Thomas From antoine at nagafix.co.uk Wed Feb 13 10:21:33 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 13 Feb 2013 17:21:33 +0700 Subject: [winswitch] nosound binary packages In-Reply-To: <511B61BA.8070700@med.uni-frankfurt.de> References: <511B61BA.8070700@med.uni-frankfurt.de> Message-ID: <511B692D.1050802@nagafix.co.uk> On 02/13/2013 04:49 PM, Thomas Sattler wrote: > Hi Antoine, > > are there any plans to additionally ship prebuild > (debian) binaries that have sound disabled and > therefore do not pull in gstreamer? Gstreamer is a soft-dependency, just ask apt to skip it: apt-get --no-install-recommends update xpra > Something like vim-nox: "This package contains a > version of vim compiled with [...] but no GUI." Sorry, I really don't have time to start doing things like this. Packaging hell takes far too much of my time already. > We switched from VNC to xpra to run stuff on a re- > mote linux server. As there is no need for sound, > I'd prefer not to install gstreamer at all. See above. FWIW: Gstreamer is just a library, you don't have to use it. You can tweak your /etc/xpra/xpra.conf to disable all sound. Antoine > > Thomas > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From dougdoole at gmail.com Wed Feb 13 13:58:48 2013 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 13 Feb 2013 08:58:48 -0500 Subject: [winswitch] Failed to encode packet error using xpra-0.8.3 In-Reply-To: <511B169E.3020202@nagafix.co.uk> References: <511A6BD6.9060601@nagafix.co.uk> <511A7B0A.9090602@nagafix.co.uk> <511B169E.3020202@nagafix.co.uk> Message-ID: Thanks Antoine. 0.8.4 works for me. On Tue, Feb 12, 2013 at 11:29 PM, Antoine Martin wrote: > Please keep this on-list. > > On 02/13/2013 01:18 AM, Douglas Doole wrote: > > This problem only occurs in 0.8.3 - 0.8.2 runs fine. > Yes, the python2.4 compatibility fix in 0.8.3 undid the workaround for > platforms where the "monitor plug name" is "None"... This is fixed in: > https://www.xpra.org/trac/changeset/2730 > > Since this is a serious bug and may well affect others, I will push out > 0.8.4 shortly with this bug fix. > > Antoine > > > > get_screen_sizes has "None" in it: > > 2013-02-12 13:10:31,491 get_screen_sizes()=[(':0.0', 3600, 1200, 709, > > 242, [(None, 0, 0, 1680, 1050, -1, -1), (None, 1680, 0, 1920, 1200, -1, > > -1)], 112, 0, 3488, 1200)] > > > > I'm running on a dual monitor configuration, configured for > > side-by-side. My laptop's built-in screen is 1680x1050 and my external > > monitor is 1920x1200. I'm using nVidia's twinview to merge them into a > > single display of 3600x1200. > > > > > > On Tue, Feb 12, 2013 at 12:25 PM, Antoine Martin > > wrote: > > > > (snip) > > > Somewhere in your initial packet is a "None" value, this shouldn't > > > happen and the encoder is failing because of that. > > > > > > (snip) > > >> > > >> Any suggestions? > > >> > > > If you can run with "-d all", you should see the full packet > printed, > > > and somewhere in it is going to be the value "None". If you can > > tell me > > > where that is, I can fix it asap. > > Just a wild guess from the depth of the stacktrace, the "None" value > > might come from the "get_screen_sizes" call, so running: > > xpra ... -d all | grep get_screen_sizes > > Might gives us a clue. > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > > > > > > -- > > -- Doug Doole > > > > aibohphobia - The irrational fear of palindromes > > -- -- Doug Doole aibohphobia - The irrational fear of palindromes From dougdoole at gmail.com Wed Feb 13 15:40:08 2013 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 13 Feb 2013 10:40:08 -0500 Subject: [winswitch] xpra and multiple desktops Message-ID: xpra seems to get a little confused when used on a system with multiple desktops and xpra managed windows on more than one desktop. (I have seen this behaviour on all 0.8.* builds.) For example: On desktop 2: start xpra managed terminal (for reference, call it term2) start gvim from term2 - appears on desktop #2 Switch to desktop 3: start xpra managed terminal (term3) - appears on desktop #2 (!) move term3 to desktop #3 start gvim from term3 - appears on desktop #3 Switch to desktop 2: click on term2 to bring it to foreground start gvim from term2 - appears in desktop #3 (!) start gvim (again) from term2 - appears in desktop #2 Switch to desktop 3: move term3 (which also brings it to foreground) start gvim from term3 - appears in desktop #3 It seems that xpra isn't aware of desktop changes until something causes a change in window state. -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Wed Feb 13 15:46:42 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 13 Feb 2013 22:46:42 +0700 Subject: [winswitch] xpra and multiple desktops In-Reply-To: References: Message-ID: <511BB562.5080409@nagafix.co.uk> On 02/13/2013 10:40 PM, Douglas Doole wrote: > xpra seems to get a little confused when used on a system with multiple > desktops and xpra managed windows on more than one desktop. (I have seen > this behaviour on all 0.8.* builds.) > > For example: > On desktop 2: > start xpra managed terminal (for reference, call it term2) > start gvim from term2 - appears on desktop #2 > Switch to desktop 3: > start xpra managed terminal (term3) - appears on desktop #2 (!) I don't understand why it would do that.. Maybe I am missing a piece of the puzzle. If this is a brand new application window, the workspace should be unset. > move term3 to desktop #3 > start gvim from term3 - appears on desktop #3 > Switch to desktop 2: > click on term2 to bring it to foreground > start gvim from term2 - appears in desktop #3 (!) > start gvim (again) from term2 - appears in desktop #2 > Switch to desktop 3: > move term3 (which also brings it to foreground) > start gvim from term3 - appears in desktop #3 > > It seems that xpra isn't aware of desktop changes until something causes a > change in window state. That's correct, and I'm not sure what can be done to change that. We just aren't notified of anything by the window manager on the client. Or maybe we are just mixing the workspace mappings for all the windows. I would have to test this for myself to know for sure, can you please file a ticket so I don't forget? Antoine From dougdoole at gmail.com Wed Feb 13 16:02:19 2013 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 13 Feb 2013 11:02:19 -0500 Subject: [winswitch] xpra and multiple desktops In-Reply-To: <511BB562.5080409@nagafix.co.uk> References: <511BB562.5080409@nagafix.co.uk> Message-ID: I'll open a ticket as soon as I recall my login information :-( My feeling was that this behaviour is relatively recent, so I did some more experimenting. When I downgrade the client to 0.7.8, I no longer see this problem, and new windows always appear in the current desktop. On Wed, Feb 13, 2013 at 10:46 AM, Antoine Martin wrote: > On 02/13/2013 10:40 PM, Douglas Doole wrote: > > xpra seems to get a little confused when used on a system with multiple > > desktops and xpra managed windows on more than one desktop. (I have seen > > this behaviour on all 0.8.* builds.) > > > > For example: > > On desktop 2: > > start xpra managed terminal (for reference, call it term2) > > start gvim from term2 - appears on desktop #2 > > Switch to desktop 3: > > start xpra managed terminal (term3) - appears on desktop #2 (!) > I don't understand why it would do that.. Maybe I am missing a piece of > the puzzle. > If this is a brand new application window, the workspace should be unset. > > move term3 to desktop #3 > > start gvim from term3 - appears on desktop #3 > > Switch to desktop 2: > > click on term2 to bring it to foreground > > start gvim from term2 - appears in desktop #3 (!) > > start gvim (again) from term2 - appears in desktop #2 > > Switch to desktop 3: > > move term3 (which also brings it to foreground) > > start gvim from term3 - appears in desktop #3 > > > > It seems that xpra isn't aware of desktop changes until something causes > a > > change in window state. > That's correct, and I'm not sure what can be done to change that. We > just aren't notified of anything by the window manager on the client. > Or maybe we are just mixing the workspace mappings for all the windows. > I would have to test this for myself to know for sure, can you please > file a ticket so I don't forget? > > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > -- -- Doug Doole aibohphobia - The irrational fear of palindromes From dougdoole at gmail.com Wed Feb 13 17:14:46 2013 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 13 Feb 2013 12:14:46 -0500 Subject: [winswitch] xpra and multiple desktops In-Reply-To: References: <511BB562.5080409@nagafix.co.uk> Message-ID: Ticket #259 opened for this. On Wed, Feb 13, 2013 at 11:02 AM, Douglas Doole wrote: > I'll open a ticket as soon as I recall my login information :-( > > My feeling was that this behaviour is relatively recent, so I did some > more experimenting. When I downgrade the client to 0.7.8, I no longer see > this problem, and new windows always appear in the current desktop. > > > On Wed, Feb 13, 2013 at 10:46 AM, Antoine Martin wrote: > >> On 02/13/2013 10:40 PM, Douglas Doole wrote: >> > xpra seems to get a little confused when used on a system with multiple >> > desktops and xpra managed windows on more than one desktop. (I have seen >> > this behaviour on all 0.8.* builds.) >> > >> > For example: >> > On desktop 2: >> > start xpra managed terminal (for reference, call it term2) >> > start gvim from term2 - appears on desktop #2 >> > Switch to desktop 3: >> > start xpra managed terminal (term3) - appears on desktop #2 (!) >> I don't understand why it would do that.. Maybe I am missing a piece of >> the puzzle. >> If this is a brand new application window, the workspace should be unset. >> > move term3 to desktop #3 >> > start gvim from term3 - appears on desktop #3 >> > Switch to desktop 2: >> > click on term2 to bring it to foreground >> > start gvim from term2 - appears in desktop #3 (!) >> > start gvim (again) from term2 - appears in desktop #2 >> > Switch to desktop 3: >> > move term3 (which also brings it to foreground) >> > start gvim from term3 - appears in desktop #3 >> > >> > It seems that xpra isn't aware of desktop changes until something >> causes a >> > change in window state. >> That's correct, and I'm not sure what can be done to change that. We >> just aren't notified of anything by the window manager on the client. >> Or maybe we are just mixing the workspace mappings for all the windows. >> I would have to test this for myself to know for sure, can you please >> file a ticket so I don't forget? >> >> Antoine >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > > > > -- > -- Doug Doole > > aibohphobia - The irrational fear of palindromes > -- -- Doug Doole aibohphobia - The irrational fear of palindromes From przemoc at gmail.com Thu Feb 14 23:53:24 2013 From: przemoc at gmail.com (=?UTF-8?Q?Przemys=C5=82aw_Pawe=C5=82czyk?=) Date: Fri, 15 Feb 2013 00:53:24 +0100 Subject: [winswitch] xpra 0.8.4, free(): invalid pointer Message-ID: Hello! I use xpra occasionally and I do it with pleasure. tmux for X done right! Frankly speaking I haven't tested some few latest releases, but I have winswitch deb repo in my apt/sources, so I have always an up-to-date version at work and at home. I use up-to-date wheezy amd64 in both places. Today, I needed my xpra and it failed hard for the first time. Before I had few cases when I couldn't attach it after attach-at-work,attach-at-home iterations, but stopping, terminating or killing xpra remnants followed by restarting always allowed me to use xpra again. Not today. It crashes right after showing windows due to attach command, every time. Connecting to empty session doesn't cause any problem, until I start xcalc for instance. *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x0000000001bf55f0 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x76d76)[0x7f111d279d76] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f111d27eaac] /usr/lib/python2.7/dist-packages/xpra/x264/codec.so(clean_decoder+0x9)[0x7f1119f90649] /usr/lib/python2.7/dist-packages/xpra/x264/codec.so(+0x6042)[0x7f1119f87042] /usr/bin/python(PyEval_EvalFrameEx+0xe1c)[0x4ad10c] /usr/bin/python(PyEval_EvalFrameEx+0xaf0)[0x4acde0] ======= Memory map: ======== Second attach is unsuccessful, I don't get the following message at all: 2013-02-15 00:44:41,603 Attached to ssh:blahblahblah:100 (press Control-C to detach) Regards. -- Przemys?aw 'Przemoc' Pawe?czyk http://przemoc.net/ From antoine at nagafix.co.uk Fri Feb 15 03:52:22 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 15 Feb 2013 10:52:22 +0700 Subject: [winswitch] xpra 0.8.4, free(): invalid pointer In-Reply-To: References: Message-ID: <511DB0F6.1030501@nagafix.co.uk> On 02/15/2013 06:53 AM, Przemys?aw Pawe?czyk wrote: > Hello! > > I use xpra occasionally and I do it with pleasure. tmux for X done right! > Frankly speaking I haven't tested some few latest releases, but I have > winswitch deb repo in my apt/sources, so I have always an up-to-date > version at work and at home. I use up-to-date wheezy amd64 in both > places. > > Today, I needed my xpra and it failed hard for the first time. Sorry about that :/ > Before I had few cases when I couldn't attach it after > attach-at-work,attach-at-home iterations, but stopping, terminating or > killing xpra remnants followed by restarting always allowed me to use > xpra again. > > Not today. It crashes right after showing windows due to attach > command, every time. > Connecting to empty session doesn't cause any problem, until I start > xcalc for instance. > > > *** glibc detected *** /usr/bin/python: free(): invalid pointer: > 0x0000000001bf55f0 *** > ======= Backtrace: ========= > /lib/x86_64-linux-gnu/libc.so.6(+0x76d76)[0x7f111d279d76] > /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f111d27eaac] > /usr/lib/python2.7/dist-packages/xpra/x264/codec.so(clean_decoder+0x9)[0x7f1119f90649] > /usr/lib/python2.7/dist-packages/xpra/x264/codec.so(+0x6042)[0x7f1119f87042] > /usr/bin/python(PyEval_EvalFrameEx+0xe1c)[0x4ad10c] > /usr/bin/python(PyEval_EvalFrameEx+0xaf0)[0x4acde0] > ======= Memory map: ======== > > > Second attach is unsuccessful, I don't get the following message at all: > > 2013-02-15 00:44:41,603 Attached to ssh:blahblahblah:100 (press > Control-C to detach) Looks like a problem with the x264 codec library built for wheezy, the build may have been missing the compatibility "old-libav.patch" for some strange reason (this should have resulted in a build failure - will check it) In the meantime, you should be able to workaround this by using a different encoding: --encoding=png (though the performance may not be quite as good as before - and may even be unusable over slow connections) Sorry Antoine > > > Regards. > From antoine at nagafix.co.uk Sun Feb 17 11:31:02 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 17 Feb 2013 18:31:02 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.5 (important bug fix) Message-ID: <5120BF76.3050601@nagafix.co.uk> Hi, This update fixes a single regression from the 0.8.x branch which caused server crashes with transient windows under some circumstances. Many thanks to Dmitry Smirnov for spending so much of his time isolating this bug. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine PS: there are no new Windows or OSX builds for this version because those platforms do not run the server and are therefore unaffected. From ndbecker2 at gmail.com Sun Feb 17 16:28:39 2013 From: ndbecker2 at gmail.com (Neal Becker) Date: Sun, 17 Feb 2013 11:28:39 -0500 Subject: [winswitch] Howto make nx work? Message-ID: Client has xpra-0.8.4-1.fc18.x86_64 winswitch-0.12.18-2.x86_64 nx-3.5.0-12.fc18.x86_64 nxclient-3.5.0-7.x86_64 server has nx-3.5.0-12.fc18.x86_64 xpra-0.8.4-1.fc18.x86_64 If I try to start an application session using NX, nothing seems to happen. xpra session works. Any ideas? What packages are required on client/server for NX? From antoine at nagafix.co.uk Mon Feb 18 02:40:21 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 18 Feb 2013 09:40:21 +0700 Subject: [winswitch] Howto make nx work? In-Reply-To: References: Message-ID: <51219495.90008@nagafix.co.uk> $ rpm -qa | grep nx nx-3.5.0-12.fc18.x86_64 Works for me, though there are some keyboard mapping issues. Please file a ticket with more details: logs, etc Antoine On 02/17/2013 11:28 PM, Neal Becker wrote: > Client has > > xpra-0.8.4-1.fc18.x86_64 > winswitch-0.12.18-2.x86_64 > nx-3.5.0-12.fc18.x86_64 > nxclient-3.5.0-7.x86_64 > > server has > > nx-3.5.0-12.fc18.x86_64 > xpra-0.8.4-1.fc18.x86_64 > > If I try to start an application session using NX, nothing seems to happen. > xpra session works. > > Any ideas? What packages are required on client/server for NX? > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From victorhooi at yahoo.com Tue Feb 19 20:19:31 2013 From: victorhooi at yahoo.com (Victor Hooi) Date: Wed, 20 Feb 2013 07:19:31 +1100 Subject: [winswitch] Trouble getting NX to work from OSX Client to Ubuntu Server? Message-ID: Hi, We're trying to get the NX protocol working with WinSwitch from a client running OSX, connecting to a server running Ubuntu. The server is running Ubuntu 13.04. We've added the FreeNX PPA, and installed nxagent and nxproxy from there (only older versions seem available, but I'm not aware of a better source of packages). - Nxagent - Version: 1:3.5.0-9-2-1-2-0~ppa1~precise2 - Nxproxy - Version: 3.5.0-1-0ubuntu1 I've started up the winswitch-applet on the server. On the client side, I've downloaded the Mac DMG, and installed it. I then start it up, and I'm able to connect to the server fine. I can startup applications fine using XPRA. However, session type only offers XPRA as an option - NX isn't available, nor is anything else. What do I need to do to get the Winswitch client on OSX to offer NX? Also, when I try to startup a Gnome desktop session in WinSwich, I get: Failed to load session "gnome" However, GDM on the local box seems to be able to startup Gnome sessions fine? Cheers, Victor From antoine at nagafix.co.uk Fri Feb 22 12:26:31 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 22 Feb 2013 19:26:31 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.6 Message-ID: <512763F7.1080601@nagafix.co.uk> Hi, This stable update fixes a number of bugs, see the release notes below. The most significant, the launcher fixes, should make it more usable on all platforms (not just MS Windows which was the problematic platform). The Mac OSX DMG installer image has not been updated in this release. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine Release notes: * fix launcher on MS Windows, better SSH support * fix python2.4 compatibility in icon grabbing code * fix libav compatibility on MS Windows with VisualStudio * fix exit message location * prevent invalid Python bindings version from being included in the MS Windows installer From antoine at nagafix.co.uk Tue Feb 26 18:22:50 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 27 Feb 2013 01:22:50 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.8.7 bugs and mistakes Message-ID: <512CFD7A.50408@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This stable update fixes a number of important bugs, some of which were introduced in recent releases when fixing other bugs. Oops, sorry. The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine Release notes: * fix x264 crash with older versions of libav * fix 32-bit builds breakage introduce by python2.4 fix in 0.8.6 * fix missing sound forwarding when using the GUI launcher * fix microphone forwarding errors * fix client window properties store * fix first workspace not preserved and other workspace issues * fix GStreamer-Info.exe output * avoid creating unused hidden "group" windows on MS Windows clients -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEs/XoACgkQGK2zHPGK1rv8nQCfW8tcQ9ckVy/Fy6jSZQc72XEo qPEAn1fCoaJbPboes8Z7WIZ3M7bBwlAn =2VN5 -----END PGP SIGNATURE-----