From rogeriobastos at dcc.ufba.br Wed Aug 1 05:24:23 2012 From: rogeriobastos at dcc.ufba.br (ROGERIO DE CARVALHO BASTOS) Date: Wed, 01 Aug 2012 01:24:23 -0300 Subject: [winswitch] xmodmap: No protocol specified In-Reply-To: <20120731152949.730870svc0emcrh9@webmail.dcc.ufba.br> References: <20120731143046.25486scgvpgvzy2u@webmail.dcc.ufba.br> <50181ECA.4060309@nagafix.co.uk> <20120731152949.730870svc0emcrh9@webmail.dcc.ufba.br> Message-ID: <20120801012423.20513k6vbkly58c7@webmail.dcc.ufba.br> Hi, I still get errors with xkbcomp, but the fonts problem was not related with this. I solve this one doing downgrade of libcairo. There is a bug in this lib that corrupt video memory, vide [1], [2], [3]. [1] https://bbs.archlinux.org/viewtopic.php?pid=1103190 [2] https://bugs.freedesktop.org/show_bug.cgi?id=47266 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377755 -- Rogerio de Carvalho Bastos http://wiki.dcc.ufba.br/Main/RogerioBastos From ndbecker2 at gmail.com Wed Aug 1 18:26:44 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 13:26:44 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50182017.1040906@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> Message-ID: xpra-0.5.0 fails on fedora f17 Built from srpm Fails to start: pra start --no-daemon :100 No handlers could be found for logger "xpra.protocol" Fatal server error: The '-logfile' option cannot be used with elevated privileges. Please consult the Fedora Project support at http://wiki.x.org for help. Xvfb command has terminated! xpra cannot continue removing socket /home/nbecker/.xpra/nbecker6-100 xpra-0.4.0 had been working on this machine (although I had built manually last time, not from srpm). From antoine at nagafix.co.uk Wed Aug 1 18:31:53 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 02 Aug 2012 00:31:53 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: References: <50182017.1040906@nagafix.co.uk> Message-ID: <50196809.2000509@nagafix.co.uk> On 08/02/2012 12:26 AM, Neal Becker wrote: > xpra-0.5.0 fails on fedora f17 > > Built from srpm > > Fails to start: > > > pra start --no-daemon :100 > No handlers could be found for logger "xpra.protocol" > > Fatal server error: > The '-logfile' option cannot be used with elevated privileges. This is a packaging issue which I will have to iron out before release (it's not easy unfortunately - distro packaging really is a curse). In the meantime: cp /usr/bin/Xorg /usr/local/bin/Xorg And use /usr/local/bin/Xorg in /etc/xpra/xpra.conf for the xvfb option. Any suggestions on how to obtain a non-suid Xorg binary from the installed suid one would be most welcome. Cheers Antoine > > Please consult the Fedora Project support > at http://wiki.x.org > for help. > > > Xvfb command has terminated! xpra cannot continue > > removing socket /home/nbecker/.xpra/nbecker6-100 > > xpra-0.4.0 had been working on this machine (although I had built > manually last time, not from srpm). > > From ndbecker2 at gmail.com Wed Aug 1 18:39:00 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 13:39:00 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50196809.2000509@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> Message-ID: So we've switched to xvfb by default? Well, it now works - but I have the xdpy issue. xdpyinfo reports 20x25dpi, while the correct value is 115x115 (iirc). On Wed, Aug 1, 2012 at 1:31 PM, Antoine Martin wrote: > On 08/02/2012 12:26 AM, Neal Becker wrote: > >> xpra-0.5.0 fails on fedora f17 >> >> Built from srpm >> >> Fails to start: >> >> >> pra start --no-daemon :100 >> No handlers could be found for logger "xpra.protocol" >> >> Fatal server error: >> The '-logfile' option cannot be used with elevated privileges. >> > This is a packaging issue which I will have to iron out before release > (it's not easy unfortunately - distro packaging really is a curse). > > In the meantime: > cp /usr/bin/Xorg /usr/local/bin/Xorg > And use /usr/local/bin/Xorg in /etc/xpra/xpra.conf for the xvfb option. > > Any suggestions on how to obtain a non-suid Xorg binary from the installed > suid one would be most welcome. > > Cheers > Antoine > > > > >> Please consult the Fedora Project support >> at http://wiki.x.org >> for help. >> >> >> Xvfb command has terminated! xpra cannot continue >> >> removing socket /home/nbecker/.xpra/nbecker6-**100 >> >> xpra-0.4.0 had been working on this machine (although I had built >> manually last time, not from srpm). >> >> >> > From antoine at nagafix.co.uk Wed Aug 1 18:48:42 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 02 Aug 2012 00:48:42 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> Message-ID: <50196BFA.7000206@nagafix.co.uk> On 08/02/2012 12:39 AM, Neal Becker wrote: > So we've switched to xvfb by default? Xdummy in place of Xvfb you mean? Well, sort of, the support has been there for ages. Distros have now started shipping a version of Xorg recent enough so it is "only" a matter of packaging it properly. (detecting support, and using the right value for xvfb in the system wide config defaults) I just wished they had installed the non-suid Xorg binary too... > Well, it now works - but I have the xdpy issue. xdpyinfo reports > 20x25dpi, while the correct value is 115x115 (iirc). Hah, let's follow this issue here: https://www.xpra.org/trac/ticket/163 Is this really a problem? What apps/toolkits use this info rather than Xft.dpi? Antoine > > On Wed, Aug 1, 2012 at 1:31 PM, Antoine Martin > wrote: > > On 08/02/2012 12:26 AM, Neal Becker wrote: > > xpra-0.5.0 fails on fedora f17 > > Built from srpm > > Fails to start: > > > pra start --no-daemon :100 > No handlers could be found for logger "xpra.protocol" > > Fatal server error: > The '-logfile' option cannot be used with elevated privileges. > > This is a packaging issue which I will have to iron out before > release (it's not easy unfortunately - distro packaging really is a > curse). > > In the meantime: > cp /usr/bin/Xorg /usr/local/bin/Xorg > And use /usr/local/bin/Xorg in /etc/xpra/xpra.conf for the xvfb option. > > Any suggestions on how to obtain a non-suid Xorg binary from the > installed suid one would be most welcome. > > Cheers > Antoine > > > > > Please consult the Fedora Project support > at http://wiki.x.org > for help. > > > Xvfb command has terminated! xpra cannot continue > > removing socket /home/nbecker/.xpra/nbecker6-__100 > > xpra-0.4.0 had been working on this machine (although I had built > manually last time, not from srpm). > > > > From ndbecker2 at gmail.com Wed Aug 1 18:52:48 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 13:52:48 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50196BFA.7000206@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> Message-ID: I remember when I tried xdummy I had this issue, so I thought I gave up on xdummy (maybe it's still being used?) Yes, it's an issue. I tested with latest emacs. Not a disaster, but not good. Then I tried konsole. The font is submicroscopic and not readable by any human. On Wed, Aug 1, 2012 at 1:48 PM, Antoine Martin wrote: > On 08/02/2012 12:39 AM, Neal Becker wrote: > >> So we've switched to xvfb by default? >> > Xdummy in place of Xvfb you mean? > > Well, sort of, the support has been there for ages. Distros have now > started shipping a version of Xorg recent enough so it is "only" a matter > of packaging it properly. (detecting support, and using the right value for > xvfb in the system wide config defaults) > I just wished they had installed the non-suid Xorg binary too... > > > Well, it now works - but I have the xdpy issue. xdpyinfo reports >> 20x25dpi, while the correct value is 115x115 (iirc). >> > Hah, let's follow this issue here: > https://www.xpra.org/trac/**ticket/163 > > Is this really a problem? What apps/toolkits use this info rather than > Xft.dpi? > > Antoine > > >> On Wed, Aug 1, 2012 at 1:31 PM, Antoine Martin > **> wrote: >> >> On 08/02/2012 12:26 AM, Neal Becker wrote: >> >> xpra-0.5.0 fails on fedora f17 >> >> Built from srpm >> >> Fails to start: >> >> >> pra start --no-daemon :100 >> No handlers could be found for logger "xpra.protocol" >> >> Fatal server error: >> The '-logfile' option cannot be used with elevated privileges. >> >> This is a packaging issue which I will have to iron out before >> release (it's not easy unfortunately - distro packaging really is a >> curse). >> >> In the meantime: >> cp /usr/bin/Xorg /usr/local/bin/Xorg >> And use /usr/local/bin/Xorg in /etc/xpra/xpra.conf for the xvfb >> option. >> >> Any suggestions on how to obtain a non-suid Xorg binary from the >> installed suid one would be most welcome. >> >> Cheers >> Antoine >> >> >> >> >> Please consult the Fedora Project support >> at http://wiki.x.org >> for help. >> >> >> Xvfb command has terminated! xpra cannot continue >> >> removing socket /home/nbecker/.xpra/nbecker6-_**_100 >> >> >> xpra-0.4.0 had been working on this machine (although I had built >> manually last time, not from srpm). >> >> >> >> >> > From ndbecker2 at gmail.com Wed Aug 1 19:04:38 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 14:04:38 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50196BFA.7000206@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> Message-ID: OK, I found I had an old config /etc/xpra/xorg.conf which was using xdummy. I mv'd it. Now, I get Fatal server error: xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) If I use the nosuid Xorg. I seem to recall seeing this before? From antoine at nagafix.co.uk Wed Aug 1 19:10:44 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 02 Aug 2012 01:10:44 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> Message-ID: <50197124.7070901@nagafix.co.uk> On 08/02/2012 01:04 AM, Neal Becker wrote: > OK, I found I had an old config /etc/xpra/xorg.conf which was using > xdummy. I mv'd it. This is not an old config. This is the new config that comes with 0.5.0, you should not need to remove it. If you do not want to use Xdummy, just comment out "xvfb=" in the config, or even set it to use Xvfb explicitly (the config contains examples for both) If you remove it, xpra *should* go back to using Xvfb as this is still the overall default. Unless you have another "xvfb=" option in ~/.xpra/xpra.conf, but since you didn't know about this file until I mentioned it, you don't ;) > Now, I get > > Fatal server error: > xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) > > If I use the nosuid Xorg. I seem to recall seeing this before? Weird, looks like an Xorg running with a non-Xdummy config. FWY: I am adding info to the DPI ticket, I cannot reproduce it here (story of my life) but others can, so we should be able to get to the bottom of this one. Antoine From ndbecker2 at gmail.com Wed Aug 1 19:20:47 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 14:20:47 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50197124.7070901@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> <50197124.7070901@nagafix.co.uk> Message-ID: If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I guess this is the old Xvfb version. Still wrong dpi, but not as bad as with xdummy. From antoine at nagafix.co.uk Wed Aug 1 19:33:11 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 02 Aug 2012 01:33:11 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> <50197124.7070901@nagafix.co.uk> Message-ID: <50197667.2090404@nagafix.co.uk> On 08/02/2012 01:20 AM, Neal Becker wrote: > If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I guess > this is the old Xvfb version. Still wrong dpi, but not as bad as with > xdummy. > Found a solution for you, just run this on your client before connecting with xpra: echo "Xft.dpi: 96" | xrdb - Looks like your DE (which one do you use?) or X11 startup scripts are not setting the Xft.dpi, so applications fallback to xdpyinfo-like data from somewhere (Xlib?) which has the wrong value. I will make a proper solution for trunk and 0.5.0 release. Thanks! Antoine From ndbecker2 at gmail.com Wed Aug 1 19:53:06 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 1 Aug 2012 14:53:06 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50197667.2090404@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> <50197124.7070901@nagafix.co.uk> <50197667.2090404@nagafix.co.uk> Message-ID: If I do this with xdummy, it's better. Fonts still look crappy compared to running emacs directly (or via ssh -X). On Wed, Aug 1, 2012 at 2:33 PM, Antoine Martin wrote: > On 08/02/2012 01:20 AM, Neal Becker wrote: > >> If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I guess >> this is the old Xvfb version. Still wrong dpi, but not as bad as with >> xdummy. >> >> Found a solution for you, just run this on your client before connecting > with xpra: > echo "Xft.dpi: 96" | xrdb - > > Looks like your DE (which one do you use?) or X11 startup scripts are not > setting the Xft.dpi, so applications fallback to xdpyinfo-like data from > somewhere (Xlib?) which has the wrong value. > > I will make a proper solution for trunk and 0.5.0 release. > > Thanks! > Antoine > From antoine at nagafix.co.uk Wed Aug 1 19:58:51 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 02 Aug 2012 01:58:51 +0700 Subject: [winswitch] DPI fonts issue (worse with Xdummy) [MOSTLY FIXED] - was xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> <50197124.7070901@nagafix.co.uk> <50197667.2090404@nagafix.co.uk> Message-ID: <50197C6B.4080107@nagafix.co.uk> On 08/02/2012 01:53 AM, Neal Becker wrote: > If I do this with xdummy, it's better. Fonts still look crappy compared > to running emacs directly (or via ssh -X). Can we continue this discussion on the ticket? https://www.xpra.org/trac/ticket/163#comment:6 (apologies to the list readers) You can attach screenshots there of what your "crappy" fonts look like. Be aware that since the rendering is done to a virtual screen, certain font features like smoothing/anti-aliasing and sub-pixel rendering will be difficult or simply impossible. Antoine > > On Wed, Aug 1, 2012 at 2:33 PM, Antoine Martin > wrote: > > On 08/02/2012 01:20 AM, Neal Becker wrote: > > If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I > guess > this is the old Xvfb version. Still wrong dpi, but not as bad > as with > xdummy. > > Found a solution for you, just run this on your client before > connecting with xpra: > echo "Xft.dpi: 96" | xrdb - > > Looks like your DE (which one do you use?) or X11 startup scripts > are not setting the Xft.dpi, so applications fallback to > xdpyinfo-like data from somewhere (Xlib?) which has the wrong value. > > I will make a proper solution for trunk and 0.5.0 release. > > Thanks! > Antoine > > From antoine at nagafix.co.uk Fri Aug 3 10:09:36 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 03 Aug 2012 16:09:36 +0700 Subject: [winswitch] DPI fonts issue (worse with Xdummy) [FIXED] - was xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 In-Reply-To: <50197C6B.4080107@nagafix.co.uk> References: <50182017.1040906@nagafix.co.uk> <50196809.2000509@nagafix.co.uk> <50196BFA.7000206@nagafix.co.uk> <50197124.7070901@nagafix.co.uk> <50197667.2090404@nagafix.co.uk> <50197C6B.4080107@nagafix.co.uk> Message-ID: <501B9550.2040004@nagafix.co.uk> trunk now supports setting the dpi with "xpra --dpi=NN", details here: https://www.xpra.org/trac/ticket/163#comment:7 Cheers Antoine On 08/02/2012 01:58 AM, Antoine Martin wrote: > On 08/02/2012 01:53 AM, Neal Becker wrote: >> If I do this with xdummy, it's better. Fonts still look crappy compared >> to running emacs directly (or via ssh -X). > Can we continue this discussion on the ticket? > https://www.xpra.org/trac/ticket/163#comment:6 > (apologies to the list readers) > > You can attach screenshots there of what your "crappy" fonts look like. > Be aware that since the rendering is done to a virtual screen, certain > font features like smoothing/anti-aliasing and sub-pixel rendering will > be difficult or simply impossible. > > Antoine > > > >> >> On Wed, Aug 1, 2012 at 2:33 PM, Antoine Martin > > wrote: >> >> On 08/02/2012 01:20 AM, Neal Becker wrote: >> >> If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I >> guess >> this is the old Xvfb version. Still wrong dpi, but not as bad >> as with >> xdummy. >> >> Found a solution for you, just run this on your client before >> connecting with xpra: >> echo "Xft.dpi: 96" | xrdb - >> >> Looks like your DE (which one do you use?) or X11 startup scripts >> are not setting the Xft.dpi, so applications fallback to >> xdpyinfo-like data from somewhere (Xlib?) which has the wrong value. >> >> I will make a proper solution for trunk and 0.5.0 release. >> >> Thanks! >> 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 Aug 17 07:47:29 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 17 Aug 2012 13:47:29 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.6 / xpra 0.4.2 / xpra 0.5.0-rc1 Message-ID: <502DE901.7040809@nagafix.co.uk> Hi, This update to the 0.3.x and 0.4.x stable branches fixes a number of bugs (full details below) As usual, the source can be found here: https://xpra.org/src/ And links to the binaries/repositories here: https://winswitch.org/downloads/ The upcoming 0.5 release is almost ready, you can find release candidate builds here: https://xpra.org/beta/ Cheers Antoine Release Notes: * fix clipboard atom packing (was more noticeable with qt and Java applications - sometimes causing crashes) * fix clipboard selection for non X11 clients: only the 'multiple' codepath requires the X11 bindings * fix python3 build * fix potential double free in x264 error path * fix logging format error on "window dimensions have changed.." (parameter grouping was wrong) * fix colour bleeding with x264 (ie: noticeable with green on black text) * remove incorrect and unnecessary callback to setup_xprops which may have caused the pulseaudio flag to use the wrong value * delay 'check packet size' to allow the limit to be raised - important over slower links where it triggers more easily * Ubuntu Lucid and Debian Squeeze builds now support both x264 and vpx via a statically linked codec module From antoine at nagafix.co.uk Mon Aug 20 15:37:53 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 20 Aug 2012 21:37:53 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.5.0 Message-ID: <50324BC1.7040106@nagafix.co.uk> Hi, This new stable release adds many improvements over previous releases, notably: faster network code, out of the box support for Xdummy (*), global and per-user preference files, automatic tuning of x264 image compression quality and speed, automatic encoding switching, DPI override support, fairer bandwidth allocation, new options, and also many fixes. As usual, the source can be found here: https://xpra.org/src/ And links to the binaries/repositories here: https://winswitch.org/downloads/ A WindowSwitch update will follow shortly so that MS Windows and Mac OS X users who use it can get the updated Xpra too. Cheers Antoine Full release notes: * new packet encoder written in C (much faster and data is now smaller too) * read provided /etc/xpra/xpra.conf and user's own ~/.xpra/xpra.conf * support Xdummy out of the box on platforms with recent enough versions of Xorg (and not installed suid) * pass dpi to server and allow clients to specify dpi on the command line * fix xsettings endianness problems * fix clipboard tokens sent twice on start * new command line options and UI to disable notifications forwarding, cursors and bell * MS Windows clients can now choose the remote clipboard they sync with ('clipboard', 'primary' or 'secondary') * x264: adapt colourspace conversion, encoding speed and picture quality according to link and encoding/decoding performance * automatically change video encoding: handle small region updates (ie: blinking cursor or spinner) without doing a full video frame refresh * fairer window batching calculations, better performance over low latency links and bandwidth constrained links * lower tcp socket connection timeout (10 seconds) * better compression of cursor data * log date and time with messages, better log messages (ie: "Ignoring ClientMessage..") * send more client and server version information (python, gtk, etc) * build cleanups: let distutils clean take care of removing all generated .c files * code cleanups: move all win32 specific headers to win32 tree, fix vpx compilation warnings, whitespace, etc * more reliable MS Windows build: detect missing/wrong DLLs and abort * removed old "--no-randr" option * drop compatibility with versions older than 0.3: we now assume the "raw_packets" feature is supported From antoine at nagafix.co.uk Mon Aug 20 15:43:02 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 20 Aug 2012 21:43:02 +0700 Subject: [winswitch] [ANNOUNCE] winswitch 0.12.15 Message-ID: <50324CF6.1020002@nagafix.co.uk> Hi, Version 0.12.15 is available now: http://winswitch.org/downloads/ This bug release contains many platform related fixes: MS Windows support for NX and ssh sessions, Mac OS X GStreamer video, SELinux warnings, Xpra "stop" command, etc. It also adds the latest Xpra 0.5.0 release to binary installers. Cheers Antoine Full release notes: * fix startup crash on osx * fix NX and ssh sessions support on MS Windows (would stop working after last session exited) * fix Xpra "force stop" (now needs password) * fix GStreamer video: try to use the default video plugin if preferences are not set * fix mDNS warning on startup (dialog was making the UI unresponsive) * fix default protocol options were ignored when not using dialogs to start sessions * fix SELinux warning counter: honour it and only shown the warning 3 times * support for Xpra 0.5 (new log file format, automatic xvfb settings) * osx GStreamer fixes: add support for menu, use SDL output (no need for x11) * osx now includes the Xpra launcher as an embedded application * use packagekit for installing new protocols easily * if sshd is not installed, assume that ssh mode will not work * avoid warning that "xpra is too old" when it is not installed * various cleanups From ndbecker2 at gmail.com Mon Aug 20 15:53:38 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Mon, 20 Aug 2012 10:53:38 -0400 Subject: [winswitch] [ANNOUNCE] winswitch 0.12.15 In-Reply-To: <50324CF6.1020002@nagafix.co.uk> References: <50324CF6.1020002@nagafix.co.uk> Message-ID: Cannot build winswitch from srpm on fedora 17: rpmbuild -ba rpmbuild/SPECS/winswitch.spec Traceback (most recent call last): File "", line 1, in ImportError: No module named winswitch error: line 72: Empty tag: Version: From antoine at nagafix.co.uk Mon Aug 20 16:04:37 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 20 Aug 2012 22:04:37 +0700 Subject: [winswitch] [ANNOUNCE] winswitch 0.12.15 In-Reply-To: References: <50324CF6.1020002@nagafix.co.uk> Message-ID: <50325205.3040401@nagafix.co.uk> On 08/20/2012 09:53 PM, Neal Becker wrote: > Cannot build winswitch from srpm on fedora 17: > > rpmbuild -ba rpmbuild/SPECS/winswitch.spec > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named winswitch > error: line 72: Empty tag: Version: Thanks for reporting this. Packaging for all these platforms really is a curse! I will try to address this for the next release. Antoine From 1kenthomas at 1kenthomas.com Wed Aug 22 05:46:41 2012 From: 1kenthomas at 1kenthomas.com (Kenneth Thomas) Date: Tue, 21 Aug 2012 23:46:41 -0500 Subject: [winswitch] Lost Keybindings, Ubuntu 12-04, xpra .4x ? Message-ID: Hello all, I'm experiencing issues (failure) of bindings to cursor, Pg*** keys using xpra .4x (all versions; running latest) under Ubuntu 12.04 (after upgrade). Googling + list search doesn't seem to reveal anything useful. Please direct me to previous discussion/docs if I've missed anything. Thanks, Ken From antoine at nagafix.co.uk Wed Aug 22 05:51:44 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 22 Aug 2012 11:51:44 +0700 Subject: [winswitch] Lost Keybindings, Ubuntu 12-04, xpra .4x ? In-Reply-To: References: Message-ID: <50346560.3090001@nagafix.co.uk> Hi, On 08/22/2012 11:46 AM, Kenneth Thomas wrote: > Hello all, > > I'm experiencing issues (failure) of bindings to cursor, Pg*** keys using > xpra .4x (all versions; running latest) under Ubuntu 12.04 (after > upgrade). I don't understand what that means! "bindings to cursor"? "after upgrade" - upgrade of what? FYI: latest xpra is 0.5.x as of yesterday... Cheers Antoine > Googling + list search doesn't seem to reveal anything useful. > Please direct me to previous discussion/docs if I've missed anything. > > 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 Fri Aug 24 22:00:11 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 25 Aug 2012 04:00:11 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.4.3 / xpra 0.5.1 Message-ID: <5037EB5B.4090407@nagafix.co.uk> Hi, This minor update to the 0.4.x and 0.5.x stable branches fixes a number of bugs (full details below) As usual, the source can be found here: https://xpra.org/src/ Links to the binaries/repositories here: https://winswitch.org/downloads/ Direct binary downloads are here: https://xpra.org/dists/ Cheers Antoine Fixes in 0.5.x branch only: * fix DPI issue with Xdummy: set virtual screen to 96dpi by default * damage data queue batch factor was being calculated but not used * ensure we update the data we use for calculations (was using zero) * ensure "send_bell" is initialized before use * add missing path string in warning message * fix test code compatibility with older xpra versions Fixes for both branches: * avoid looping forever doing maths on 'infinity' value * fix incomplete cloning of batch config attributes * statistics shown for 'damage_packet_queue_pixels' were incorrect From 1kenthomas at 1kenthomas.com Tue Aug 28 20:51:02 2012 From: 1kenthomas at 1kenthomas.com (Kenneth Thomas) Date: Tue, 28 Aug 2012 14:51:02 -0500 Subject: [winswitch] Lost Keybindings, Ubuntu 12-04, xpra .4x ? In-Reply-To: References: Message-ID: WRT: >>I've lost... [snip] >I don't understand what that means! "bindings to cursor"? Sorry; was trying verbosity set to low... I mean, keys such as the cursor, PgUp/PgDw & etc are no longer bound correctly... either do not work at all, or produce the wrong output. > "after upgrade" - upgrade of what? After upgrade of Ubuntu from 11.10 to 12.04... > FYI: latest xpra is 0.5.x as of yesterday... Fails to run under my install of 12.04; haven't tested on any other system. Thanks, Ken From antoine at nagafix.co.uk Wed Aug 29 12:32:52 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 29 Aug 2012 18:32:52 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.7 / 0.4.4 / 0.5.2 - and 0.6.0 beta Message-ID: <503DFDE4.1020206@nagafix.co.uk> Hi, This minor update to the stable branches fixes a number of bugs (full details below) Please note that there is now an RPM repository for CentOS and Fedora: http://winswitch.org/downloads/rpm-repository.html The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine Fixes for all branches: * fix zlib compression in raw packet mode: always flush the buffer * fix big clipboard packets causing disconnection: just drop them * force disconnection after irrecoverable network parsing error * fix window refresh: do not skip all windows after a hidden one! 0.3.x only: * support compressed cursors * fix incomplete cloning of attributes causing default values to be used 0.4.x and 0.5.x only: * fix xpra launcher icon lookup on *nix From ndbecker2 at gmail.com Wed Aug 29 12:55:03 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 29 Aug 2012 07:55:03 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.7 / 0.4.4 / 0.5.2 - and 0.6.0 beta In-Reply-To: <503DFDE4.1020206@nagafix.co.uk> References: <503DFDE4.1020206@nagafix.co.uk> Message-ID: I just tried winswitch on fedora f17. I get a traceback: traceback.py:13:_print:ValueError: I/O operation on closed file Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 586, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 386, in _introspect_reply_handler self._introspect_error_handler(e) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 400, in _introspect_error_handler error) File "/usr/lib64/python2.7/logging/__init__.py", line 1166, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib64/python2.7/logging/__init__.py", line 1258, in _log self.handle(record) File "/usr/lib64/python2.7/logging/__init__.py", line 1268, in handle self.callHandlers(record) File "/usr/lib64/python2.7/logging/__init__.py", line 1308, in callHandlers hdlr.handle(record) File "/usr/lib64/python2.7/logging/__init__.py", line 748, in handle self.emit(record) File "/usr/lib64/python2.7/logging/__init__.py", line 874, in emit self.handleError(record) File "/usr/lib64/python2.7/logging/__init__.py", line 801, in handleError None, sys.stderr) File "/usr/lib64/python2.7/traceback.py", line 124, in print_exception _print(file, 'Traceback (most recent call last):') File "/usr/lib64/python2.7/traceback.py", line 13, in _print file.write(str+terminator) ValueError: I/O operation on closed file Local variables in innermost frame: file: terminator: '\n' str: 'Traceback (most recent call last):' From antoine at nagafix.co.uk Wed Aug 29 13:00:48 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 29 Aug 2012 19:00:48 +0700 Subject: [winswitch] winswitch traceback on F17 (was xpra 0.3.7 / 0.4.4 / 0.5.2 - and 0.6.0 beta) In-Reply-To: References: <503DFDE4.1020206@nagafix.co.uk> Message-ID: <503E0470.6070902@nagafix.co.uk> On 08/29/2012 06:55 PM, Neal Becker wrote: > I just tried winswitch on fedora f17. I get a traceback: > > traceback.py:13:_print:ValueError: I/O operation on closed file (...) Is this all there is?? None of this code is actually in winswitch.. What command line did you use to start it? Can you try adding: --debug-mode Thanks Antoine From ndbecker2 at gmail.com Wed Aug 29 13:01:59 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 29 Aug 2012 08:01:59 -0400 Subject: [winswitch] winswitch traceback on F17 (was xpra 0.3.7 / 0.4.4 / 0.5.2 - and 0.6.0 beta) In-Reply-To: <503E0470.6070902@nagafix.co.uk> References: <503DFDE4.1020206@nagafix.co.uk> <503E0470.6070902@nagafix.co.uk> Message-ID: This is what I get when I started winswitch using the 'start' menu (using kde, this is in the 'internet' app menu) On Wed, Aug 29, 2012 at 8:00 AM, Antoine Martin wrote: > On 08/29/2012 06:55 PM, Neal Becker wrote: > >> I just tried winswitch on fedora f17. I get a traceback: >> >> traceback.py:13:_print:**ValueError: I/O operation on closed file >> > (...) > Is this all there is?? None of this code is actually in winswitch.. > What command line did you use to start it? > Can you try adding: > --debug-mode > > Thanks > Antoine > From antoine at nagafix.co.uk Wed Aug 29 13:10:34 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 29 Aug 2012 19:10:34 +0700 Subject: [winswitch] Lost Keybindings, Ubuntu 12-04, xpra .4x ? In-Reply-To: References: Message-ID: <503E06BA.3050600@nagafix.co.uk> On 08/29/2012 02:51 AM, Kenneth Thomas wrote: > WRT: >>> I've lost... [snip] > >> I don't understand what that means! "bindings to cursor"? > > Sorry; was trying verbosity set to low... > > I mean, keys such as the cursor, PgUp/PgDw & etc are no longer bound > correctly... either do not work at all, or produce the wrong output. Please specify your keyboard settings: layout, especially anything unusual about your setup (if any). setxkbmap -print setxkbmap -query >> "after upgrade" - upgrade of what? > After upgrade of Ubuntu from 11.10 to 12.04... > >> FYI: latest xpra is 0.5.x as of yesterday... > Fails to run under my install of 12.04; haven't tested on any other system. "Fails to run" as in... Anything specific, any error messages? Obviously tested fine here before release. 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 Thu Aug 30 05:37:33 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 30 Aug 2012 11:37:33 +0700 Subject: [winswitch] winswitch traceback on F17 (was xpra 0.3.7 / 0.4.4 / 0.5.2 - and 0.6.0 beta) In-Reply-To: <503E0470.6070902@nagafix.co.uk> References: <503DFDE4.1020206@nagafix.co.uk> <503E0470.6070902@nagafix.co.uk> Message-ID: <503EEE0D.2060400@nagafix.co.uk> On 08/29/2012 07:00 PM, Antoine Martin wrote: > On 08/29/2012 06:55 PM, Neal Becker wrote: >> I just tried winswitch on fedora f17. I get a traceback: >> >> traceback.py:13:_print:ValueError: I/O operation on closed file > (...) > Is this all there is?? None of this code is actually in winswitch.. > What command line did you use to start it? > Can you try adding: > --debug-mode OK, 500MB of download later (..) and I can reproduce this, but not exactly the same way: this only happens with the auto-start in KDE (for me it works OK in other desktop environments, with or without autostart, and works OK in KDE when started from the application menu). The abrt backtrace includes much more useful information (including the name of the file which is closed and being written to), included below. I've added it all to a new ticket: https://winswitch.org/trac/ticket/217 Please follow up there. Cheers Antoine