Hi Antoine, Thanks for the response. While the Java Swing app might serve the purpose, I was looking for something that would require no client side install. I know the Xpra protocol works a little differently, in that it does not stream frame buffers as in VNC. However, I was wondering if there is a way to latch onto an Xpra DISPLAY on the server site through a web page and stream the application (not necessarily embedded into the browser). I guess, the main idea is to take away any client side configuration and deliver the application through a website. There are several people in my project group, who do not use a terminal/ have winswitch installed etc. Thanks! Ammar
On Thu, Apr 25, 2013 at 5:46 AM, <[email protected] > wrote: > Send shifter-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of shifter-users digest..." > > > Today's Topics: > > 1. Re: xpra issuses (Randy) > 2. xpra using cygwin ssh ([email protected]) > 3. Re: xpra using cygwin ssh (Antoine Martin) > 4. Re: xpra using cygwin ssh (Antoine Martin) > 5. Web browser based Xpra viewer (Ammar Husain) > 6. Re: Web browser based Xpra viewer (Antoine Martin) > 7. [ANNOUNCE] xpra 0.9.0 (Antoine Martin) > 8. Re: xpra using cygwin ssh ([email protected]) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Apr 2013 10:35:42 -0400 > From: Randy <[email protected]> > To: [email protected] > Subject: Re: [winswitch] xpra issuses > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Thanks. > > > You should be able to workaround this problem by defining another > > default encoding, either in /etc/xpra/xpra.conf or in ~/.xpra/xpra.conf > > Just got back from vacation myself only to find my systems crashed. That > and > work, when I get a chance I will look into this. > > -- > If it ain't broke tweek it > > > ------------------------------ > > Message: 2 > Date: Tue, 23 Apr 2013 16:08:17 +0200 > From: "[email protected]" <[email protected]> > To: [email protected] > Subject: [winswitch] xpra using cygwin ssh > Message-ID: > < > camfbs5mwmxqke9h8f4he_nfbyrjbiufb04f3arqmxyy4a7k...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Dear All, > > I'm using xpra with great satisfaction. Recently I bumped into a issue > while trying to attach to a server from a client behind a proxy. I've set > up cygwin, ssh and connect-proxy to work hand-in-hand, for command line > communication this pipeline is functional. Now, I would also like to use > this working ssh setup for xpra too. To this end, I've changed this line > > ssh = c:/cygwin/bin/ssh.exe > > in c:\Program Files (x86)\Xpra\xpra.conf to point ssh to cygwin's. Then > running Xpra_cmd.exe from a cygwin shell produced the output below: > > user@laptop /cygdrive/c/Program Files (x86)/Xpra > $ ./Xpra_cmd.exe attach ssh:[email protected]:1001 > ** Message: pygobject_register_sinkfunc is deprecated (GstObject) > xpra client version 0.8.8 > cannot read using ['c:/cygwin/bin/ssh.exe', '-l', 'user', '-T', ' > example.com', > '-ssh', '-agent', '.xpra/run-xpra', '--socket-dir=~/.xpra', '_proxy', > ':1001']: the SSH process has terminated with exit code=255 > 2013-04-23 15:03:08,441 connection closed after 0 packets received (0 > bytes) and 0 packets sent (0 bytes) > Exception in thread format (most likely raised during interpreter > shutdown): > > Is there a way to print the output of ssh for debugging? Or any hints that > I should consider? > > Thanks in advance, > Kristof > > > ------------------------------ > > Message: 3 > Date: Tue, 23 Apr 2013 21:20:00 +0700 > From: Antoine Martin <[email protected]> > To: [email protected] > Subject: Re: [winswitch] xpra using cygwin ssh > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 04/23/2013 09:08 PM, [email protected] wrote: > > Dear All, > > > > I'm using xpra with great satisfaction. Recently I bumped into a issue > > while trying to attach to a server from a client behind a proxy. I've set > > up cygwin, ssh and connect-proxy to work hand-in-hand, for command line > > communication this pipeline is functional. Now, I would also like to use > > this working ssh setup for xpra too. To this end, I've changed this line > > > > ssh = c:/cygwin/bin/ssh.exe > > > > in c:\Program Files (x86)\Xpra\xpra.conf to point ssh to cygwin's. > You should be modifying the user's xpra.conf rather than the system > default, creating one if it doesn't exist. > IIRC, on win32 this would be %APPDATA%\Xpra\xpra.conf > > This way it won't get overwritten with every Xpra software update. > > > Then > > running Xpra_cmd.exe from a cygwin shell produced the output below: > > > > user@laptop /cygdrive/c/Program Files (x86)/Xpra > > $ ./Xpra_cmd.exe attach ssh:[email protected]:1001 > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject) > > xpra client version 0.8.8 > > cannot read using ['c:/cygwin/bin/ssh.exe', '-l', 'user', '-T', ' > example.com', > > '-ssh', '-agent', '.xpra/run-xpra', '--socket-dir=~/.xpra', '_proxy', > > ':1001']: the SSH process has terminated with exit code=255 > > 2013-04-23 15:03:08,441 connection closed after 0 packets received (0 > > bytes) and 0 packets sent (0 bytes) > > Exception in thread format (most likely raised during interpreter > shutdown): > > > > Is there a way to print the output of ssh for debugging? Or any hints > that > > I should consider? > On win32 we don't use putty.exe but plink.exe (and not the one from > putty, but the one from tortoise to get a GUI for accepting host keys > and asking for passwords). > The connection stage is too early to get any meaningful debugging > information using the "xpra -d all" flag I think. > > Have you tried running that ssh command line by hand to make sure it > does work? I'm pretty sure it won't because it assumes that we're > dealing with "plink.exe" on win32, so the flags "-ssh" and "-agent" are > probably causing ssh.exe to abort with an error. > > If the patch below works for you, I guess I could use the "ssh" syntax > when the ssh command looks like a proper ssh... ugly, but that's win32 > for you. > > Cheers > Antoine > > > > > ### Eclipse Workspace Patch 1.0 > #P Xpra > Index: src/xpra/scripts/main.py > =================================================================== > --- src/xpra/scripts/main.py (revision 3132) > +++ src/xpra/scripts/main.py (working copy) > @@ -531,7 +531,7 @@ > dtype = display_desc["type"] > if dtype == "ssh": > cmd = display_desc["full_ssh"] > - if sys.platform.startswith("win"): > + if False: > password = display_desc.get("password") > if password: > cmd += ["-pw", password] > > > > ------------------------------ > > Message: 4 > Date: Tue, 23 Apr 2013 23:34:05 +0700 > From: Antoine Martin <[email protected]> > To: [email protected] > Subject: Re: [winswitch] xpra using cygwin ssh > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > (snip) > >> cannot read using ['c:/cygwin/bin/ssh.exe', '-l', 'user', '-T', ' > example.com', > >> '-ssh', '-agent', '.xpra/run-xpra', '--socket-dir=~/.xpra', '_proxy', > >> ':1001']: the SSH process has terminated with exit code=255 > >> 2013-04-23 15:03:08,441 connection closed after 0 packets received (0 > >> bytes) and 0 packets sent (0 bytes) > >> Exception in thread format (most likely raised during interpreter > shutdown): > (snip) > > If the patch below works for you, I guess I could use the "ssh" syntax > > when the ssh command looks like a proper ssh... ugly, but that's win32 > > for you. > The solution seemed simple enough so I've merged it already: > http://xpra.org/trac/changeset/3136/xpra > > You can find the latest beta win32 packages with this change included > here (r3136): > http://xpra.org/beta/windows/ > > Cheers > Antoine > > > ------------------------------ > > Message: 5 > Date: Wed, 24 Apr 2013 13:11:00 -0400 > From: Ammar Husain <[email protected]> > To: [email protected] > Subject: [winswitch] Web browser based Xpra viewer > Message-ID: > < > capms+rgzoea+vmseuoutzdo-ajaxfmvdd4h4tbzkzhajjgf...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi All, > Xpra has greatly helped me to remotely connect to applications on my work > computer. However I was wondering if there is an Xpra viewer that is > entirely web-based? I was reading through the documentation and it seems > like the Xpra viewer utilises the windowing system on the client machine. > Has anyone given it a try to embed the windowing in a web browser, possibly > using HTML5 canvas / AJAX? I mean something similar to NX WebPlayer or > noVNC. Would it even be possible to do something like that with Xpra > viewer? That would be of great help to me. > Thanks, > Ammar > > > ------------------------------ > > Message: 6 > Date: Thu, 25 Apr 2013 00:15:10 +0700 > From: Antoine Martin <[email protected]> > To: [email protected] > Subject: Re: [winswitch] Web browser based Xpra viewer > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Ammar, > > There are Java versions of the client (AWT and Swing) which could be > delivered to a browser. But: > * this Java code is not production ready by any means > * I've never tried doing that > * you would lose many of the benefits of Xpra (mainly: seamlessness) > > Cheers > Antoine > > On 04/25/2013 12:11 AM, Ammar Husain wrote: > > Hi All, > > Xpra has greatly helped me to remotely connect to applications on my work > > computer. However I was wondering if there is an Xpra viewer that is > > entirely web-based? I was reading through the documentation and it seems > > like the Xpra viewer utilises the windowing system on the client machine. > > Has anyone given it a try to embed the windowing in a web browser, > possibly > > using HTML5 canvas / AJAX? I mean something similar to NX WebPlayer or > > noVNC. Would it even be possible to do something like that with Xpra > > viewer? That would be of great help to me. > > Thanks, > > Ammar > > _______________________________________________ > > shifter-users mailing list > > [email protected] > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > > ------------------------------ > > Message: 7 > Date: Thu, 25 Apr 2013 01:49:40 +0700 > From: Antoine Martin <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: [winswitch] [ANNOUNCE] xpra 0.9.0 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > This new major release brings many new features, but more importantly > a large number of important bug fixes throughout. > > Here are some of the key new features and fixes: > * remote session start: xpra start ssh:host:DISP --start-child=cmd > * more sound codec support (wav, flac, opus..) > * MS Windows fixes (clipboard, caps and num lock synchronization) > * Platform fixes: IPv6 server, Python 2.4 fixes, SELinux labels, etc > * better launcher and support for launching from ".xpra" session files > > > The source: > https://xpra.org/src/ > Binaries/repositories: > https://winswitch.org/downloads/ > Direct binary downloads: > https://xpra.org/dists/ > > Cheers > Antoine > > PS: as usual, the Mac OSX build failed some last minute testing and > will be posted later. > > > Full releases notes: > - - fix focus problems with old Xvfb display servers > - - fix RPM SELinux labelling of static codec builds (CentOS) > - - fix CentOS 5.x compatibility > - - fix Python 2.4 and 2.5 compatibility (many) > - - fix clipboard with MS Windows clients > - - fix failed server upgrades killing the virtual display > - - fix screenshot command with "OR" windows > - - fix support for "OR" windows that move and resize > - - IPv6 server support > - - support for many more audio codecs: flac, opus, wavpack, wav, speex > - - support starting remote sessions with "xpra start" > - - support for Xdummy with CentOS 6.4 onwards > - - add --log-file command line option > - - add clipboard regex string filtering > - - add clipboard transfer in progress animation via system tray > - - detect broken/slow connections and temporarily grey out windows > - - reduce regular packet header sizes using numeric lookup tables > - - allow more options in xpra config and launcher files > - - MS Windows fixes for Caps Lock and Num Lock synchronization > - - MS Windows and OSX builds trim the amount of GStreamer plugins shipped > - - MS Windows, OSX and static codec builds (Ubuntu Lucid, Debian > Squeeze) updated to libav 9.4 > - - MS Windows and OSX builds updated to use Python 2.7.4 > - - MS Windows library updates (pyasn1, numpy, webp) > - - OSX library updates (mpfr, x264, pyasn1, numpy, webp), fixed sound > packaging > - - safer test for windows to ignore (window IDs starts at 1 again) > - - expose more version and statistical data via xpra info > - - improved OpenGL client rendering (still disabled by default) > - - upgrade to rencode 1.0.2 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.13 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlF4KT4ACgkQGK2zHPGK1rsargCeLDdEZp1wZX2KQfywAnagSr3A > k3YAn1MbLozE9JJex/V9fc4MdbYwx+Sd > =5Aw+ > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 8 > Date: Thu, 25 Apr 2013 11:45:27 +0200 > From: "[email protected]" <[email protected]> > To: Antoine Martin <[email protected]> > Cc: [email protected] > Subject: Re: [winswitch] xpra using cygwin ssh > Message-ID: > < > camfbs5ovyhr22ac__5ash2gnn+qi4qq0ktlwgepoqbz3mag...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Tue, Apr 23, 2013 at 6:34 PM, Antoine Martin <[email protected] > >wrote: > > > (snip) > > >> cannot read using ['c:/cygwin/bin/ssh.exe', '-l', 'user', '-T', ' > > example.com', > > >> '-ssh', '-agent', '.xpra/run-xpra', '--socket-dir=~/.xpra', '_proxy', > > >> ':1001']: the SSH process has terminated with exit code=255 > > >> 2013-04-23 15:03:08,441 connection closed after 0 packets received (0 > > >> bytes) and 0 packets sent (0 bytes) > > >> Exception in thread format (most likely raised during interpreter > > shutdown): > > (snip) > > > If the patch below works for you, I guess I could use the "ssh" syntax > > > when the ssh command looks like a proper ssh... ugly, but that's win32 > > > for you. > > The solution seemed simple enough so I've merged it already: > > http://xpra.org/trac/changeset/3136/xpra > > > > You can find the latest beta win32 packages with this change included > > here (r3136): > > http://xpra.org/beta/windows/ > > > > Cheers > > Antoine > > > > Dear Antoine, > > thank your for the quick reply! I don't have the build environment to try > the source patch, and http://xpra.org/beta/windows/ seems to be empty when > I've checked. I'll probably wait for the next release to try this out. > > Thanks a lot! > Kristof > > > > _______________________________________________ > > shifter-users mailing list > > [email protected] > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > shifter-users mailing list > [email protected] > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > ------------------------------ > > End of shifter-users Digest, Vol 26, Issue 4 > ******************************************** > _______________________________________________ shifter-users mailing list [email protected] http://lists.devloop.org.uk/mailman/listinfo/shifter-users
