From timo.lindfors at iki.fi Wed Oct 2 07:53:39 2013 From: timo.lindfors at iki.fi (Timo Juhani Lindfors) Date: Wed, 02 Oct 2013 09:53:39 +0300 Subject: [winswitch] secure clipboard syncing? Message-ID: <84r4c4jh8s.fsf@sauna.l.org> Hi, I recently became aware that if I keep xpra connections open to potentially malicious servers they can see everything that I copy to my clipboard. This is natural and often probably not a huge problem. However, would it be possible to have something like "--no-clipboard" that I could toggle at runtime so that I could enable clipboard syncing for one server just for the duration when I need to actively copy&paste stuff between that server and my local system? -Timo From antoine at nagafix.co.uk Wed Oct 2 11:41:53 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 02 Oct 2013 17:41:53 +0700 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <84r4c4jh8s.fsf@sauna.l.org> References: <84r4c4jh8s.fsf@sauna.l.org> Message-ID: <524BF871.1010804@nagafix.co.uk> On 02/10/13 13:53, Timo Juhani Lindfors wrote: > Hi, > > I recently became aware that if I keep xpra connections open to > potentially malicious servers they can see everything that I copy to my > clipboard. This is natural and often probably not a huge problem. > > However, would it be possible to have something like "--no-clipboard" > that I could toggle at runtime so that I could enable clipboard syncing > for one server just for the duration when I need to actively copy&paste > stuff between that server and my local system? That's exactly what the "Clipboard" toggle in your xpra system tray does. Antoine From thomas at koch.ro Fri Oct 4 10:25:14 2013 From: thomas at koch.ro (Thomas Koch) Date: Fri, 4 Oct 2013 11:25:14 +0200 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <524BF871.1010804@nagafix.co.uk> References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> Message-ID: <201310041125.14982.thomas@koch.ro> On Wednesday, October 02, 2013 12:41:53 PM Antoine Martin wrote: > On 02/10/13 13:53, Timo Juhani Lindfors wrote: > > Hi, > > > > I recently became aware that if I keep xpra connections open to > > potentially malicious servers they can see everything that I copy to my > > clipboard. This is natural and often probably not a huge problem. > > > > However, would it be possible to have something like "--no-clipboard" > > that I could toggle at runtime so that I could enable clipboard syncing > > for one server just for the duration when I need to actively copy&paste > > stuff between that server and my local system? > > That's exactly what the "Clipboard" toggle in your xpra system tray does. It might be a useful security enhancement to have a third option for the clipboard syncinc besides on and off: Sync only on request. This third option could be used for untrusted systems. I could define a keybinding that would sync my current clipboard content from the local system to the remote system. The other sync direction from remote to local could still remain enabled. The only danger I can imagine is that the guest system could put compromising commands in my clipboard in exactly the right moment before I paste from my clipboard into my local (root) shell. But how should an attacker now the right moment? Regards, Thomas Koch From antoine at nagafix.co.uk Sun Oct 6 06:20:16 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 06 Oct 2013 12:20:16 +0700 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <201310041125.14982.thomas@koch.ro> References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <201310041125.14982.thomas@koch.ro> Message-ID: <5250F310.6090508@nagafix.co.uk> On 04/10/13 16:25, Thomas Koch wrote: > On Wednesday, October 02, 2013 12:41:53 PM Antoine Martin wrote: >> On 02/10/13 13:53, Timo Juhani Lindfors wrote: >>> Hi, >>> >>> I recently became aware that if I keep xpra connections open to >>> potentially malicious servers they can see everything that I copy to my >>> clipboard. This is natural and often probably not a huge problem. >>> >>> However, would it be possible to have something like "--no-clipboard" >>> that I could toggle at runtime so that I could enable clipboard syncing >>> for one server just for the duration when I need to actively copy&paste >>> stuff between that server and my local system? >> That's exactly what the "Clipboard" toggle in your xpra system tray does. > It might be a useful security enhancement to have a third option for the > clipboard syncinc besides on and off: Sync only on request. You seem to misunderstand how the X11 clipboard works: what is synchronized is not the clipboard contents themselves, but the ownership of the clipboard selection. In other terms: which application will provide the clipboard data when requested by another application. In our terms: which end (client or server) owns a particular clipboard selection. For more information, there are lots of pointers on the wiki: http://xpra.org/trac/wiki/Clipboard > This third option could be used for untrusted systems. I could define a > keybinding that would sync my current clipboard content from the local system > to the remote system. > > The other sync direction from remote to local could still remain enabled. The > only danger I can imagine is that the guest system could put compromising > commands in my clipboard in exactly the right moment before I paste from my > clipboard into my local (root) shell. But how should an attacker now the right > moment? There is already a ticket for limiting the clipboard direction: http://xpra.org/trac/ticket/276 It would not be very difficult to implement, but it isn't high on the priority list either. These sorts of options are usually added to the tray menu and adding a key shortcut would be just a matter of adding an option to the "--key-shortcut=XXX" command line option. Please also note that the paranoid can already use clipboard contents filters: http://xpra.org/trac/ticket/274 I am in no way claiming that it is possible to provide a comprehensive list of regular expressions that would filter out all dangerous clipboard data - just mentioning that the option exists. Antoine > > Regards, Thomas Koch From timo.lindfors at iki.fi Sun Oct 6 09:05:55 2013 From: timo.lindfors at iki.fi (Timo Juhani Lindfors) Date: Sun, 06 Oct 2013 11:05:55 +0300 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <5250F310.6090508@nagafix.co.uk> (Antoine Martin's message of "Sun, 06 Oct 2013 12:20:16 +0700") References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <201310041125.14982.thomas@koch.ro> <5250F310.6090508@nagafix.co.uk> Message-ID: <84zjqmygbg.fsf@sauna.l.org> Antoine Martin writes: > You seem to misunderstand how the X11 clipboard works: what is > synchronized is not the clipboard contents themselves, but the ownership > of the clipboard selection. Do you mean "primary selection" here? I use #!/bin/bash function show_container { name="$1" cmd="$2" escaped_data="`$cmd | cat -A | tr -d '\n' | cut --bytes=1-70`" echo "$name: \"$escaped_data\"" } for i in primary secondary clipboard; do show_container $i "xclip -o -selection $i" done; for i in `seq 0 7`; do show_container cut$i "xcb -p $i" done to debug things: $ xcutselprint primary: "" secondary: "" clipboard: "http://xpra.org/trac/wiki/Clipboard" cut0: ":~$ $" cut1: "" cut2: "" cut3: "" cut4: "" cut5: "" cut6: "" cut7: "" Running this in a loop on the malicious server led me to discover that sometimes they can see data that I did not intend to send over network. From antoine at nagafix.co.uk Sun Oct 6 09:48:27 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 06 Oct 2013 15:48:27 +0700 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <84zjqmygbg.fsf@sauna.l.org> References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <201310041125.14982.thomas@koch.ro> <5250F310.6090508@nagafix.co.uk> <84zjqmygbg.fsf@sauna.l.org> Message-ID: <525123DB.2030308@nagafix.co.uk> On 06/10/13 15:05, Timo Juhani Lindfors wrote: > Antoine Martin writes: >> You seem to misunderstand how the X11 clipboard works: what is >> synchronized is not the clipboard contents themselves, but the ownership >> of the clipboard selection. > Do you mean "primary selection" here? I use No. There are 3 types of selections, and this applies to all 3. Sorry I should have been clearer. The OP's question was about: > It might be a useful security enhancement to have a third option for the > clipboard syncinc besides on and off: Sync only on request. And maybe I misunderstand what this "sync only on request" would do. Of course when using an application (like the xclip example you posted), the application can request the actual contents of the clipboard whenever it feels like it. The point I was trying to make is that by then it is a little too late: returning empty data at that point would be anti-social and would unnecessarily cripple the clipboard behaviour at both ends. Antoine From antoine at nagafix.co.uk Sun Oct 6 09:58:29 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 06 Oct 2013 15:58:29 +0700 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <525123DB.2030308@nagafix.co.uk> References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <201310041125.14982.thomas@koch.ro> <5250F310.6090508@nagafix.co.uk> <84zjqmygbg.fsf@sauna.l.org> <525123DB.2030308@nagafix.co.uk> Message-ID: <52512635.6060804@nagafix.co.uk> > The OP's question was about: > >> It might be a useful security enhancement to have a third option for the >> clipboard syncinc besides on and off: Sync only on request. Ooops, just realized that *you* are the OP, this part was from Thomas and I was responding to that. Antoine From swagatn at gmail.com Wed Oct 9 09:57:51 2013 From: swagatn at gmail.com (Swagat) Date: Wed, 9 Oct 2013 08:57:51 +0000 (UTC) Subject: [winswitch] does xpra raise windows? References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> Message-ID: Antoine Martin writes: > > On 15/09/13 23:07, Thomas Koch wrote: > > Is xpra supposed to support raising X clients? If this is not implemented yet, > > then it would be a very nice feature to have. > You're right, it wasn't implemented, it is now: > http://xpra.org/trac/changeset/4335/xpra > > Antoine > Do we have any build available with this change? I am using 0.10.4-2 (published on 10th Sep) and if I close a window instead of detaching from the commandline, I cannot raise that window again. Thanks, Swagat From antoine at nagafix.co.uk Wed Oct 9 11:31:41 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 09 Oct 2013 17:31:41 +0700 Subject: [winswitch] does xpra raise windows? In-Reply-To: References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> Message-ID: <5255308D.5080508@nagafix.co.uk> On 09/10/13 15:57, Swagat wrote: > Antoine Martin writes: > >> On 15/09/13 23:07, Thomas Koch wrote: >>> Is xpra supposed to support raising X clients? If this is not implemented > yet, >>> then it would be a very nice feature to have. >> You're right, it wasn't implemented, it is now: >> http://xpra.org/trac/changeset/4335/xpra >> >> Antoine >> > > Do we have any build available with this change? I am using 0.10.4-2 No, the change is in trunk and will be in 0.11.0, but not in the upcoming 0.10.5 release as only bug fixes go in stable releases. > (published on 10th Sep) and if I close a window instead of detaching from the > commandline, I cannot raise that window again. I don't understand what you've said. Sounds like a different issue and maybe a bug, hard to tell. Antoine > > Thanks, > Swagat > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From ilikeoj at gmail.com Wed Oct 9 22:41:11 2013 From: ilikeoj at gmail.com (Ivan) Date: Wed, 9 Oct 2013 14:41:11 -0700 Subject: [winswitch] xpra over ssh Message-ID: Hi, I am trying to use xpra on amazon ec2 micro with ubuntu 12. everything works except this: [local box] xpra attach ssh:amazonhost:11 It just hangs there and nothing happens. Any ideas? Thanks. From antoine at nagafix.co.uk Thu Oct 10 07:11:27 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 10 Oct 2013 13:11:27 +0700 Subject: [winswitch] xpra over ssh In-Reply-To: References: Message-ID: <5256450F.9040800@nagafix.co.uk> On 10/10/13 04:41, Ivan wrote: > Hi, I am trying to use xpra on amazon ec2 micro with ubuntu 12. > everything works except this: [local box] xpra attach ssh:amazonhost:11 > It just hangs there and nothing happens. Any ideas? Thanks. Hangs? Do you get the tray icon? Does the command exit? First check that your server is running correctly using (from the server): xpra list or xpra info If so, then try running the client in debug mode ("-d all") and see where it gets stuck. From swagatn at gmail.com Thu Oct 10 07:27:17 2013 From: swagatn at gmail.com (Swagat) Date: Thu, 10 Oct 2013 06:27:17 +0000 (UTC) Subject: [winswitch] does xpra raise windows? References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> Message-ID: Antoine Martin writes: > > On 09/10/13 15:57, Swagat wrote: > > Antoine Martin ...> writes: > > > >> On 15/09/13 23:07, Thomas Koch wrote: > >>> Is xpra supposed to support raising X clients? If this is not implemented > > yet, > >>> then it would be a very nice feature to have. > >> You're right, it wasn't implemented, it is now: > >> http://xpra.org/trac/changeset/4335/xpra > >> > >> Antoine > >> > > > > Do we have any build available with this change? I am using 0.10.4-2 > No, the change is in trunk and will be in 0.11.0, but not in the > upcoming 0.10.5 release as only bug fixes go in stable releases. > > > (published on 10th Sep) and if I close a window instead of detaching from the > > commandline, I cannot raise that window again. > I don't understand what you've said. > Sounds like a different issue and maybe a bug, hard to tell. > > Antoine > > > > > Thanks, > > Swagat > > > > > > _______________________________________________ > > shifter-users mailing list > > shifter-users at ... > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > Do we have any tentative timeline for 0.11.0 release? Adding a little more detail on the issue we are facing. Do let me know if you want me to start a new thread though. After starting a session via xpra on a linux host, I can attach to it from the Windows desktop without any issues. However, if I close the window (by clicking on the window close icon on top right), instead of running 'xpra detach' on the command line, the window minimizes and I cannot raise it again even after disconnecting/attaching to the display afresh. Thanks, Swagat From antoine at nagafix.co.uk Thu Oct 10 07:35:21 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 10 Oct 2013 13:35:21 +0700 Subject: [winswitch] does xpra raise windows? In-Reply-To: References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> Message-ID: <52564AA9.5020200@nagafix.co.uk> > Do we have any tentative timeline for 0.11.0 release? When it is ready ;) Hopefully this month. I will make beta packages before too long. > Adding a little more detail on the issue we are facing. Do let me know if > you want me to start a new thread though. This looks like a separate issue. So the fix from this thread is unlikely to make any difference. > After starting a session via xpra on a linux host, I can attach to it from > the Windows desktop without any issues. However, if I close the window (by > clicking on the window close icon on top right), instead of running 'xpra > detach' on the command line, the window minimizes What sort of application minimizes when you close it? > and I cannot raise it > again even after disconnecting/attaching to the display afresh. How does this application gets shown again normally? (without xpra involved) Does it not have a tray icon or something to interact with it? Windows that are actually minimized (and not destroyed) are shown again when you connect, and whilst you are still connected they would still be shown in your task manager (or via alt-tab style window switchers). If the client application discards its own window, there is nothing xpra can do to make it show again. The application should offer a way of doing that. Antoine From antoine at nagafix.co.uk Fri Oct 11 12:41:08 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 11 Oct 2013 18:41:08 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.10.5 (bug fixes) Message-ID: <5257E3D4.7030407@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This fixes a few minor bugs and restores shadow mode: * fix client time out when the initial connection fails * fix shadow mode * fix connection failures when some system information is missing * fix client disconnection requests * fix encryption cipher error messages * fix client errors when some features are disabled * fix potential rencode bug with unhandled data types * error out if the client requests authentication and none is available Those feeling more adventurous can try the new beta packages which contain new acceleration code (GPU acceleration using OpenCL and CUDA should be usable, NVENC h264 encoding is more experimental), a new proxy server mode (for channeling multiple instances through one port), lz4 compression, etc The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Beta: https://xpra.org/beta/ Cheers Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJX49AACgkQGK2zHPGK1rvDuACZAY8Qr/XvHzOTFdFxKex+99mY wgcAn0RM6WjTtWaAGILPy8i+6UfxzSU5 =DZfc -----END PGP SIGNATURE----- From swagatn at gmail.com Mon Oct 14 06:15:06 2013 From: swagatn at gmail.com (Swagat) Date: Mon, 14 Oct 2013 05:15:06 +0000 (UTC) Subject: [winswitch] does xpra raise windows? References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> <52564AA9.5020200@nagafix.co.uk> Message-ID: Thanks Antoine! I'll test around a bit more with my issue and start a new thread and add a short video to clarify the issue further (If I can't fix it). -Swagat From antoine at nagafix.co.uk Tue Oct 15 05:05:50 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 15 Oct 2013 11:05:50 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.10.6 (bug fixes) Message-ID: <525CBF1E.1090200@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes only 2 bugs, one of which was introduced in 0.10.5 and may have caused early client disconnections when forwarding system trays, sorry about that. * fix window titles reverting to "unknown host" * fix tray forwarding bug causing client disconnections * replace previous rencode fix with warning 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.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJcvx4ACgkQGK2zHPGK1rvcWACdGebiOh1W42pu9yNsLI0/3PQF 54UAn3eDGNPZlZk07tIrYC1xP9mngHxk =vw1s -----END PGP SIGNATURE----- From timo.lindfors at iki.fi Tue Oct 15 13:39:06 2013 From: timo.lindfors at iki.fi (Timo Juhani Lindfors) Date: Tue, 15 Oct 2013 15:39:06 +0300 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <524BF871.1010804@nagafix.co.uk> (Antoine Martin's message of "Wed, 02 Oct 2013 17:41:53 +0700") References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> Message-ID: <84txgig13p.fsf@sauna.l.org> Hi, Antoine Martin writes: > That's exactly what the "Clipboard" toggle in your xpra system tray does. If I use --no-clipboard on the client then the tray says that it can not enable clipboard since it is disabled by the server. If I don't use "--no-clipboard" then the remote server can see my clipboard until I have had time to go to the tray to disable it. I auto-connect to several servers when network connection goes up. I'd like to disable clipboard by default and then enable it only if necessary. -Timo From antoine at nagafix.co.uk Tue Oct 15 13:44:21 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 15 Oct 2013 19:44:21 +0700 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <84txgig13p.fsf@sauna.l.org> References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <84txgig13p.fsf@sauna.l.org> Message-ID: <525D38A5.3070505@nagafix.co.uk> On 15/10/13 19:39, Timo Juhani Lindfors wrote: > Hi, > > Antoine Martin writes: >> That's exactly what the "Clipboard" toggle in your xpra system tray does. > If I use --no-clipboard on the client then the tray says that it can not > enable clipboard since it is disabled by the server. If I don't use > "--no-clipboard" then the remote server can see my clipboard until I > have had time to go to the tray to disable it. > > I auto-connect to several servers when network connection goes up. I'd > like to disable clipboard by default and then enable it only if > necessary. OK, I've added this here: http://xpra.org/trac/ticket/276 Antoine From timo.lindfors at iki.fi Tue Oct 15 13:53:40 2013 From: timo.lindfors at iki.fi (Timo Juhani Lindfors) Date: Tue, 15 Oct 2013 15:53:40 +0300 Subject: [winswitch] secure clipboard syncing? In-Reply-To: <525D38A5.3070505@nagafix.co.uk> (Antoine Martin's message of "Tue, 15 Oct 2013 19:44:21 +0700") References: <84r4c4jh8s.fsf@sauna.l.org> <524BF871.1010804@nagafix.co.uk> <84txgig13p.fsf@sauna.l.org> <525D38A5.3070505@nagafix.co.uk> Message-ID: <84hacig0ff.fsf@sauna.l.org> Antoine Martin writes: > OK, I've added this here: > http://xpra.org/trac/ticket/276 Thanks! From ndbecker2 at gmail.com Fri Oct 18 11:24:40 2013 From: ndbecker2 at gmail.com (Neal Becker) Date: Fri, 18 Oct 2013 06:24:40 -0400 Subject: [winswitch] Tunneling xpra Message-ID: I can connect from work to amazon aws via ssh. A connection cannot be initiated in the reverse direction. Could I use xpra to tunnel in this situation? That is, connect to my aws machine and display graphics back on my work machine? From troycauble at gmail.com Fri Oct 18 13:24:40 2013 From: troycauble at gmail.com (Troy Cauble) Date: Fri, 18 Oct 2013 08:24:40 -0400 Subject: [winswitch] Tunneling xpra In-Reply-To: References: Message-ID: I do this all the time. (To home not aws.) ssh $RHOST "xpra start :$RDISPLAY -d all --start-child="$RAPP" --exit-with-children --no-microphone --no-speaker --no-pulseaudio" sleep 2 /Applications/Xpra.app/Contents/MacOS/Xpra -d all attach ssh:$RHOST:$RDISPLAY > $HOME/.xpra/client.$RDISPLAY.output 2>&1 On Fri, Oct 18, 2013 at 6:24 AM, Neal Becker wrote: > I can connect from work to amazon aws via ssh. A connection cannot be > initiated in the reverse direction. > > Could I use xpra to tunnel in this situation? That is, connect to my aws > machine and display graphics back on my work machine? > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From simon at ruderich.org Sat Oct 19 20:31:43 2013 From: simon at ruderich.org (Simon Ruderich) Date: Sat, 19 Oct 2013 21:31:43 +0200 Subject: [winswitch] [PATCH] xpra.1: Misc fixes. Message-ID: <20131019193142.GA591@ruderich.org> --- Hello, This patches fixes a few issues in the man page. - - vs \- - Always use uppercase for option arguments. - Add a few missing newlines (.TP). Some options were merged with the previous option. - Improve "DISPLAY=:7 firefox" example. - Add missing spaces after sentences, e.g. ". Next sentence" vs. ". Next sentence". - Use DISPLAY instead of NUMBER (only two instances of NUMBER). - Move available --title placeholders in a list. Regards Simon src/man/xpra.1 | 162 ++++++++++++++++++++++++++++++--------------------------- 1 file changed, 86 insertions(+), 76 deletions(-) diff --git a/src/man/xpra.1 b/src/man/xpra.1 index 3856140..71ca11d 100644 --- a/src/man/xpra.1 +++ b/src/man/xpra.1 @@ -31,13 +31,13 @@ xpra \- viewer for remote, persistent X applications [\fB\-\-speaker\-codec\fP=\fICODEC\fP] [\fB\-\-no\-microphone\fP] [\fB\-\-microphone\-codec\fP=\fICODEC\fP] -[\fB\-\-enable-sharing\fP] +[\fB\-\-enable\-sharing\fP] [\fB\-\-bind\-tcp\fP=\fI[HOST]:PORT\fP] [\fB\-\-encryption\fP=\fICIPHER\fP] [\fB\-\-encryption\-keyfile\fP=\fIFILENAME\fP] -[\fB\-\-auth\fP=\fImodule\fP] -[\fB\-\-password\-file\fP=\fIfilename\fP] -[\fB\-\-clipboard-filter\-file\fP=\fIfilename\fP] +[\fB\-\-auth\fP=\fIMODULE\fP] +[\fB\-\-password\-file\fP=\fIFILENAME\fP] +[\fB\-\-clipboard\-filter\-file\fP=\fIFILENAME\fP] [\fB\-\-dpi\fP=\fIVALUE\fP] [\fB\-\-socket\-dir\fP=\fIDIR\fP] .HP @@ -66,16 +66,16 @@ xpra \- viewer for remote, persistent X applications [\fB\-\-speed\fP=\fISPEED\fP] [\fB\-\-min-speed\fP=\fIMIN-SPEED\fP] [\fB\-\-auto\-refresh\-delay\fP=\fIDELAY\fP] -[\fB\-\-key\-shortcut\fP=\fIkey:action\fP] +[\fB\-\-key\-shortcut\fP=\fIKEY:ACTION\fP] [\fB\-\-readonly\fP] [\fB\-\-enable-sharing\fP] [\fB\-\-title\fP=\fIVALUE\fP] [\fB\-\-client\-toolkit\fP=\fITOOLKIT\fP] [\fB\-\-window\-layout\fP=\fILAYOUT\fP] [\fB\-\-window\-icon\fP=\fIFILENAME\fP] -[\fB\-\-tray\-icon\fP=\fIfilename\fP] +[\fB\-\-tray\-icon\fP=\fIFILENAME\fP] [\fB\-\-ssh\fP=\fICMD\fP] [\fB\-\-remote\-xpra\fP=\fICMD\fP] -[\fB\-\-password\-file\fP=\fIfilename\fP] +[\fB\-\-password\-file\fP=\fIFILENAME\fP] [\fB\-\-dpi\fP=\fIVALUE\fP] [\fB\-\-socket\-dir\fP=\fIDIR\fP] [\fB\-\-mmap\-group\fP] @@ -94,8 +94,8 @@ xpra \- viewer for remote, persistent X applications [\fB\-\-no\-microphone\fP] [\fB\-\-microphone\-codec\fP=\fICODEC\fP] [\fB\-\-bind\-tcp\fP=\fI[HOST]:PORT\fP] -[\fB\-\-auth\fP=\fImodule\fP] -[\fB\-\-password\-file\fP=\fIfilename\fP] +[\fB\-\-auth\fP=\fIMODULE\fP] +[\fB\-\-password\-file\fP=\fIFILENAME\fP] [\fB\-\-socket\-dir\fP=\fIDIR\fP] .HP \fBxpra\fP \fBproxy\fP \fI:DISPLAY\fP @@ -147,12 +147,14 @@ Xpra can also be used to shadow an existing X11 display. \fBxpra start\fP \fI:7\fP Start an xpra server using display number \fI:7\fP. .TP -\fBxpra start\fP \fIssh:bigbox:8 \-\-start\-child=xterm\fP +\fBxpra start\fP \fIssh:bigbox:7 \-\-start\-child=xterm\fP Start an xpra server on \fIbigbox\fP with an xterm in it, and connect to it. +.TP \fBDISPLAY=\fP\fI:7 firefox\fP -Start \fIfirefox\fP running inside the xpra server. No window will -appear. +Start \fIfirefox\fP running inside the xpra server. Run this on the host +where xpra was started or in terminal forwarded by xpra. No window will +appear until you attach with \fBxpra attach\fP. .TP \fBxpra list\fP Show a list of xpra servers you have running on the current host. @@ -195,7 +197,7 @@ the xpra server. When starting an xpra server, you must specify the name of the display to use. To do this, simply pick any number you like and stick a colon -in front of it. For instance :7, :12, and :3117 are all valid display +in front of it. For instance :7, :12, and :3117 are all valid display names. Just keep in mind that: .IP \(bu Every X or xpra server that is running on a single machine must use a @@ -212,8 +214,8 @@ When specifying an xpra server to a client program like \fBxpra attach\fP, \fBxpra detach\fP, \fBxpra stop\fP, \fBxpra version\fP, \fBxpra info\fP, \fBxpra list\fP or \fBxpra screenshot\fP then you can use a display of the form -\fB:\fP\fINUMBER\fP to refer to a server on the local host, or one of -the form \fBssh:\fP\fI[USER@]HOST\fP\fB:\fP\fINUMBER\fP to refer to a server +\fB:\fP\fIDISPLAY\fP to refer to a server on the local host, or one of +the form \fBssh:\fP\fI[USER@]HOST\fP\fB:\fP\fIDISPLAY\fP to refer to a server on a remote host; xpra will automatically connect to the remote host using \fBssh\fP(1). Generally, if you have only one xpra session running on a machine (which you can verify by running \fBxpra list\fP @@ -224,17 +226,17 @@ similarly attach to the lone xpra session on a remote machine. If the xpra server was given the \fB\-\-bind\-tcp\fP option when started then you can also connect to it using a display of -the form \fBtcp:HOST:PORT\fP. (Notice that \fBssh:\fP takes an optional +the form \fBtcp:HOST:PORT\fP. (Notice that \fBssh:\fP takes an optional \fIdisplay\fP number, while \fBtcp:\fP takes a required \fIport\fP number.) .\" -------------------------------------------------------------------- .SH SUBCOMMANDS .SS xpra start This command starts a new xpra server, including any necessary setup. -(when starting a remote server with the \fBssh:HOST:PORT\fP syntax, -the new session will also be attached) +(When starting a remote server with the \fBssh:HOST:DISPLAY\fP syntax, +the new session will also be attached.) .SS xpra attach -This command attachs to a running xpra server, and forwards any +This command attaches to a running xpra server, and forwards any applications using that server to appear on your current screen. .SS xpra detach Detaches the given xpra display. @@ -248,7 +250,7 @@ Note: older servers may not support this feature. Queries the server for version, status and statistics. Note: older servers may not support this feature. .SS xpra stop -This command attachs to a running xpra server, and requests that it +This command attaches to a running xpra server, and requests that it terminate immediately. This generally causes any applications using that server to terminate as well. .SS xpra list @@ -351,12 +353,12 @@ or force it enabled (\fIyes\fP). .TP \fB\-\-socket\-dir\fP=\fIDIR\fP Location where to write and look for the Xpra socket files. -Defaults to "~/.xpra". It may also be specified using the +Defaults to "~/.xpra". It may also be specified using the XPRA_SOCKET_DIR environment variable. When using the socket-dir option, it is generally necessary to specify socket-dir on all following commands, for xpra to work with the -open sessions. Mixing different socket-dir options is not +open sessions. Mixing different socket-dir options is not recommended. By specifying a shared directory this can be coupled with the @@ -369,7 +371,7 @@ By default, the xpra server puts itself into the background, i.e. 'daemonizes', and redirects its output to a log file. This prevents that behavior (useful mostly for debugging). .TP -\fB\-\-auth\fP=\fImodule\fP +\fB\-\-auth\fP=\fIMODULE\fP Specifies the authentication module to use. This can be used to secure sockets in a different way from the \fB\-\-encryption\fP switch: authentication modules can @@ -382,7 +384,7 @@ and should only be used for testing always fails authentication, useful for testing .IP \fBfile\fP checks the password against the file specified using -\fBpassword\-file\fP switch. The file can either contain +\fBpassword\-file\fP switch. The file can either contain a single password, in which case it will be used for all usernames, or a list of user credentials of the form (one per line): @@ -402,7 +404,7 @@ automatically (either \fBpam\fP or \fBwin32\fP) .TP \fB\-\-start\-child\fP=\fICMD\fP After starting the server, runs the command \fICMD\fP using the -default shell. The command is run with its $DISPLAY set to point to +default shell. The command is run with its \fB$DISPLAY\fP set to point to the newly-started server. This option may be given multiple times to start multiple children. .TP @@ -420,15 +422,15 @@ xpra server instance crashed. .TP \fB\-\-xvfb\fP=\fICMD\fP When starting the server, xpra starts a virtual X server to run the -clients on. By default, this is 'Xvfb'. If your Xvfb is installed in a +clients on. By default, this is 'Xvfb'. If your Xvfb is installed in a funny location, or you want to use some other virtual X server, then this switch allows you to specify how to run your preferred X server -executable. The default value used is: +executable. The default value used is: \fIXvfb +extension Composite \-screen 0 3840x2560x24+32 \-nolisten tcp \-noreset \-auth $XAUTHORITY\fP This can also be used to specify Xdummy as an alternative to Xvfb, this requires Xorg server version 1.12 or later and the dummy driver -version 0.3.5 or later. For more information, see: +version 0.3.5 or later. For more information, see: https://xpra.org/Xdummy.html .TP @@ -436,10 +438,10 @@ https://xpra.org/Xdummy.html The xpra server always listens for connections on a local Unix domain socket, and supports local connections with the \fB:7\fP-style display address, and remote connections with the \fBssh:frodo:7\fP-style -display address. If you want, it can also listen for connections on a -raw TCP socket. This behavior is enabled with \fB\-\-bind-\-tcp\fP. If +display address. If you want, it can also listen for connections on a +raw TCP socket. This behavior is enabled with \fB\-\-bind-\-tcp\fP. If the host portion is omitted, then 127.0.0.1 (localhost) will be -used. If you wish to accept connections on all interfaces, pass +used. If you wish to accept connections on all interfaces, pass 0.0.0.0 for the host portion. Using this switch without using the auth option is not recommended, @@ -452,14 +454,14 @@ of your actions. .TP \fB\-\-password\-file\fP=\fIFILENAME\fP This allows sessions to be secured with a password stored in a text -file. You should use this if you use the \fB\-\-bind-\-tcp\fP option. +file. You should use this if you use the \fB\-\-bind\-tcp\fP option. If this is used on the server, it will reject any client connections that do not provide the same password value. .TP \fB\-\-encryption\fP=\fICIPHER\fP Specifies the cipher to use for securing the connection from -prying eyes. This is only really useful with the \fB--bind-tcp\fP option. -This option requires the use of the \fB--encryption-keyfile\fP option. +prying eyes. This is only really useful with the \fB\-\-bind\-tcp\fP option. +This option requires the use of the \fB\-\-encryption\-keyfile\fP option. The only cipher supported at present is \fIAES\fP, if the client requests encryption it will be used by both the client and server for all communication after the initial password verification, @@ -469,10 +471,10 @@ it should not be considered safe from determined attackers. .TP \fB\-\-encryption\-keyfile\fP=\fIFILENAME\fP Specifies the key to use with the encryption cipher specified -with \fB\-\-encryption\fP. The client and server must use the +with \fB\-\-encryption\fP. The client and server must use the same keyfile contents. .TP -\fB\-\-clipboard-filter\-file\fP=\fIfilename\fP +\fB\-\-clipboard\-filter\-file\fP=\fIFILENAME\fP Name of a file containing regular expressions, any clipboard data that matches one of these regular expressions will be dropped. Note: at present this only applies to copying from the machine where @@ -495,11 +497,11 @@ This disables the feature. Disable forwarding of system notifications. System notifications require the xpra server to have its own instance of a dbus daemon, if it is missing a warning will be printed on -startup. This switch disables the feature entirely, and avoids +startup. This switch disables the feature entirely, and avoids the warning. .TP \fB\-\-no\-xsettings\fP -Disable xsettings synchronization. Xsettings are only forwarded +Disable xsettings synchronization. Xsettings are only forwarded from posix clients connecting to real posix servers (not shadows). .TP \fB\-\-no\-system\-tray\fP @@ -514,9 +516,9 @@ Disable forwarding of the system bell. .TP \fB-z\fP\fILEVEL\fP, \fB\-\-compress\fP=\fILEVEL\fP Select the level of zlib compression xpra will use when transmitting data -over the network. Higher levels of compression transmit less data over -the network, but use more CPU power. Valid options are between 0 -(meaning no compression) and 9, inclusive. Higher levels take +over the network. Higher levels of compression transmit less data over +the network, but use more CPU power. Valid options are between 0 +(meaning no compression) and 9, inclusive. Higher levels take progressively more CPU while giving diminishing returns in terms of actual compression achieved; the default is 3, which gives a reasonable trade-off in general. @@ -528,9 +530,8 @@ This compression is not used on pixel data (except when using the \fBrgb\fP encoding). .TP \fB\-\-jpeg\-quality\fP=\fIVALUE\fP -Deprecated, use \fB\-\-quality\fP: +Deprecated, use \fB\-\-quality\fP. .TP - \fB\-\-quality\fP=\fIVALUE\fP This option sets a fixed image compression quality lossy encodings (\fBjpeg\fP, \fBwebp\fP or \fBx264\fP). @@ -545,7 +546,7 @@ This option sets the minimum encoding quality allowed when the quality option is set to automatic mode. .TP \fB\-\-speed\fP=\fISPEED\fP -This option sets the encoding speed. Slower compresses more, faster +This option sets the encoding speed. Slower compresses more, faster will give better latency. The system normally uses a variable speed, this option forces a fixed speed setting to be used instead. @@ -563,29 +564,29 @@ This option is only relevant when using a lossy encoding (\fBjpeg\fP, \fBwebp\fP, \fBx264\fP or \fBvpx\fP) with a quality lower than 95%. .TP -\fB\-\-key\-shortcut\fP=\fIkey:action\fP +\fB\-\-key\-shortcut\fP=\fIKEY:ACTION\fP Can be specified multiple times to add multiple key shortcuts. These keys will be caught by the client and trigger the action specified and the key presses will not be passed to the server. -.br -The \fBkey\fP specification may include keyboard modifiers in the form - \fB[modifier\+]*key\fP, for example: \fIShift+F10\fP or \fIShift+Control+B\fP -.br + +The \fIKEY\fP specification may include keyboard modifiers in the form +\fB[modifier\+]*key\fP, for example: \fIShift+F10\fP or \fIShift+Control+B\fP + If no shortcuts are defined on the command line, the following default one will be used: \fIMeta+Shift+F4:quit\fP .br -The following \fBaction\fPs are currently defined: +The following \fIACTION\fPs are currently defined: .RS .IP \fBquit\fP -disconnects the xpra client +Disconnect the xpra client. .IP \fBvoid\fP -does not do anything, and can therefore be used to prevent +Does not do anything, and can therefore be used to prevent certain key combinations from ever being sent to the server. .IP \fBrefresh_window\fP -forces the currently focused window to be refreshed. +Force the currently focused window to be refreshed. .IP \fBrefresh_all_windows\fP -forces all windows to be refreshed. +Force all windows to be refreshed. .RE .PP @@ -594,7 +595,7 @@ forces all windows to be refreshed. Read only mode prevents all keyboard and mouse activity from being sent to the server. .TP -\fB\-\-enable-sharing\fP +\fB\-\-enable\-sharing\fP Allow more than one client to connect to the same session. This must be enabled on both the server and all co-operating clients to function. @@ -605,14 +606,14 @@ and key release events are sent to the server as they occur so that the server can maintain a consistent keyboard state. Using this option can prevent keys from repeating unexpectedly on high latency links but it may also disrupt applications which access -the keyboard directly (games, etc). +the keyboard directly (games, etc.). .TP \fB\-\-no\-speaker\fP -Disable sound output forwarding support. Application sound output will +Disable sound output forwarding support. Application sound output will not be sent to the client(s). .TP \fB\-\-no\-microphone\fP -Disable sound input forwarding support. Application sound input will +Disable sound input forwarding support. Application sound input will not be sent from the client(s) to the server. .TP \fB\-\-speaker\-codec\fP=\fICODEC\fP and \fB\-\-microphone\-codec\fP=\fICODEC\fP @@ -626,40 +627,49 @@ When unspecified, all the available codecs are allowed and the first one is used Sets the text shown as window title. The string supplied can make use of remote metadata placeholders which will be populated at runtime with the values from the -remote server. ie: - \f\@title\@\fP will be replaced by the remote window's title, - \f\@client-machine\@\fP will be replaced by the remote server's -hostname. - +remote server. The default value used is "@title@ on @client-machine@". + +The following placeholders are defined: +.RS +.IP \fB\@title\@\fP +Will be replaced by the remote window's title. +.IP \fB\@client-machine\@\fP +Will be replaced by the remote server's hostname. +.RE +.PP + .TP \fB\-\-client\-toolkit\fP=\fITOOLKIT\fP -Specifies the client toolkit to use. This changes the user interface toolkit -used to draw the windows and may affect the availibility of other features. +Specifies the client toolkit to use. This changes the user interface toolkit +used to draw the windows and may affect the availability of other features. The 'gtk2' toolkit is the one with the most features. Use the special value 'help' to get a list of options. .TP \fB\-\-window\-layout\fP=\fILAYOUT\fP Specifies how main windows are drawn, this can be used to add widgets or coloured borders to the window frame. -Use the special value 'help' to get a list of options. Each client toolkit +Use the special value 'help' to get a list of options. Each client toolkit may or may not provide different window layouts. .TP \fB\-\-window\-icon\fP=\fIFILENAME\fP Path to the default image which will be used for all windows. This icon may be shown in the window's bar, its iconified -state or task switchers. This depends on the operating system, +state or task switchers. This depends on the operating system, the window manage and the application may override this too. +.TP \fB\-\-no\-tray\fP -Disables the system tray. Not available on OSX since the dock +Disables the system tray. Not available on OSX since the dock icon is always shown. +.TP \fB\-\-delay\-tray\fP Waits for the first window or notification to appear before showing the system tray. (posix only) +.TP \fB\-\-tray\-icon\fP=\fIFILENAME\fP Specifies the icon shown in the dock/tray. By default it uses a simple default 'xpra' icon. -(on Microsoft Windows, the icon must be in \fBico\fP format) +(On Microsoft Windows, the icon must be in \fBico\fP format.) .TP \fB\-\-mmap\-group\fP Sets the mmap file's gid to match the socket file's gid and sets @@ -669,11 +679,11 @@ This is necessary to share the mmap file across user accounts. \fB\-\-enable\-pings\fP The client and server will exchange ping and echo packets which are used to gather latency statistics. -Those statistics can be seen using the "xpra info" command. +Those statistics can be seen using the \fBxpra info\fP command. .SS Options for attach, stop .TP -\fB\-\-ssh\fP\=fICMD\fP +\fB\-\-ssh\fP\=\fICMD\fP When you use an \fBssh:\fP address to connect to a remote display, xpra runs \fBssh\fP(1) to make the underlying connection. By default, it does this by running the command "ssh". If your ssh program is in @@ -689,9 +699,9 @@ arcfour encryption, then you should run \fBxpra attach \-\-ssh\fP=\fI"ssh \-c arcfour" ssh:frodo:7\fP .RE -(\fINote:\fP don't bother to enable ssh compression; this +\fINote:\fP Don't bother to enable ssh compression; this is redundant with xpra's own compression, and will just waste your -CPU. See also xpra's \fB\-\-compress\fP switch.) +CPU. See also xpra's \fB\-\-compress\fP switch. .RE .TP \fB\-\-remote\-xpra\fP=\fICMD\fP @@ -722,7 +732,7 @@ which display the remote applications should be shown on. There is a global config file in \fI/etc\fP or \fI/usr/local/etc\fP, and each user may override it using \fI.xpra/xpra.conf\fP. Xpra uses the directory \fI~/.xpra\fP to store a number of files. -(the examples below are given for the display \fI:7\fP) +(The examples below are given for the display \fI:7\fP.) .TP \fI~/.xpra/:7\fP The unix domain socket that clients use to contact the xpra server. @@ -744,14 +754,14 @@ Xpra has no test suite. Xpra does not fully handle all aspects of the X protocol; for instance, fancy input features like pressure-sensitivity on tablets, some window manager hints, and probably other more obscure parts of the -X protocol. It does, however, degrade gracefully, and patches for each +X protocol. It does, however, degrade gracefully, and patches for each feature would be gratefully accepted. The xpra server allocates an over-large framebuffer when using Xvfb; this wastes memory, and can cause applications to misbehave (e.g., by letting menus go off-screen). Conversely, if the framebuffer is ever insufficiently large, clients will misbehave in other ways (e.g., -input events will be misdirected). This is not a problem when using +input events will be misdirected). This is not a problem when using Xdummy, see the \fB\-\-xvfb\fP= switch for details. The need to choose display numbers by hand is annoying. -- 1.8.4.rc3 -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 From antoine at nagafix.co.uk Sun Oct 20 07:25:58 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 20 Oct 2013 13:25:58 +0700 Subject: [winswitch] [PATCH] xpra.1: Misc fixes. In-Reply-To: <20131019193142.GA591@ruderich.org> References: <20131019193142.GA591@ruderich.org> Message-ID: <52637776.2020709@nagafix.co.uk> On 20/10/13 02:31, Simon Ruderich wrote: > --- > Hello, > > This patches fixes a few issues in the man page. > > - - vs \- > - Always use uppercase for option arguments. > - Add a few missing newlines (.TP). Some options were merged with > the previous option. > - Improve "DISPLAY=:7 firefox" example. > - Add missing spaces after sentences, > e.g. ". Next sentence" vs. ". Next sentence". > - Use DISPLAY instead of NUMBER (only two instances of NUMBER). > - Move available --title placeholders in a list. Applied: http://xpra.org/trac/changeset/4568/xpra Thank you very much! Antoine > > Regards > Simon From antoine at nagafix.co.uk Tue Oct 22 09:37:20 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 22 Oct 2013 15:37:20 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.10.7 (bug fixes) Message-ID: <52663940.5050107@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This release fixes a number of bugs, and once again one of them is a regression related to tray forwarding (on MS Windows this time). It also works around an important bug in AMD's Linux drivers which could cause an X11 server crash: * fix client crash on Linux with AMD cards and fglrx driver * fix MS Windows tray forwarding (was broken by fix from 0.10.6) * fix missing WM_CLASS on X11 clients * fix Mac OSX shadow server * fix "xpra info" on shadow servers * add usable 1366x768 dummy resolution 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.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJmOTwACgkQGK2zHPGK1rsTcwCfbRS6rJnohjCGDuZXyXzi3Tu1 F9AAnR3lGgAkJb8TIyT8BNeJh7B4fm4X =pMZl -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Tue Oct 22 14:58:08 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 22 Oct 2013 20:58:08 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.10.8 (one important fix) Message-ID: <52668470.8040406@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, There was a major bug in 0.10.7 which would cause all windows with transparency to not render at all, on all platforms. (ouch!) This is the only bug that 0.10.8 fixes. Sorry about that. (the 'patch' command had made a real mess of the change) 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.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJmhHAACgkQGK2zHPGK1rtH/QCdEH2S8tYinhRL2JGwdce9/P1i XTsAn3ufTBuZ3F7yl7OVM5TF3P2yTSKg =NyON -----END PGP SIGNATURE----- From vrkorada at yahoo.co.in Wed Oct 23 11:09:07 2013 From: vrkorada at yahoo.co.in (Venkat) Date: Wed, 23 Oct 2013 10:09:07 +0000 (UTC) Subject: [winswitch] does xpra raise windows? References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> <52564AA9.5020200@nagafix.co.uk> Message-ID: > Windows that are actually minimized (and not destroyed) are shown again > when you connect, and whilst you are still connected they would still be > shown in your task manager (or via alt-tab style window switchers). > If the client application discards its own window, there is nothing xpra > can do to make it show again. > The application should offer a way of doing that. > > Antoine > I don't think the windows are minimized. The issue is that the window is closed, but he session in Xpra is still live without any windows. Steps to reproduce... Start a session with xemacs appliction. Attach the same from windows machine Close the xemacs window by clicking on 'X' button. You still see the command shell running and the session is listed on Linux machine. This leaves the session unused/orphan. You need to stop the session explicitly to cleanup. Since the window is closed, there is no way you can bring it back. It would good (for end users) if we can dettach the session on closing the window. If we provide a prompt (Do you want to close OR dettach?), that would be ideal. Thanks, Venkat From antoine at nagafix.co.uk Wed Oct 23 11:50:39 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 23 Oct 2013 17:50:39 +0700 Subject: [winswitch] does xpra raise windows? In-Reply-To: References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> <52564AA9.5020200@nagafix.co.uk> Message-ID: <5267A9FF.6090502@nagafix.co.uk> On 23/10/13 17:09, Venkat wrote: >> Windows that are actually minimized (and not destroyed) are shown again >> when you connect, and whilst you are still connected they would still be >> shown in your task manager (or via alt-tab style window switchers). >> If the client application discards its own window, there is nothing xpra >> can do to make it show again. >> The application should offer a way of doing that. >> >> Antoine >> > > I don't think the windows are minimized. The issue is that the window is > closed, but he session in Xpra is still live without any windows. > Steps to reproduce... > Start a session with xemacs appliction. > Attach the same from windows machine > Close the xemacs window by clicking on 'X' button. > You still see the command shell running and the session is listed on Linux > machine. This leaves the session unused/orphan. You need to stop the session > explicitly to cleanup. > > Since the window is closed, there is no way you can bring it back. > > It would good (for end users) if we can dettach the session on closing the > window. If we provide a prompt (Do you want to close OR dettach?), that > would be ideal. If that is what you need then simply start the server with: --exit-with-children Antoine From vrkorada at yahoo.co.in Thu Oct 24 10:28:16 2013 From: vrkorada at yahoo.co.in (venkat) Date: Thu, 24 Oct 2013 09:28:16 +0000 (UTC) Subject: [winswitch] does xpra raise windows? References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> <52564AA9.5020200@nagafix.co.uk> <5267A9FF.6090502@nagafix.co.uk> Message-ID: Antoine Martin writes: > >> > > > > I don't think the windows are minimized. The issue is that the window is > > closed, but he session in Xpra is still live without any windows. > > Steps to reproduce... > > Start a session with xemacs appliction. > > Attach the same from windows machine > > Close the xemacs window by clicking on 'X' button. > > You still see the command shell running and the session is listed on Linux > > machine. This leaves the session unused/orphan. You need to stop the session > > explicitly to cleanup. > > > > Since the window is closed, there is no way you can bring it back. > > > > It would good (for end users) if we can dettach the session on closing the > > window. If we provide a prompt (Do you want to close OR dettach?), that > > would be ideal. > If that is what you need then simply start the server with: > --exit-with-children > > Antoine > Hi Antoine, Thanks for the reply and this worked well. This solved one problem. However, is there any way to detach the session on closing (OR providing prompt to users to select close/detach)? Regards, Venkat From antoine at nagafix.co.uk Thu Oct 24 10:57:12 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 24 Oct 2013 16:57:12 +0700 Subject: [winswitch] does xpra raise windows? In-Reply-To: References: <201309151807.47923.thomas@koch.ro> <523694E8.8050108@nagafix.co.uk> <5255308D.5080508@nagafix.co.uk> <52564AA9.5020200@nagafix.co.uk> <5267A9FF.6090502@nagafix.co.uk> Message-ID: <5268EEF8.4050006@nagafix.co.uk> >>> explicitly to cleanup. >>> Since the window is closed, there is no way you can bring it back. >>> It would good (for end users) if we can dettach the session on closing >>> the window. If we provide a prompt (Do you want to close OR dettach?), that >>> would be ideal. >> If that is what you need then simply start the server with: >> --exit-with-children > Hi Antoine, > Thanks for the reply and this worked well. This solved one problem. However, > is there any way to detach the session on closing (OR providing prompt to > users to select close/detach)? When you click the close window button, we just forward it to the remote application which then takes whatever action it wants (in some cases, none at all). Some will close, some will minimize, some will show you their own alert box, etc Interposing some UI prompt here would just cause headaches in too many cases: it would be very hard to give the user a meaningful UI alternative because we would not even know in advance what that choice does. If you want to detach, just use the system tray menu. Antoine From antoine at devloop.org.uk Fri Oct 25 02:03:06 2013 From: antoine at devloop.org.uk (Antoine Martin) Date: Fri, 25 Oct 2013 08:03:06 +0700 Subject: [winswitch] Xpra on PyPI In-Reply-To: References: Message-ID: <5269C34A.8050402@devloop.org.uk> > I tried to install it from PyPI using "pip install > xpra", but that failed. It appears that the announced version(s) of > Xpra on PyPI are sadly outdated. Yes, they are about 4 years out of date! > I've attached the pip log for > details. > > Skip Montanaro Pip is using the old upstream instead of xpra.org: > Getting page http://pypi.python.org/simple/xpra > Getting page http://partiwm.org/wiki/xpra > Could not find any downloads that satisfy the requirement xpra I have no idea how to tell pip to update the links. (Also, things have changed quite a bit so the installation is likely to fail unless all the new dependencies used by default are installed) Until someone figures this out, install from your distribution package or from source: http://xpra.org/trac/wiki/Building Cheers Antoine From antoine at nagafix.co.uk Mon Oct 28 13:31:50 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 28 Oct 2013 20:31:50 +0700 Subject: [winswitch] Xpra on PyPI In-Reply-To: <5269C34A.8050402@devloop.org.uk> References: <5269C34A.8050402@devloop.org.uk> Message-ID: <526E6746.1050302@nagafix.co.uk> >> I tried to install it from PyPI using "pip install >> xpra", but that failed. It appears that the announced version(s) of >> Xpra on PyPI are sadly outdated. I have created a Pypi ticket requesting the URL to be updated: https://bitbucket.org/pypa/pypi/issue/83 And you can vote for it too... (hint hint) Antoine