From antoine at nagafix.co.uk Sun Jun 1 16:01:10 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 01 Jun 2014 22:01:10 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.13.2 (minor fixes) Message-ID: <538B4036.5040207@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a few minor bugs: * fix painting of forwarded trays * fix initial window workspace * fix launcher with debug option in config file * fix compilation of x265 encoder * fix infinite recursion in cython csc module * don't include sound utilities when building without sound There is no urgency to upgrade if you were not affected by those 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/ iEYEARECAAYFAlOLQDEACgkQGK2zHPGK1ruTHgCcCNHjEGVBwHRWLr6JGR7kgp61 UF0Anis1Ov4W5wp8UedIjQtYc9EWaGWN =u0+A -----END PGP SIGNATURE----- From dougdoole at gmail.com Mon Jun 2 14:03:40 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Mon, 2 Jun 2014 09:03:40 -0400 Subject: [winswitch] 0.13.2 xpra upgrade broken Message-ID: I installed 0.13.2 on my server today. (It was running 0.13.1.) When I did "xpra upgrade :1", it wiped out my xpra instance. There's not much in :1.log: 2014-06-02 08:10:42,810 failed to load the mdns avahi publisher: No module named avahi 2014-06-02 08:10:42,811 either fix your installation or use the '--no-mdns' flag 2014-06-02 08:10:42,937 found previous Xpra instance 2014-06-02 08:10:42,947 server uuid is f48c3494e00e44e9baa1066a0151abe8 2014-06-02 08:10:42,952 buggy Ubuntu swscale version detected: (2, 1, 0) 2014-06-02 08:10:42,952 cowardly refusing to use it to avoid problems, set the environment variable: 2014-06-02 08:10:42,952 XPRA_FORCE_SWSCALE=1 2014-06-02 08:10:42,952 to use it anyway, at your own risk 2014-06-02 08:10:42,953 cannot import csc_swscale (swscale colorspace conversion): unsupported Ubuntu swscale version: (2, 1, 0) 2014-06-02 08:10:42,956 buggy avcodec version detected: (53, 35, 0) 2014-06-02 08:10:42,956 cowardly refusing to use it to avoid crashes, set the environment variable: 2014-06-02 08:10:42,956 XPRA_FORCE_AVCODEC=1 2014-06-02 08:10:42,956 to use it anyway, at your own risk 2014-06-02 08:10:42,956 cannot import dec_avcodec (avcodec decoder): unsupported avcodec version: (53, 35, 0) 2014-06-02 08:10:42,957 cannot import enc_webm (webp encoder): Could not find webp library from ['libwebp.so.5', 'libwebp.so.4'] 2014-06-02 08:10:42,957 cannot import dec_webm (webp encoder): Could not find webp library from ['libwebp.so.5', 'libwebp.so.4'] g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Xpra: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Mon Jun 2 14:21:42 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 02 Jun 2014 20:21:42 +0700 Subject: [winswitch] 0.13.2 xpra upgrade broken In-Reply-To: References: Message-ID: <538C7A66.4060003@nagafix.co.uk> On 02/06/14 20:03, Douglas Doole wrote: > I installed 0.13.2 on my server today. (It was running 0.13.1.) When I did > "xpra upgrade :1", it wiped out my xpra instance. Sorry about that! Just fixed: http://xpra.org/trac/changeset/6630/xpra I will backport in the next few days. As a temporary workaround, you can use "exit" which works OK: xpra exit :1 xpra start --use-display :1 Antoine From dougdoole at gmail.com Mon Jun 2 14:31:25 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Mon, 2 Jun 2014 09:31:25 -0400 Subject: [winswitch] 0.13.2 xpra upgrade broken In-Reply-To: <538C7A66.4060003@nagafix.co.uk> References: <538C7A66.4060003@nagafix.co.uk> Message-ID: Thanks for the quick fix. (I wasn't running anything important at the time, so losing the session wasn't a big deal.) On Mon, Jun 2, 2014 at 9:21 AM, Antoine Martin wrote: > On 02/06/14 20:03, Douglas Doole wrote: > > I installed 0.13.2 on my server today. (It was running 0.13.1.) When I > did > > "xpra upgrade :1", it wiped out my xpra instance. > Sorry about that! Just fixed: > http://xpra.org/trac/changeset/6630/xpra > I will backport in the next few days. > > As a temporary workaround, you can use "exit" which works OK: > xpra exit :1 > xpra start --use-display :1 > > 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 antoine at nagafix.co.uk Thu Jun 5 09:58:59 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 05 Jun 2014 15:58:59 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.13.3 (minor fixes) Message-ID: <53903153.7030703@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes some minor issues and one import bug ("broken xpra upgrade"): * fix "xpra upgrade" * fix "xpra control" error handling * fix window refresh on inactive workspace * fix slow cursor updates * fix error in rgb strict mode * add missing x11 server type information There is no urgency to upgrade if you were not affected by those 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/ iEYEARECAAYFAlOQMU8ACgkQGK2zHPGK1rtTEACfR4AWOIWcB1nSRyjZ5g3M0C5g uroAnRezMDU0ttQCx+/L4NS2zlki9rkX =KGEO -----END PGP SIGNATURE----- From dougdoole at gmail.com Thu Jun 5 17:56:00 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Thu, 5 Jun 2014 12:56:00 -0400 Subject: [winswitch] xpra upgrade still failing in 0.13.3 Message-ID: I just moved to 0.13.3 and tried xpra upgrade :1. My xpra session was wiped out again. Here's the end of :1.log.old. I did the upgrade at 12:51 today. 2014-06-02 13:10:46,469 Connection lost 2014-06-02 13:10:46,470 xpra client disconnected. 2014-06-05 12:49:14,403 New connection received: SocketConnection(/home/doole/.xpra/reorx-1) 2014-06-05 12:49:14,408 Handshake complete; enabling connection 2014-06-05 12:49:14,409 Python/Gtk2 Linux client version 0.13.3 connected from 'andammo' as 'doole' ('Doug Doole') 2014-06-05 12:49:14,410 client supplied an mmap_file: /tmp/xpra.IMScRK.mmap but we cannot find it 2014-06-05 12:49:14,410 using png as primary encoding, also available: vp8, png/P, png/L, rgb24, jpeg, rgb32 2014-06-05 12:49:14,410 client root window size is 1600x900 with 1 displays: 2014-06-05 12:49:14,410 ':0.0' (423x238 mm) workarea: 1487x900 at 113x0 2014-06-05 12:49:14,410 LVDS1 (309x174 mm) 2014-06-05 12:49:14,421 server virtual display now set to 1600x900 2014-06-05 12:49:14,422 setting key repeat rate from client: 250ms delay / 33ms interval 2014-06-05 12:49:14,424 keyboard mapping already configured (skipped) 2014-06-05 12:49:14,434 DPI set to 19 x 21 (wanted 96 x 96) 2014-06-05 12:49:40,416 Connection lost 2014-06-05 12:49:40,417 xpra client disconnected. 2014-06-05 12:51:34,641 Lost WM selection ManagerSelection(WM_S0), exiting 2014-06-05 12:51:34,641 xpra is terminating. 2014-06-05 12:51:34,643 removing socket /home/doole/.xpra/reorx-1 2014-06-05 12:51:34,643 killing xvfb with pid 32415 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. ddxSigGiveUp: Closing log -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Thu Jun 5 18:00:50 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 06 Jun 2014 00:00:50 +0700 Subject: [winswitch] xpra upgrade still failing in 0.13.3 In-Reply-To: References: Message-ID: <5390A242.3040801@nagafix.co.uk> On 05/06/14 23:56, Douglas Doole wrote: > I just moved to 0.13.3 and tried xpra upgrade :1. My xpra session was wiped > out again. I've just verified again and 0.13.3 upgrades fine here. My guess is that the session you upgraded was running on a server which was not running 0.13.3 but an older version, and therefore did not have the fix... Until the server is running a version with the fix, you have to use the workaround I posted earlier: xpra exit xpra start --use-display Cheers Antoine From dougdoole at gmail.com Thu Jun 5 18:04:04 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Thu, 5 Jun 2014 13:04:04 -0400 Subject: [winswitch] xpra upgrade still failing in 0.13.3 In-Reply-To: <5390A242.3040801@nagafix.co.uk> References: <5390A242.3040801@nagafix.co.uk> Message-ID: Ah. That would be it. The server was running 0.13.2. Sorry for the false alarm. On Thu, Jun 5, 2014 at 1:00 PM, Antoine Martin wrote: > On 05/06/14 23:56, Douglas Doole wrote: > > I just moved to 0.13.3 and tried xpra upgrade :1. My xpra session was > wiped > > out again. > I've just verified again and 0.13.3 upgrades fine here. > My guess is that the session you upgraded was running on a server which > was not running 0.13.3 but an older version, and therefore did not have > the fix... > Until the server is running a version with the fix, you have to use the > workaround I posted earlier: > xpra exit > xpra start --use-display > > Cheers > 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 antoine at nagafix.co.uk Sun Jun 8 15:33:47 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 08 Jun 2014 21:33:47 +0700 Subject: [winswitch] NVENC developer key? In-Reply-To: <5334EEAB.7090000@nagafix.co.uk> References: <5334EEAB.7090000@nagafix.co.uk> Message-ID: <5394744B.4090802@nagafix.co.uk> On 28/03/14 10:38, Antoine Martin wrote: > 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. Quick update on this: NVidia's contempt for Linux users continues unabated. The latest Linux drivers still require a license key to function with consumer cards, not only that but they have also changed those keys during the stable updates to their drivers: the latest 331 and 334 drivers now require different keys than they did before. With the 337 branch it is even worse: the newer keys are accepted, but the API has changed and so the codec needs to be rebuilt against the newer API headers, which have not been released yet.. So this one is a complete no go at present. It also means that the nvenc codec in xpra is actually tied to specific versions of the drivers, which is another system maintenance headache. Start of rant: "Proprietary Tyrants" http://www.gnu.org/philosophy/proprietary-tyrants.html " A/tyrant/device is one that refuses to allow users to install a different operating system or a modified operating system. These devices have measures to block execution of anything other than the ?approved? system versions. We also refer to this practice as/tivoization/." "Proprietary Sabotage" http://www.gnu.org/philosophy/proprietary-sabotage.html "Every nonfree program has a lord, a master--and if you use the program, he is your master." - RMS End of rant. Cheers Antoine From offonoffoffonoff at gmail.com Mon Jun 9 02:15:59 2014 From: offonoffoffonoff at gmail.com (...) Date: Sun, 8 Jun 2014 20:15:59 -0500 Subject: [winswitch] NVENC developer key? In-Reply-To: <5394744B.4090802@nagafix.co.uk> References: <5334EEAB.7090000@nagafix.co.uk> <5394744B.4090802@nagafix.co.uk> Message-ID: Boooo! Thanks for the analysis. On Jun 8, 2014 9:34 AM, "Antoine Martin" wrote: > On 28/03/14 10:38, Antoine Martin wrote: > > 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. > Quick update on this: NVidia's contempt for Linux users continues unabated. > The latest Linux drivers still require a license key to function with > consumer cards, not only that but they have also changed those keys > during the stable updates to their drivers: the latest 331 and 334 > drivers now require different keys than they did before. > With the 337 branch it is even worse: the newer keys are accepted, but > the API has changed and so the codec needs to be rebuilt against the > newer API headers, which have not been released yet.. So this one is a > complete no go at present. > It also means that the nvenc codec in xpra is actually tied to specific > versions of the drivers, which is another system maintenance headache. > > > Start of rant: > "Proprietary Tyrants" > http://www.gnu.org/philosophy/proprietary-tyrants.html > " A/tyrant/device is one that refuses to allow users to install a > different operating system or a modified operating system. These devices > have measures to block execution of anything other than the ?approved? > system versions. We also refer to this practice as/tivoization/." > > "Proprietary Sabotage" > http://www.gnu.org/philosophy/proprietary-sabotage.html > > "Every nonfree program has a lord, a master--and if you use the program, > he is your master." - RMS > End of rant. > > Cheers > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From hugo1000 at gmail.com Mon Jun 9 11:04:40 2014 From: hugo1000 at gmail.com (Hugo) Date: Mon, 9 Jun 2014 11:04:40 +0100 Subject: [winswitch] Awkward... Message-ID: Hi, I really don't want to make this any longer than necessary as it is embarrassing as hell, but is this software for real? The reason I ask is that while the website looks like this is a mature product still under active development, but: 1) The starter instructions on the initial page are missing the bit that you must start a session on the server, even when the first suggested command strongly looks like it should create the damm session itself. 2) Every single command I have tried on this has lead to a variety of unhandled python exceptions which... well... have you guys heard of try, except, and all that? I mean if you can't code it right the first fucking time, at least try to catch the fucking exceptions in some fucking useful error messages. 3) Couldn't get it work at all in any way. Following is some of the output I have had to endure: 1) running your own fucking example command: xpra start ssh:192.168.1.114:100 --start-child=/home/hugo/jmeter/runjmeter.sh 2014-06-09 10:46:01,970 OpenGL support not enabled: No module named gdkgl bash: .xpra/run-xpra: No such file or directory 2014-06-09 10:46:02,293 connection closed after 0 packets received (0.0 bytes) and 1 packets sent (25K bytes) 2014-06-09 10:46:02,293 Connection lost 2) running your won fucking example command AGAIN: xpra start ssh:192.168.1.114:100 --start-child=/home/hugo/jmeter/runjmeter.sh 2014-06-09 10:47:55,424 OpenGL support not enabled: No module named gdkgl bash: .xpra/run-xpra: No such file or directory 2014-06-09 10:47:55,646 read error for TwoFileConnection(ssh: 192.168.1.114:100) Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, in _io_thread_loop callback() File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 485, in _read buf = self._conn.read(8192) File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 70, in read self.may_abort("read") File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 67, in may_abort self._abort_test(action) File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, in abort_test raise IOError(error_message) IOError: cannot read using ['ssh', '-T', '192.168.1.114', '.xpra/run-xpra', '_proxy_start', ':100', '--start-child=/etc/X11/Xsession true', '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process has terminated with exit code=127 2014-06-09 10:47:55,654 write error for TwoFileConnection(ssh: 192.168.1.114:100) Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, in _io_thread_loop callback() File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 471, in _write written = self._conn.write(buf) File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 74, in write self.may_abort("write") File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 67, in may_abort self._abort_test(action) File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, in abort_test raise IOError(error_message) IOError: cannot write using ['ssh', '-T', '192.168.1.114', '.xpra/run-xpra', '_proxy_start', ':100', '--start-child=/etc/X11/Xsession true', '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process has terminated with exit code=127 2014-06-09 10:47:55,654 connection closed after 0 packets received (0.0 bytes) and 1 packets sent (0.0 bytes) 3) running your own fucking example command AFTER STARTING A SERVER SESSION: xpra start ssh:192.168.1.114:100 --start-child=/home/hugo/jmeter/runjmeter.sh 2014-06-09 10:52:54,778 OpenGL support not enabled: No module named gdkgl Traceback (most recent call last): File "/usr/bin/xpra", line 8, in sys.exit(main(sys.argv[0], sys.argv)) File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 70, in main return run_mode(script_file, parser, options, args, mode) File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 620, in run_mode return run_proxy(parser, options, script_file, args, mode) File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 1074, in run_proxy assert len(args)==1, "proxy/shadow-start: expected 1 argument but got %s" % len(args) AssertionError: proxy/shadow-start: expected 1 argument but got 2 2014-06-09 10:52:55,062 Connection lost 2014-06-09 10:52:55,063 connection closed after 0 packets received (0.0 bytes) and 1 packets sent (25K bytes) Stop developing software. I rest my case. Hugo Campos PS: send any replies directly as I have obviously not subscribed this mailing list From antoine at nagafix.co.uk Mon Jun 9 12:47:31 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 09 Jun 2014 18:47:31 +0700 Subject: [winswitch] Awkward... In-Reply-To: References: Message-ID: <53959ED3.9000705@nagafix.co.uk> Hi, On 09/06/14 17:04, Hugo wrote: (..) > 1) The starter instructions on the initial page are missing the bit that > you must start a session on the server, even when the first suggested > command strongly looks like it should create the damm session itself. Yes, I think this is a legitimate problem right there. Thank you for pointing that out. You need to have run "xpra start" at least once in the lifetime of the target user account. Sorry about that, we will fix that. > 2) Every single command I have tried on this has lead to a variety of > unhandled python exceptions which... well... have you guys heard of try, > except, and all that? I mean if you can't code it right the first fucking > time, at least try to catch the fucking exceptions in some fucking useful > error messages. Does swearing on a mailing list usually help? You will find that most exceptions are documented on the FAQ, and generally caused by packaging issues. If you find some that are not, we'll make sure to fix them. > 3) Couldn't get it work at all in any way. Even with: xpra start :10 --start-child=xterm xpra attach ? > Stop developing software. I rest my case. You seem to have been quite frustrated by this experience, I'm sorry about that. Next time, please get some help here or on IRC, and also check the FAQ. Cheers Antoine From blade.eric at gmail.com Mon Jun 9 13:46:17 2014 From: blade.eric at gmail.com (Eric Blade) Date: Mon, 9 Jun 2014 05:46:17 -0700 Subject: [winswitch] Awkward... In-Reply-To: References: Message-ID: ... Perhaps you should try the more user-friendly front-end http://winswitch.org/ instead of xpra directly. On Mon, Jun 9, 2014 at 3:04 AM, Hugo wrote: > Hi, I really don't want to make this any longer than necessary as it is > embarrassing as hell, but is this software for real? The reason I ask is > that while the website looks like this is a mature product still under > active development, but: > > 1) The starter instructions on the initial page are missing the bit that > you must start a session on the server, even when the first suggested > command strongly looks like it should create the damm session itself. > > 2) Every single command I have tried on this has lead to a variety of > unhandled python exceptions which... well... have you guys heard of try, > except, and all that? I mean if you can't code it right the first fucking > time, at least try to catch the fucking exceptions in some fucking useful > error messages. > > 3) Couldn't get it work at all in any way. > > Following is some of the output I have had to endure: > > 1) running your own fucking example command: > xpra start ssh:192.168.1.114:100 > --start-child=/home/hugo/jmeter/runjmeter.sh > 2014-06-09 10:46:01,970 OpenGL support not enabled: No module named gdkgl > bash: .xpra/run-xpra: No such file or directory > 2014-06-09 10:46:02,293 connection closed after 0 packets received (0.0 > bytes) and 1 packets sent (25K bytes) > 2014-06-09 10:46:02,293 Connection lost > > 2) running your won fucking example command AGAIN: > xpra start ssh:192.168.1.114:100 > --start-child=/home/hugo/jmeter/runjmeter.sh > 2014-06-09 10:47:55,424 OpenGL support not enabled: No module named gdkgl > bash: .xpra/run-xpra: No such file or directory > 2014-06-09 10:47:55,646 read error for TwoFileConnection(ssh: > 192.168.1.114:100) > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, > in _io_thread_loop > callback() > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 485, > in _read > buf = self._conn.read(8192) > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 70, > in read > self.may_abort("read") > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 67, > in may_abort > self._abort_test(action) > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, > in abort_test > raise IOError(error_message) > IOError: cannot read using ['ssh', '-T', '192.168.1.114', '.xpra/run-xpra', > '_proxy_start', ':100', '--start-child=/etc/X11/Xsession true', > '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process has > terminated with exit code=127 > 2014-06-09 10:47:55,654 write error for TwoFileConnection(ssh: > 192.168.1.114:100) > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, > in _io_thread_loop > callback() > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 471, > in _write > written = self._conn.write(buf) > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 74, > in write > self.may_abort("write") > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line 67, > in may_abort > self._abort_test(action) > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, > in abort_test > raise IOError(error_message) > IOError: cannot write using ['ssh', '-T', '192.168.1.114', > '.xpra/run-xpra', '_proxy_start', ':100', '--start-child=/etc/X11/Xsession > true', '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process has > terminated with exit code=127 > 2014-06-09 10:47:55,654 connection closed after 0 packets received (0.0 > bytes) and 1 packets sent (0.0 bytes) > > 3) running your own fucking example command AFTER STARTING A SERVER > SESSION: > xpra start ssh:192.168.1.114:100 > --start-child=/home/hugo/jmeter/runjmeter.sh > 2014-06-09 10:52:54,778 OpenGL support not enabled: No module named gdkgl > Traceback (most recent call last): > File "/usr/bin/xpra", line 8, in > sys.exit(main(sys.argv[0], sys.argv)) > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 70, in > main > return run_mode(script_file, parser, options, args, mode) > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 620, > in run_mode > return run_proxy(parser, options, script_file, args, mode) > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 1074, > in run_proxy > assert len(args)==1, "proxy/shadow-start: expected 1 argument but got > %s" % len(args) > AssertionError: proxy/shadow-start: expected 1 argument but got 2 > 2014-06-09 10:52:55,062 Connection lost > 2014-06-09 10:52:55,063 connection closed after 0 packets received (0.0 > bytes) and 1 packets sent (25K bytes) > > > > > Stop developing software. I rest my case. > > Hugo Campos > > PS: send any replies directly as I have obviously not subscribed this > mailing list > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > -- Eric Blade - 707-99-BLADE http://www.ericbla.de/ When they broke open molecules, they found they were only stuffed with atoms. But when they broke open atoms, they found them stuffed with explosions. "I hate how the assembly directions for my new desk are more difficult to understand than the programming languages I use while at the desk."- Phil Miller From offonoffoffonoff at gmail.com Mon Jun 9 23:54:25 2014 From: offonoffoffonoff at gmail.com (...) Date: Mon, 9 Jun 2014 17:54:25 -0500 Subject: [winswitch] Awkward... In-Reply-To: References: Message-ID: Hugo, Did you try doing anything about the error you were getting? Or did you keep running the same commands ignoring the fact that xpra was complaining about a missing dependency? The error seems pretty clear about a fatal error, so I don't think a try/except would be helpful. On Mon, Jun 9, 2014 at 7:46 AM, Eric Blade wrote: > ... Perhaps you should try the more user-friendly front-end > http://winswitch.org/ instead of xpra directly. > > > > On Mon, Jun 9, 2014 at 3:04 AM, Hugo wrote: > > > Hi, I really don't want to make this any longer than necessary as it is > > embarrassing as hell, but is this software for real? The reason I ask is > > that while the website looks like this is a mature product still under > > active development, but: > > > > 1) The starter instructions on the initial page are missing the bit that > > you must start a session on the server, even when the first suggested > > command strongly looks like it should create the damm session itself. > > > > 2) Every single command I have tried on this has lead to a variety of > > unhandled python exceptions which... well... have you guys heard of try, > > except, and all that? I mean if you can't code it right the first fucking > > time, at least try to catch the fucking exceptions in some fucking useful > > error messages. > > > > 3) Couldn't get it work at all in any way. > > > > Following is some of the output I have had to endure: > > > > 1) running your own fucking example command: > > xpra start ssh:192.168.1.114:100 > > --start-child=/home/hugo/jmeter/runjmeter.sh > > 2014-06-09 10:46:01,970 OpenGL support not enabled: No module named gdkgl > > bash: .xpra/run-xpra: No such file or directory > > 2014-06-09 10:46:02,293 connection closed after 0 packets received (0.0 > > bytes) and 1 packets sent (25K bytes) > > 2014-06-09 10:46:02,293 Connection lost > > > > 2) running your won fucking example command AGAIN: > > xpra start ssh:192.168.1.114:100 > > --start-child=/home/hugo/jmeter/runjmeter.sh > > 2014-06-09 10:47:55,424 OpenGL support not enabled: No module named gdkgl > > bash: .xpra/run-xpra: No such file or directory > > 2014-06-09 10:47:55,646 read error for TwoFileConnection(ssh: > > 192.168.1.114:100) > > Traceback (most recent call last): > > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, > > in _io_thread_loop > > callback() > > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 485, > > in _read > > buf = self._conn.read(8192) > > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line > 70, > > in read > > self.may_abort("read") > > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line > 67, > > in may_abort > > self._abort_test(action) > > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, > > in abort_test > > raise IOError(error_message) > > IOError: cannot read using ['ssh', '-T', '192.168.1.114', > '.xpra/run-xpra', > > '_proxy_start', ':100', '--start-child=/etc/X11/Xsession true', > > '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process has > > terminated with exit code=127 > > 2014-06-09 10:47:55,654 write error for TwoFileConnection(ssh: > > 192.168.1.114:100) > > Traceback (most recent call last): > > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 437, > > in _io_thread_loop > > callback() > > File "/usr/lib/python2.7/dist-packages/xpra/net/protocol.py", line 471, > > in _write > > written = self._conn.write(buf) > > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line > 74, > > in write > > self.may_abort("write") > > File "/usr/lib/python2.7/dist-packages/xpra/net/bytestreams.py", line > 67, > > in may_abort > > self._abort_test(action) > > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 602, > > in abort_test > > raise IOError(error_message) > > IOError: cannot write using ['ssh', '-T', '192.168.1.114', > > '.xpra/run-xpra', '_proxy_start', ':100', > '--start-child=/etc/X11/Xsession > > true', '--start-child=/home/hugo/jmeter/runjmeter.sh']: the SSH process > has > > terminated with exit code=127 > > 2014-06-09 10:47:55,654 connection closed after 0 packets received (0.0 > > bytes) and 1 packets sent (0.0 bytes) > > > > 3) running your own fucking example command AFTER STARTING A SERVER > > SESSION: > > xpra start ssh:192.168.1.114:100 > > --start-child=/home/hugo/jmeter/runjmeter.sh > > 2014-06-09 10:52:54,778 OpenGL support not enabled: No module named gdkgl > > Traceback (most recent call last): > > File "/usr/bin/xpra", line 8, in > > sys.exit(main(sys.argv[0], sys.argv)) > > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 70, > in > > main > > return run_mode(script_file, parser, options, args, mode) > > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 620, > > in run_mode > > return run_proxy(parser, options, script_file, args, mode) > > File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line > 1074, > > in run_proxy > > assert len(args)==1, "proxy/shadow-start: expected 1 argument but got > > %s" % len(args) > > AssertionError: proxy/shadow-start: expected 1 argument but got 2 > > 2014-06-09 10:52:55,062 Connection lost > > 2014-06-09 10:52:55,063 connection closed after 0 packets received (0.0 > > bytes) and 1 packets sent (25K bytes) > > > > > > > > > > Stop developing software. I rest my case. > > > > Hugo Campos > > > > PS: send any replies directly as I have obviously not subscribed this > > mailing list > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > > -- > Eric Blade - 707-99-BLADE > http://www.ericbla.de/ > > When they broke open molecules, they found they were only stuffed with > atoms. > But when they broke open atoms, they found them stuffed with explosions. > > "I hate how the assembly directions for my new desk are more difficult to > understand than the programming languages I use while at the desk."- Phil > Miller > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From hugo1000 at gmail.com Tue Jun 10 13:24:28 2014 From: hugo1000 at gmail.com (Hugo) Date: Tue, 10 Jun 2014 13:24:28 +0100 Subject: [winswitch] Awkward... In-Reply-To: References: Message-ID: Hello all, Regarding some questions that I received related to my post: 1) I am sorry for the inappropriate wording. 2) I still don't see what dependencies are missing. 3) I consider the message regarding gdkgl to be informative (not an error) but not important as I will not be requiring OpenGL for my usage. It's great that it is supported, when dependencies are present. This should not stop the xpra from working. If these assumptions are wrong, please tell me. 4) Looking at the error and exceptions I posted, Antoine Martin kindly informed me that you needed to have run a session before the frontpage example would work. So if we ignore the errors that are about reading or writing to the then non-existent ~/.xpra files, we are left with the last one: AssertionError: proxy/shadow-start: expected 1 argument but got 2 Im sure that due to the introspective nature of python, some contrived example could be crafted where a missing dependency will result in a call with the wrong number of arguments, but to me this looks like unfinished code. 5) I am using Ubuntu so if the package dependencies for the package 'xpra' are wrong, the package maintainer should be contacted. The issue could be present in Debian as well, as it is most likely Debian's package in Ubuntu. I don't even know how to get my setup working so I certainly can't provide the maintainer with an authoritative answer. Thank you Hugo. From antoine at nagafix.co.uk Tue Jun 10 16:01:06 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 10 Jun 2014 22:01:06 +0700 Subject: [winswitch] Awkward... In-Reply-To: References: Message-ID: <53971DB2.5040701@nagafix.co.uk> Hi, (..) > 3) I consider the message regarding gdkgl to be informative (not an error) > but not important as I will not be requiring OpenGL for my usage. It's > great that it is supported, when dependencies are present. This should not > stop the xpra from working. If these assumptions are wrong, please tell me. All correct: not having OpenGL installed is not a showstopper, it is sub-optimal but definitely supported. >From your previous log samples, I can only see a single line of warning related to OpenGL: "OpenGL support not enabled: No module named gdkgl" On Debian systems, I believe that the package required for this is "python-gtkglext1": https://packages.debian.org/search?searchon=names&keywords=python-gtkglext1 Note however that in practice, you are likely to see more warnings and not less! (and that is despite a large amount of our code dedicated to trimming down those annoying warnings) The rest of your error messages are caused by the ssh connection dropping from underneath us. I agree that it isn't very pretty, but I'm not seeing anything like this here. Maybe your version of xpra is outdated? Anything older than 0.13 is no longer supported, your distribution vendor may claim to support older versions, but I have never seen it happen (as in, fixing known bugs). > 4) Looking at the error and exceptions I posted, Antoine Martin kindly > informed me that you needed to have run a session before the frontpage > example would work. FYI: the fix for this has been committed, and will be released in the next 24 hours in our source release and binary packages (if you choose to use those). > So if we ignore the errors that are about reading or > writing to the then non-existent ~/.xpra files, we are left with the last > one: > > AssertionError: proxy/shadow-start: expected 1 argument but got 2 > > Im sure that due to the introspective nature of python, some contrived > example could be crafted where a missing dependency will result in a call > with the wrong number of arguments, but to me this looks like unfinished > code. You're not posting the exact commands that you've used, but I've just tested this repeatedly with: xpra shadow ssh:localhost:0 And apart from just fixing a bug which prevented the following variant from working properly (only in some cases): xpra shadow ssh:localhost I am not seeing the error that you refer to. I have modified the code in trunk to provide more detailed error message in this case. > 5) I am using Ubuntu so if the package dependencies for the package 'xpra' > are wrong, the package maintainer should be contacted. I don't know which Ubuntu release you are running, or even which xpra package you have installed.. Cheers Antoine > The issue could be > present in Debian as well, as it is most likely Debian's package in Ubuntu. > I don't even know how to get my setup working so I certainly can't provide > the maintainer with an authoritative answer. > > Thank you > > Hugo. > _______________________________________________ > 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 Jun 10 17:13:43 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 10 Jun 2014 23:13:43 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.13.4 (many fixes) Message-ID: <53972EB7.5010706@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a number of issues, upgrading is recommended. * fix numeric keypad period key mapping on some non-us keyboards * fix client launcher GUI on OSX * fix remote ssh start with clean user accounts * fix remote shadow start with automatic display selection * fix avoid scaling during resize * fix changes of speed and quality via xpra control (make it stick) * fix xpra info global batch statistics * fix focus issue with some applications * fix batch delay use The last fix is a tricky one, although it is "correct" in a very obvious way, it may in some cases cause xpra to delay updates more than it did before. If you find such a problem, please do let us know. 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/ iEYEARECAAYFAlOXLrIACgkQGK2zHPGK1rv5fQCfRAd8ZGZB2p6NXXTytgj4bnm5 3uUAn3LuL1eB3FYGocNPQzM5/A5rA6Ae =JRgY -----END PGP SIGNATURE----- From support at mnavers.net Thu Jun 12 11:54:12 2014 From: support at mnavers.net (Support) Date: Thu, 12 Jun 2014 12:54:12 +0200 Subject: [winswitch] Question regarding licensing Message-ID: We're currently looking at the possibility of integrating some xpra functionality into our products, I was wondering if it would be possible to buy a commercial license of winswitch/xpra? This due to oss contamination and export restrictions. Thanks in advance for any answers. From antoine at nagafix.co.uk Thu Jun 12 14:13:02 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Jun 2014 20:13:02 +0700 Subject: [winswitch] Question regarding licensing In-Reply-To: References: Message-ID: <5399A75E.1080006@nagafix.co.uk> Very large disclaimer: I am not a lawyer. If you have legal questions and want definitive answers, you should probably ask a lawyer. On 12/06/14 17:54, Support wrote: > We're currently looking at the possibility of integrating some xpra > functionality into our products, > I was wondering if it would be possible to buy a commercial license of > winswitch/xpra? Both winswitch and xpra are licensed under the GPL (GPL2+ for xpra, GPL3 for winswitch) Are you sure that you need a commercial license for what you are doing? IANAL and most of this is open to interpretation, but unless you are modifying and re-distributing the code, chances are that you don't need one. If you would like to have either projects re-licensed under a different license: * xpra has had a few contributors, you would need to contact and get an agreement from all of them (I believe all the copyright holders can be contacted, whether they would agree with your plans is a different issue) * I hold all the copyrights for winswitch, so this could be arranged more easily > This due to oss contamination and export restrictions. Again, without further details, it is difficult to say what, if anything, would apply here. AFAIK, running the software does not "contaminate" anything. As for export restrictions, I'm not sure if / how licensing could change the legal status. Cheers Antoine > Thanks in advance for any answers. From sattler at med.uni-frankfurt.de Fri Jun 13 12:41:27 2014 From: sattler at med.uni-frankfurt.de (Thomas Sattler) Date: Fri, 13 Jun 2014 13:41:27 +0200 Subject: [winswitch] bash: .xpra/run-xpra: No such file or directory Message-ID: <539AE367.1010507@med.uni-frankfurt.de> Hi there ... I found a regression in recent xpra Version: bash: .xpra/run-xpra: No such file or directory The file does exist as ~/.xpra/run-xpra but when I ssh into that box, my shell does not start in $HOME. If I link ~/.xpra to the directory where my remote shell starts, xpra works fine. I'm running Gentoo Linux with xpra 0.13.3 on the client and Debian with 0.13.4-1 on the server. Thomas From antoine at nagafix.co.uk Fri Jun 13 14:11:24 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 13 Jun 2014 20:11:24 +0700 Subject: [winswitch] bash: .xpra/run-xpra: No such file or directory In-Reply-To: <539AE367.1010507@med.uni-frankfurt.de> References: <539AE367.1010507@med.uni-frankfurt.de> Message-ID: <539AF87C.1040007@nagafix.co.uk> On 13/06/14 18:41, Thomas Sattler wrote: > Hi there ... > > I found a regression in recent xpra Version: How "recent" do you mean? > bash: .xpra/run-xpra: No such file or directory I thought we had been using this path form for a while. > The file does exist as ~/.xpra/run-xpra but when > I ssh into that box, my shell does not start in > $HOME. If I link ~/.xpra to the directory where > my remote shell starts, xpra works fine. You patch (sent separately) changes it to: confdir + "run-xpra" But that's not *necessarily* where the script lives. We should not be expanding the path locally of something that is then used remotely. Doesn't it work if you just replace it with: ~/.xpra/run-xpra or even: $HOME/.xpra/run-xpra Thanks Antoine > > I'm running Gentoo Linux with xpra 0.13.3 on the > client and Debian with 0.13.4-1 on the server. > > Thomas > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From sattler at med.uni-frankfurt.de Fri Jun 13 14:27:17 2014 From: sattler at med.uni-frankfurt.de (Thomas Sattler) Date: Fri, 13 Jun 2014 15:27:17 +0200 Subject: [winswitch] bash: .xpra/run-xpra: No such file or directory In-Reply-To: <539AF87C.1040007@nagafix.co.uk> References: <539AE367.1010507@med.uni-frankfurt.de> <539AF87C.1040007@nagafix.co.uk> Message-ID: <539AFC35.7000408@med.uni-frankfurt.de> On 13/06/14 15:11, Antoine Martin wrote: > On 13/06/14 18:41, Thomas Sattler wrote: >> I found a regression in recent xpra Version: > > How "recent" do you mean? I'm running Gentoo Linux with xpra 0.13.3 on the client and Debian with 0.13.4-1 on the server. Client side is installed via Gentoo portage, server gets xpra via http://winswitch.org/ > I thought we had been using this path form for a while. I do not use xpra every day but at least once per week. Today I updated both machines and couldn't connect anymore. But yes, thinking about it for a second time, there might have been changes on our side this week. So calling it a regression might have been wrong. > We should not be expanding the path locally of something > that is then used remotely. > > Doesn't it work if you just replace it with: > ~/.xpra/run-xpra I (successfully) tested this but thought you would prefer doing it via confdir. > or even: > $HOME/.xpra/run-xpra Yes, this works, too. Thomas From antoine at nagafix.co.uk Fri Jun 13 15:43:05 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 13 Jun 2014 21:43:05 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.13.5 (many fixes) Message-ID: <539B0DF9.6050803@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a number of issues, upgrading is recommended. * fix use correct dimensions when evaluating video * fix invalid latency statistics recording * fix auto-refresh wrongly canceled * fix connection via nested ssh commands * fix statically linked builds of swscale codec * fix system tray icons when upgrading server * fix OpenGL compatibility with older libraries * fix SSH connection with shells not starting in home directory * fix keyboard layout change forwarding There are no OSX builds for this release and I have had to pull the 0.13.4 OSX builds because of crashes caused by the GTK OpenGL libraries. Hopefully we can fix the build host without having to downgrade back to older library versions (work in progress). 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/ iEYEARECAAYFAlObDfUACgkQGK2zHPGK1rv5GACfaWViytY1hYHEaWtw95Jx2RjD CT4An0n3d/H7qvEXIQjMdvqNkvWOnHbI =3bfn -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Mon Jun 16 05:55:04 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 16 Jun 2014 11:55:04 +0700 Subject: [winswitch] NVENC developer key? In-Reply-To: <5394744B.4090802@nagafix.co.uk> References: <5334EEAB.7090000@nagafix.co.uk> <5394744B.4090802@nagafix.co.uk> Message-ID: <539E78A8.5080101@nagafix.co.uk> > Quick update on this: NVidia's contempt for Linux users continues unabated. > The latest Linux drivers still require a license key to function with > consumer cards, not only that but they have also changed those keys > during the stable updates to their drivers: the latest 331 and 334 > drivers now require different keys than they did before. > With the 337 branch it is even worse: the newer keys are accepted, but > the API has changed and so the codec needs to be rebuilt against the > newer API headers, which have not been released yet.. So this one is a > complete no go at present. > It also means that the nvenc codec in xpra is actually tied to specific > versions of the drivers, which is another system maintenance headache. Slight correction: * it is the 340 branch that breaks the API and looks like it will need a new SDK * the 337 branch does run, but breaks the YUV444 mode, so we now disable support for it when this driver version is detected. I have summarized this nvidia driver mess here: http://xpra.org/trac/ticket/595#comment:1 Antoine > > > Start of rant: > "Proprietary Tyrants" > http://www.gnu.org/philosophy/proprietary-tyrants.html > " A/tyrant/device is one that refuses to allow users to install a > different operating system or a modified operating system. These devices > have measures to block execution of anything other than the ?approved? > system versions. We also refer to this practice as/tivoization/." > > "Proprietary Sabotage" > http://www.gnu.org/philosophy/proprietary-sabotage.html > > "Every nonfree program has a lord, a master--and if you use the program, > he is your master." - RMS > End of rant. > > Cheers > Antoine From dougdoole at gmail.com Mon Jun 16 15:05:28 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Mon, 16 Jun 2014 10:05:28 -0400 Subject: [winswitch] xpra 0.13.5 misbehaving Message-ID: I upgraded to xpra 0.13.5 this morning, and I'm having some very strange behaviour with click and drag. I'll click and drag on the title bar to move a window and sometime it will move, but other times I'll get behaviour such as the window collapsing to just the title bar, or being pushed behind an overlapping window. Similar problems when I click and drag on the edge of a window to resize it. Sometime it resizes and other times the window gets pushed behind an overlapping window. The behaviour seems to be random (at least I haven't found anything that specifically causes the strange behaviour). The bad behaviour seems more likely to occur when the xpra managed window is overlapping another window. The second window can be local or from xpra. I don't see anything useful in the client or server logs. I did not see this problem on xpra 0.13.4. Both my client and server are running Ubuntu 12.04. My desktop is KDE. Anything I can gather to help narrow this down? (I'm going to have to roll back to 0.13.4. soon, because this is making 0.13.5 pretty much unusable.) -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Mon Jun 16 15:18:26 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 16 Jun 2014 21:18:26 +0700 Subject: [winswitch] xpra 0.13.5 misbehaving In-Reply-To: References: Message-ID: <539EFCB2.6040500@nagafix.co.uk> On 16/06/14 21:05, Douglas Doole wrote: > I upgraded to xpra 0.13.5 this morning, and I'm having some very strange > behaviour with click and drag. I'll click and drag on the title bar to move > a window and sometime it will move, but other times I'll get behaviour such > as the window collapsing to just the title bar, or being pushed behind an > overlapping window. This sound like a client side window manager issue, and not an xpra issue. > Similar problems when I click and drag on the edge of a window to resize > it. Sometime it resizes and other times the window gets pushed behind an > overlapping window. As above. > The behaviour seems to be random (at least I haven't found anything that > specifically causes the strange behaviour). The bad behaviour seems more > likely to occur when the xpra managed window is overlapping another window. > The second window can be local or from xpra. > > I don't see anything useful in the client or server logs. > > I did not see this problem on xpra 0.13.4. Looking at the changelog from 0.13.4 to 0.13.5, there is nothing at all in there that should be able to cause the problems you report. So I suspect that the problem comes from somewhere else and that downgrading back down may not help, did you do any other updates today? > Both my client and server are running Ubuntu 12.04. My desktop is KDE. > > Anything I can gather to help narrow this down? (I'm going to have to roll > back to 0.13.4. soon, because this is making 0.13.5 pretty much unusable.) Maybe running the client with "-d window" will tell us something useful. Cheers Antoine From dougdoole at gmail.com Mon Jun 16 15:57:27 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Mon, 16 Jun 2014 10:57:27 -0400 Subject: [winswitch] xpra 0.13.5 misbehaving In-Reply-To: <539EFCB2.6040500@nagafix.co.uk> References: <539EFCB2.6040500@nagafix.co.uk> Message-ID: You're right Antoine, this is caused by something else. (The vast majority of the windows that I move and resize are managed by xpra, so that's the only place I had seen the problem.) Time to go hunting elsewhere. Sorry for the false alarm. On Mon, Jun 16, 2014 at 10:18 AM, Antoine Martin wrote: > On 16/06/14 21:05, Douglas Doole wrote: > > I upgraded to xpra 0.13.5 this morning, and I'm having some very strange > > behaviour with click and drag. I'll click and drag on the title bar to > move > > a window and sometime it will move, but other times I'll get behaviour > such > > as the window collapsing to just the title bar, or being pushed behind an > > overlapping window. > This sound like a client side window manager issue, and not an xpra issue. > > Similar problems when I click and drag on the edge of a window to resize > > it. Sometime it resizes and other times the window gets pushed behind an > > overlapping window. > As above. > > The behaviour seems to be random (at least I haven't found anything that > > specifically causes the strange behaviour). The bad behaviour seems more > > likely to occur when the xpra managed window is overlapping another > window. > > The second window can be local or from xpra. > > > > I don't see anything useful in the client or server logs. > > > > I did not see this problem on xpra 0.13.4. > Looking at the changelog from 0.13.4 to 0.13.5, there is nothing at all > in there that should be able to cause the problems you report. > So I suspect that the problem comes from somewhere else and that > downgrading back down may not help, did you do any other updates today? > > Both my client and server are running Ubuntu 12.04. My desktop is KDE. > > > > Anything I can gather to help narrow this down? (I'm going to have to > roll > > back to 0.13.4. soon, because this is making 0.13.5 pretty much > unusable.) > Maybe running the client with "-d window" will tell us something useful. > > Cheers > 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 antoine at nagafix.co.uk Tue Jun 17 17:11:11 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 17 Jun 2014 23:11:11 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.13.6 (minor platform fixes) Message-ID: <53A0689F.1080002@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes some minor platform specific problems, there is no urgency to upgrade: * fix compatibility older versions of pygtk (centos5) * fix compatibility with python 2.4 (centos5) * fix AltGr workaround with win32 clients * fix some missing keys with 'fr' keyboard layout (win32) * fix installation on systems without python-glib (centos5) * fix Xorg version detection for Fedora rawhide The MS Windows builds also have an updated ffmpeg build. The OSX build is still pending.. sorry about that. The RPM repositories also have an updated "netifaces" package. 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/ iEYEARECAAYFAlOgaJQACgkQGK2zHPGK1ruwTwCeIjFynLH6iC58pCwb3wVKqg4V X1cAn21Dt8t0FjzBKnWfAObeS9bPRfYL =Skn4 -----END PGP SIGNATURE----- From dougdoole at gmail.com Fri Jun 20 15:53:35 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Fri, 20 Jun 2014 10:53:35 -0400 Subject: [winswitch] Feature request - move all windows Message-ID: I've got a feature request for you, and was wondering if it's practical. I use my laptop in one of two configurations: At home, I have just my laptop. I keep my browser, mail program, etc. and virtual desktop #1 and I put all my xpra windows on virtual desktop #2. At work, I have an external monitor and my desktop spans the laptop display and the monitor. With the extra screen space, I keep everything on virtual desktop #1. My local program are all on my laptop display and my xpra windows are on the external monitor. When I change environments (at least once a day), I'll move each xpra window between virtual desktops and then reposition them on the screen. Would it be possible (and practical) to add an option (probably off the tray icon) that would move all the xpra windows to a different virtual desktop? As a bonus, could the same be done for moving xpra windows between monitors? Thanks. -- -- Doug Doole aibohphobia - The irrational fear of palindromes