From dougdoole at gmail.com Tue Dec 2 18:46:34 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Tue, 2 Dec 2014 13:46:34 -0500 Subject: [winswitch] Seeing lots of delays with xpra Message-ID: Lately when using xpra, I've been seeing lots of spinners over top of my windows. (And I mean "lots" in the sense that xpra is pretty much unusable at times.) In the past, xpra was working without these delays. When this happens, I see messages like this in the client log: 2014-12-02 13:20:53,784 server is not responding, drawing spinners over the windows 2014-12-02 13:21:05,074 server is OK again In the server log, I see messages like this: 2014-12-02 13:20:23,261 delayed_region_timeout: region is 15001ms old, bad connection? 2014-12-02 13:20:28,963 send_delayed for wid 23, elapsed time 5701.0 is above limit of 500.0 - sending now Occasionally it is so bad that xpra disconnects. At that point the server log will contain: 2014-12-02 13:24:08,767 Disconnecting client Protocol(SocketConnection(/home/doole/.xpra/reorx-1)): client ping timeout (waited 60 seconds without a response) 2014-12-02 13:24:08,769 xpra client disconnected. Both my xpra server and client are on the same network (but not the same subnet). If I use "ssh -X" directly to the box, I do not see any sort of delays. My windows are mostly konsole and gvim. I'd love to be able to say "this problem started with version X", but I haven't been able to pin it down. Unfortunately, my environment went though multiple changes at the same time (xpra 0.13.x to 0.14.x, Ubuntu 12.04 to 14.04), so I may not be able to get back to a good state for comparison purposes. I am running without speaker/microphone forwarding but everything else enabled. I have tried various encoding options, but it doesn't seem to make a difference. My client and server are both running Ubuntu 14.04. I'm currently running xpra 0.14.12 at both the client and server, but I've been seeing this on all the xpra 0.14.x builds that I've tried. Any suggestions? Anything I can do to help narrow this down further? Thanks. -- -- Doug Doole aibohphobia - The irrational fear of palindromes From antoine at nagafix.co.uk Tue Dec 2 20:23:43 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 02 Dec 2014 12:23:43 -0800 Subject: [winswitch] Seeing lots of delays with xpra In-Reply-To: References: Message-ID: <547E1FCF.5000201@nagafix.co.uk> Hi, On 02/12/14 10:46, Douglas Doole wrote: > Lately when using xpra, I've been seeing lots of spinners over top of my > windows. (And I mean "lots" in the sense that xpra is pretty much unusable > at times.) In the past, xpra was working without these delays. > > When this happens, I see messages like this in the client log: > > 2014-12-02 13:20:53,784 server is not responding, drawing spinners over the > windows > 2014-12-02 13:21:05,074 server is OK again > > In the server log, I see messages like this: > > 2014-12-02 13:20:23,261 delayed_region_timeout: region is 15001ms old, bad > connection? > 2014-12-02 13:20:28,963 send_delayed for wid 23, elapsed time 5701.0 is > above limit of 500.0 - sending now Funny coincidence, a ticket just got created with very similar symptoms: http://xpra.org/trac/ticket/750 > Occasionally it is so bad that xpra disconnects. At that point the server > log will contain: > > 2014-12-02 13:24:08,767 Disconnecting client > Protocol(SocketConnection(/home/doole/.xpra/reorx-1)): client ping timeout > (waited 60 seconds without a response) > 2014-12-02 13:24:08,769 xpra client disconnected. > > Both my xpra server and client are on the same network (but not the same > subnet). If I use "ssh -X" directly to the box, I do not see any sort of > delays. > > My windows are mostly konsole and gvim. > > I'd love to be able to say "this problem started with version X", but I > haven't been able to pin it down. Unfortunately, my environment went though > multiple changes at the same time (xpra 0.13.x to 0.14.x, Ubuntu 12.04 to > 14.04), so I may not be able to get back to a good state for comparison > purposes. > > I am running without speaker/microphone forwarding but everything else > enabled. I have tried various encoding options, but it doesn't seem to make > a difference. > > My client and server are both running Ubuntu 14.04. I'm currently running > xpra 0.14.12 at both the client and server, but I've been seeing this on > all the xpra 0.14.x builds that I've tried. > > Any suggestions? Anything I can do to help narrow this down further? Can you please add your info to the ticket and subscribe to it? If we know how to reproduce it, we should be able to fix it quickly. Cheers Antoine > > Thanks. From lukashaase at gmx.at Wed Dec 3 01:31:09 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Wed, 3 Dec 2014 02:31:09 +0100 Subject: [winswitch] "Simultanuous" start/upgrade In-Reply-To: <547B7503.1070101@nagafix.co.uk> References: , <547AC79D.9000602@nagafix.co.uk> , <547B7503.1070101@nagafix.co.uk> Message-ID: Hi Antoine > [...] > This look like a real xpra bug. If you file a ticket, we should be able > to fix it. > Try triggering the error with: > XPRA_SYNCHRONIZE=1 xpra ... > and / or: > xpra -d error ... > It will print a lot of debug, which should include more details about > the caller. > > We do have a call to trap.swallow_synced, so it should have flushed the > error on the spot instead of allowing it to go through to gdk where it > causes the crash. I am 100% sure this was reproduceable. Because in the beginning, I always called with "--no-mdns" and it crashed. At some point I realized without this argument it works. It it always worked. Now I want to reproduce it again and I fail :-( Seems a mix of coincidence and fails always now ... Before I start meaningless bug reports, can you tell me if any of those outputs are of any use? In my opinion, the "-d error" does not print "a lot of debug". This is the output when xpra did not crash (interestingly, I still see errors): 2014-12-02 17:14:08,449DISPLAY2 1280x768 at 0x193 (452x271 mm) 2014-12-02 17:14:08,515 server virtual display now set to 3600x1200 (best match for 3200x1200) 2014-12-02 17:14:08,517 setting key repeat rate from client: 500ms delay / 33ms interval 2014-12-02 17:14:08,518 setting keyboard layout to 'us' 2014-12-02 17:14:08,620 DPI set to 96 x 96 2014-12-02 17:14:08,621 sent updated screen size to 1 clients: 3600x1200 (max 8192x4096) 2014-12-02 17:14:14,456 _call(True,,(12582913L, 'WM_WINDOW_ROLE', 'STRING', 'latin1'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:14:14,457 _call(True,,(12582913L, '_NET_WM_NAME', 'UTF8_STRING', 'utf8'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:14:14,458 _call(True,,(12582913L, 'WM_NAME', 'STRING', 'latin1'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:14:14,459 _call(True,,(12582913L, '_NET_WM_NAME', 'UTF8_STRING', 'utf8'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:14:14,459 _call(True,,(12582913L, 'WM_NAME', 'STRING', 'latin1'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:14:14,460 _call(True,,(12582913L, '_NET_WM_WINDOW_OPACITY', 'CARDINAL', 'u32'),{}) no such window Traceback (most recent call last): Tr File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window /usr/lib64/python2.6/site-packages/xpra/server/picture_encode.py:352: DeprecationWarning: tostring() is deprecated. Please call tobytes() instead. /u data = img.tostring("raw", target_format) FreeType: couldn't open face /usr/share/fonts/default/ghostscript/bchb.pfa: 1 [...] And this is now the output when xpra crashes: [...] 2014-12-02 17:18:30,206 using rgb as primary encoding, also available: h264, vp8, png, png/P, png/L, webp, rgb24, jpeg, rgb32 2014-12-02 17:18:30,206 client root window size is 3200x1200 with 1 displays: 2014-12-02 17:18:30,206 '1\WinSta-Default' (846x317 mm) workarea: 1920x1167 2014-12-02 17:18:30,206 DISPLAY1 1920x1200 at 1280x0 (677x423 mm) 2014-12-02 17:18:30,206 DISPLAY2 1280x768 at 0x193 (452x271 mm) 2014-12-02 17:18:30,252 server virtual display now set to 3600x1200 (best match for 3200x1200) 2014-12-02 17:18:30,253 setting key repeat rate from client: 500ms delay / 33ms interval 2014-12-02 17:18:30,254 setting keyboard layout to 'us' 2014-12-02 17:18:30,331 DPI set to 96 x 96 2014-12-02 17:18:30,343 sent updated screen size to 1 clients: 3600x1200 (max 8192x4096) 2014-12-02 17:18:38,767 _call(True,,(12582913L, 'WM_TRANSIENT_FOR', 'WINDOW', 'window'),{}) no such window Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window 2014-12-02 17:18:38,768 _call(True,,(12582913L, '_NET_WM_WINDOW_TYPE', 'ATOM', ['atom']),{}) no such window Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 110, in _call value = fun(*args, **kwargs) File "window_bindings.pyx", line 707, in xpra.x11.bindings.window_bindings.X11WindowBindings.XGetWindowProperty (xpra/x11/bindings/window_bindings.c:6926) PropertyError: no such window Gdk-ERROR **: The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 1112 error_code 9 request_code 14 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... FreeType: couldn't open face /usr/share/fonts/default/ghostscript/bchb.pfa: 1 Both instances were started with XPRA_SYNCHRONIZE=1 xpra start :1984 -d error --no-daemon > [...] > > I understand that these errors might be caused by "the application should not behave like this" and therefore xpra crashes. > > On the other hand, it works over plain X and VNC. Furthermore, neither the application, nor the X server crashes (only xpra) meaning that it's related to xpra (even if it might behave correctly in a strict sense). > Plain-X and VNC are not window managers... so they just do not have any > code to run at all. Apples and oranges really. No, sorry, I mean "Plain-X" with cygwins X server in windowed mode. This includes the window manager. For VNC I agree of course. Thanks Lukas From antoine at nagafix.co.uk Wed Dec 10 04:13:43 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 09 Dec 2014 20:13:43 -0800 Subject: [winswitch] [ANNOUNCE] xpra 0.14.13 (many fixes) Message-ID: <5487C877.8050007@nagafix.co.uk> Hi, This minor update fixes a large number of issues, some of which were fairly recent regressions, others very old ones. Upgrading is strongly recommended. The refresh fixes will ensure that in almost all cases, your windows should get pixel perfect quality, at worst after a brief "auto refresh delay" following any lossy paint. The downside is a little bit more bandwidth and CPU consumption. The OSX and MS Windows builds have been updated to ffmpeg 2.4.4, which is also available in the RPM repositories. The Intel OpenGL driver has been blacklisted on MS Windows (it was already blacklisted on OSX) because it causes client crashes, you can still re-enable it using the opengl=yes command line switch or config file option (at your own risk obviously). Also included are a fair amount of fixes for warnings, corner cases and error handling code. The launcher also received a number of important fixes. Many thanks to those who patiently reported bugs and tested the fixes. Release notes: * fix cursor scaling (aka "giant cursors") * fix auto-refresh: encoding selection and requirements * fix exit-with-children with older python versions * fix timer execution vs cleanup races * fix screen information parsing error * fix dummy Xorg resolutions and add new ones * fix utility window decorations * ignore message for background image changes on win32 * blacklist Intel OpenGL driver on MS Windows as well as OSX * launcher fixes: ssh mode, honour encoding selection, tray cleanup on exit, improved debug mode * fix pygst metadata signed long value * fix encryption error handling * fix Python Pillow server 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 From johnss1221 at gmail.com Thu Dec 11 03:01:10 2014 From: johnss1221 at gmail.com (John Smith) Date: Thu, 11 Dec 2014 10:01:10 +0700 Subject: [winswitch] Tooltips have a title bar Message-ID: Hi all, I running Internet Explorer with wine 1.7.x via xpra. Tooltips have a title bar when I move cursor around areas which can display tooltip. I run IE from real machine and tooltips aren't display the title bar. My Server and client use xpra version 0.14.13. From lukashaase at gmx.at Thu Dec 11 03:53:13 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Thu, 11 Dec 2014 04:53:13 +0100 Subject: [winswitch] Tooltips have a title bar In-Reply-To: References: Message-ID: Hi, > I running Internet Explorer with wine 1.7.x via xpra. > Tooltips have a title bar when I move cursor around areas which can display > tooltip. > I run IE from real machine and tooltips aren't display the title bar. > My Server and client use xpra version 0.14.13. No solution but I have the same (or at least very similar) issue with MATLAB: The small tooltips as they appear in autocompletion/tab completion show up as separate small windows (I think they even show up quickly in the Windows taskbar). That slows down tremendously so that I disabled them wherever I could. Thanks Lukas From antoine at nagafix.co.uk Thu Dec 11 04:28:15 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 10 Dec 2014 20:28:15 -0800 Subject: [winswitch] Tooltips have a title bar In-Reply-To: References: Message-ID: <54891D5F.8060407@nagafix.co.uk> On 10/12/14 19:01, John Smith wrote: > Hi all, > > I running Internet Explorer with wine 1.7.x via xpra. > Tooltips have a title bar when I move cursor around areas which can display > tooltip. > I run IE from real machine and tooltips aren't display the title bar. I believe I have a fix for this already, but I will need to check the specification again to make sure what we do is correct and doesn't cause regressions elsewhere - and maybe re-work the code, at least in trunk. Can you please create a ticket so we can track this issue? > My Server and client use xpra version 0.14.13. Good! Cheers Antoine PS: the patch against trunk: --- xpra/client/gtk_base/gtk_client_window_base.py (revision 8229) +++ xpra/client/gtk_base/gtk_client_window_base.py (working copy) @@ -89,6 +89,10 @@ if self._override_redirect: return True window_types = metadata.get("window-type", []) + if "NORMAL" not in window_types: + tf = metadata.intget("transient-for", -1) + if tf>0: + return True popup_types = list(POPUP_TYPE_HINTS.intersection(window_types)) log("popup_types(%s)=%s", window_types, popup_types) if popup_types: From johnss1221 at gmail.com Thu Dec 11 06:55:35 2014 From: johnss1221 at gmail.com (John Smith) Date: Thu, 11 Dec 2014 13:55:35 +0700 Subject: [winswitch] Tooltips have a title bar In-Reply-To: <54891D5F.8060407@nagafix.co.uk> References: <54891D5F.8060407@nagafix.co.uk> Message-ID: Hi, I created a new ticket for this issue. https://www.xpra.org/trac/ticket/762 From utku at um-ic.com Tue Dec 16 16:41:29 2014 From: utku at um-ic.com (Utku Altunkaya) Date: Tue, 16 Dec 2014 18:41:29 +0200 Subject: [winswitch] CentOS 5.11 and Python 2.4 support Message-ID: <549060B9.6000109@um-ic.com> Hello Antoine, I understand that you are dropping support for pre-2.6 versions of Python, as mentioned in ticket #665 with the milestone set as 0.15. I installed a fresh CentOS 5.11 system today with xpra 0.14.13, and running xpra start results in xpra main error: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 103, in main return run_mode(script_file, err, options, args, mode, defaults) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 759, in run_mode return run_server(error_cb, options, mode, script_file, args) File "/usr/lib64/python2.4/site-packages/xpra/scripts/server.py", line 956, in run_server from xpra.x11.gtk_x11.wm import wm_check File "/usr/lib64/python2.4/site-packages/xpra/x11/gtk_x11/wm.py", line 449 except Exception as e: ^ SyntaxError: invalid syntax So, are these changes already in place? What will be the latest xpra version to support RHEL/CentOS 5? Regards. Utku / / From antoine at nagafix.co.uk Thu Dec 18 07:39:42 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 18 Dec 2014 14:39:42 +0700 Subject: [winswitch] CentOS 5.11 and Python 2.4 support In-Reply-To: <549060B9.6000109@um-ic.com> References: <549060B9.6000109@um-ic.com> Message-ID: <549284BE.9030505@nagafix.co.uk> On 16/12/14 23:41, Utku Altunkaya wrote: > Hello Antoine, > > I understand that you are dropping support for pre-2.6 versions of > Python, as mentioned in ticket #665 with the milestone set as 0.15. I > installed a fresh CentOS 5.11 system today with xpra 0.14.13, and > running xpra start results in (...) > except Exception as e: > ^ > SyntaxError: invalid syntax > > So, are these changes already in place? What will be the latest xpra > version to support RHEL/CentOS 5? Sorry about the delay. You're right of course, I missed this syntax error when I backported the changes from trunk to the v0.14.x branch for 0.14.11 (earlier versions do not have this bug). That's now fixed: http://xpra.org/trac/changeset/8251 I've pushed updated 0.14.13 packages for the distros that use python 2.5 or older, like CentOS 5. Cheers Antoine From utku at um-ic.com Thu Dec 18 12:41:21 2014 From: utku at um-ic.com (Utku Altunkaya) Date: Thu, 18 Dec 2014 14:41:21 +0200 Subject: [winswitch] CentOS 5.11 and Python 2.4 support In-Reply-To: <549284BE.9030505@nagafix.co.uk> References: <549060B9.6000109@um-ic.com> <549284BE.9030505@nagafix.co.uk> Message-ID: <5492CB71.20002@um-ic.com> On 18/12/14 09:39, Antoine Martin wrote: > On 16/12/14 23:41, Utku Altunkaya wrote: >> Hello Antoine, >> >> I understand that you are dropping support for pre-2.6 versions of >> Python, as mentioned in ticket #665 with the milestone set as 0.15. I >> installed a fresh CentOS 5.11 system today with xpra 0.14.13, and >> running xpra start results in > (...) >> except Exception as e: >> ^ >> SyntaxError: invalid syntax >> >> So, are these changes already in place? What will be the latest xpra >> version to support RHEL/CentOS 5? > Sorry about the delay. > You're right of course, I missed this syntax error when I backported the > changes from trunk to the v0.14.x branch for 0.14.11 (earlier versions > do not have this bug). > That's now fixed: > http://xpra.org/trac/changeset/8251 > > I've pushed updated 0.14.13 packages for the distros that use python 2.5 > or older, like CentOS 5. > > Cheers > Antoine Hello Antoine, Thank you for the fix. I updated to xpra-0.14.13-2.el5_11, ran "xpra start :1001", and xpra started successfully. However, when I try to attach to or stop the xpra instance, I'm getting the following errors: utku at vm5:[~]$ xpra attach :1001 xpra main error: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 103, in main return run_mode(script_file, err, options, args, mode, defaults) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 761, in run_mode return run_client(error_cb, options, args, mode) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 1111, in run_client app = make_client(error_cb, opts) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 1174, in make_client toolkit_module = __import__(client_module, globals(), locals(), ['XpraClient']) File "/usr/lib64/python2.4/site-packages/xpra/client/gtk2/client.py", line 26, in ? from xpra.client.gtk_base.gtk_client_base import GTKXpraClient, xor_str File "/usr/lib64/python2.4/site-packages/xpra/client/gtk_base/gtk_client_base.py", line 22, in ? from xpra.client.ui_client_base import UIXpraClient File "/usr/lib64/python2.4/site-packages/xpra/client/ui_client_base.py", line 28, in ? from xpra.client.client_base import XpraClientBase, EXIT_TIMEOUT, EXIT_MMAP_TOKEN_FAILURE File "/usr/lib64/python2.4/site-packages/xpra/client/client_base.py", line 220 except Exception as e: ^ SyntaxError: invalid syntax utku at vm5:[~]$ xpra stop :1001 xpra main error: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 103, in main return run_mode(script_file, err, options, args, mode, defaults) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 764, in run_mode return run_stopexit(mode, error_cb, options, args) File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line 1376, in run_stopexit app.cleanup() UnboundLocalError: local variable 'app' referenced before assignment The stop command doesn't have any effect and xpra still keeps running: utku at vm5:[~]$ ps aux | grep -i xpra utku 30422 0.0 1.4 427732 30124 ? S 14:03 0:00 /usr/bin/python /usr/bin/xpra start :1001 utku 30425 0.0 2.0 79080 42200 ? Ss 14:03 0:00 Xvfb-for-Xpra-:1001 +extension Composite -screen 0 3840x2560x24+32 -nolisten tcp -noreset -auth /home/utku/.Xauthority :1001 Regards, Utku From antoine at nagafix.co.uk Thu Dec 18 13:36:25 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 18 Dec 2014 20:36:25 +0700 Subject: [winswitch] CentOS 5.11 and Python 2.4 support In-Reply-To: <5492CB71.20002@um-ic.com> References: <549060B9.6000109@um-ic.com> <549284BE.9030505@nagafix.co.uk> <5492CB71.20002@um-ic.com> Message-ID: <5492D859.10306@nagafix.co.uk> (snip) > Hello Antoine, > > Thank you for the fix. I updated to xpra-0.14.13-2.el5_11, ran "xpra > start :1001", and xpra started successfully. However, when I try to > attach to or stop the xpra instance, I'm getting the following errors: > > utku at vm5:[~]$ xpra attach :1001 > xpra main error: (..) > File "/usr/lib64/python2.4/site-packages/xpra/client/client_base.py", > line 220 > except Exception as e: > ^ > SyntaxError: invalid syntax Ah. I had not tested CentOS 5 as a client. I've now fixed all occurrences of this non backwards compatible syntax - which is what I should have done in the first place: http://xpra.org/trac/changeset/8258 > utku at vm5:[~]$ xpra stop :1001 > xpra main error: > Traceback (most recent call last): > File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line > 103, in main > return run_mode(script_file, err, options, args, mode, defaults) > File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line > 764, in run_mode > return run_stopexit(mode, error_cb, options, args) > File "/usr/lib64/python2.4/site-packages/xpra/scripts/main.py", line > 1376, in run_stopexit > app.cleanup() > UnboundLocalError: local variable 'app' referenced before assignment That's a different one, thanks for reporting it, it should be fixed in (though you need an error somewhere else to hit this error): http://xpra.org/trac/changeset/8260 > The stop command doesn't have any effect and xpra still keeps running: > > utku at vm5:[~]$ ps aux | grep -i xpra > utku 30422 0.0 1.4 427732 30124 ? S 14:03 0:00 > /usr/bin/python /usr/bin/xpra start :1001 > utku 30425 0.0 2.0 79080 42200 ? Ss 14:03 0:00 > Xvfb-for-Xpra-:1001 +extension Composite -screen 0 3840x2560x24+32 > -nolisten tcp -noreset -auth /home/utku/.Xauthority :1001 Yes, all the clients were broken, including the stop command. I am preparing 0.14.14 with those fixes. Thanks Antoine From antoine at nagafix.co.uk Thu Dec 18 14:31:30 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 18 Dec 2014 21:31:30 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.14.14 (minor fixes) Message-ID: <5492E542.7060409@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This update fixes a few minor issues. There is no urgency to update if you were not affected by them. It is now possible to run Internet Explorer via wine (should you really wish to do so), and quite possibly many other MS Windows applications. This also fixes support for CentOS 5. (just like above for IE, this should be strongly discouraged, but it should work) The MS Windows and OSX builds now use the latest Python 2.7.9 Release notes: * fix Python < 2.6 compatibility (syntax errors) * remove window decorations from non-normal transient windows * fix error message of X11 client started without a valid display * fix invalid time recorded in statistics and heuristics * fix video stream decoding errors by restarting the stream * blacklist mesa's "Software Rasterizer" (user reported visual corruption) 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 v2 iEYEARECAAYFAlSS5UIACgkQGK2zHPGK1rt5DACfRW7c0R7lxGvxJshg/fijwNT8 WQMAnRB/NAD2o3DwPZpJ0nwqNMjOQUrj =fsK7 -----END PGP SIGNATURE----- From hzhou1 at cs.uml.edu Wed Dec 24 10:16:15 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Wed, 24 Dec 2014 05:16:15 -0500 Subject: [winswitch] How to connect using ssh when I have to specify the private key file? Message-ID: Hi, I tried to use xpra on Amazon EC2 ubuntu instance. But to connect to this instance using ssh, Amazon requires that we have to specify the private key (identity) file using -i parameter, and this is the only way to connect to it through ssh. So how should I write the ssh parameter in the "xpra attach" command line for which it seems that only ssh:SERVERUSERNAME at SERVERHOST:100 form is allowed. As an alternative, if I plan to connect to EC2 instance using TCP, how to let the xpra server specify the TCP port? Thanks for any help. From antoine at nagafix.co.uk Wed Dec 24 13:45:30 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 24 Dec 2014 20:45:30 +0700 Subject: [winswitch] How to connect using ssh when I have to specify the private key file? In-Reply-To: References: Message-ID: <549AC37A.1010004@nagafix.co.uk> On 24/12/14 17:16, Heng Zhou wrote: > Hi, I tried to use xpra on Amazon EC2 ubuntu instance. But to connect to > this instance using ssh, Amazon requires that we have to specify the > private key (identity) file using -i parameter, and this is the only way to > connect to it through ssh. So how should I write the ssh parameter in the > "xpra attach" command line for which it seems that only > ssh:SERVERUSERNAME at SERVERHOST:100 form is allowed. Use the "--ssh=ssh -i YOURKEYFILE" command line option. > As an alternative, if I plan to connect to EC2 instance using TCP, how to > let the xpra server specify the TCP port? This is covered in the man page, the "xpra --help" information, the wiki, etc.. Cheers Antoine From hzhou1 at cs.uml.edu Thu Dec 25 13:06:32 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Thu, 25 Dec 2014 08:06:32 -0500 Subject: [winswitch] How to connect using ssh when I have to specify the private key file? In-Reply-To: <549AC37A.1010004@nagafix.co.uk> References: <549AC37A.1010004@nagafix.co.uk> Message-ID: Thank you for the reply. I have successfully connected from command line. Also, I learnt to use Pageant to store the key file so that I can use Xpra launcher in Windows to connect without providing a password. Thank you again and Merry Christmas! On Wed, Dec 24, 2014 at 8:45 AM, Antoine Martin wrote: > On 24/12/14 17:16, Heng Zhou wrote: > > Hi, I tried to use xpra on Amazon EC2 ubuntu instance. But to connect to > > this instance using ssh, Amazon requires that we have to specify the > > private key (identity) file using -i parameter, and this is the only way > to > > connect to it through ssh. So how should I write the ssh parameter in the > > "xpra attach" command line for which it seems that only > > ssh:SERVERUSERNAME at SERVERHOST:100 form is allowed. > Use the "--ssh=ssh -i YOURKEYFILE" command line option. > > As an alternative, if I plan to connect to EC2 instance using TCP, how to > > let the xpra server specify the TCP port? > This is covered in the man page, the "xpra --help" information, the > wiki, etc.. > > Cheers > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From hzhou1 at cs.uml.edu Sat Dec 27 15:18:51 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Sat, 27 Dec 2014 10:18:51 -0500 Subject: [winswitch] How to use "randr" to resize the desktop? Message-ID: Hi, I can display a whole desktop using the instruction in http://xpra.org/trac/wiki/Usage. Now I hope I can miximize the window containing the desktop if I double click the title bar of the xpra window, just like miximizing a normal window in Windows. The same webpage says that "you can resize the desktop using the standard "randr" desktop tools (and not by resizing the window at present)", so I think this is the approach to accomplish what I want. But after search the internet, I still have no idea how to do it. Could you please give me a step by step configuration to accomplish miximizing the window containing the whole desktop by double click? Thank you very much! From antoine at nagafix.co.uk Sat Dec 27 15:25:47 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 27 Dec 2014 22:25:47 +0700 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: References: Message-ID: <549ECF7B.4050008@nagafix.co.uk> On 27/12/14 22:18, Heng Zhou wrote: > Hi, > > I can display a whole desktop using the instruction in > http://xpra.org/trac/wiki/Usage. Now I hope I can miximize the window > containing the desktop if I double click the title bar of the xpra window, > just like miximizing a normal window in Windows. "Double-click-to-maximize" is going to be desktop environment specific, often mapped as a shortcut for the maximize button. In this case, it is not possible because the window has a fixed size, and for that reason the maximize button should be disabled too. > The same webpage says that > "you can resize the desktop using the standard "randr" desktop tools (and > not by resizing the window at present)", so I think this is the approach to > accomplish what I want. randr is the X11 protocol, you may use any tool that uses it, ie: xrandr -s 1024x768 "man xrandr" for details > But after search the internet, I still have no idea > how to do it. Could you please give me a step by step configuration to > accomplish miximizing the window containing the whole desktop by double > click? It cannot be done at present because the window has a fixed size. There is a ticket for that: http://xpra.org/trac/ticket/530 It doesn't look hard to implement, I just haven't had the time. > Thank you very much! Cheers Antoine From hzhou1 at cs.uml.edu Sat Dec 27 15:45:17 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Sat, 27 Dec 2014 10:45:17 -0500 Subject: [winswitch] How to use the Xdummy with Xpra? Message-ID: Hi, According to The webpage https://www.xpra.org/trac/wiki/Xdummy and http://en.wikipedia.org/wiki/Xvfb, my understanding is that, using "Xdummy with Xpra", we can run any program that produce graphical output on a computer that does not install any physical graphics card and physical screen, because the output of the program can be produced by Xdummy and transfered to my local computer through Xpra. It is true for OpenGL program in particular, assuming I have installed mesa in which a software simulation of OpenGL rasterization is implemented. Am I right? If I am, how can we run an OpenGL program, say, glxinfo or glmark2, on a remote machine that has no physical graphics card (so /dev/dri/card0 and /dev/fb0 do not exist as a result), e.g., the Amazon EC2 t2.micro instance running ubuntu 14.04, and transfer the output (the animation) back to my local computer? I can not grasp the idea of the example in the aforementioned Xdummy webpage, and searching the internet (for a couple of days already) did not gives me any useful hint. So could you please help me with this question? Thank you very much. From antoine at nagafix.co.uk Sat Dec 27 16:16:07 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 27 Dec 2014 23:16:07 +0700 Subject: [winswitch] How to use the Xdummy with Xpra? In-Reply-To: References: Message-ID: <549EDB47.2030008@nagafix.co.uk> On 27/12/14 22:45, Heng Zhou wrote: > Hi, > > According to The webpage https://www.xpra.org/trac/wiki/Xdummy and > http://en.wikipedia.org/wiki/Xvfb, my understanding is that, using "Xdummy > with Xpra", we can run any program that produce graphical output on a > computer that does not install any physical graphics card and physical > screen, because the output of the program can be produced by Xdummy and > transfered to my local computer through Xpra. It is true for OpenGL program > in particular, assuming I have installed mesa in which a software > simulation of OpenGL rasterization is implemented. Am I right? If I am, how > can we run an OpenGL program, say, glxinfo or glmark2, on a remote machine > that has no physical graphics card (so /dev/dri/card0 and /dev/fb0 do not > exist as a result), e.g., the Amazon EC2 t2.micro instance running ubuntu > 14.04, and transfer the output (the animation) back to my local computer? I > can not grasp the idea of the example in the aforementioned Xdummy webpage, > and searching the internet (for a couple of days already) did not gives me > any useful hint. So could you please help me with this question? Thank you > very much. The default xpra installations using Xdummy support OpenGL as the Xorg command line includes "+extension GLX". Forwarding "glxgears" (or any other gl application) works fine out of the box, if you have access to a real graphics card in the server system you can also use VirtualGL to get hardware acceleration. Unfortunately, Ubuntu does weird things with their Xorg server installation and so you may not be able to use Xdummy on Ubuntu. Cheers Antoine From hzhou1 at cs.uml.edu Sat Dec 27 16:53:10 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Sat, 27 Dec 2014 11:53:10 -0500 Subject: [winswitch] How to use the Xdummy with Xpra? In-Reply-To: <549EDB47.2030008@nagafix.co.uk> References: <549EDB47.2030008@nagafix.co.uk> Message-ID: Thanks for the reply. I don't understand "if you have access to a real graphics card in the server system". By "server system" here do you mean the remote machine? I asked the question in the original post just because the remote machine is not installed a physical graphics card, so I tried to use Xdummy (or Xvfb) to setup a virtual graphics card (or virtual frame buffer). So the settings of my question is that there is no physical graphics card on the remote machine, and I tried to run glxgears on it and return the animation back to me. You said your forwarding of glxgears works fine. Is it working on a remote machine without physical graphics card? If so, could you please share your settings and running steps? To be specific, is the remote machine running Red Hat? Is the following commands the sequence of steps you did: (1) xpra start :100 (2) sudo DISPLAY=:100 Xorg -noreset +extension GLX :200 My remote ubuntu machine dies at this step. (3) Use Xpra Launcher in Windows to connect to the remote machine using display :200 (4) sudo DISPLAY=:200 glxgears Then the Xpra window in WIndows should display the animation of rolling gears, right? On Sat, Dec 27, 2014 at 11:16 AM, Antoine Martin wrote: > On 27/12/14 22:45, Heng Zhou wrote: > > Hi, > > > > According to The webpage https://www.xpra.org/trac/wiki/Xdummy and > > http://en.wikipedia.org/wiki/Xvfb, my understanding is that, using > "Xdummy > > with Xpra", we can run any program that produce graphical output on a > > computer that does not install any physical graphics card and physical > > screen, because the output of the program can be produced by Xdummy and > > transfered to my local computer through Xpra. It is true for OpenGL > program > > in particular, assuming I have installed mesa in which a software > > simulation of OpenGL rasterization is implemented. Am I right? If I am, > how > > can we run an OpenGL program, say, glxinfo or glmark2, on a remote > machine > > that has no physical graphics card (so /dev/dri/card0 and /dev/fb0 do not > > exist as a result), e.g., the Amazon EC2 t2.micro instance running ubuntu > > 14.04, and transfer the output (the animation) back to my local > computer? I > > can not grasp the idea of the example in the aforementioned Xdummy > webpage, > > and searching the internet (for a couple of days already) did not gives > me > > any useful hint. So could you please help me with this question? Thank > you > > very much. > The default xpra installations using Xdummy support OpenGL as the Xorg > command line includes "+extension GLX". > Forwarding "glxgears" (or any other gl application) works fine out of > the box, if you have access to a real graphics card in the server system > you can also use VirtualGL to get hardware acceleration. > > Unfortunately, Ubuntu does weird things with their Xorg server > installation and so you may not be able to use Xdummy on Ubuntu. > > Cheers > Antoine > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sat Dec 27 17:01:11 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 28 Dec 2014 00:01:11 +0700 Subject: [winswitch] How to use the Xdummy with Xpra? In-Reply-To: References: <549EDB47.2030008@nagafix.co.uk> Message-ID: <549EE5D7.6070201@nagafix.co.uk> On 27/12/14 23:53, Heng Zhou wrote: > Thanks for the reply. I don't understand "if you have access to a real > graphics card in the server system". By "server system" here do you > mean the remote machine? I said the "server", which may or may not be remote (which is not irrelevant). > I asked the question in the original post just because the remote > machine is not installed a physical graphics card, Then you can skip VirtualGL, you will get unaccelerated software rendering. > so I tried to use Xdummy (or Xvfb) to setup a virtual graphics card > (or virtual frame buffer). So the settings of my question is that > there is no physical graphics card on the remote machine, and I tried > to run glxgears on it and return the animation back to me. You said > your forwarding of glxgears works fine. It does. > Is it working on a remote machine without physical graphics card? Yes. > If so, could you please share your settings and running steps? Default settings, default steps. > To be specific, is the remote machine running Red Hat? Non-specific response: some are. What does remote mean here? Client? Server? > Is the following commands the sequence of steps you did: > (1) xpra start :100 > (2) sudo DISPLAY=:100 Xorg -noreset +extension GLX :200 I have no idea what you are trying to accomplish with the command above. xpra starts the display, or alternatively it can use an existing display, trying to start the display after starting xpra makes no sense whatsoever. > My remote ubuntu machine dies at this step. Like I said: Xdummy is broken with Ubuntu. It will not work. > (3) Use Xpra Launcher in Windows to connect to the remote machine > using display :200 > (4) sudo DISPLAY=:200 glxgears > Then the Xpra window in WIndows should display the animation of > rolling gears, right? Assuming that you started xpra with Xdummy as its vfb server, yes. Antoine > > On Sat, Dec 27, 2014 at 11:16 AM, Antoine Martin > > wrote: > > On 27/12/14 22:45, Heng Zhou wrote: > > Hi, > > > > According to The webpage https://www.xpra.org/trac/wiki/Xdummy and > > http://en.wikipedia.org/wiki/Xvfb, my understanding is that, > using "Xdummy > > with Xpra", we can run any program that produce graphical output > on a > > computer that does not install any physical graphics card and > physical > > screen, because the output of the program can be produced by > Xdummy and > > transfered to my local computer through Xpra. It is true for > OpenGL program > > in particular, assuming I have installed mesa in which a software > > simulation of OpenGL rasterization is implemented. Am I right? > If I am, how > > can we run an OpenGL program, say, glxinfo or glmark2, on a > remote machine > > that has no physical graphics card (so /dev/dri/card0 and > /dev/fb0 do not > > exist as a result), e.g., the Amazon EC2 t2.micro instance > running ubuntu > > 14.04, and transfer the output (the animation) back to my local > computer? I > > can not grasp the idea of the example in the aforementioned > Xdummy webpage, > > and searching the internet (for a couple of days already) did > not gives me > > any useful hint. So could you please help me with this question? > Thank you > > very much. > The default xpra installations using Xdummy support OpenGL as the Xorg > command line includes "+extension GLX". > Forwarding "glxgears" (or any other gl application) works fine out of > the box, if you have access to a real graphics card in the server > system > you can also use VirtualGL to get hardware acceleration. > > Unfortunately, Ubuntu does weird things with their Xorg server > installation and so you may not be able to use Xdummy on Ubuntu. > > Cheers > Antoine > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > From hzhou1 at cs.uml.edu Sat Dec 27 17:25:16 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Sat, 27 Dec 2014 12:25:16 -0500 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: <549ECF7B.4050008@nagafix.co.uk> References: <549ECF7B.4050008@nagafix.co.uk> Message-ID: Thanks for the reply. So RandR only works at the server side (because window manage runs at server side); resizing at client side does not work, right? But after I run the following commands at the server side: (1) xpra start :100 (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry 800x600+24 & (3) Use Xpra Launcher to connect to the server. A 800x600 Xpra window comes out. (4) sudo DISPLAY=:200 metacity & There is an error: "Xlib: extension "RANDR" missing on display ":200"." (5) sudo DISPLAY=:200 gnome-settings-daemon & (6) sudo DISPLAY=:200 gnome-panel & The GNOME Panel desktop environment appears (7) sudo DISPLAY=:200 xrandr --size 1024x768 , I received an error: "RandR extension missing" and the size of the Xpra window containing the whole desktop is unchanged. I don't know what is the matter. I also tried "sudo DISPLAY=:100 xrandr --size 1024x768" but nothing is changed. It seems that the RANDR extension is not enabled on display :200 (or :100? I don't know), but how should I enable it? I have already include the +extension RANDR option in step (2). Should I install some other packages? The server is running ubuntu 14.04. Looking forward to your further clarification. On Sat, Dec 27, 2014 at 10:25 AM, Antoine Martin wrote: > On 27/12/14 22:18, Heng Zhou wrote: > > Hi, > > > > I can display a whole desktop using the instruction in > > http://xpra.org/trac/wiki/Usage. Now I hope I can miximize the window > > containing the desktop if I double click the title bar of the xpra > window, > > just like miximizing a normal window in Windows. > "Double-click-to-maximize" is going to be desktop environment specific, > often mapped as a shortcut for the maximize button. > In this case, it is not possible because the window has a fixed size, > and for that reason the maximize button should be disabled too. > > The same webpage says that > > "you can resize the desktop using the standard "randr" desktop tools (and > > not by resizing the window at present)", so I think this is the approach > to > > accomplish what I want. > randr is the X11 protocol, you may use any tool that uses it, ie: > xrandr -s 1024x768 > "man xrandr" for details > > But after search the internet, I still have no idea > > how to do it. Could you please give me a step by step configuration to > > accomplish miximizing the window containing the whole desktop by double > > click? > It cannot be done at present because the window has a fixed size. > There is a ticket for that: > http://xpra.org/trac/ticket/530 > It doesn't look hard to implement, I just haven't had the time. > > Thank you very much! > Cheers > Antoine > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sat Dec 27 17:35:09 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 28 Dec 2014 00:35:09 +0700 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: References: <549ECF7B.4050008@nagafix.co.uk> Message-ID: <549EEDCD.8080705@nagafix.co.uk> Please don't top post. On 28/12/14 00:25, Heng Zhou wrote: > Thanks for the reply. So RandR only works at the server side (because > window manage runs at server side); resizing at client side does not > work, right? Sort of. RandR has nothing to do with the window manager. You can't resize client-side because the xpra protocol does not support it yet. > But after I run the following commands at the server side: > > (1) xpra start :100 > (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry > 800x600+24 & > (3) Use Xpra Launcher to connect to the server. A 800x600 Xpra window > comes out. > (4) sudo DISPLAY=:200 metacity & > There is an error: "Xlib: extension "RANDR" missing on display ":200"." > (5) sudo DISPLAY=:200 gnome-settings-daemon & > (6) sudo DISPLAY=:200 gnome-panel & > The GNOME Panel desktop environment appears > (7) sudo DISPLAY=:200 xrandr --size 1024x768 Xdummy supports RandR, Xvfb does not, hence the error. And don't run everything root... > > , I received an error: "RandR extension missing" and the size of the > Xpra window containing the whole desktop is unchanged. Like the error says... > > I don't know what is the matter. I also tried "sudo DISPLAY=:100 > xrandr --size 1024x768" but nothing is changed. It seems that the > RANDR extension is not enabled on display :200 (or :100? I don't > know), but how should I enable it? By using Xdummy instead of Xvfb. > I have already include the +extension RANDR option in step (2). Should > I install some other packages? The server is running ubuntu 14.04. And here is your problem again. > > Looking forward to your further clarification. Let's just make it crystal clear: Ubuntu is creating all these problems, either move away from it or be prepared to solve those problems on your own. Cheers Antoine > > On Sat, Dec 27, 2014 at 10:25 AM, Antoine Martin > > wrote: > > On 27/12/14 22:18, Heng Zhou wrote: > > Hi, > > > > I can display a whole desktop using the instruction in > > http://xpra.org/trac/wiki/Usage. Now I hope I can miximize the > window > > containing the desktop if I double click the title bar of the > xpra window, > > just like miximizing a normal window in Windows. > "Double-click-to-maximize" is going to be desktop environment > specific, > often mapped as a shortcut for the maximize button. > In this case, it is not possible because the window has a fixed size, > and for that reason the maximize button should be disabled too. > > The same webpage says that > > "you can resize the desktop using the standard "randr" desktop > tools (and > > not by resizing the window at present)", so I think this is the > approach to > > accomplish what I want. > randr is the X11 protocol, you may use any tool that uses it, ie: > xrandr -s 1024x768 > "man xrandr" for details > > But after search the internet, I still have no idea > > how to do it. Could you please give me a step by step > configuration to > > accomplish miximizing the window containing the whole desktop by > double > > click? > It cannot be done at present because the window has a fixed size. > There is a ticket for that: > http://xpra.org/trac/ticket/530 > It doesn't look hard to implement, I just haven't had the time. > > Thank you very much! > Cheers > Antoine > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > From antoine at nagafix.co.uk Sat Dec 27 17:38:16 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 28 Dec 2014 00:38:16 +0700 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: References: <549ECF7B.4050008@nagafix.co.uk> Message-ID: <549EEE88.4050305@nagafix.co.uk> On 28/12/14 00:25, Heng Zhou wrote: > Thanks for the reply. So RandR only works at the server side (because > window manage runs at server side); resizing at client side does not > work, right? But after I run the following commands at the server side: > > (1) xpra start :100 > (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry > 800x600+24 & One more thing: try Xephyr instead of Xnest. Antoine From hzhou1 at cs.uml.edu Sat Dec 27 18:09:58 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Sat, 27 Dec 2014 13:09:58 -0500 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: <549EEDCD.8080705@nagafix.co.uk> References: <549ECF7B.4050008@nagafix.co.uk> <549EEDCD.8080705@nagafix.co.uk> Message-ID: I'm sorry I'm getting more and more confused. To run RandR, i.e., xrandr, I have to use xpra to hold the whole desktop (if xpra forwards only application, the xpra window can resize at the client side. Yes it can), but the http://xpra.org/trac/wiki/Usage webpage requires using Xnest as a nested X11 server. I did not run Xdummy or Xvfb. Actually I don't know how to run Xdummy -- there is a command "xvfb" in ubuntu, but there is no command of Xdummy or xdummy. So I don't understand your reply "Xdummy supports RandR, Xvfb does not, hence the error.". I only run Xnest. Do you mean Xnest is equivalent to Xdummy or Xvfb? For the former, Xdummy doesn't work on ubuntu so RANDR doesn't work. For the latter, Xvfb does not support GLX so metacity and all other OpenGL applications do not work. Am I right? If I am, which one is Xnest equivalent to? And as for Xdummy, does it run automatically after I run xpra, so it is expected that a virtual frame buffer, or a virtual graphics card exists on display :100 after xpra start :100, so I can run glxgears on a remote Red Hat machine (on display :100), e.g., Amazon EC2 Red Hat instance, without any trouble like those I encountered on ubuntu, right? Hopefully my understanding is right. Gnome Panel is the only desktop I can use on Amazon EC2 instance, which appears only under Xnest. If I run Xephyr, the xpra window is black. There are bugs anywhere in Linux world. On Sat, Dec 27, 2014 at 12:35 PM, Antoine Martin wrote: > Please don't top post. > > On 28/12/14 00:25, Heng Zhou wrote: > > Thanks for the reply. So RandR only works at the server side (because > window manage runs at server side); resizing at client side does not work, > right? > > Sort of. RandR has nothing to do with the window manager. > You can't resize client-side because the xpra protocol does not support it > yet. > > But after I run the following commands at the server side: > > (1) xpra start :100 > (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry 800x600+24 > & > (3) Use Xpra Launcher to connect to the server. A 800x600 Xpra window > comes out. > (4) sudo DISPLAY=:200 metacity & > There is an error: "Xlib: extension "RANDR" missing on display ":200"." > (5) sudo DISPLAY=:200 gnome-settings-daemon & > (6) sudo DISPLAY=:200 gnome-panel & > The GNOME Panel desktop environment appears > (7) sudo DISPLAY=:200 xrandr --size 1024x768 > > Xdummy supports RandR, Xvfb does not, hence the error. > > And don't run everything root... > > > , I received an error: "RandR extension missing" and the size of the Xpra > window containing the whole desktop is unchanged. > > Like the error says... > > > I don't know what is the matter. I also tried "sudo DISPLAY=:100 xrandr > --size 1024x768" but nothing is changed. It seems that the RANDR extension > is not enabled on display :200 (or :100? I don't know), but how should I > enable it? > > By using Xdummy instead of Xvfb. > > I have already include the +extension RANDR option in step (2). Should I > install some other packages? The server is running ubuntu 14.04. > > And here is your problem again. > > > Looking forward to your further clarification. > > Let's just make it crystal clear: Ubuntu is creating all these problems, > either move away from it or be prepared to solve those problems on your own. > > Cheers > Antoine > > > > > > On Sat, Dec 27, 2014 at 10:25 AM, Antoine Martin > wrote: > >> On 27/12/14 22:18, Heng Zhou wrote: >> > Hi, >> > >> > I can display a whole desktop using the instruction in >> > http://xpra.org/trac/wiki/Usage >> . >> Now I hope I can miximize the window >> > containing the desktop if I double click the title bar of the xpra >> window, >> > just like miximizing a normal window in Windows. >> "Double-click-to-maximize" is going to be desktop environment specific, >> often mapped as a shortcut for the maximize button. >> In this case, it is not possible because the window has a fixed size, >> and for that reason the maximize button should be disabled too. >> > The same webpage says that >> > "you can resize the desktop using the standard "randr" desktop tools >> (and >> > not by resizing the window at present)", so I think this is the >> approach to >> > accomplish what I want. >> randr is the X11 protocol, you may use any tool that uses it, ie: >> xrandr -s 1024x768 >> "man xrandr" for details >> > But after search the internet, I still have no idea >> > how to do it. Could you please give me a step by step configuration to >> > accomplish miximizing the window containing the whole desktop by double >> > click? >> It cannot be done at present because the window has a fixed size. >> There is a ticket for that: >> http://xpra.org/trac/ticket/530 >> >> It doesn't look hard to implement, I just haven't had the time. >> > Thank you very much! >> Cheers >> Antoine >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> >> > > > From antoine at nagafix.co.uk Sat Dec 27 18:21:37 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 28 Dec 2014 01:21:37 +0700 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: References: <549ECF7B.4050008@nagafix.co.uk> <549EEDCD.8080705@nagafix.co.uk> Message-ID: <549EF8B1.1030101@nagafix.co.uk> Please don't top post. Again. On 28/12/14 01:09, Heng Zhou wrote: > I'm sorry I'm getting more and more confused. To run RandR, i.e., > xrandr, I have to use xpra to hold the whole desktop This sounds like you have it backwards, but whatever. > (if xpra forwards only application, the xpra window can resize at the > client side. Yes it can), but the http://xpra.org/trac/wiki/Usage > webpage requires using Xnest as a nested X11 server. I did not run > Xdummy or Xvfb. Xnest (or Xephyr) runs nested inside another X11 server, which can either be Xdummy or Xvfb. > Actually I don't know how to run Xdummy -- there is a command "xvfb" > in ubuntu, but there is no command of Xdummy or xdummy. So I don't > understand your reply "Xdummy supports RandR, Xvfb does not, hence the > error.". I only run Xnest. No you don't. Xpra runs a display server (either Xdummy or Xvfb) and you start Xnest in it. See the wiki page on Xdummy. > Do you mean Xnest is equivalent to Xdummy or Xvfb? No. > For the former, Xdummy doesn't work on ubuntu so RANDR doesn't work. > For the latter, Xvfb does not support GLX so metacity and all other > OpenGL applications do not work. Am I right? If I am, which one is > Xnest equivalent to? Xpra supports OpenGL with Xdummy only. AFAIK, even with Xdummy, you will not be able to get OpenGL with Xnest or Xephyr, which you need for running a full desktop. > And as for Xdummy, does it run automatically after I run xpra, so it > is expected that a virtual frame buffer, or a virtual graphics card > exists on display :100 after xpra start :100, so I can run glxgears on > a remote Red Hat machine (on display :100), e.g., Amazon EC2 Red Hat > instance, without any trouble like those I encountered on ubuntu, > right? Hopefully my understanding is right. Yes, xpra starts the virtual display server when you run "xpra start". > Gnome Panel is the only desktop I can use on Amazon EC2 instance, > which appears only under Xnest. If I run Xephyr, the xpra window is > black. There are bugs anywhere in Linux world. Xephyr works fine here. Antoine > > > On Sat, Dec 27, 2014 at 12:35 PM, Antoine Martin > > wrote: > > Please don't top post. > > On 28/12/14 00:25, Heng Zhou wrote: >> Thanks for the reply. So RandR only works at the server side >> (because window manage runs at server side); resizing at client >> side does not work, right? > Sort of. RandR has nothing to do with the window manager. > You can't resize client-side because the xpra protocol does not > support it yet. >> But after I run the following commands at the server side: >> >> (1) xpra start :100 >> (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry >> 800x600+24 & >> (3) Use Xpra Launcher to connect to the server. A 800x600 Xpra >> window comes out. >> (4) sudo DISPLAY=:200 metacity & >> There is an error: "Xlib: extension "RANDR" missing on display >> ":200"." >> (5) sudo DISPLAY=:200 gnome-settings-daemon & >> (6) sudo DISPLAY=:200 gnome-panel & >> The GNOME Panel desktop environment appears >> (7) sudo DISPLAY=:200 xrandr --size 1024x768 > Xdummy supports RandR, Xvfb does not, hence the error. > > And don't run everything root... >> >> , I received an error: "RandR extension missing" and the size of >> the Xpra window containing the whole desktop is unchanged. > Like the error says... >> >> I don't know what is the matter. I also tried "sudo DISPLAY=:100 >> xrandr --size 1024x768" but nothing is changed. It seems that the >> RANDR extension is not enabled on display :200 (or :100? I don't >> know), but how should I enable it? > By using Xdummy instead of Xvfb. >> I have already include the +extension RANDR option in step (2). >> Should I install some other packages? The server is running >> ubuntu 14.04. > And here is your problem again. >> >> Looking forward to your further clarification. > Let's just make it crystal clear: Ubuntu is creating all these > problems, either move away from it or be prepared to solve those > problems on your own. > > Cheers > Antoine > > > > >> >> On Sat, Dec 27, 2014 at 10:25 AM, Antoine Martin >> > wrote: >> >> On 27/12/14 22:18, Heng Zhou wrote: >> > Hi, >> > >> > I can display a whole desktop using the instruction in >> > http://xpra.org/trac/wiki/Usage >> . >> Now I hope I can miximize the window >> > containing the desktop if I double click the title bar of >> the xpra window, >> > just like miximizing a normal window in Windows. >> "Double-click-to-maximize" is going to be desktop environment >> specific, >> often mapped as a shortcut for the maximize button. >> In this case, it is not possible because the window has a >> fixed size, >> and for that reason the maximize button should be disabled too. >> > The same webpage says that >> > "you can resize the desktop using the standard "randr" >> desktop tools (and >> > not by resizing the window at present)", so I think this is >> the approach to >> > accomplish what I want. >> randr is the X11 protocol, you may use any tool that uses it, ie: >> xrandr -s 1024x768 >> "man xrandr" for details >> > But after search the internet, I still have no idea >> > how to do it. Could you please give me a step by step >> configuration to >> > accomplish miximizing the window containing the whole >> desktop by double >> > click? >> It cannot be done at present because the window has a fixed size. >> There is a ticket for that: >> http://xpra.org/trac/ticket/530 >> >> It doesn't look hard to implement, I just haven't had the time. >> > Thank you very much! >> Cheers >> Antoine >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> >> >> > > From antoine at nagafix.co.uk Mon Dec 29 05:29:58 2014 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 29 Dec 2014 12:29:58 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.14.15 (many fixes) Message-ID: <54A0E6D6.9010805@nagafix.co.uk> Hi, This update fixes quite a few issues, mostly with window state handling: some were recent regressions with window decorations (more fixes still to come in that area), others were more ancient bugs. There is no urgency to update if you were not affected by them. The binary builds (MS Windows and OSX) and the RPM repositories now include Cython 0.21.2 and ffmpeg 2.4.5 Release notes: * fix VP9 decoding support * fix full-window update heuristics * fix library linking order (preserve pkg-config order) * fix windows that iconify programmatically * fix dialog windows wrongly shown without decorations * fix border paint mode with OpenGL * fix maximize / unmaxmize and fullscreen state synchronization * fix window WM_STATE property handling (Java applications, etc) * add missing "dbus-proxy" option 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 From hzhou1 at cs.uml.edu Tue Dec 30 02:56:55 2014 From: hzhou1 at cs.uml.edu (Heng Zhou) Date: Mon, 29 Dec 2014 21:56:55 -0500 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: <549EF8B1.1030101@nagafix.co.uk> References: <549ECF7B.4050008@nagafix.co.uk> <549EEDCD.8080705@nagafix.co.uk> <549EF8B1.1030101@nagafix.co.uk> Message-ID: Sorry for the late reply. I was doing a research on X window server architecture these days, but I still can not fully understand your reply. I can not find any webpage in wikipedia titled "Xdummy". Btw, what do you mean by "top post"? I don't understand this word. It seems like I am making some mistake, but I don't mean to offend. It is often the case in forums, I asked some technical questions in a polite way (at least as much as can), but someone just becomes unhappy at my questions, downvoting my question, or saying something I don't understand like "top post". Why someone (everyone actually) is so hostile, so against me? What did I ever do to them? On Sat, Dec 27, 2014 at 1:21 PM, Antoine Martin wrote: > Please don't top post. Again. > > On 28/12/14 01:09, Heng Zhou wrote: > > I'm sorry I'm getting more and more confused. To run RandR, i.e., xrandr, > I have to use xpra to hold the whole desktop > > This sounds like you have it backwards, but whatever. > > (if xpra forwards only application, the xpra window can resize at the > client side. Yes it can), but the http://xpra.org/trac/wiki/Usage > > webpage requires using Xnest as a nested X11 server. I did not run Xdummy > or Xvfb. > > Xnest (or Xephyr) runs nested inside another X11 server, which can either > be Xdummy or Xvfb. > > Actually I don't know how to run Xdummy -- there is a command "xvfb" in > ubuntu, but there is no command of Xdummy or xdummy. So I don't > understand your reply "Xdummy supports RandR, Xvfb does not, hence the > error.". I only run Xnest. > > No you don't. Xpra runs a display server (either Xdummy or Xvfb) and you > start Xnest in it. > See the wiki page on Xdummy. > > Do you mean Xnest is equivalent to Xdummy or Xvfb? > > No. > > For the former, Xdummy doesn't work on ubuntu so RANDR doesn't work. > For the latter, Xvfb does not support GLX so metacity and all other > OpenGL applications do not work. Am I right? If I am, which one is Xnest equivalent > to? > > Xpra supports OpenGL with Xdummy only. > AFAIK, even with Xdummy, you will not be able to get OpenGL with Xnest or > Xephyr, which you need for running a full desktop. > > And as for Xdummy, does it run automatically after I run xpra, so it is > expected that a virtual frame buffer, or a virtual graphics card exists on > display :100 after xpra start :100, so I can run glxgears on a remote Red > Hat machine (on display :100), e.g., Amazon EC2 Red Hat instance, without > any trouble like those I encountered on ubuntu, right? Hopefully my > understanding is right. > > Yes, xpra starts the virtual display server when you run "xpra start". > > Gnome Panel is the only desktop I can use on Amazon EC2 instance, which > appears only under Xnest. If I run Xephyr, the xpra window is black. > There are bugs anywhere in Linux world. > > Xephyr works fine here. > > > Antoine > > > > On Sat, Dec 27, 2014 at 12:35 PM, Antoine Martin > wrote: > >> Please don't top post. >> >> On 28/12/14 00:25, Heng Zhou wrote: >> >> Thanks for the reply. So RandR only works at the server side (because >> window manage runs at server side); resizing at client side does not work, >> right? >> >> Sort of. RandR has nothing to do with the window manager. >> You can't resize client-side because the xpra protocol does not support >> it yet. >> >> But after I run the following commands at the server side: >> >> (1) xpra start :100 >> (2) sudo DISPLAY=:100 Xnest +extension RANDR :200 -ac -geometry >> 800x600+24 & >> (3) Use Xpra Launcher to connect to the server. A 800x600 Xpra window >> comes out. >> (4) sudo DISPLAY=:200 metacity & >> There is an error: "Xlib: extension "RANDR" missing on display ":200"." >> (5) sudo DISPLAY=:200 gnome-settings-daemon & >> (6) sudo DISPLAY=:200 gnome-panel & >> The GNOME Panel desktop environment appears >> (7) sudo DISPLAY=:200 xrandr --size 1024x768 >> >> Xdummy supports RandR, Xvfb does not, hence the error. >> >> And don't run everything root... >> >> >> , I received an error: "RandR extension missing" and the size of the >> Xpra window containing the whole desktop is unchanged. >> >> Like the error says... >> >> >> I don't know what is the matter. I also tried "sudo DISPLAY=:100 xrandr >> --size 1024x768" but nothing is changed. It seems that the RANDR extension >> is not enabled on display :200 (or :100? I don't know), but how should I >> enable it? >> >> By using Xdummy instead of Xvfb. >> >> I have already include the +extension RANDR option in step (2). Should I >> install some other packages? The server is running ubuntu 14.04. >> >> And here is your problem again. >> >> >> Looking forward to your further clarification. >> >> Let's just make it crystal clear: Ubuntu is creating all these problems, >> either move away from it or be prepared to solve those problems on your own. >> >> Cheers >> Antoine >> >> >> >> >> >> On Sat, Dec 27, 2014 at 10:25 AM, Antoine Martin >> wrote: >> >>> On 27/12/14 22:18, Heng Zhou wrote: >>> > Hi, >>> > >>> > I can display a whole desktop using the instruction in >>> > http://xpra.org/trac/wiki/Usage >>> . >>> Now I hope I can miximize the window >>> > containing the desktop if I double click the title bar of the xpra >>> window, >>> > just like miximizing a normal window in Windows. >>> "Double-click-to-maximize" is going to be desktop environment specific, >>> often mapped as a shortcut for the maximize button. >>> In this case, it is not possible because the window has a fixed size, >>> and for that reason the maximize button should be disabled too. >>> > The same webpage says that >>> > "you can resize the desktop using the standard "randr" desktop tools >>> (and >>> > not by resizing the window at present)", so I think this is the >>> approach to >>> > accomplish what I want. >>> randr is the X11 protocol, you may use any tool that uses it, ie: >>> xrandr -s 1024x768 >>> "man xrandr" for details >>> > But after search the internet, I still have no idea >>> > how to do it. Could you please give me a step by step configuration to >>> > accomplish miximizing the window containing the whole desktop by double >>> > click? >>> It cannot be done at present because the window has a fixed size. >>> There is a ticket for that: >>> http://xpra.org/trac/ticket/530 >>> >>> It doesn't look hard to implement, I just haven't had the time. >>> > Thank you very much! >>> Cheers >>> Antoine >>> >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users at lists.devloop.org.uk >>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>> >>> >> >> >> > > From ntlong0210 at gmail.com Tue Dec 30 03:27:34 2014 From: ntlong0210 at gmail.com (Long Nguyen Thanh) Date: Tue, 30 Dec 2014 10:27:34 +0700 Subject: [winswitch] How to use "randr" to resize the desktop? In-Reply-To: References: <549ECF7B.4050008@nagafix.co.uk> <549EEDCD.8080705@nagafix.co.uk> <549EF8B1.1030101@nagafix.co.uk> Message-ID: On Tue, Dec 30, 2014 at 9:56 AM, Heng Zhou wrote: > Sorry for the late reply. I was doing a research on X window server > architecture these days, but I still can not fully understand your reply. I > can not find any webpage in wikipedia titled "Xdummy". Btw, what do you > mean by "top post"? I don't understand this word. It seems like I am making > some mistake, but I don't mean to offend. It is often the case in forums, I > asked some technical questions in a polite way (at least as much as can), > but someone just becomes unhappy at my questions, downvoting my question, > or saying something I don't understand like "top post". Why someone > (everyone actually) is so hostile, so against me? What did I ever do to > them? > Top post mean your reply precedes the quoted original message. "For a long time the traditional style was to post the answer below as much of the quoted original as was necessary to understand the reply (bottom or inline)". You can see more details here . From dougdoole at gmail.com Wed Dec 31 15:28:59 2014 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 31 Dec 2014 10:28:59 -0500 Subject: [winswitch] [ANNOUNCE] xpra 0.14.15 (many fixes) In-Reply-To: <54A0E6D6.9010805@nagafix.co.uk> References: <54A0E6D6.9010805@nagafix.co.uk> Message-ID: Has the 0.14.15 update been pushed out for Ubuntu 14.04? None of my 14.04 systems have seen it appear. On Mon, Dec 29, 2014 at 12:29 AM, Antoine Martin wrote: > Hi, > > This update fixes quite a few issues, mostly with window state handling: > some were recent regressions with window decorations (more fixes still > to come in that area), others were more ancient bugs. > There is no urgency to update if you were not affected by them. > > The binary builds (MS Windows and OSX) and the RPM repositories now > include Cython 0.21.2 and ffmpeg 2.4.5 > > Release notes: > * fix VP9 decoding support > * fix full-window update heuristics > * fix library linking order (preserve pkg-config order) > * fix windows that iconify programmatically > * fix dialog windows wrongly shown without decorations > * fix border paint mode with OpenGL > * fix maximize / unmaxmize and fullscreen state synchronization > * fix window WM_STATE property handling (Java applications, etc) > * add missing "dbus-proxy" option > > 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 > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > -- -- Doug Doole aibohphobia - The irrational fear of palindromes