|
|
Log in / Subscribe / Register

Announcing xpra 0.0.5 - 'screen for X'

From:  "Nathaniel Smith" <njs-AT-pobox.com>
To:  lwn-AT-lwn.net
Subject:  Announcing xpra 0.0.5 -- 'screen for X'
Date:  Sun, 2 Nov 2008 01:56:05 -0700
Message-ID:  <961fa2b40811020156l764ba0f6u8ecd9cafdeac817e@mail.gmail.com>

Dear LWN,
Your readers may be interested in this announcement:

I'm pleased to announce the release of xpra 0.0.5.

Xpra is 'screen for X' -- it allows you to run X programs, usually on
a remote host, direct their display to your local machine, and then
to disconnect from these programs and reconnect from the same or
another machine, without losing any state.  It is licensed under the
GPLv2+.  For more information, see the FAQ:
 http://partiwm.org/browser/README.xpra

This is primarily a bug-fix release; 0.0.4 was the first release to
see real use by people other than me, and of course they found a wide
variety of interesting bugs, the vast majority of which are now fixed.
 This release is be substantially usable in real-world situations.

NEWS:

v0.0.5 (2008-11-02)
===================

Xpra:
  -- Protocol changes; v0.0.5 clients can only be used with v0.0.5
     servers, and vice-versa.  Use 'xpra upgrade' to upgrade old
     servers without losing your session state.
  -- Man page now included.
  Important bug fixes:
  -- Qt apps formerly could not receive keyboard input due to a focus
     handling bug; now fixed.
  -- Fedora's pygtk2 has mysterious local hacks that broke xpra;
     a workaround is now included.
  UI improvements:
  -- Logging cleanup -- all logging now goes through the Python
     logging framework instead of using raw 'prints'.  By default
     debug logging is suppressed, but can be enabled in a fine- or
     coarse-grained way.
  -- 'xpra attach ssh:machine' now works out-of-the-box even if xpra
     is not present in the remote machine's PATH, or requires
     PYTHONPATH tweaks, or whatever.  (The server does still need to
     be running on the remote machine, though, of course.)
  -- Commands that connect to a running xpra server ('attach', 'stop',
     etc.) now can generally be used without specifying the name of
     the server, assuming only one server is running.  (E.g., instead
     of 'xpra attach :10', you can use 'xpra attach'; ditto for remote
     hosts, you can now use plain 'xpra attach ssh:remote'.)
  -- Mouse scroll wheels now supported.
  -- 'xpra start' can now spawn child programs directly (--with-child)
     and exit automatically when these children have exited
     (--exit-with-children).
  Other:
  -- More robust strategy for handling window stacking order.
     (Side-effect: the xpra client no longer requires you to be using
     an EWMH-compliant window manager.)
  -- The xpra client no longer crashes when receiving an unknown key
     event (e.g. a multimedia key).
  -- Very brief transient windows (e.g., tooltips) no longer create
     persistent "litter" on the screen.
  -- Windows with non-empty X borders (e.g., xterm popup menus) are
     now handled properly.
  -- Withdrawn windows no longer reappear after 'xpra upgrade'.

Share and enjoy,
-- Nathaniel




to post comments

Announcing xpra 0.0.5 - 'screen for X'

Posted Nov 6, 2008 7:27 UTC (Thu) by jengelh (subscriber, #33263) [Link] (3 responses)

What makes it different to VNC?

Announcing xpra 0.0.5 - 'screen for X'

Posted Nov 6, 2008 9:23 UTC (Thu) by hjernemadsen (subscriber, #5676) [Link] (1 responses)

From http://partiwm.org/browser/README.xpra:

"Wait, isn't that what VNC does?
-------------------------------

VNC is another system for using apps remotely. The main difference between xpra
and VNC is that xpra is "rootless" -- i.e., programs you run under it show up on your
desktop as regular programs, managed by your regular window manager, instead of
being trapped inside a box. It gives you "remote applications", not a "remote
desktop". (Hence the name -- "X Persistent Remote Applications".)"

So basically what you can do with regular remote X, with the added bonus that the
program can be disconnected from, and reconnected to on another system.

Announcing xpra 0.0.5 - 'screen for X'

Posted Nov 8, 2008 20:40 UTC (Sat) by njs (subscriber, #40338) [Link]

>So basically what you can do with regular remote X, with the added bonus that the program can be disconnected from, and reconnected to on another system.

It's also much more responsive than regular remote X, because (like VNC) it has much better latency hiding -- so it's actually usable over non-LAN connections.

Announcing xpra 0.0.5 - 'screen for X'

Posted Dec 8, 2008 6:07 UTC (Mon) by undefined (guest, #40876) [Link]

disclaimer: i haven't had a chance to actually use xpra, but the below is based on my reading about xpra and experience with xmove, vnc, & nx.

what vnc does for an entire display (eg ":0.0"), xpra does for a x client. also it does not require a special x client, as vnc requires (xvncviewer), so therefor it does not have its own intermediate window between the xserver and the x client (ignoring rootless vnc, which i have only heard about and not experienced in a free software implementation).

freenx is a more featureful vnc, but still whole-desktop-oriented last i checked.

i'm mainly interested because sometimes i need to switch between computers, but want to take apps with me (eg my current firefox session), without taking the entire desktop (my 1680x1050 desktop is a pain to view with a 1280x800 laptop with all the scrolling around that is required and you can't switch the x server from the current VT or x11vnc displays garbage). i want to be able to change computers and take particular apps with me (firefox mainly because it won't run two instances of the same profile and even saving the current "session" on exit doesn't restore each web pages state, like session cookies, from what i remember). and i don't want to have "remote x client" (firefox) window in a "protocol client" (xvncviewer) window on my desktop. i want the remote x client's window to appear "native" and like every other "local" x client displaying through my x server's display.

i tried xmove and it worked... when it didn't crash, which was much too frequently to be useful (25-50% of detach/reattach cycles). so i'm hopeful xpra works (when i get a chance to install and try it).


Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds