From direkt1 at wolframhumann.de Thu Aug 1 15:36:45 2019 From: direkt1 at wolframhumann.de (Wolfram Humann) Date: Thu, 1 Aug 2019 16:36:45 +0200 Subject: [winswitch] Downgrading xpra In-Reply-To: <9bd89603-ea33-b764-2b34-acf3b1221b8e@nagafix.co.uk> References: <9bd89603-ea33-b764-2b34-acf3b1221b8e@nagafix.co.uk> Message-ID: Thanks for your reply. Some observations: 1. I managed to install 1.0.13 doing "sudo yum --releasever=7.1 install xpra" (had to manually install python-crypto before it would work but that's all) I had tried something similar before editing winswitch.repo and replacing "baseurl=http://winswitch.org/dists/CentOS/$releasever/$basearch/" with "baseurl=http://winswitch.org/dists/CentOS/7.1/$basearch/" but to my surprise yum still wanted to install version 2.5.3 (and failed as mentioned before when I tried to force yum to install 1.0.13) 2. I have a Konsole window receiving lots of output from a program and therefore scrolling fast. In 1.0.13 there is no problem with that. In 2.5.3 it always hangs a bit between screen updates. Also in 2.5.3 I sometimes receive messages about my connection being slow with some options what to do about it. I've never seen those in 1.0.13 3. In 2.5.3 when I have menus hitting the bottom of the screen, I will have a vertical offset between the mouse-pointer and the selected entry (see attached screenshots -- the mouse pointer is 6-7 entries higher than the selection). That does not happen in 1.0.13. It might be worth mentioning that I have an (unusual?) setup of one horizontal (main) monitor and one vertical on the left, so there are screen coordinates on the left monitor extending below and above the main screen. If you have any suggestions, I can go back to 2.5.3. and try them out. But I will be on vacation for one week starting tomorrow, so I would do that afterwards. Thanks for maintaining and supporting this nice and very useful piece of software! Wolfram From antoine at nagafix.co.uk Fri Aug 2 12:50:51 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 2 Aug 2019 18:50:51 +0700 Subject: [winswitch] Downgrading xpra In-Reply-To: References: <9bd89603-ea33-b764-2b34-acf3b1221b8e@nagafix.co.uk> Message-ID: On 01/08/2019 21:36, Wolfram Humann via shifter-users wrote: > Thanks for your reply. Some observations: > 1. I managed to install 1.0.13 doing "sudo yum --releasever=7.1 install > xpra" (had to manually install python-crypto before it would work but > that's all) That's generally a bad idea. It might have worked this time but the repository for 7.1 and 7.6 are different for a reason and you should not mix them up. For example, you could easily get ABI breakage issues with the dummy driver. > I had tried something similar before editing winswitch.repo and replacing > "baseurl=http://winswitch.org/dists/CentOS/$releasever/$basearch/" with > "baseurl=http://winswitch.org/dists/CentOS/7.1/$basearch/" but to my > surprise yum still wanted to install version 2.5.3 (and failed as mentioned > before when I tried to force yum to install 1.0.13) > > 2. I have a Konsole window receiving lots of output from a program and > therefore scrolling fast. In 1.0.13 there is no problem with that. In 2.5.3 > it always hangs a bit between screen updates. That should not happen. In fact, a number of improvements since v2.0 were specifically designed for dealing with fast scrolling windows. Is your client also up to date? Is it also a CentOS 7.x system? Did you make any changes to your configuration? Can you reproduce the problem without your program? (ie: just typing "dmesg" repeatedly in a terminal window?) What sort of connection speed would I need to use to reproduce the problem? > Also in 2.5.3 I sometimes > receive messages about my connection being slow with some options what to > do about it. I've never seen those in 1.0.13 These notifications don't exist in 1.0. The older code is rather dumb: it would just saturate your link and / or slow down too much. > 3. In 2.5.3 when I have menus hitting the bottom of the screen, I will have > a vertical offset between the mouse-pointer and the selected entry (see > attached screenshots -- the mouse pointer is 6-7 entries higher than the > selection). FYI: the mailing-list scrubs attachments. > That does not happen in 1.0.13. It might be worth mentioning > that I have an (unusual?) setup of one horizontal (main) monitor and one > vertical on the left, so there are screen coordinates on the left monitor > extending below and above the main screen. Sounds similar to: https://xpra.org/trac/ticket/1339 > If you have any suggestions, I can go back to 2.5.3. and try them out. But > I will be on vacation for one week starting tomorrow, so I would do that > afterwards. Can you either add to that ticket if it looks similar or create a new one? > Thanks for maintaining and supporting this nice and very useful piece of > software! Thanks, Antoine > Wolfram > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From daniel.kane at Clarivate.com Mon Aug 5 17:17:28 2019 From: daniel.kane at Clarivate.com (Kane, Daniel) Date: Mon, 5 Aug 2019 16:17:28 +0000 Subject: [winswitch] XPRA via SSH proxy problem Message-ID: Hello all, I have tested the following from both OSX 10.14.4 and Fedora 30 both using xpra v2.5.3-r23271 , with identical results : xpra start ssh:user at proxied_host --start=xterm where my .ssh/config has a ProxyCommand entry for proxied_host (this works fine, I can ssh directly to user at proxied_host) ?yet the final error I see in the output is: 2019-08-05 12:14:31,395 xpra initialization error: _proxy_start: expected 1 argument but got 0: [] 2019-08-05 12:14:31,408 Connection lost Is there any more information I could provide to help figure this out? All the best, Dan From antoine at nagafix.co.uk Mon Aug 5 17:47:23 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 5 Aug 2019 23:47:23 +0700 Subject: [winswitch] XPRA via SSH proxy problem In-Reply-To: References: Message-ID: <699a9afe-a819-aa91-6024-7489900cbde3@nagafix.co.uk> On 05/08/2019 23:17, Kane, Daniel via shifter-users wrote: > Hello all, > > > I have tested the following from both OSX 10.14.4 and Fedora 30 both using xpra v2.5.3-r23271 , with identical results : > > > xpra start ssh:user at proxied_host --start=xterm > > where my .ssh/config has a ProxyCommand entry for proxied_host (this works fine, I can ssh directly to user at proxied_host) > > ?yet the final error I see in the output is: > > 2019-08-05 12:14:31,395 xpra initialization error: _proxy_start: expected 1 argument but got 0: [] > 2019-08-05 12:14:31,408 Connection lost This looks like a bug. > Is there any more information I could provide to help figure this out? Can you provide a minimal test case? I've just tried it with this entry in my .ssh/config: Host test ProxyCommand ssh -v localhost nc 127.0.0.1 22 And this command worked fine: xpra start ssh://test/ --start=xterm -d ssh The "-d ssh" should give you more details about what is going on. It may be that your configuration is incompatible with the paramiko backend, in which case you should be able to revert to openssh with xpra --ssh="ssh -x" But I would prefer figuring out what the problem is and fixing it. Cheers, Antoine > > > All the best, > > Dan > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Mon Aug 5 17:50:38 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 5 Aug 2019 23:50:38 +0700 Subject: [winswitch] Downgrading xpra In-Reply-To: References: <9bd89603-ea33-b764-2b34-acf3b1221b8e@nagafix.co.uk> Message-ID: >> 3. In 2.5.3 when I have menus hitting the bottom of the screen, I will have >> a vertical offset between the mouse-pointer and the selected entry (see >> attached screenshots -- the mouse pointer is 6-7 entries higher than the >> selection). > FYI: the mailing-list scrubs attachments. > >> That does not happen in 1.0.13. It might be worth mentioning >> that I have an (unusual?) setup of one horizontal (main) monitor and one >> vertical on the left, so there are screen coordinates on the left monitor >> extending below and above the main screen. > Sounds similar to: > https://xpra.org/trac/ticket/1339 I have managed to reproduce the bug using your "unusual" monitor layout, I should have fix ready before the next release, the details are here: https://xpra.org/trac/ticket/1339#comment:34 Cheers, Antoine From perry at piermont.com Sat Aug 10 21:55:04 2019 From: perry at piermont.com (Perry E. Metzger) Date: Sat, 10 Aug 2019 16:55:04 -0400 Subject: [winswitch] Several small questions... Message-ID: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> Howdy! Several small questions about Xpra... 1) I note the latest Xpra is 2.5.3, but when I download a recent copy for the mac, it claims to be v2.3.3-r20112. I find this a bit confusing? 2) I note that even if I set speaker and microphone to disabled on my linux server, pulse audio seems to start up when I start up an X server. Is this normal? 3) I'm running (as you might guess) on a Linux server with a mac client. The mac has a retina display. I'd like to take advantage of that to have nicer looking fonts and such while working remotely, but if I set DPI to 144 (as opposed to 72, which I was experimenting with before), it just makes everything twice as big. Is there a way to tell Xpra that I want to see higher pixels per inch on the client? Perry -- Perry E. Metzger perry at piermont.com From antoine at nagafix.co.uk Sun Aug 11 06:14:42 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 11 Aug 2019 12:14:42 +0700 Subject: [winswitch] Several small questions... In-Reply-To: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> References: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> Message-ID: On 11/08/2019 03:55, Perry E. Metzger via shifter-users wrote: > Howdy! Several small questions about Xpra... > > 1) I note the latest Xpra is 2.5.3, but when I download a recent copy > for the mac, it claims to be v2.3.3-r20112. I find this a bit > confusing? I don't know which download link you are using but I have just verified and all the canonical names from the download page point to the correct version, which at this time is 2.5.3: https://xpra.org/trac/wiki/Download Maybe you have multiple DMG or PKG files with slightly different names? Also, MacOS is known to do some really weird things when you have multiple copies of the same application on the same filesystem. You can see the download link for individual versions by browsing here: http://xpra.org/dists/MacOS/x86_64/ > 2) I note that even if I set speaker and microphone to disabled on my > linux server, pulse audio seems to start up when I start up an X > server. Is this normal? Yes, if you don't want that then use "--pulseaudio=no" instead. > 3) I'm running (as you might guess) on a Linux server with a mac > client. The mac has a retina display. I'd like to take advantage of > that to have nicer looking fonts and such while working remotely, but > if I set DPI to 144 (as opposed to 72, which I was experimenting with > before), it just makes everything twice as big. Is there a way to > tell Xpra that I want to see higher pixels per inch on the client? That's a known issue: https://xpra.org/trac/ticket/1933 The changes are not trivial, but I may be able to get something done for v4.0. Feel free to subscribe to that ticket. Cheers, Antoine From perry at piermont.com Sun Aug 11 15:21:25 2019 From: perry at piermont.com (Perry E. Metzger) Date: Sun, 11 Aug 2019 10:21:25 -0400 Subject: [winswitch] Several small questions... In-Reply-To: References: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> Message-ID: <20190811102125.2b13c662@jabberwock.cb.piermont.com> On Sun, 11 Aug 2019 12:14:42 +0700 Antoine Martin via shifter-users wrote: > On 11/08/2019 03:55, Perry E. Metzger via shifter-users wrote: > > Howdy! Several small questions about Xpra... > > > > 1) I note the latest Xpra is 2.5.3, but when I download a recent > > copy for the mac, it claims to be v2.3.3-r20112. I find this a bit > > confusing? > I don't know which download link you are using but I have just > verified and all the canonical names from the download page point > to the correct version, which at this time is 2.5.3: > https://xpra.org/trac/wiki/Download > Maybe you have multiple DMG or PKG files with slightly different > names? Also, MacOS is known to do some really weird things when you > have multiple copies of the same application on the same filesystem. > You can see the download link for individual versions by browsing > here: http://xpra.org/dists/MacOS/x86_64/ Is it possible that installing a new version of the .pkg file fails if the /Application is already installed? I downloaded the .pkg, installed it, got the same result. I downloaded the .dmg, copied it over, and all is fine. I may try some experiments with this later. > > 2) I note that even if I set speaker and microphone to disabled > > on my linux server, pulse audio seems to start up when I start up > > an X server. Is this normal? > Yes, if you don't want that then use "--pulseaudio=no" instead. Thanks! I didn't realize that option existed. > > 3) I'm running (as you might guess) on a Linux server with a mac > > client. The mac has a retina display. I'd like to take advantage > > of that to have nicer looking fonts and such while working > > remotely, but if I set DPI to 144 (as opposed to 72, which I was > > experimenting with before), it just makes everything twice as > > big. Is there a way to tell Xpra that I want to see higher pixels > > per inch on the client? > That's a known issue: > https://xpra.org/trac/ticket/1933 > The changes are not trivial, but I may be able to get something > done for v4.0. Feel free to subscribe to that ticket. Will do! And thank you so much for maintaining xpra! It takes a bit of work to get going with it, but it's super-useful once things are up and running. BTW, I noticed the documentation doesn't mention that if you use the --sharing option that it will create a socket in /run/xpra if and only if you are a member of group xpra on the server. It might be useful to put that into the manual somewhere? Perry -- Perry E. Metzger perry at piermont.com From perry at piermont.com Sun Aug 11 15:53:09 2019 From: perry at piermont.com (Perry E. Metzger) Date: Sun, 11 Aug 2019 10:53:09 -0400 Subject: [winswitch] A couple of more small questions... Message-ID: <20190811105309.09970807@jabberwock.cb.piermont.com> 1) I'm seeing the following at the start of my server log on Ubuntu 19.04 ("disco"). Any idea what is causing it? Is there perhaps a dependency missing on the package? Does it matter? 2019-08-11 10:26:17,783 cannot access python uinput module: 2019-08-11 10:26:17,783 No module named uinput 2) I'm an old-fashioned person and like to run xterm; to have it work well, I need to run xrdb to read in an Xdefaults file before running xterm. I've noticed that I can't really reliably do this with multiple --start commands because the xrdb might or might not finish before xterm starts. Any thoughts on a better method? 3) Since upgrading to 2.5.3 a little while ago, the client prompts me for my ssh passphrase every time, ignoring my ssh-agent. Any idea why this might be? It was not happening under the old version. Perry -- Perry E. Metzger perry at piermont.com From antoine at nagafix.co.uk Sun Aug 11 19:49:11 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 12 Aug 2019 01:49:11 +0700 Subject: [winswitch] Several small questions... In-Reply-To: <20190811102125.2b13c662@jabberwock.cb.piermont.com> References: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> <20190811102125.2b13c662@jabberwock.cb.piermont.com> Message-ID: <6815dca4-1939-0a52-924c-e15a5bea2bab@nagafix.co.uk> On 11/08/2019 21:21, Perry E. Metzger wrote: > On Sun, 11 Aug 2019 12:14:42 +0700 Antoine Martin via shifter-users > wrote: >> On 11/08/2019 03:55, Perry E. Metzger via shifter-users wrote: >>> Howdy! Several small questions about Xpra... >>> >>> 1) I note the latest Xpra is 2.5.3, but when I download a recent >>> copy for the mac, it claims to be v2.3.3-r20112. I find this a bit >>> confusing? >> I don't know which download link you are using but I have just >> verified and all the canonical names from the download page point >> to the correct version, which at this time is 2.5.3: >> https://xpra.org/trac/wiki/Download >> Maybe you have multiple DMG or PKG files with slightly different >> names? Also, MacOS is known to do some really weird things when you >> have multiple copies of the same application on the same filesystem. >> You can see the download link for individual versions by browsing >> here: http://xpra.org/dists/MacOS/x86_64/ > > Is it possible that installing a new version of the .pkg file fails > if the /Application is already installed? I downloaded the .pkg, > installed it, got the same result. I downloaded the .dmg, copied it > over, and all is fine. I may try some experiments with this later. That's what I meant by "really weird things". A few years back, it was reported that even having the application installed in a private directory still triggered some odd behaviour. >>> 2) I note that even if I set speaker and microphone to disabled >>> on my linux server, pulse audio seems to start up when I start up >>> an X server. Is this normal? >> Yes, if you don't want that then use "--pulseaudio=no" instead. > > Thanks! I didn't realize that option existed. > >>> 3) I'm running (as you might guess) on a Linux server with a mac >>> client. The mac has a retina display. I'd like to take advantage >>> of that to have nicer looking fonts and such while working >>> remotely, but if I set DPI to 144 (as opposed to 72, which I was >>> experimenting with before), it just makes everything twice as >>> big. Is there a way to tell Xpra that I want to see higher pixels >>> per inch on the client? >> That's a known issue: >> https://xpra.org/trac/ticket/1933 >> The changes are not trivial, but I may be able to get something >> done for v4.0. Feel free to subscribe to that ticket. > > Will do! And thank you so much for maintaining xpra! It takes a bit > of work to get going with it, but it's super-useful once things are > up and running. How can we make it easier to get going with it? > BTW, I noticed the documentation doesn't mention that if you use the > --sharing option that it will create a socket in /run/xpra if and > only if you are a member of group xpra on the server. It might be > useful to put that into the manual somewhere? Does this help: http://xpra.org/trac/changeset/23487/xpra Cheers, Antoine > > Perry > From antoine at nagafix.co.uk Sun Aug 11 19:52:26 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 12 Aug 2019 01:52:26 +0700 Subject: [winswitch] A couple of more small questions... In-Reply-To: <20190811105309.09970807@jabberwock.cb.piermont.com> References: <20190811105309.09970807@jabberwock.cb.piermont.com> Message-ID: <2814e296-0f83-6ac1-b8a1-2f099376ec79@nagafix.co.uk> On 11/08/2019 21:53, Perry E. Metzger via shifter-users wrote: > 1) I'm seeing the following at the start of my server log on Ubuntu > 19.04 ("disco"). Any idea what is causing it? Is there perhaps a > dependency missing on the package? Does it matter? > > 2019-08-11 10:26:17,783 cannot access python uinput module: > 2019-08-11 10:26:17,783 No module named uinput I have added this to the FAQ: https://xpra.org/trac/wiki/FAQ TLDR: you don't have python-uinput installed, but it is not required and even if you did have it installed, it normally requires special permissions to use. For more details, see: https://xpra.org/trac/ticket/1611 > 2) I'm an old-fashioned person and like to run xterm; to have it work > well, I need to run xrdb to read in an Xdefaults file before running > xterm. I've noticed that I can't really reliably do this with multiple > --start commands because the xrdb might or might not finish before > xterm starts. Any thoughts on a better method? Something like this is ugly but should do the job: xpra --start="sh -c 'xrdb -load Xdefaults;xterm'" Or you could place it in a wrapper script. This is not exactly elegant, but there is no start command synchronization in xpra, so that's the best you can do. > 3) Since upgrading to 2.5.3 a little while ago, the client prompts me > for my ssh passphrase every time, ignoring my ssh-agent. Any idea why > this might be? It was not happening under the old version. That's because v2.5 switched to paramiko as the default ssh backend: https://xpra.org/trac/ticket/1646 paramiko is meant to handle ssh agents, it does work fine on Linux, but maybe there is a bug or missing feature on MacOS. You should be able to see detailed ssh diagnostics by running the client with: xpra attach -d ssh ... Alternatively, you can switch back to the openssh backend with: xpra attach --ssh="ssh" Cheers, Antoine > > Perry > From perry at piermont.com Mon Aug 12 18:11:53 2019 From: perry at piermont.com (Perry E. Metzger) Date: Mon, 12 Aug 2019 13:11:53 -0400 Subject: [winswitch] Several small questions... In-Reply-To: <6815dca4-1939-0a52-924c-e15a5bea2bab@nagafix.co.uk> References: <20190810165504.6b8c295e@jabberwock.cb.piermont.com> <20190811102125.2b13c662@jabberwock.cb.piermont.com> <6815dca4-1939-0a52-924c-e15a5bea2bab@nagafix.co.uk> Message-ID: <20190812131153.61e7d84a@jabberwock.cb.piermont.com> On Mon, 12 Aug 2019 01:49:11 +0700 Antoine Martin wrote: > >> That's a known issue: > >> https://xpra.org/trac/ticket/1933 > >> The changes are not trivial, but I may be able to get something > >> done for v4.0. Feel free to subscribe to that ticket. BTW, I had trouble creating a trac account. The captcha was too hard for me as a human. :( > > Will do! And thank you so much for maintaining xpra! It takes a > > bit of work to get going with it, but it's super-useful once > > things are up and running. > > How can we make it easier to get going with it? I'd say the biggest improvements would be better documentation. So far, almost everything I've wanted to do has been pretty easy once I figured it out, but sometimes it's taken asking. > > BTW, I noticed the documentation doesn't mention that if you use > > the --sharing option that it will create a socket in /run/xpra if > > and only if you are a member of group xpra on the server. It > > might be useful to put that into the manual somewhere? > Does this help: > http://xpra.org/trac/changeset/23487/xpra That's excellent. Perry -- Perry E. Metzger perry at piermont.com From direkt1 at wolframhumann.de Wed Aug 14 15:13:08 2019 From: direkt1 at wolframhumann.de (Wolfram Humann) Date: Wed, 14 Aug 2019 16:13:08 +0200 Subject: [winswitch] Downgrading xpra In-Reply-To: References: <9bd89603-ea33-b764-2b34-acf3b1221b8e@nagafix.co.uk> Message-ID: Thanks for the fix. I will wait for the next release and then re-upgrade and have a closer look at the scroll-issue. To answer some of your questions already: The client is Windows 10. I had server and client both at 2.5.3. Transfer speed between the Windows and the Linux machines is about 30 Mbytes/s when I copy a single large file; ping times are around 0.3 ms. Regards Wolfram From suhail at mightyapp.com Thu Aug 22 16:37:22 2019 From: suhail at mightyapp.com (Suhail Doshi) Date: Thu, 22 Aug 2019 15:37:22 +0000 Subject: [winswitch] Xpra / C++ bindings Message-ID: Hi there, Are there C/C++ bindings or is there sample C/C++ code to use Xpra? If not, what might my options be? My goal is to capture a window composite, encode it, and send the encoded data over the network--I'd like to do frame/window capture and encoding without touching system memory. It needs to happen all on the GPU and noticed Xpra seems like it could do that with NVENC. Thank you! Suhail From antoine at nagafix.co.uk Thu Aug 22 16:55:13 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 22 Aug 2019 22:55:13 +0700 Subject: [winswitch] Xpra / C++ bindings In-Reply-To: References: Message-ID: <073cc109-2c37-9c89-bec9-c630dbf9f2df@nagafix.co.uk> On 22/08/2019 22:37, Suhail Doshi via shifter-users wrote: > Hi there, > > Are there C/C++ bindings or is there sample C/C++ code to use Xpra? No. Some of Xpra's code is already in C though. > If not, what might my options be? Do you really need to use C/C++? > My goal is to capture a window composite, encode it, and send the encoded data over the network--I'd like to do frame/window capture and encoding without touching system memory. The X11 composite extension captures the pixels from X11 windows in system memory, so you will need to upload it to the GPU to use NVENC. Xpra does that for seamless servers. ("xpra start") > It needs to happen all on the GPU and noticed Xpra seems like it could do that with NVENC. Xpra does zero-copy of screen pixels directly to NVENC with the shadow server ("xpra shadow") when NVFBC is used. In that case, the pixels of an existing X11 server are captured on the GPU and then transferred to NVENC without using any system memory. The downside is that this captures the whole X11 display and not individual windows. Cheers, Antoine > > Thank you! > > Suhail