From 1kenthomas at 1kenthomas.com Tue Mar 20 05:47:03 2012 From: 1kenthomas at 1kenthomas.com (Kenneth Thomas) Date: Tue, 20 Mar 2012 00:47:03 -0500 Subject: [winswitch] shift particular windows of an application...? Message-ID: Hello again all, Wondering if there are any methods for shifting particular windows from an application to another DISPLAY: ? For instance, this would be very useful when using PhotoShop pallet tools, or Firebug/Web Developer with Firefox (etc). (Yes, I run Photoshop ... and suppose that a program running under Wine may be "yet another story," of course). Thanks, Ken From antoine at nagafix.co.uk Tue Mar 20 07:20:36 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 20 Mar 2012 14:20:36 +0700 Subject: [winswitch] shift particular windows of an application...? In-Reply-To: References: Message-ID: <4F682FC4.8010000@nagafix.co.uk> On 03/20/2012 12:47 PM, Kenneth Thomas wrote: > Hello again all, > > Wondering if there are any methods for shifting particular windows from an > application to another DISPLAY: ? At present, no, and it is unlikely to be supported anytime soon, sorry. > For instance, this would be very > useful when using PhotoShop pallet tools, or Firebug/Web Developer with > Firefox (etc). The problem is that all those windows are part of the same application and therefore share the same DISPLAY. Xpra only supports one client at a time, so all the windows are shifted to the same client display. Supporting multiple concurrent clients would be the first step towards what you would like to achieve, but even that is a long way off.. > (Yes, I run Photoshop ... and suppose that a program running under Wine > may be "yet another story," of course). Cheers Antoine > > Thanks, > > Ken > _______________________________________________ > 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 Wed Mar 21 15:58:27 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 21 Mar 2012 22:58:27 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.1.0 Message-ID: <4F69FAA3.7090501@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This is the long awaited first major release, it contains a very large number of significant bug fixes and improvements. (please see release notes below) As usual, the source can be found here: http://xpra.org/src/ And the binaries here: http://winswitch.org/downloads/ Release details: * security: strict filtering of packet handlers until connection authenticated * prevent DoS: limit number of concurrent connections attempting login * prevent DoS: limit initial packet size (memory exhaustion: 32KB) * mmap: options to place sockets in /tmp and share mmap area across users via unix groups * remove large amount of compatiblity code for older versions * fix for Mac OS X clients sending hexadecimal keysyms * fix for clipboard sharing and some applications (ie: Qt) * notifications systems with dbus: re-connect if needed * notifications: try not to interfere with existing notification services * mmap: check for protected file access and ignore rather than error out (oops) * clipboard: handle empty data rather than timing out * spurious warnings: remove many harmless stacktraces/error messages * detect and discard broken windows with invalid atoms, avoids vfb + xpra crash * unpress keys all keys on start (if any) * fix screen size check: also check vertical size is sufficient * fix for invisible 0 by 0 windows: restore a minimum size * fix for window dimensions causing enless resizing or missing window contents * toggle cursors, bell and notifications by telling the server not to bother sending them, saves bandwidth * build/deploy: don't modify file in source tree, generate it at build time only * add missing GPL2 license file to show in about dialog * Python 2.5: workarounds to restore support * turn off compression over local connections (when mmap is enabled) * Android fixes: locking, maximize, focus, window placement, handle rotation, partial non-soft keyboard support * clients can specify maximum refresh rate and screen update batching options Cheers Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9p+qMACgkQGK2zHPGK1rtCjACeKuQCza3NRdzw96F0lBYkM/Oq u6kAn23VWMAxnrXumMV9gYOHkI32TcYs =y8sa -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Wed Mar 21 16:00:43 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 21 Mar 2012 23:00:43 +0700 Subject: [winswitch] [ANNOUNCE] winswitch 0.12.12 Message-ID: <4F69FB2B.4060908@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Version 0.12.12 is available now: http://winswitch.org/downloads/ This release consists mostly of platform bug fixes (Ubuntu and Mac OS X mostly) and makes the Android version finally usable. (please see the release notes below) Cheers Antoine Release Notes: * fix missing tray icon with Ubuntu 11.10 (properly this time) * fix keyboard mapping issues with NX sessions * fix NX sessions on Mac OS X * fix for xpra sessions wrongly detected as X11 sessions * Android improvements: ability to start sessions, update all dialogs as needed, handle sessions with shadows * Android fixes: allow spaces in message text, etc * new configuration file for each protocol backend, so individual protocols can easily be disabled * GStreamer codecs were not detected when reloading settings from file * Mac OS X library updates: gtk-osx, netifaces 0.8, Twisted 12, etc * MS Windows library updates: pywin32 217, Twisted 12, netifaces 0.7,etc * avoid error when stopping a local embedded connection * better default sizes for windows so they don't overflow the screen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9p+ysACgkQGK2zHPGK1rulRACdEVgv1p/Rq22+miKqAhsMf/u5 YMUAniYYJSwb+hYeUMVOOQ8W/0G4u4Ha =WFs7 -----END PGP SIGNATURE----- From ndbecker2 at gmail.com Thu Mar 22 13:05:45 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Thu, 22 Mar 2012 09:05:45 -0400 Subject: [winswitch] [newb] 0.1.0 fedora nothing happens Message-ID: Built on fedora f16 x86_64. Install like this: python setup.py install --user Then: xpra start :100 DISPLAY=:100 xterm [sits and waits but nothing happens...] ---nbecker1-100.log: Xlib: extension "RANDR" missing on display ":100". Xlib: extension "RANDR" missing on display ":100". Xlib: extension "RANDR" missing on display ":100". Randr not supported: X server does not support required extension Randr cannot register our notification forwarder: the name 'org.freedesktop.Notifications' is already claimed on the session bus xpra is ready. --------------- All commands run as user (not root). Any ideas? From ndbecker2 at gmail.com Thu Mar 22 14:18:09 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Thu, 22 Mar 2012 10:18:09 -0400 Subject: [winswitch] xpra doesn't handle menus Message-ID: Looks like xpra-0.1.0 is useless on Fedora 16. Nothing happens when clicking on menus - which seems to be a pretty serious problem. The only possibly relevant message I see is: /home/nbecker/.local/lib/python2.7/site-packages/xpra/client.py:532: GtkWarning: IA__gdk_window_get_root_coords: assertion `GDK_IS_WINDOW (window)' failed gtk.main() From antoine at nagafix.co.uk Thu Mar 22 18:47:52 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 23 Mar 2012 01:47:52 +0700 Subject: [winswitch] [newb] 0.1.0 fedora nothing happens In-Reply-To: References: Message-ID: <4F6B73D8.1010107@nagafix.co.uk> On 03/22/2012 08:05 PM, Neal Becker wrote: > Built on fedora f16 x86_64. Install like this: > > python setup.py install --user > > Then: > > xpra start :100 > > DISPLAY=:100 xterm > > [sits and waits but nothing happens...] That's because your xterm is running on the Xpra display :100, you need to attach to this session from somewhere to be able to interact with it. ie: in its simplest form, run from the same machine's GUI: xpra attach :100 As per: https://xpra.org/#get_started Cheers Antoine > > ---nbecker1-100.log: > > Xlib: extension "RANDR" missing on display ":100". > Xlib: extension "RANDR" missing on display ":100". > Xlib: extension "RANDR" missing on display ":100". > Randr not supported: X server does not support required extension Randr > cannot register our notification forwarder: the name > 'org.freedesktop.Notifications' is already claimed on the session bus > > xpra is ready. > --------------- > > All commands run as user (not root). > > Any ideas? > _______________________________________________ > 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 Thu Mar 22 19:04:45 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 23 Mar 2012 02:04:45 +0700 Subject: [winswitch] xpra doesn't handle menus In-Reply-To: References: Message-ID: <4F6B77CD.5090304@nagafix.co.uk> On 03/22/2012 09:18 PM, Neal Becker wrote: > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing happens when > clicking on menus - which seems to be a pretty serious problem. Are you talking about xpra's own tray menu or about a specific application you are running through xpra and which is having problems displaying its own menus properly? And if the latter, which application is it? Does it happen with other applications? Is it a Qt application by any chance? If this is the case then this may well be a theme/style problem which can be remedied using an environment variable I just cannot find right now... Note for those who hit this issue, you may be able to get those Qt styles to work properly using an Xvfb server with the required extensions, ie: https://xpra.org/Xdummy.html Cheers Antoine From ndbecker2 at gmail.com Thu Mar 22 19:26:40 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Thu, 22 Mar 2012 15:26:40 -0400 Subject: [winswitch] xpra doesn't handle menus In-Reply-To: <4F6B77CD.5090304@nagafix.co.uk> References: <4F6B77CD.5090304@nagafix.co.uk> Message-ID: I tried with both emacs GNU Emacs 24.0.93.1 and with konsole. konsole is Qt, but it looks like emacs is gtk. As mouse cursor goes over the menu, the cursor does not change, and the menu is not sensitive. Click on 'File' for example does nothing. On Thu, Mar 22, 2012 at 3:04 PM, Antoine Martin wrote: > On 03/22/2012 09:18 PM, Neal Becker wrote: > > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing happens when > > clicking on menus - which seems to be a pretty serious problem. > Are you talking about xpra's own tray menu or about a specific > application you are running through xpra and which is having problems > displaying its own menus properly? And if the latter, which application > is it? Does it happen with other applications? > > Is it a Qt application by any chance? > If this is the case then this may well be a theme/style problem which > can be remedied using an environment variable I just cannot find right > now... > Note for those who hit this issue, you may be able to get those Qt > styles to work properly using an Xvfb server with the required > extensions, ie: > https://xpra.org/Xdummy.html > > 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 Fri Mar 23 09:41:34 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 23 Mar 2012 16:41:34 +0700 Subject: [winswitch] re-release: xpra 0.1.0.1 and winswitch 0.12.12.1 Message-ID: <4F6C454E.7000303@nagafix.co.uk> Hi, The latest source snapshots would not build due to a missing file... The new .1 source snapshots fix this problem. Unless you build from source, there is no need to upgrade. Sorry Antoine From antoine at nagafix.co.uk Fri Mar 23 10:08:53 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 23 Mar 2012 17:08:53 +0700 Subject: [winswitch] xpra doesn't handle menus In-Reply-To: References: <4F6B77CD.5090304@nagafix.co.uk> Message-ID: <4F6C4BB5.5030209@nagafix.co.uk> On 03/23/2012 02:26 AM, Neal Becker wrote: > I tried with both emacs GNU Emacs 24.0.93.1 and with konsole. I've just tried with the default Fedora 16 Emacs (23.3.1) which worked fine. I am now installing emacs 24 from source. (600MB d/l - slow DSL..) I've also tried konsole v2.8.1, and still no problem.. There must be something different about your environment that makes it fail. Maybe your desktop's environment variables are interfering. Can you try launching the applications from a "clean" session, ie: one with a sanitized environment (maybe via ssh to localhost to clear it?). Antoine > konsole is Qt, but it looks like emacs is gtk. > > As mouse cursor goes over the menu, the cursor does not change, and the > menu is not sensitive. Click on 'File' for example does nothing. > > > On Thu, Mar 22, 2012 at 3:04 PM, Antoine Martin > wrote: > > On 03/22/2012 09:18 PM, Neal Becker wrote: > > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing happens when > > clicking on menus - which seems to be a pretty serious problem. > Are you talking about xpra's own tray menu or about a specific > application you are running through xpra and which is having problems > displaying its own menus properly? And if the latter, which application > is it? Does it happen with other applications? > > Is it a Qt application by any chance? > If this is the case then this may well be a theme/style problem which > can be remedied using an environment variable I just cannot find right > now... > Note for those who hit this issue, you may be able to get those Qt > styles to work properly using an Xvfb server with the required > extensions, ie: > https://xpra.org/Xdummy.html > > Cheers > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > From ndbecker2 at gmail.com Fri Mar 23 11:33:26 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Fri, 23 Mar 2012 07:33:26 -0400 Subject: [winswitch] xpra doesn't handle menus In-Reply-To: <4F6C4BB5.5030209@nagafix.co.uk> References: <4F6B77CD.5090304@nagafix.co.uk> <4F6C4BB5.5030209@nagafix.co.uk> Message-ID: I'm using kde for desktop (4.8.1), if that matters. What I told you is not quite accurate. 1. xpra attach ssh:nbecker6:100 This attaches to 'konsole' on remote. The cursor changes as I mouse over the menu, but left click on a menu does nothing. I see in .xsession-errors (and the mod time is quite recent): QObject: Cannot create children for a parent that is in a different thread. (Parent is Soprano::Client::LocalSocketClient(0x255b998), parent's thread is QThread(0x23d8330), current thread is RankingsUpdateThread(0x2599e30) Now from that konosole, launch emacs. Cursor changes from i-beam to X, as I move from text area to the window frame. But click on a menu does nothing. .xsession-errors seems to have a new modtime, and I see the same message as above. On Fri, Mar 23, 2012 at 6:08 AM, Antoine Martin wrote: > On 03/23/2012 02:26 AM, Neal Becker wrote: > > I tried with both emacs GNU Emacs 24.0.93.1 and with konsole. > I've just tried with the default Fedora 16 Emacs (23.3.1) which worked > fine. I am now installing emacs 24 from source. (600MB d/l - slow DSL..) > I've also tried konsole v2.8.1, and still no problem.. > > There must be something different about your environment that makes it > fail. Maybe your desktop's environment variables are interfering. > Can you try launching the applications from a "clean" session, ie: one > with a sanitized environment (maybe via ssh to localhost to clear it?). > > Antoine > > > konsole is Qt, but it looks like emacs is gtk. > > > > > As mouse cursor goes over the menu, the cursor does not change, and the > > menu is not sensitive. Click on 'File' for example does nothing. > > > > > > On Thu, Mar 22, 2012 at 3:04 PM, Antoine Martin > > wrote: > > > > On 03/22/2012 09:18 PM, Neal Becker wrote: > > > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing happens > when > > > clicking on menus - which seems to be a pretty serious problem. > > Are you talking about xpra's own tray menu or about a specific > > application you are running through xpra and which is having problems > > displaying its own menus properly? And if the latter, which > application > > is it? Does it happen with other applications? > > > > Is it a Qt application by any chance? > > If this is the case then this may well be a theme/style problem which > > can be remedied using an environment variable I just cannot find > right > > now... > > Note for those who hit this issue, you may be able to get those Qt > > styles to work properly using an Xvfb server with the required > > extensions, ie: > > https://xpra.org/Xdummy.html > > > > 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 Fri Mar 23 12:12:06 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 23 Mar 2012 19:12:06 +0700 Subject: [winswitch] xpra doesn't handle menus In-Reply-To: References: <4F6B77CD.5090304@nagafix.co.uk> <4F6C4BB5.5030209@nagafix.co.uk> Message-ID: <4F6C6896.5050405@nagafix.co.uk> On 03/23/2012 06:33 PM, Neal Becker wrote: > I'm using kde for desktop (4.8.1), if that matters. > > What I told you is not quite accurate. > > 1. xpra attach ssh:nbecker6:100 Using ssh *should not* make much of a difference, certainly not a complete failure to display like you are reporting. Is there anything in the xpra server log at all? > This attaches to 'konsole' on remote. > The cursor changes as I mouse over the menu, but left click on a menu > does nothing. I see in .xsession-errors (and the mod time is quite recent): > > QObject: Cannot create children for a parent that is in a different thread. > (Parent is Soprano::Client::LocalSocketClient(0x255b998), parent's > thread is QThread(0x23d8330), current thread is > RankingsUpdateThread(0x2599e30) This error comes from the Qt application itself. Why it would encounter this sort of problems when xpra is its window manager, I have absolutely no idea! But there were some qt/kde theming fixes in the past few months and I am running Fedora 16 here (which has them) whereas Fedora 15 may not have them (yet).. > Now from that konosole, launch emacs. > Cursor changes from i-beam to X, as I move from text area to the window > frame. But click on a menu does nothing. .xsession-errors seems to > have a new modtime, and I see the same message as above. I am installing the full KDE on a Fedora 15 virtual machine to test. Cheers Antoine PS: emacs 24 from source also works fine. > > On Fri, Mar 23, 2012 at 6:08 AM, Antoine Martin > wrote: > > On 03/23/2012 02:26 AM, Neal Becker wrote: > > I tried with both emacs GNU Emacs 24.0.93.1 and with konsole. > I've just tried with the default Fedora 16 Emacs (23.3.1) which worked > fine. I am now installing emacs 24 from source. (600MB d/l - slow DSL..) > I've also tried konsole v2.8.1, and still no problem.. > > There must be something different about your environment that makes it > fail. Maybe your desktop's environment variables are interfering. > Can you try launching the applications from a "clean" session, ie: one > with a sanitized environment (maybe via ssh to localhost to clear it?). > > Antoine > > > konsole is Qt, but it looks like emacs is gtk. > > > > > As mouse cursor goes over the menu, the cursor does not change, > and the > > menu is not sensitive. Click on 'File' for example does nothing. > > > > > > On Thu, Mar 22, 2012 at 3:04 PM, Antoine Martin > > > >> wrote: > > > > On 03/22/2012 09:18 PM, Neal Becker wrote: > > > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing > happens when > > > clicking on menus - which seems to be a pretty serious problem. > > Are you talking about xpra's own tray menu or about a specific > > application you are running through xpra and which is having > problems > > displaying its own menus properly? And if the latter, which > application > > is it? Does it happen with other applications? > > > > Is it a Qt application by any chance? > > If this is the case then this may well be a theme/style > problem which > > can be remedied using an environment variable I just cannot > find right > > now... > > Note for those who hit this issue, you may be able to get those Qt > > styles to work properly using an Xvfb server with the required > > extensions, ie: > > https://xpra.org/Xdummy.html > > > > 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 Fri Mar 23 19:35:51 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 24 Mar 2012 02:35:51 +0700 Subject: [winswitch] KDE + Xpra problem (was: xpra doesn't handle menus) In-Reply-To: <4F6C6896.5050405@nagafix.co.uk> References: <4F6B77CD.5090304@nagafix.co.uk> <4F6C4BB5.5030209@nagafix.co.uk> <4F6C6896.5050405@nagafix.co.uk> Message-ID: <4F6CD097.3040900@nagafix.co.uk> You are hitting this unfixed KDE bug: https://bugs.kde.org/show_bug.cgi?id=274485 Which the developers do not seem to understand or want to fix. I can only suggest that you avoid KDE until this is resolved, sorry. Antoine On 03/23/2012 07:12 PM, Antoine Martin wrote: > On 03/23/2012 06:33 PM, Neal Becker wrote: >> I'm using kde for desktop (4.8.1), if that matters. >> >> What I told you is not quite accurate. >> >> 1. xpra attach ssh:nbecker6:100 > Using ssh *should not* make much of a difference, certainly not a > complete failure to display like you are reporting. > > Is there anything in the xpra server log at all? > >> This attaches to 'konsole' on remote. >> The cursor changes as I mouse over the menu, but left click on a menu >> does nothing. I see in .xsession-errors (and the mod time is quite recent): >> >> QObject: Cannot create children for a parent that is in a different thread. >> (Parent is Soprano::Client::LocalSocketClient(0x255b998), parent's >> thread is QThread(0x23d8330), current thread is >> RankingsUpdateThread(0x2599e30) > This error comes from the Qt application itself. > Why it would encounter this sort of problems when xpra is its window > manager, I have absolutely no idea! > But there were some qt/kde theming fixes in the past few months and I am > running Fedora 16 here (which has them) whereas Fedora 15 may not have > them (yet).. > >> Now from that konosole, launch emacs. >> Cursor changes from i-beam to X, as I move from text area to the window >> frame. But click on a menu does nothing. .xsession-errors seems to >> have a new modtime, and I see the same message as above. > I am installing the full KDE on a Fedora 15 virtual machine to test. > > Cheers > Antoine > > PS: emacs 24 from source also works fine. > > > >> >> On Fri, Mar 23, 2012 at 6:08 AM, Antoine Martin > > wrote: >> >> On 03/23/2012 02:26 AM, Neal Becker wrote: >> > I tried with both emacs GNU Emacs 24.0.93.1 and with konsole. >> I've just tried with the default Fedora 16 Emacs (23.3.1) which worked >> fine. I am now installing emacs 24 from source. (600MB d/l - slow DSL..) >> I've also tried konsole v2.8.1, and still no problem.. >> >> There must be something different about your environment that makes it >> fail. Maybe your desktop's environment variables are interfering. >> Can you try launching the applications from a "clean" session, ie: one >> with a sanitized environment (maybe via ssh to localhost to clear it?). >> >> Antoine >> >> > konsole is Qt, but it looks like emacs is gtk. >> >> > >> > As mouse cursor goes over the menu, the cursor does not change, >> and the >> > menu is not sensitive. Click on 'File' for example does nothing. >> > >> > >> > On Thu, Mar 22, 2012 at 3:04 PM, Antoine Martin >> >> > >> wrote: >> > >> > On 03/22/2012 09:18 PM, Neal Becker wrote: >> > > Looks like xpra-0.1.0 is useless on Fedora 16. Nothing >> happens when >> > > clicking on menus - which seems to be a pretty serious problem. >> > Are you talking about xpra's own tray menu or about a specific >> > application you are running through xpra and which is having >> problems >> > displaying its own menus properly? And if the latter, which >> application >> > is it? Does it happen with other applications? >> > >> > Is it a Qt application by any chance? >> > If this is the case then this may well be a theme/style >> problem which >> > can be remedied using an environment variable I just cannot >> find right >> > now... >> > Note for those who hit this issue, you may be able to get those Qt >> > styles to work properly using an Xvfb server with the required >> > extensions, ie: >> > https://xpra.org/Xdummy.html >> > >> > Cheers >> > Antoine >> > _______________________________________________ >> > shifter-users mailing list >> > shifter-users at lists.devloop.org.uk >> >> > > > >> > http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > >> > >> >> > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From troycauble at gmail.com Tue Mar 27 21:33:51 2012 From: troycauble at gmail.com (Troy Cauble) Date: Tue, 27 Mar 2012 16:33:51 -0400 Subject: [winswitch] xpra and the letter A Message-ID: Running xpra start :100 DISPLAY=:100 xterm on my ubuntu box and /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 on my Macbook I get an xterm that works except the letter A won't type (!) and copy and paste don't work. Both of my winswitch installs were updated last night. From antoine at nagafix.co.uk Tue Mar 27 21:42:37 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 28 Mar 2012 03:42:37 +0700 Subject: [winswitch] xpra and the letter A In-Reply-To: References: Message-ID: <4F72263D.2040502@nagafix.co.uk> On 03/28/2012 03:33 AM, Troy Cauble wrote: > Running > xpra start :100 > DISPLAY=:100 xterm > on my ubuntu box > > and > /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 > > on my Macbook > > I get an xterm that works except > the letter A won't type (!) Hah, that is a bit of a problem! Can you post the xpra server log? I suspect that the keymap ran out of free keys to use to map your client keys.. Is it just the uppercase version or, any 'a'? The default keyboard map (us) should have an 'a' anyway, very strange. Please post "xmodmap -pke" in an xpra client window. > and copy and paste don't work. Cut&paste lacks a decent API on Mac OS X, so it may never be supported properly (if at all): https://xpra.org/trac/ticket/11 Antoine > > Both of my winswitch installs were updated last night. > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From troycauble at gmail.com Tue Mar 27 21:51:12 2012 From: troycauble at gmail.com (Troy Cauble) Date: Tue, 27 Mar 2012 16:51:12 -0400 Subject: [winswitch] xpra and the letter A In-Reply-To: <4F72263D.2040502@nagafix.co.uk> References: <4F72263D.2040502@nagafix.co.uk> Message-ID: See attached. -troy On Tue, Mar 27, 2012 at 4:42 PM, Antoine Martin wrote: > On 03/28/2012 03:33 AM, Troy Cauble wrote: >> Running >> xpra start :100 >> DISPLAY=:100 xterm >> on my ubuntu box >> >> and >> /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 >> >> on my Macbook >> >> I get an xterm that works except >> the letter A won't type (!) > Hah, that is a bit of a problem! Can you post the xpra server log? > I suspect that the keymap ran out of free keys to use to map your client > keys.. Is it just the uppercase version or, any 'a'? > The default keyboard map (us) should have an 'a' anyway, very strange. > Please post "xmodmap -pke" in an xpra client window. > >> and copy and paste don't work. > Cut&paste lacks a decent API on Mac OS X, so it may never be supported > properly (if at all): > https://xpra.org/trac/ticket/11 > > Antoine > >> >> Both of my winswitch installs were updated last night. >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users -------------- next part -------------- keycode 8 = keycode 9 = Escape NoSymbol Escape NoSymbol Escape keycode 10 = section plusminus section plusminus section plusminus keycode 11 = 2 at 2 at trademark EuroSign keycode 12 = 3 numbersign 3 numbersign sterling keycode 13 = 4 dollar 4 dollar cent keycode 14 = 5 percent 5 percent infinity keycode 15 = 6 asciicircum 6 asciicircum section keycode 16 = 7 ampersand 7 ampersand paragraph doubledagger keycode 17 = 8 asterisk 8 asterisk enfilledcircbullet degree keycode 18 = 9 parenleft 9 parenleft ordfeminine periodcentered keycode 19 = 0 parenright 0 parenright masculine singlelowquotemark keycode 20 = minus underscore minus underscore endash emdash keycode 21 = equal plus equal plus notequal plusminus keycode 22 = BackSpace NoSymbol BackSpace NoSymbol BackSpace keycode 23 = Tab ISO_Left_Tab Tab ISO_Left_Tab Tab keycode 24 = q Q q Q oe OE keycode 25 = w W w W doublelowquotemark keycode 26 = e E e E dead_acute acute keycode 27 = r R r R registered keycode 28 = t T t T dagger caron keycode 29 = y Y y Y yen Aacute keycode 30 = u U u U dead_diaeresis diaeresis keycode 31 = i I i I dead_circumflex keycode 32 = o O o O oslash Oslash keycode 33 = p P p P Greek_pi Greek_PI keycode 34 = bracketleft braceleft bracketleft braceleft leftdoublequotemark rightdoublequotemark keycode 35 = bracketright braceright bracketright braceright leftsinglequotemark rightsinglequotemark keycode 36 = Return NoSymbol Return NoSymbol Return keycode 37 = Control_L NoSymbol Control_L NoSymbol Control_L keycode 38 = a A a A aring Aring keycode 39 = s S s S ssharp Iacute keycode 40 = d D d D partialderivative Icircumflex keycode 41 = f F f F function Idiaeresis keycode 42 = g G g G copyright doubleacute keycode 43 = h H h H abovedot Oacute keycode 44 = j J j J ocircumflex Ocircumflex keycode 45 = k K k K k K keycode 46 = l L l L notsign Ograve keycode 47 = semicolon colon semicolon colon ellipsis Uacute keycode 48 = apostrophe quotedbl apostrophe quotedbl ae AE keycode 49 = grave asciitilde grave asciitilde dead_grave grave keycode 50 = Shift_L NoSymbol Shift_L NoSymbol Shift_L keycode 51 = backslash bar backslash bar guillemotleft guillemotright keycode 52 = z Z z Z Greek_OMEGA cedilla keycode 53 = x X x X ogonek keycode 54 = c C c C ccedilla Ccedilla keycode 55 = v V v V radical keycode 56 = b B b B integral idotless keycode 57 = n N n N n N keycode 58 = m M m M mu Acircumflex keycode 59 = comma less comma less lessthanequal macron keycode 60 = period greater period greater greaterthanequal breve keycode 61 = slash question slash question division questiondown keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R keycode 63 = KP_Multiply NoSymbol KP_Multiply NoSymbol KP_Multiply keycode 64 = Alt_L NoSymbol Alt_L NoSymbol Alt_L keycode 65 = space nobreakspace space nobreakspace space nobreakspace keycode 66 = Caps_Lock NoSymbol Caps_Lock NoSymbol Caps_Lock keycode 67 = keycode 68 = keycode 69 = keycode 70 = keycode 71 = keycode 72 = keycode 73 = keycode 74 = keycode 75 = keycode 76 = keycode 77 = keycode 78 = keycode 79 = keycode 80 = keycode 81 = keycode 82 = KP_Subtract NoSymbol KP_Subtract NoSymbol KP_Subtract keycode 83 = KP_1 NoSymbol KP_1 NoSymbol KP_1 keycode 84 = KP_2 NoSymbol KP_2 NoSymbol KP_2 keycode 85 = KP_3 NoSymbol KP_3 NoSymbol KP_3 keycode 86 = KP_Add NoSymbol KP_Add NoSymbol KP_Add keycode 87 = KP_5 NoSymbol KP_5 NoSymbol KP_5 keycode 88 = KP_6 NoSymbol KP_6 NoSymbol KP_6 keycode 89 = KP_7 NoSymbol KP_7 NoSymbol KP_7 keycode 90 = keycode 91 = KP_8 NoSymbol KP_8 NoSymbol KP_8 keycode 92 = KP_9 NoSymbol KP_9 NoSymbol KP_9 keycode 93 = 1 exclam 1 exclam exclamdown keycode 94 = keycode 95 = keycode 96 = keycode 97 = keycode 98 = keycode 99 = keycode 100 = keycode 101 = keycode 102 = keycode 103 = keycode 104 = keycode 105 = Control_R NoSymbol Control_R NoSymbol Control_R keycode 106 = KP_Divide NoSymbol KP_Divide NoSymbol KP_Divide keycode 107 = keycode 108 = Alt_R NoSymbol Alt_R NoSymbol Alt_R keycode 109 = keycode 110 = keycode 111 = Up slash Up slash Up slash keycode 112 = keycode 113 = Left plus Left plus Left plus keycode 114 = Right asterisk Right asterisk Right asterisk keycode 115 = End NoSymbol End NoSymbol End keycode 116 = Down equal Down equal Down equal keycode 117 = Next NoSymbol Next NoSymbol Next keycode 118 = keycode 119 = Delete NoSymbol Delete NoSymbol Delete keycode 120 = keycode 121 = keycode 122 = keycode 123 = keycode 124 = keycode 125 = KP_Equal NoSymbol KP_Equal NoSymbol KP_Equal keycode 126 = keycode 127 = keycode 128 = 0x271a0c0 0x270fed0 0x271a0c0 0x270fed0 0x271a1b0 0x271a2d0 keycode 129 = KP_Decimal NoSymbol KP_Decimal NoSymbol KP_Decimal keycode 130 = keycode 131 = keycode 132 = Return NoSymbol Return NoSymbol Return keycode 133 = keycode 134 = keycode 135 = keycode 136 = Meta_R NoSymbol Meta_R NoSymbol Meta_R keycode 137 = Meta_L NoSymbol Meta_L NoSymbol Meta_L keycode 138 = keycode 139 = keycode 140 = keycode 141 = keycode 142 = keycode 143 = keycode 144 = keycode 145 = keycode 146 = keycode 147 = keycode 148 = keycode 149 = Escape NoSymbol Escape NoSymbol Escape keycode 150 = keycode 151 = keycode 152 = keycode 153 = Return NoSymbol Return NoSymbol Return keycode 154 = KP_0 NoSymbol KP_0 NoSymbol KP_0 keycode 155 = keycode 156 = keycode 157 = keycode 158 = keycode 159 = keycode 160 = keycode 161 = KP_4 NoSymbol KP_4 NoSymbol KP_4 keycode 162 = keycode 163 = keycode 164 = keycode 165 = keycode 166 = keycode 167 = keycode 168 = keycode 169 = keycode 170 = keycode 171 = keycode 172 = keycode 173 = keycode 174 = keycode 175 = keycode 176 = keycode 177 = keycode 178 = keycode 179 = keycode 180 = keycode 181 = keycode 182 = Home NoSymbol Home NoSymbol Home keycode 183 = Prior NoSymbol Prior NoSymbol Prior keycode 184 = Left NoSymbol Left NoSymbol Left keycode 185 = keycode 186 = keycode 187 = keycode 188 = keycode 189 = keycode 190 = keycode 191 = keycode 192 = keycode 193 = keycode 194 = keycode 195 = keycode 196 = keycode 197 = Right NoSymbol Right NoSymbol Right keycode 198 = Down NoSymbol Down NoSymbol Down keycode 199 = keycode 200 = keycode 201 = keycode 202 = Up NoSymbol Up NoSymbol Up keycode 203 = Mode_switch NoSymbol Mode_switch NoSymbol Mode_switch keycode 204 = NoSymbol Alt_L NoSymbol Alt_L NoSymbol Alt_L keycode 205 = NoSymbol Meta_L NoSymbol Meta_L NoSymbol Meta_L keycode 206 = NoSymbol Super_L NoSymbol Super_L NoSymbol Super_L keycode 207 = NoSymbol Hyper_L NoSymbol Hyper_L NoSymbol Hyper_L keycode 208 = XF86AudioPlay NoSymbol XF86AudioPlay NoSymbol XF86AudioPlay keycode 209 = XF86AudioPause NoSymbol XF86AudioPause NoSymbol XF86AudioPause keycode 210 = XF86Launch3 NoSymbol XF86Launch3 NoSymbol XF86Launch3 keycode 211 = XF86Launch4 NoSymbol XF86Launch4 NoSymbol XF86Launch4 keycode 212 = XF86LaunchB NoSymbol XF86LaunchB NoSymbol XF86LaunchB keycode 213 = XF86Suspend NoSymbol XF86Suspend NoSymbol XF86Suspend keycode 214 = XF86Close NoSymbol XF86Close NoSymbol XF86Close keycode 215 = XF86AudioPlay NoSymbol XF86AudioPlay NoSymbol XF86AudioPlay keycode 216 = XF86AudioForward NoSymbol XF86AudioForward NoSymbol XF86AudioForward keycode 217 = keycode 218 = Print NoSymbol Print NoSymbol Print keycode 219 = keycode 220 = XF86WebCam NoSymbol XF86WebCam NoSymbol XF86WebCam keycode 221 = keycode 222 = keycode 223 = XF86Mail NoSymbol XF86Mail NoSymbol XF86Mail keycode 224 = XF86Messenger NoSymbol XF86Messenger NoSymbol XF86Messenger keycode 225 = XF86Search NoSymbol XF86Search NoSymbol XF86Search keycode 226 = XF86Go NoSymbol XF86Go NoSymbol XF86Go keycode 227 = XF86Finance NoSymbol XF86Finance NoSymbol XF86Finance keycode 228 = XF86Game NoSymbol XF86Game NoSymbol XF86Game keycode 229 = XF86Shop NoSymbol XF86Shop NoSymbol XF86Shop keycode 230 = keycode 231 = Cancel NoSymbol Cancel NoSymbol Cancel keycode 232 = XF86MonBrightnessDown NoSymbol XF86MonBrightnessDown NoSymbol XF86MonBrightnessDown keycode 233 = XF86MonBrightnessUp NoSymbol XF86MonBrightnessUp NoSymbol XF86MonBrightnessUp keycode 234 = XF86AudioMedia NoSymbol XF86AudioMedia NoSymbol XF86AudioMedia keycode 235 = XF86Display NoSymbol XF86Display NoSymbol XF86Display keycode 236 = XF86KbdLightOnOff NoSymbol XF86KbdLightOnOff NoSymbol XF86KbdLightOnOff keycode 237 = XF86KbdBrightnessDown NoSymbol XF86KbdBrightnessDown NoSymbol XF86KbdBrightnessDown keycode 238 = XF86KbdBrightnessUp NoSymbol XF86KbdBrightnessUp NoSymbol XF86KbdBrightnessUp keycode 239 = XF86Send NoSymbol XF86Send NoSymbol XF86Send keycode 240 = XF86Reply NoSymbol XF86Reply NoSymbol XF86Reply keycode 241 = XF86MailForward NoSymbol XF86MailForward NoSymbol XF86MailForward keycode 242 = XF86Save NoSymbol XF86Save NoSymbol XF86Save keycode 243 = XF86Documents NoSymbol XF86Documents NoSymbol XF86Documents keycode 244 = XF86Battery NoSymbol XF86Battery NoSymbol XF86Battery keycode 245 = XF86Bluetooth NoSymbol XF86Bluetooth NoSymbol XF86Bluetooth keycode 246 = XF86WLAN NoSymbol XF86WLAN NoSymbol XF86WLAN keycode 247 = keycode 248 = keycode 249 = keycode 250 = keycode 251 = keycode 252 = keycode 253 = keycode 254 = keycode 255 = From troycauble at gmail.com Tue Mar 27 21:53:18 2012 From: troycauble at gmail.com (Troy Cauble) Date: Tue, 27 Mar 2012 16:53:18 -0400 Subject: [winswitch] xpra and the letter A In-Reply-To: References: <4F72263D.2040502@nagafix.co.uk> Message-ID: And it was lower and upper case A. The other lowercase letters worked. On Tue, Mar 27, 2012 at 4:51 PM, Troy Cauble wrote: > See attached. > -troy > > On Tue, Mar 27, 2012 at 4:42 PM, Antoine Martin wrote: >> On 03/28/2012 03:33 AM, Troy Cauble wrote: >>> Running >>> xpra start :100 >>> DISPLAY=:100 xterm >>> on my ubuntu box >>> >>> and >>> /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 >>> >>> on my Macbook >>> >>> I get an xterm that works except >>> the letter A won't type (!) >> Hah, that is a bit of a problem! Can you post the xpra server log? >> I suspect that the keymap ran out of free keys to use to map your client >> keys.. Is it just the uppercase version or, any 'a'? >> The default keyboard map (us) should have an 'a' anyway, very strange. >> Please post "xmodmap -pke" in an xpra client window. >> >>> and copy and paste don't work. >> Cut&paste lacks a decent API on Mac OS X, so it may never be supported >> properly (if at all): >> https://xpra.org/trac/ticket/11 >> >> Antoine >> >>> >>> Both of my winswitch installs were updated last night. >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users at lists.devloop.org.uk >>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users From troycauble at gmail.com Tue Mar 27 22:15:25 2012 From: troycauble at gmail.com (Troy Cauble) Date: Tue, 27 Mar 2012 17:15:25 -0400 Subject: [winswitch] xpra and the letter A In-Reply-To: References: <4F72263D.2040502@nagafix.co.uk> Message-ID: Just for fun I ssh'd to my server and ran 'xpra attach :100' locally and back through my ssh tunnel. The letter A/a worked on that. But when I backspaced to my prompt (which I think would cause a BELL), xpra attach died with $ xpra attach :100 Xlib: extension "RANDR" missing on display "localhost:12.0". cannot import dbus.glib notification wrapper: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files mmap enabled using /tmp/xpra.k81xUq.mmap disabling compression Attached (press Control-C to detach) The program 'xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'XkbBadKeyboard'. (Details: serial 807 error_code 143 request_code 140 minor_code 3) (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.) On Tue, Mar 27, 2012 at 4:53 PM, Troy Cauble wrote: > And it was lower and upper case A. ?The other lowercase letters worked. > > On Tue, Mar 27, 2012 at 4:51 PM, Troy Cauble wrote: >> See attached. >> -troy >> >> On Tue, Mar 27, 2012 at 4:42 PM, Antoine Martin wrote: >>> On 03/28/2012 03:33 AM, Troy Cauble wrote: >>>> Running >>>> xpra start :100 >>>> DISPLAY=:100 xterm >>>> on my ubuntu box >>>> >>>> and >>>> /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 >>>> >>>> on my Macbook >>>> >>>> I get an xterm that works except >>>> the letter A won't type (!) >>> Hah, that is a bit of a problem! Can you post the xpra server log? >>> I suspect that the keymap ran out of free keys to use to map your client >>> keys.. Is it just the uppercase version or, any 'a'? >>> The default keyboard map (us) should have an 'a' anyway, very strange. >>> Please post "xmodmap -pke" in an xpra client window. >>> >>>> and copy and paste don't work. >>> Cut&paste lacks a decent API on Mac OS X, so it may never be supported >>> properly (if at all): >>> https://xpra.org/trac/ticket/11 >>> >>> Antoine >>> >>>> >>>> Both of my winswitch installs were updated last night. >>>> _______________________________________________ >>>> shifter-users mailing list >>>> shifter-users at lists.devloop.org.uk >>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>> >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users at lists.devloop.org.uk >>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users From troycauble at gmail.com Wed Mar 28 03:40:14 2012 From: troycauble at gmail.com (Troy Cauble) Date: Tue, 27 Mar 2012 22:40:14 -0400 Subject: [winswitch] xpra and the letter A In-Reply-To: References: <4F72263D.2040502@nagafix.co.uk> Message-ID: FYI, I rolled back to xpra_0.0.7.34-1_amd64.deb on the ubuntu box and winswitch 0.12.9 on the mac and they work. -troy On Tue, Mar 27, 2012 at 5:15 PM, Troy Cauble wrote: > Just for fun I ssh'd to my server and ran 'xpra attach :100' locally > and back through my ssh tunnel. > The letter A/a worked on that. ?But when I backspaced to my prompt > (which I think would cause a BELL), > xpra attach died with > > $ xpra attach :100 > Xlib: ?extension "RANDR" missing on display "localhost:12.0". > cannot import dbus.glib notification wrapper: > org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.Notifications was not provided by any .service files > mmap enabled using /tmp/xpra.k81xUq.mmap > disabling compression > Attached (press Control-C to detach) > The program 'xpra' received an X Window System error. > This probably reflects a bug in the program. > The error was 'XkbBadKeyboard'. > ?(Details: serial 807 error_code 143 request_code 140 minor_code 3) > ?(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.) > > > > > On Tue, Mar 27, 2012 at 4:53 PM, Troy Cauble wrote: >> And it was lower and upper case A. ?The other lowercase letters worked. >> >> On Tue, Mar 27, 2012 at 4:51 PM, Troy Cauble wrote: >>> See attached. >>> -troy >>> >>> On Tue, Mar 27, 2012 at 4:42 PM, Antoine Martin wrote: >>>> On 03/28/2012 03:33 AM, Troy Cauble wrote: >>>>> Running >>>>> xpra start :100 >>>>> DISPLAY=:100 xterm >>>>> on my ubuntu box >>>>> >>>>> and >>>>> /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 >>>>> >>>>> on my Macbook >>>>> >>>>> I get an xterm that works except >>>>> the letter A won't type (!) >>>> Hah, that is a bit of a problem! Can you post the xpra server log? >>>> I suspect that the keymap ran out of free keys to use to map your client >>>> keys.. Is it just the uppercase version or, any 'a'? >>>> The default keyboard map (us) should have an 'a' anyway, very strange. >>>> Please post "xmodmap -pke" in an xpra client window. >>>> >>>>> and copy and paste don't work. >>>> Cut&paste lacks a decent API on Mac OS X, so it may never be supported >>>> properly (if at all): >>>> https://xpra.org/trac/ticket/11 >>>> >>>> Antoine >>>> >>>>> >>>>> Both of my winswitch installs were updated last night. >>>>> _______________________________________________ >>>>> shifter-users mailing list >>>>> shifter-users at lists.devloop.org.uk >>>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>> >>>> _______________________________________________ >>>> 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 Wed Mar 28 09:04:54 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 28 Mar 2012 15:04:54 +0700 Subject: [winswitch] xpra and the letter A In-Reply-To: References: <4F72263D.2040502@nagafix.co.uk> Message-ID: <4F72C626.9060806@nagafix.co.uk> Thanks for all the details, I've moved it all to 2 new tickets: https://xpra.org/trac/ticket/92 https://xpra.org/trac/ticket/93 Feel free to add more info there if I've missed anything. Antoine On 03/28/2012 09:40 AM, Troy Cauble wrote: > FYI, I rolled back to xpra_0.0.7.34-1_amd64.deb on the ubuntu box and > winswitch 0.12.9 on the mac and they work. > > -troy > > On Tue, Mar 27, 2012 at 5:15 PM, Troy Cauble wrote: >> Just for fun I ssh'd to my server and ran 'xpra attach :100' locally >> and back through my ssh tunnel. >> The letter A/a worked on that. But when I backspaced to my prompt >> (which I think would cause a BELL), >> xpra attach died with >> >> $ xpra attach :100 >> Xlib: extension "RANDR" missing on display "localhost:12.0". >> cannot import dbus.glib notification wrapper: >> org.freedesktop.DBus.Error.ServiceUnknown: The name >> org.freedesktop.Notifications was not provided by any .service files >> mmap enabled using /tmp/xpra.k81xUq.mmap >> disabling compression >> Attached (press Control-C to detach) >> The program 'xpra' received an X Window System error. >> This probably reflects a bug in the program. >> The error was 'XkbBadKeyboard'. >> (Details: serial 807 error_code 143 request_code 140 minor_code 3) >> (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.) >> >> >> >> >> On Tue, Mar 27, 2012 at 4:53 PM, Troy Cauble wrote: >>> And it was lower and upper case A. The other lowercase letters worked. >>> >>> On Tue, Mar 27, 2012 at 4:51 PM, Troy Cauble wrote: >>>> See attached. >>>> -troy >>>> >>>> On Tue, Mar 27, 2012 at 4:42 PM, Antoine Martin wrote: >>>>> On 03/28/2012 03:33 AM, Troy Cauble wrote: >>>>>> Running >>>>>> xpra start :100 >>>>>> DISPLAY=:100 xterm >>>>>> on my ubuntu box >>>>>> >>>>>> and >>>>>> /Applications/Window-Switch.app/Contents/Helpers/xpra attach ssh:mybox:100 >>>>>> >>>>>> on my Macbook >>>>>> >>>>>> I get an xterm that works except >>>>>> the letter A won't type (!) >>>>> Hah, that is a bit of a problem! Can you post the xpra server log? >>>>> I suspect that the keymap ran out of free keys to use to map your client >>>>> keys.. Is it just the uppercase version or, any 'a'? >>>>> The default keyboard map (us) should have an 'a' anyway, very strange. >>>>> Please post "xmodmap -pke" in an xpra client window. >>>>> >>>>>> and copy and paste don't work. >>>>> Cut&paste lacks a decent API on Mac OS X, so it may never be supported >>>>> properly (if at all): >>>>> https://xpra.org/trac/ticket/11 >>>>> >>>>> Antoine >>>>> >>>>>> >>>>>> Both of my winswitch installs were updated last night. >>>>>> _______________________________________________ >>>>>> shifter-users mailing list >>>>>> shifter-users at lists.devloop.org.uk >>>>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>>> >>>>> _______________________________________________ >>>>> shifter-users mailing list >>>>> shifter-users at lists.devloop.org.uk >>>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users From solenskiner at gmail.com Thu Mar 29 09:45:36 2012 From: solenskiner at gmail.com (Henrik Asp) Date: Thu, 29 Mar 2012 10:45:36 +0200 Subject: [winswitch] Can not connect to winswitch running on OS X Message-ID: Hey, I'm having some trouble setting up winswitch. I have a working connection from my OSX laptop to my Debian one. Connecting in the other direction doesn't work though. I can successfully connect to OSX with ssx -X, however runninng winswitch_stdio_socket returns "command not found". Updating my locate database and searching for it returns only the manual entry. Where to go from here? Henrik Asp ------------------------------ Phone no. +46 (0)722 137500 From solenskiner at gmail.com Thu Mar 29 10:19:49 2012 From: solenskiner at gmail.com (Henrik Asp) Date: Thu, 29 Mar 2012 11:19:49 +0200 Subject: [winswitch] Can not connect to winswitch running on OS X In-Reply-To: References: Message-ID: By the way, I'm running Aptosid (Debian Sid) fully updated with xserver 1:7.6+12, xpra 0.1.0.1+dfsg-1 and winswitch 0.12.12-1; and OS X 10.7.3 on an x86 mac with winswitch 0.12.12 and XQuartz 2.7.1 Henrik Asp ------------------------------ Phone no. +46 (0)722 137500 On Thu, Mar 29, 2012 at 10:45, Henrik Asp wrote: > Hey, > > I'm having some trouble setting up winswitch. I have a working connection > from my OSX laptop to my Debian one. Connecting in the other direction > doesn't work though. > I can successfully connect to OSX with ssx -X, however runninng > winswitch_stdio_socket returns "command not found". > Updating my locate database and searching for it returns only the manual > entry. Where to go from here? > Henrik Asp > ------------------------------ > Phone no. +46 (0)722 137500 > > From antoine at nagafix.co.uk Thu Mar 29 12:19:29 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 29 Mar 2012 18:19:29 +0700 Subject: [winswitch] Can not connect to winswitch running on OS X In-Reply-To: References: Message-ID: <4F744541.7050808@nagafix.co.uk> On 03/29/2012 03:45 PM, Henrik Asp wrote: > Hey, > > I'm having some trouble setting up winswitch. I have a working connection > from my OSX laptop to my Debian one. Connecting in the other direction > doesn't work though. > I can successfully connect to OSX with ssx -X, however runninng > winswitch_stdio_socket returns "command not found". Hah, yes, this is not going to work as it won't find the command. (the software is installed wherever you put it, not in a specific location on Mac OS X, so the command is not on your PATH) I've created a ticket for it and I'll see what I can do: https://winswitch.org/trac/ticket/195 I don't have a firewall on the macs I use for testing so I connect directly to the winswitch server without any need for ssh. (auto-configuration via mdns) Maybe you can try that (I am surprised you aren't doing this as this is so much easier and automatic) or open up the winswitch port through the firewall? Cheers Antoine > Updating my locate database and searching for it returns only the manual > entry. Where to go from here? > Henrik Asp > ------------------------------ > Phone no. +46 (0)722 137500 > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users