From antoine at nagafix.co.uk Tue Jul 10 18:08:30 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 00:08:30 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 Message-ID: <4FFC618E.9050106@nagafix.co.uk> Hi, This third update to the stable 0.3.x branch contains numerous important bug fixes (more details in the release notes below). As usual, the source can be found here: http://xpra.org/src/ And the binaries here: http://winswitch.org/downloads/ Cheers Antoine Full release notes: * do not try to free the empty x264/vpx buffers after a decompression failure * fix Xvfb deadlock on shutdown * fix wrongly removing unix domain socket on startup failure * fix wrongly killing Xvfb on startup failure * fix race in network code and meta data packets * ensure clients use raw_packets if the server supports it (fixes 'gibberish' compressed packet errors) * fix screen resolution reported by the server * fix maximum packet size check wrongly dropping valid connections * honour the --no-tray command line argument * detect Xvfb startup failures and avoid taking over other displays * don't record invalid placeholder value for "server latency" * fix missing "damage-sequence" packet for sequence zero * fix window focus with some Tk based application (ie: git gui) * prevent large clipboard packets from causing the connection to drop * fix for connection with older clients and server without raw packet support and rgb24 encoding * high latency fix: reduce batch delay when screen updates slow down * non-US keyboard layout fix * correctly calculate min_batch_delay shown in statistics via "xpra info" * require x264-libs for x264 support on Fedora From ndbecker2 at gmail.com Tue Jul 10 19:29:33 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Tue, 10 Jul 2012 14:29:33 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFC618E.9050106@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> Message-ID: Thanks for 0.3.3. Just tried. Running emacs, it looks to me that the fonts look thin. I don't think that was the case on 0.3.2 (I might be mistaken). From ndbecker2 at gmail.com Tue Jul 10 20:11:25 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Tue, 10 Jul 2012 15:11:25 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> Message-ID: I thin the problem is this: runing on xpra: xdpyinfo: screen #0: dimensions: 3840x2560 pixels (975x650 millimeters) resolution: 100x100 dots per inch using ssh -X: xdpyinfo: screen #0: dimensions: 1680x1050 pixels (371x231 millimeters) resolution: 115x115 dots per inch On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker wrote: > Thanks for 0.3.3. > > Just tried. Running emacs, it looks to me that the fonts look thin. I > don't think that was the case on 0.3.2 (I might be mistaken). > > From antoine at nagafix.co.uk Tue Jul 10 20:15:58 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 02:15:58 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> Message-ID: <4FFC7F6E.30408@nagafix.co.uk> On 11/07/12 02:11, Neal Becker wrote: > I thin the problem is this: > > runing on xpra: > xdpyinfo: > > screen #0: > dimensions: 3840x2560 pixels (975x650 millimeters) > resolution: 100x100 dots per inch > > > using ssh -X: > > xdpyinfo: > > screen #0: > dimensions: 1680x1050 pixels (371x231 millimeters) > resolution: 115x115 dots per inch You are problably right, although this is nothing new in 0.3.3 The solution is well known too: https://xpra.org/Xdummy.html I have discussed the packaging issue today with some Debian developers and I intend to try to make it the default to use Xdummy on distributions that ship sufficiently recent X11 packages. Probably not before v0.5 though, as v0.4.0 is almost ready. Cheers Antoine > > > On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker > wrote: > > Thanks for 0.3.3. > > Just tried. Running emacs, it looks to me that the fonts look thin. > I don't think that was the case on 0.3.2 (I might be mistaken). > > From ndbecker2 at gmail.com Tue Jul 10 20:23:08 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Tue, 10 Jul 2012 15:23:08 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFC7F6E.30408@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> Message-ID: So if I'm on Fedora 17, I already have: rpm -qf /usr/bin/Xorg xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 So I'm guessing I would need: https://www.xpra.org/src/Xdummy/Fedora/17/xorg-x11-drv-dummy-0.3.4-9.fc17.x86_64.rpm And also since X is installed suid, need to follow instructions for that. Is that the basic install then? Any config needed? On Tue, Jul 10, 2012 at 3:15 PM, Antoine Martin wrote: > On 11/07/12 02:11, Neal Becker wrote: > >> I thin the problem is this: >> >> runing on xpra: >> xdpyinfo: >> >> screen #0: >> dimensions: 3840x2560 pixels (975x650 millimeters) >> resolution: 100x100 dots per inch >> >> >> using ssh -X: >> >> xdpyinfo: >> >> screen #0: >> dimensions: 1680x1050 pixels (371x231 millimeters) >> resolution: 115x115 dots per inch >> > You are problably right, although this is nothing new in 0.3.3 > > The solution is well known too: > https://xpra.org/Xdummy.html > > I have discussed the packaging issue today with some Debian developers and > I intend to try to make it the default to use Xdummy on distributions that > ship sufficiently recent X11 packages. > Probably not before v0.5 though, as v0.4.0 is almost ready. > > Cheers > Antoine > > > > >> >> On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker > > wrote: >> >> Thanks for 0.3.3. >> >> Just tried. Running emacs, it looks to me that the fonts look thin. >> I don't think that was the case on 0.3.2 (I might be mistaken). >> >> >> > > From antoine at nagafix.co.uk Tue Jul 10 20:25:35 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 02:25:35 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> Message-ID: <4FFC81AF.1070706@nagafix.co.uk> On 11/07/12 02:23, Neal Becker wrote: > So if I'm on Fedora 17, So am I. > I already have: > > rpm -qf /usr/bin/Xorg > xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 > > So I'm guessing I would need: > > https://www.xpra.org/src/Xdummy/Fedora/17/xorg-x11-drv-dummy-0.3.4-9.fc17.x86_64.rpm No, you don't need that, F17 is more recent than this. (I'll remove these old builds) > And also since X is installed suid, need to follow instructions for > that. Yes, simple "cp". > Is that the basic install then? Any config needed? Yes, you need an xorg.conf with dummy screen, the one on that page works fine. Cheers Antoine > > On Tue, Jul 10, 2012 at 3:15 PM, Antoine Martin > wrote: > > On 11/07/12 02:11, Neal Becker wrote: > > I thin the problem is this: > > runing on xpra: > xdpyinfo: > > screen #0: > dimensions: 3840x2560 pixels (975x650 millimeters) > resolution: 100x100 dots per inch > > > using ssh -X: > > xdpyinfo: > > screen #0: > dimensions: 1680x1050 pixels (371x231 millimeters) > resolution: 115x115 dots per inch > > You are problably right, although this is nothing new in 0.3.3 > > The solution is well known too: > https://xpra.org/Xdummy.html > > I have discussed the packaging issue today with some Debian > developers and I intend to try to make it the default to use Xdummy > on distributions that ship sufficiently recent X11 packages. > Probably not before v0.5 though, as v0.4.0 is almost ready. > > Cheers > Antoine > > > > > > On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker > > >> wrote: > > Thanks for 0.3.3. > > Just tried. Running emacs, it looks to me that the fonts > look thin. > I don't think that was the case on 0.3.2 (I might be > mistaken). > > > > > From ndbecker2 at gmail.com Tue Jul 10 20:25:32 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Tue, 10 Jul 2012 15:25:32 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> Message-ID: Also: Randr not supported: X server does not support required extension Randr Which is probably because I'm using the nvidia binary blob. Don't know if this changes the answer. On Tue, Jul 10, 2012 at 3:23 PM, Neal Becker wrote: > So if I'm on Fedora 17, I already have: > > rpm -qf /usr/bin/Xorg > xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 > > So I'm guessing I would need: > > > https://www.xpra.org/src/Xdummy/Fedora/17/xorg-x11-drv-dummy-0.3.4-9.fc17.x86_64.rpm > > And also since X is installed suid, need to follow instructions for that. > Is that the basic install then? Any config needed? > > On Tue, Jul 10, 2012 at 3:15 PM, Antoine Martin wrote: > >> On 11/07/12 02:11, Neal Becker wrote: >> >>> I thin the problem is this: >>> >>> runing on xpra: >>> xdpyinfo: >>> >>> screen #0: >>> dimensions: 3840x2560 pixels (975x650 millimeters) >>> resolution: 100x100 dots per inch >>> >>> >>> using ssh -X: >>> >>> xdpyinfo: >>> >>> screen #0: >>> dimensions: 1680x1050 pixels (371x231 millimeters) >>> resolution: 115x115 dots per inch >>> >> You are problably right, although this is nothing new in 0.3.3 >> >> The solution is well known too: >> https://xpra.org/Xdummy.html >> >> I have discussed the packaging issue today with some Debian developers >> and I intend to try to make it the default to use Xdummy on distributions >> that ship sufficiently recent X11 packages. >> Probably not before v0.5 though, as v0.4.0 is almost ready. >> >> Cheers >> Antoine >> >> >> >> >>> >>> On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker >> > wrote: >>> >>> Thanks for 0.3.3. >>> >>> Just tried. Running emacs, it looks to me that the fonts look thin. >>> I don't think that was the case on 0.3.2 (I might be mistaken). >>> >>> >>> >> >> > From antoine at nagafix.co.uk Tue Jul 10 20:28:43 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 02:28:43 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> Message-ID: <4FFC826B.9030802@nagafix.co.uk> On 11/07/12 02:25, Neal Becker wrote: > Also: > > Randr not supported: X server does not support required extension Randr No, that doesn't really matter. If anything, it simplifies things since the client will not have to tell the server to resize itself after the initial connection. Antoine > > Which is probably because I'm using the nvidia binary blob. Don't know > if this changes the answer. > > On Tue, Jul 10, 2012 at 3:23 PM, Neal Becker > wrote: > > So if I'm on Fedora 17, I already have: > > rpm -qf /usr/bin/Xorg > xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 > > So I'm guessing I would need: > > https://www.xpra.org/src/Xdummy/Fedora/17/xorg-x11-drv-dummy-0.3.4-9.fc17.x86_64.rpm > > And also since X is installed suid, need to follow instructions for > that. Is that the basic install then? Any config needed? > > On Tue, Jul 10, 2012 at 3:15 PM, Antoine Martin > > wrote: > > On 11/07/12 02:11, Neal Becker wrote: > > I thin the problem is this: > > runing on xpra: > xdpyinfo: > > screen #0: > dimensions: 3840x2560 pixels (975x650 millimeters) > resolution: 100x100 dots per inch > > > using ssh -X: > > xdpyinfo: > > screen #0: > dimensions: 1680x1050 pixels (371x231 millimeters) > resolution: 115x115 dots per inch > > You are problably right, although this is nothing new in 0.3.3 > > The solution is well known too: > https://xpra.org/Xdummy.html > > I have discussed the packaging issue today with some Debian > developers and I intend to try to make it the default to use > Xdummy on distributions that ship sufficiently recent X11 packages. > Probably not before v0.5 though, as v0.4.0 is almost ready. > > Cheers > Antoine > > > > > > On Tue, Jul 10, 2012 at 2:29 PM, Neal Becker > > >> > wrote: > > Thanks for 0.3.3. > > Just tried. Running emacs, it looks to me that the > fonts look thin. > I don't think that was the case on 0.3.2 (I might be > mistaken). > > > > > > From ndbecker2 at gmail.com Wed Jul 11 12:19:39 2012 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 11 Jul 2012 07:19:39 -0400 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFC826B.9030802@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> Message-ID: Got it to work with xdummy after a few tries, but it's only worse: screen #0: dimensions: 1680x1050 pixels (2167x1084 millimeters) resolution: 20x25 dots per inch I used: xpra --xvfb="Xorg-nosuid -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile /tmp/10.log -config /home/nbecker/xorg-dummy.conf" start :10 (need to give paths for -logfile and -config, not '.') From antoine at nagafix.co.uk Wed Jul 11 12:54:48 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 18:54:48 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> Message-ID: <4FFD6988.70400@nagafix.co.uk> On 11/07/12 18:19, Neal Becker wrote: > Got it to work with xdummy after a few tries, but it's only worse: > > screen #0: > dimensions: 1680x1050 pixels (2167x1084 millimeters) > resolution: 20x25 dots per inch > > I used: > xpra --xvfb="Xorg-nosuid -nolisten tcp +extension GLX +extension RANDR > +extension RENDER -logfile /tmp/10.log -config > /home/nbecker/xorg-dummy.conf" start :10 > > (need to give paths for -logfile and -config, not '.') So, you now have Xdummy instead of Xvfb, by "worse" I assume you mean that the dpi is lower which makes the fonts/lines smaller? I think we can tell the X11 server to use a different DPI, even with the dummy driver. Anyone? Cheers Antoine From lists at ebourne.me.uk Wed Jul 11 16:17:34 2012 From: lists at ebourne.me.uk (Martin Ebourne) Date: Thu, 12 Jul 2012 00:47:34 +0930 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFD6988.70400@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> <4FFD6988.70400@nagafix.co.uk> Message-ID: <1342019854.2744.0.camel@avenin.ebourne.me.uk> On Wed, 2012-07-11 at 18:54 +0700, Antoine Martin wrote: > On 11/07/12 18:19, Neal Becker wrote: > > Got it to work with xdummy after a few tries, but it's only worse: > > > > screen #0: > > dimensions: 1680x1050 pixels (2167x1084 millimeters) > > resolution: 20x25 dots per inch > > > > I used: > > xpra --xvfb="Xorg-nosuid -nolisten tcp +extension GLX +extension RANDR > > +extension RENDER -logfile /tmp/10.log -config > > /home/nbecker/xorg-dummy.conf" start :10 > > > > (need to give paths for -logfile and -config, not '.') > > So, you now have Xdummy instead of Xvfb, by "worse" I assume you mean > that the dpi is lower which makes the fonts/lines smaller? > > I think we can tell the X11 server to use a different DPI, even with the > dummy driver. Anyone? Xorg takes: -dpi int screen resolution in dots per inch Cheers, Martin From antoine at nagafix.co.uk Wed Jul 11 16:29:11 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 11 Jul 2012 22:29:11 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <1342019854.2744.0.camel@avenin.ebourne.me.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> <4FFD6988.70400@nagafix.co.uk> <1342019854.2744.0.camel@avenin.ebourne.me.uk> Message-ID: <4FFD9BC7.8030809@nagafix.co.uk> On 11/07/12 22:17, Martin Ebourne wrote: > On Wed, 2012-07-11 at 18:54 +0700, Antoine Martin wrote: >> On 11/07/12 18:19, Neal Becker wrote: >>> Got it to work with xdummy after a few tries, but it's only worse: >>> >>> screen #0: >>> dimensions: 1680x1050 pixels (2167x1084 millimeters) >>> resolution: 20x25 dots per inch >>> >>> I used: >>> xpra --xvfb="Xorg-nosuid -nolisten tcp +extension GLX +extension RANDR >>> +extension RENDER -logfile /tmp/10.log -config >>> /home/nbecker/xorg-dummy.conf" start :10 >>> >>> (need to give paths for -logfile and -config, not '.') >> >> So, you now have Xdummy instead of Xvfb, by "worse" I assume you mean >> that the dpi is lower which makes the fonts/lines smaller? >> >> I think we can tell the X11 server to use a different DPI, even with the >> dummy driver. Anyone? > > Xorg takes: > -dpi int screen resolution in dots per inch That should take care of this particular session for a single client configuration, but ideally I would like to find a more general solution where the xpra client could send the xpra server the DPI it already uses and get the server to adapt on the fly. (if at all possible) I have seen a number of posts referring to xrdb and Xft.dpi, but I have no idea how that interacts with toolkits (gtk, qt, tk..) I will need to investigate, pointers welcome. Cheers Antoine > > Cheers, > Martin > From lists at ebourne.me.uk Thu Jul 12 05:57:56 2012 From: lists at ebourne.me.uk (Martin Ebourne) Date: Thu, 12 Jul 2012 14:27:56 +0930 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFD9BC7.8030809@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> <4FFD6988.70400@nagafix.co.uk> <1342019854.2744.0.camel@avenin.ebourne.me.uk> <4FFD9BC7.8030809@nagafix.co.uk> Message-ID: <1342069076.2744.4.camel@avenin.ebourne.me.uk> On Wed, 2012-07-11 at 22:29 +0700, Antoine Martin wrote: > On 11/07/12 22:17, Martin Ebourne wrote: > > Xorg takes: > > -dpi int screen resolution in dots per inch > That should take care of this particular session for a single client > configuration, but ideally I would like to find a more general solution > where the xpra client could send the xpra server the DPI it already uses > and get the server to adapt on the fly. (if at all possible) > I have seen a number of posts referring to xrdb and Xft.dpi, but I have > no idea how that interacts with toolkits (gtk, qt, tk..) > I will need to investigate, pointers welcome. xrandr also takes --dpi to set the resolution. I don't know if you can directly query the dpi but xrandr does give the screen dimensions and display mode dimensions so it's easy to calculate dpi from that. I guess you just need to query it on the client side and set on the server side. I don't know what you'd do about heterogeneous multi-screen setups though, my displays are 125dpi and 100dpi. Cheers, Martin From antoine at nagafix.co.uk Thu Jul 12 06:07:29 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Jul 2012 12:07:29 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <1342069076.2744.4.camel@avenin.ebourne.me.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> <4FFD6988.70400@nagafix.co.uk> <1342019854.2744.0.camel@avenin.ebourne.me.uk> <4FFD9BC7.8030809@nagafix.co.uk> <1342069076.2744.4.camel@avenin.ebourne.me.uk> Message-ID: <4FFE5B91.8020909@nagafix.co.uk> On 12/07/12 11:57, Martin Ebourne wrote: > On Wed, 2012-07-11 at 22:29 +0700, Antoine Martin wrote: >> On 11/07/12 22:17, Martin Ebourne wrote: >>> Xorg takes: >>> -dpi int screen resolution in dots per inch >> That should take care of this particular session for a single client >> configuration, but ideally I would like to find a more general solution >> where the xpra client could send the xpra server the DPI it already uses >> and get the server to adapt on the fly. (if at all possible) >> I have seen a number of posts referring to xrdb and Xft.dpi, but I have >> no idea how that interacts with toolkits (gtk, qt, tk..) >> I will need to investigate, pointers welcome. > > xrandr also takes --dpi to set the resolution. I don't know if you can > directly query the dpi but xrandr does give the screen dimensions and > display mode dimensions so it's easy to calculate dpi from that. I guess > you just need to query it on the client side and set on the server side. Oh, I had missed that. We already have some randr code in there so it shouldn't be too hard to add. > I don't know what you'd do about heterogeneous multi-screen setups > though, my displays are 125dpi and 100dpi. I'm looking at the randr API, and it looks like xrandr uses the DPI to calculate the screen dimensions. So that gives us more options than just using min/max/avg in the case of multi-screen setups. But it also complicates things because you then need to care about how the screens are arranged (overlapping, below or to the side...), so I will probably just use the average for now. Cheers Antoine > > Cheers, > Martin > From antoine at nagafix.co.uk Thu Jul 12 06:15:20 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Jul 2012 12:15:20 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.3 In-Reply-To: <4FFE5B91.8020909@nagafix.co.uk> References: <4FFC618E.9050106@nagafix.co.uk> <4FFC7F6E.30408@nagafix.co.uk> <4FFC826B.9030802@nagafix.co.uk> <4FFD6988.70400@nagafix.co.uk> <1342019854.2744.0.camel@avenin.ebourne.me.uk> <4FFD9BC7.8030809@nagafix.co.uk> <1342069076.2744.4.camel@avenin.ebourne.me.uk> <4FFE5B91.8020909@nagafix.co.uk> Message-ID: <4FFE5D68.9090506@nagafix.co.uk> I have create a ticket for this issue so we can stop spamming the list: https://www.xpra.org/trac/ticket/163 Antoine On 12/07/12 12:07, Antoine Martin wrote: > On 12/07/12 11:57, Martin Ebourne wrote: >> On Wed, 2012-07-11 at 22:29 +0700, Antoine Martin wrote: >>> On 11/07/12 22:17, Martin Ebourne wrote: >>>> Xorg takes: >>>> -dpi int screen resolution in dots per inch >>> That should take care of this particular session for a single client >>> configuration, but ideally I would like to find a more general solution >>> where the xpra client could send the xpra server the DPI it already uses >>> and get the server to adapt on the fly. (if at all possible) >>> I have seen a number of posts referring to xrdb and Xft.dpi, but I have >>> no idea how that interacts with toolkits (gtk, qt, tk..) >>> I will need to investigate, pointers welcome. >> >> xrandr also takes --dpi to set the resolution. I don't know if you can >> directly query the dpi but xrandr does give the screen dimensions and >> display mode dimensions so it's easy to calculate dpi from that. I guess >> you just need to query it on the client side and set on the server side. > Oh, I had missed that. We already have some randr code in there so it > shouldn't be too hard to add. > >> I don't know what you'd do about heterogeneous multi-screen setups >> though, my displays are 125dpi and 100dpi. > I'm looking at the randr API, and it looks like xrandr uses the DPI to > calculate the screen dimensions. So that gives us more options than just > using min/max/avg in the case of multi-screen setups. > But it also complicates things because you then need to care about how > the screens are arranged (overlapping, below or to the side...), so I > will probably just use the average for now. > > Cheers > Antoine > > >> >> Cheers, >> Martin From punx120 at gmail.com Thu Jul 12 13:45:32 2012 From: punx120 at gmail.com (Sylvain Archenault) Date: Thu, 12 Jul 2012 08:45:32 -0400 Subject: [winswitch] Can't connect from windows Message-ID: Hello, I built xpra 0.3.3 on one of my linux server, and it seems to work correcly. I also installed the last version of WinSwitch on my windows desktop. The problem is that I can't connect to my server. I'm using a SSH key to connect to the server, it works fine with putty. But WinSwitch is unable to establish the connection. here is the log from applet.log [II] 2012/12/07 08:42:54 ConchStdioRemoteClientLinkFactory.__init__(syarc,#######,tlmlb001,22,,###############################,,ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44) [II] 2012/12/07 08:42:54 ConchTransport.connectionMade() [II] 2012/12/07 08:42:55 WinSwitchApplet.get_link_client(ServerConfig(tlmlb001:),None) no link client [II] 2012/12/07 08:42:55 ConchTransport.verifyHostKey([...],ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44) dialog_util=, factory=, hostkey_fingerprint=ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44 [II] 2012/12/07 08:42:55 ConchConnection.__init__() [II] 2012/12/07 08:42:55 ConchUserAuth.__init__(,) [II] 2012/12/07 08:42:55 ConchTransport.connectionSecure() auth= [II] 2012/12/07 08:42:55 ConchUserAuth.serviceStarted() agent_socket_filename=None [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( publickey,keyboard-interactive ) TWISTED_MAJOR=12 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(None,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, 0 agentKeys [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(False,) attempts=0 [II] 2012/12/07 08:42:55 ConchUserAuth._cbUserauthFailure(True,) attempts=0 [II] 2012/12/07 08:42:55 ConchStdioRemoteClientLinkFactory.clientConnectionLost(,[Failure instance: Traceback (failure with no frames): : Connection was closed cleanly.\n]) [EE] 2012/12/07 08:42:55 ConchStdioRemoteClientLinkFactory.disconnected() [II] 2012/12/07 08:42:55 WinSwitchApplet.get_link_client(ServerConfig(tlmlb001:),None) no link client A few months ago, I was able to make it work with xpra 0.1 on a different server, but using the same connection setup. Do you know what could be wrong ? Thanks Sylvain From antoine at nagafix.co.uk Thu Jul 12 14:38:29 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 12 Jul 2012 20:38:29 +0700 Subject: [winswitch] Can't connect from windows In-Reply-To: References: Message-ID: <4FFED355.3000200@nagafix.co.uk> On 12/07/12 19:45, Sylvain Archenault wrote: > Hello, > > I built xpra 0.3.3 on one of my linux server, and it seems to work > correcly. I also installed the last version of WinSwitch on my windows > desktop. What version of winswitch is installed on the server and how did you install it? > The problem is that I can't connect to my server. I'm using a SSH key > to connect to the server, it works fine with putty. But WinSwitch is > unable to establish the connection. here is the log from applet.log (snip) > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys Normal, ssh agent is not supported on win32. (totally undocumented) > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= Hah, looks like the public key to use is not set!? > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 The counter never seems to increase, which is odd. > ConchStdioRemoteClientLinkFactory.clientConnectionLost( instance at 0x0212F828>,[Failure instance: Traceback (failure with no > frames): : Connection > was closed cleanly.\n]) Well, at this point it tried all it could and gives up... > A few months ago, I was able to make it work with xpra 0.1 on a > different server, but using the same connection setup. I have to admit that I don't test ssh keys support on win32 much, I'll have to try to see if I can reproduce. > Do you know what could be wrong ? Hmm, apart from the ssh public key not being set for this server no. But I suspect you have probably double checked that already.. I've created a ticket to keep track of this: https://winswitch.org/trac/ticket/206 Feel free to add any details there. Cheers Antoine > > Thanks > Sylvain > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From punx120 at gmail.com Thu Jul 12 15:03:25 2012 From: punx120 at gmail.com (Sylvain Archenault) Date: Thu, 12 Jul 2012 10:03:25 -0400 Subject: [winswitch] Can't connect from windows In-Reply-To: References: Message-ID: The server is running RHEL 6.2. Here is what to make it work with SSH # Terminal 1: $ ./xpra start :100 I # Terminal 2: $ ./xpra attach :100 failed to locate the dbus notification service cannot import pynotify wrapper: No module named pynotify turning notifications off '['setxkbmap', '-query']' failed with exit code 255 the server will try to guess your keyboard mapping, which works reasonably well in most cases however, upgrading 'setxkbmap' to a version that supports the '-query' parameter is preferred mmap enabled using /tmp/xpra.dgjfUh.mmap Attached (press Control-C to detach) In the log file, i have this: _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet Xlib: extension "RANDR" missing on display ":100.0". Xlib: extension "RANDR" missing on display ":100.0". your version of PyGTK is too old - expect some bugs Xlib: extension "RANDR" missing on display ":100.0". Randr not supported: X server does not support required extension Randr error loading or registering our dbus notifications forwarder: org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/dbus-launch terminated abnormally without any error message xpra is ready. New connection received: /home/team13/syarc/.xpra/tlmlb001-100 Handshake complete; enabling connection encoding set to rgb24, client supports ['rgb24', 'x264', 'vpx'], server supports ['rgb24', 'x264', 'vpx'] using client supplied mmap file=/tmp/xpra.dgjfUh.mmap, size=134217728 client resolution is [3840, 1024], current server resolution is 3840x2560 setting key repeat rate from client: 500 / 32 guessing keyboard layout='pc+us+inet' The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Symbol map for key redefined > Using last definition for conflicting fields ... A lot like that and then: expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet Errors from xkbcomp are not fatal to the X server ['setxkbmap', 'pc+us+inet'] ['xkbcomp', '-', ':100'] with stdin=xkb_keymap {\n xkb_keycodes { .. Then if I try to run ./xpra list, i have this: syarc at tlmlb001 bin$ ./xpra list Found the following xpra sessions: DEAD session at :100 (cleaned up) Which erases ~/.xpra/tlmlb001-100= so I can't attach anymore If I start a GUI application, everything works as I expect. Thanks Sylvain On Thu, Jul 12, 2012 at 8:45 AM, Sylvain Archenault wrote: > Hello, > > I built xpra 0.3.3 on one of my linux server, and it seems to work > correcly. I also installed the last version of WinSwitch on my windows > desktop. > > The problem is that I can't connect to my server. I'm using a SSH key > to connect to the server, it works fine with putty. But WinSwitch is > unable to establish the connection. here is the log from applet.log > > [II] 2012/12/07 08:42:54 > ConchStdioRemoteClientLinkFactory.__init__(syarc,#######,tlmlb001,22,,###############################,,ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44) > [II] 2012/12/07 08:42:54 ConchTransport.connectionMade() > [II] 2012/12/07 08:42:55 > WinSwitchApplet.get_link_client(ServerConfig(tlmlb001:),None) no link > client > [II] 2012/12/07 08:42:55 > ConchTransport.verifyHostKey([...],ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44) > dialog_util= 0x01EC52B0>, factory= instance at 0x01F440D0>, > hostkey_fingerprint=ff:1c:c6:41:b6:0d:71:e3:73:37:17:77:bc:f3:a4:44 > [II] 2012/12/07 08:42:55 > ConchConnection.__init__( instance at 0x01F440D0>) > [II] 2012/12/07 08:42:55 > ConchUserAuth.__init__( instance at 0x01F440D0>, instance at 0x021352B0>) > [II] 2012/12/07 08:42:55 ConchTransport.connectionSecure() > auth= > [II] 2012/12/07 08:42:55 ConchUserAuth.serviceStarted() > agent_socket_filename=None > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.ssh_USERAUTH_FAILURE( > publickey,keyboard-interactive ) TWISTED_MAJOR=12 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(None, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() agentKeyIndex=0, > 0 agentKeys > [II] 2012/12/07 08:42:55 ConchUserAuth.getPublicKey() testing public_key= > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(False, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchUserAuth._cbUserauthFailure(True, 0x01F41890>) attempts=0 > [II] 2012/12/07 08:42:55 > ConchStdioRemoteClientLinkFactory.clientConnectionLost( instance at 0x0212F828>,[Failure instance: Traceback (failure with no > frames): : Connection > was closed cleanly.\n]) > [EE] 2012/12/07 08:42:55 ConchStdioRemoteClientLinkFactory.disconnected() > [II] 2012/12/07 08:42:55 > WinSwitchApplet.get_link_client(ServerConfig(tlmlb001:),None) no link > client > > A few months ago, I was able to make it work with xpra 0.1 on a > different server, but using the same connection setup. > > Do you know what could be wrong ? > > Thanks > Sylvain From antoine at nagafix.co.uk Mon Jul 23 09:19:23 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 23 Jul 2012 15:19:23 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.4.0 Message-ID: <500D090B.2000106@nagafix.co.uk> Hi, There are many bug fixes and some significant improvements in this release, see the full release notes below for details. Here is a brief summary: * fixes for window dimensions, command exit code, packaging, etc * many fixes and improvements for x264/vpx video encoding/decoding * keyboard fixes (still), partial revert of the previous "fix" * better latency and interactivity * more dynamic framerate adjustments, based on more metrics * improved launcher GUI * various build and packaging improvements This new release will be supported for about 6 months. The 0.3 release will continue to be supported for about 3 months with major bug-fixes, maybe slightly longer if needed. As usual, the source can be found here: http://xpra.org/src/ And the binaries here: http://winswitch.org/downloads/ Cheers Antoine Full release notes: * fix client application resizing its own window * fix window dimensions hints not applied * fix memleak in x264 cleanup code * fix xpra command exit code (more complete fix) * fix latency bottleneck in processing of damage requests * fix free uninitialized pointers in video decoder initialization error codepath * fix x264 related crash when resizing windows to one pixel width or height * fix accounting of client decode time: ignore figure in case of decoding error * fix subversion build information detection on MS Windows * fix some binary packages which were missing some menu icons * restore keyboard compatiblity code for MS Windows and OSX clients * use padded buffers to prevent colourspace conversion from reading random memory * release Python's GIL during vpx and x264 compression and colourspace conversion * better UI launcher: UI improvements, detect encodings, fix standalone/win32 usage, minimize window once the client has started * "xpra stop" disconnects all potential clients cleanly before exiting * x264 used memory aligned buffer for better performance * avoid vpx/x264 overhead for very small damage regions * detect dead connection with ping packets: disconnect if echo not received * force a full refresh when the encoding is changed * more dynamic framerate performance adjustments, based on more metrics * new menu option to toggle keyboard sync at runtime * vpx/x264 runtime imports: detect broken installations and warn, but ignore when the codec is simply not installed * enable environment debugging for damage batching via "XPRA_DEBUG_LATENCY" env variable * simplify build by using setup file to generate all constants * text clients now ignore packets they are not meant to handle * removed compression menu since the default is good enough * "xpra info" reports all build version information * report server pygtk/gtk versions and show them on session info dialog and "xpra info" * ignore dependency issues during sdist/clean phase of build * record more statistics (mostly latency) in test reports * documentation and logging added to code, moved test code out of main packages * better MS Windows installer graphics * include distribution name in RPM version/filename * CentOS 6 RPMs now depends on libvpx rather than a statically linked library * CentOS static ffmpeg build with memalign for better performance * debian: build with hardening features * debian: don't record as modified the files we know we modify during debian build * MS Windows build: allow user to set --without-vpx / --without-x264 in the batch file * MS Windows build fix: simpler/cleaner build for vpx/x264's codec.pyd * no longer bundle parti window manager From antoine at nagafix.co.uk Mon Jul 23 12:37:01 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 23 Jul 2012 18:37:01 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.4 Message-ID: <500D375D.9000104@nagafix.co.uk> Hi, This small update to the 0.3.x stable branch fixes a few bugs which had already been fixed in the 0.4.0 release, namely: * fix window size hints not applied * fix free uninitialized pointers in error codepath * fix crash with 1 pixel wide/high windows * fix keyboard support for MS Windows and OSX clients * explicitly include all icons * handle invalid packets in the correct thread * try harder to exit cleanly * ensure all required attributes are set by the GUI launcher Users of the 0.3.x stable branch are strongly advised to update, anyone else should be using the 0.4.0 release. As usual, the source can be found here: http://xpra.org/src/ And the binaries here: http://winswitch.org/downloads/ Cheers Antoine From dougdoole at gmail.com Sun Jul 29 18:36:08 2012 From: dougdoole at gmail.com (Douglas Doole) Date: Sun, 29 Jul 2012 13:36:08 -0400 Subject: [winswitch] xpra-0.4.0, KDE, and window dragging Message-ID: I just set up a new system with Ubuntu 12.04, KDE, and xpra 0.4.0. I use the system as a client for xpra; the server is also running xpra 0.4.0. On this particular client, when I left-click anywhere in a window, the cursor turns into a closed hand (grab) icon and the window moves with my mouse movements. This makes it impossible to cut&paste text, interact with scroll bars, etc. Only widows from xpra have this behaviour - local windows interact normally. On my other Ubuntu 12.04 system with KDE and xpra 0.4.0, using the same xpra server, I do not get this behaviour. Both machines attach to the server using "xpra attach ssh:reorx:1". So the problem is obviously something in my client side configuration, but I have no idea what is different between the two systems. I've looked at all the obvious window manager settings and they are the same on both machines. Does anyone have any suggestions on what I need to reconfigure? -- -- Doug Doole aibohphobia - The irrational fear of palindromes From totaam at gmail.com Sun Jul 29 18:50:04 2012 From: totaam at gmail.com (Antoine Martin) Date: Mon, 30 Jul 2012 00:50:04 +0700 Subject: [winswitch] xpra-0.4.0, KDE, and window dragging In-Reply-To: References: Message-ID: This is covered in the faq, you need an up to date oxygen-gtk. Sorry, short reply, I'm on the move.. On Jul 30, 2012 12:36 AM, "Douglas Doole" wrote: > I just set up a new system with Ubuntu 12.04, KDE, and xpra 0.4.0. I use > the system as a client for xpra; the server is also running xpra 0.4.0. > > On this particular client, when I left-click anywhere in a window, the > cursor turns into a closed hand (grab) icon and the window moves with my > mouse movements. This makes it impossible to cut&paste text, interact with > scroll bars, etc. Only widows from xpra have this behaviour - local windows > interact normally. > > On my other Ubuntu 12.04 system with KDE and xpra 0.4.0, using the same > xpra server, I do not get this behaviour. Both machines attach to the > server using "xpra attach ssh:reorx:1". > > So the problem is obviously something in my client side configuration, but > I have no idea what is different between the two systems. I've looked at > all the obvious window manager settings and they are the same on both > machines. > > Does anyone have any suggestions on what I need to reconfigure? > -- > -- Doug Doole > > aibohphobia - The irrational fear of palindromes > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From totaam at gmail.com Mon Jul 30 07:17:20 2012 From: totaam at gmail.com (Antoine Martin) Date: Mon, 30 Jul 2012 13:17:20 +0700 Subject: [winswitch] Fwd: xpra-0.4.0, KDE, and window dragging In-Reply-To: References: Message-ID: Forwarding to the list as this may help other KDE users. ---------- Forwarded message ---------- From: Douglas Doole Date: Mon, Jul 30, 2012 at 7:29 AM Subject: Re: [winswitch] xpra-0.4.0, KDE, and window dragging To: Antoine Martin Of course, right after sending the note I discovered the "Application Appearance" menu where there was still more Oxygen stuff selected. Everything's good now. Thanks. On Sun, Jul 29, 2012 at 8:21 PM, Douglas Doole wrote: > Fair enough. I don't have any particular attachment to Oxygen so changing > isn't a problem > > On the machine that works, I'm using: Plastik window decorations, KDE > classic cursors, and the Air desktop theme. I changed the new machine to > match but I'm still having problems. Is there something I'm missing to > switch off the Oxygen theme? > > > On Sun, Jul 29, 2012 at 1:50 PM, Antoine Martin wrote: > >> This is covered in the faq, you need an up to date oxygen-gtk. >> Sorry, short reply, I'm on the move.. >> On Jul 30, 2012 12:36 AM, "Douglas Doole" wrote: >> >>> I just set up a new system with Ubuntu 12.04, KDE, and xpra 0.4.0. I use >>> the system as a client for xpra; the server is also running xpra 0.4.0. >>> >>> On this particular client, when I left-click anywhere in a window, the >>> cursor turns into a closed hand (grab) icon and the window moves with my >>> mouse movements. This makes it impossible to cut&paste text, interact >>> with >>> scroll bars, etc. Only widows from xpra have this behaviour - local >>> windows >>> interact normally. >>> >>> On my other Ubuntu 12.04 system with KDE and xpra 0.4.0, using the same >>> xpra server, I do not get this behaviour. Both machines attach to the >>> server using "xpra attach ssh:reorx:1". >>> >>> So the problem is obviously something in my client side configuration, >>> but >>> I have no idea what is different between the two systems. I've looked at >>> all the obvious window manager settings and they are the same on both >>> machines. >>> >>> Does anyone have any suggestions on what I need to reconfigure? >>> -- >>> -- Doug Doole >>> >>> aibohphobia - The irrational fear of palindromes >>> _______________________________________________ >>> 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 > > -- -- Doug Doole aibohphobia - The irrational fear of palindromes From dougdoole at gmail.com Mon Jul 30 13:09:11 2012 From: dougdoole at gmail.com (Douglas Doole) Date: Mon, 30 Jul 2012 08:09:11 -0400 Subject: [winswitch] Fwd: xpra-0.4.0, KDE, and window dragging In-Reply-To: References: Message-ID: Oops, I'd missed that I was only replying to you, not to the list. Thanks for forwarding. Just to add to this: after experimenting some more, it turns out that it's only System Settings -> Application Appearance -> Widget Style that matters. That must not be Oxygen. The several settings under System Settings -> Workspace Appearance can use Oxygen with no negative effect on xpra. On Mon, Jul 30, 2012 at 2:17 AM, Antoine Martin wrote: > Forwarding to the list as this may help other KDE users. > > ---------- Forwarded message ---------- > From: Douglas Doole > Date: Mon, Jul 30, 2012 at 7:29 AM > Subject: Re: [winswitch] xpra-0.4.0, KDE, and window dragging > To: Antoine Martin > > > Of course, right after sending the note I discovered the "Application > Appearance" menu where there was still more Oxygen stuff selected. > Everything's good now. Thanks. > > > On Sun, Jul 29, 2012 at 8:21 PM, Douglas Doole > wrote: > > > Fair enough. I don't have any particular attachment to Oxygen so changing > > isn't a problem > > > > On the machine that works, I'm using: Plastik window decorations, KDE > > classic cursors, and the Air desktop theme. I changed the new machine to > > match but I'm still having problems. Is there something I'm missing to > > switch off the Oxygen theme? > > > > > > On Sun, Jul 29, 2012 at 1:50 PM, Antoine Martin > wrote: > > > >> This is covered in the faq, you need an up to date oxygen-gtk. > >> Sorry, short reply, I'm on the move.. > >> On Jul 30, 2012 12:36 AM, "Douglas Doole" wrote: > >> > >>> I just set up a new system with Ubuntu 12.04, KDE, and xpra 0.4.0. I > use > >>> the system as a client for xpra; the server is also running xpra 0.4.0. > >>> > >>> On this particular client, when I left-click anywhere in a window, the > >>> cursor turns into a closed hand (grab) icon and the window moves with > my > >>> mouse movements. This makes it impossible to cut&paste text, interact > >>> with > >>> scroll bars, etc. Only widows from xpra have this behaviour - local > >>> windows > >>> interact normally. > >>> > >>> On my other Ubuntu 12.04 system with KDE and xpra 0.4.0, using the same > >>> xpra server, I do not get this behaviour. Both machines attach to the > >>> server using "xpra attach ssh:reorx:1". > >>> > >>> So the problem is obviously something in my client side configuration, > >>> but > >>> I have no idea what is different between the two systems. I've looked > at > >>> all the obvious window manager settings and they are the same on both > >>> machines. > >>> > >>> Does anyone have any suggestions on what I need to reconfigure? > >>> -- > >>> -- Doug Doole > >>> > >>> aibohphobia - The irrational fear of palindromes > >>> _______________________________________________ > >>> 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 > > > > > > > -- > -- Doug Doole > > aibohphobia - The irrational fear of palindromes > _______________________________________________ > 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 From rogeriobastos at dcc.ufba.br Tue Jul 31 18:30:46 2012 From: rogeriobastos at dcc.ufba.br (ROGERIO DE CARVALHO BASTOS) Date: Tue, 31 Jul 2012 14:30:46 -0300 Subject: [winswitch] xmodmap: No protocol specified Message-ID: <20120731143046.25486scgvpgvzy2u@webmail.dcc.ufba.br> Hi, I have problems when I use winswitch + NX, I'm using NX programs distributeds by x2go project [http://www.x2go.org/doku.php/wiki:libs:nx-libs], but when I test with desktop.devloop.org.uk server NX works normally. The problem is described below: First, when a start winswitch_server a notice this error: [II] 2012/31/07 11:58:06 process_util.exec_nopipe(['/usr/bin/xset', 'q'],None,{'DISPLAY': ':0'},True,False,None,True) waiting on process= /usr/bin/xset: unable to open display ":0" But, I can connect and start Desktop/Application Sessions. However, when I detach and resume a NX session all fonts are hidden and server print this error: [II] 2012/31/07 11:59:10 NXServerUtil.set_user_keyboard() session connected, setting user keyboard mappings No protocol specified Error: Cannot open display ":60" Exiting [EE] 2012/31/07 11:59:10 NXServerUtil.set_keymap(ServerSession(:60 - nx - connected),User(Suporte REMO : f7258258b3f641e4b75a40883151cd41)) xkbcomp failed with exit code 1\n [II] 2012/31/07 11:59:10 NXServerUtil.do_set_xmodmap(ServerSession(:60 - nx - connected),User(Suporte REMO : f7258258b3f641e4b75a40883151cd41),False) [II] 2012/31/07 11:59:10 xmodmap_util.threaded_set_xmodmap(ServerSession(:60 - nx - connected),User(Suporte REMO : f7258258b3f641e4b75a40883151cd41),False) [EE] 2012/31/07 11:59:10 xmodmap_util.exec_xmodmap({'LANG': 'en_US.UTF-8', 'TERM': 'xterm', 'SHELL': '/bin/bash', 'XDG_SESSION_COOKIE': 'd4fd079ba37b93c95f1ff27a501002e6-1343746681.747292-97588504', 'SHLVL': '1', 'SSH_TTY': '/dev/pts/0', 'SSH_CLIENT': '10.1.0.70 52664 22', 'HISTCONTROL': 'ignoreboth', 'PWD': '/home/neptuno/rogeriobastos', 'LOGNAME': 'rogeriobastos', 'USER': 'rogeriobastos', 'MAIL': '/var/mail/rogeriobastos', 'PATH': '/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games', 'LS_COLORS': 'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:', 'HOME': '/home/neptuno/rogeriobastos', 'DISPLAY': ':60', '_': '/usr/bin/winswitch_server', 'SSH_CONNECTION': '10.1.0.70 52664 10.1.0.17 22'},-pke) process terminated with error code 1, stdout=, stderr=No protocol specified/usr/bin/xmodmap: unable to open display ':60' Any idea? -- Rogerio de Carvalho Bastos http://wiki.dcc.ufba.br/Main/RogerioBastos From antoine at nagafix.co.uk Tue Jul 31 19:07:06 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 01 Aug 2012 01:07:06 +0700 Subject: [winswitch] xmodmap: No protocol specified In-Reply-To: <20120731143046.25486scgvpgvzy2u@webmail.dcc.ufba.br> References: <20120731143046.25486scgvpgvzy2u@webmail.dcc.ufba.br> Message-ID: <50181ECA.4060309@nagafix.co.uk> On 08/01/2012 12:30 AM, ROGERIO DE CARVALHO BASTOS wrote: > Hi, > > I have problems when I use winswitch + NX, I'm using NX programs > distributeds by x2go project > [http://www.x2go.org/doku.php/wiki:libs:nx-libs], but when I test with > desktop.devloop.org.uk server NX works normally. The problem is > described below: > > First, when a start winswitch_server a notice this error: > > [II] 2012/31/07 11:58:06 process_util.exec_nopipe(['/usr/bin/xset', > 'q'],None,{'DISPLAY': ':0'},True,False,None,True) waiting on > process= > /usr/bin/xset: unable to open display ":0" That's the server trying to figure out if it has access to this display. Do you own the DISPLAY at ":0" ? Is it running from the same user-id and environment as the winswitch_server? In any case, this should not be a problem, this is only used for detecting existing X11 display sessions to then give you the option of shadowing them (either via NX or VNC) > But, I can connect and start Desktop/Application Sessions. > However, when I detach and resume a NX session all fonts are hidden and Are you saying that the fonts are there the first time (when you initially start the application) but not the second time? (when you re-connect) If so, that's very odd and I've never seen that. > server print this error: > [II] 2012/31/07 11:59:10 NXServerUtil.set_user_keyboard() session > connected, setting user keyboard mappings > No protocol specified > Error: Cannot open display ":60" > Exiting > [EE] 2012/31/07 11:59:10 NXServerUtil.set_keymap(ServerSession(:60 - nx > - connected),User(Suporte REMO : f7258258b3f641e4b75a40883151cd41)) > xkbcomp failed with exit code 1\n > [II] 2012/31/07 11:59:10 NXServerUtil.do_set_xmodmap(ServerSession(:60 - > nx - connected),User(Suporte REMO : > f7258258b3f641e4b75a40883151cd41),False) > [II] 2012/31/07 11:59:10 > xmodmap_util.threaded_set_xmodmap(ServerSession(:60 - nx - > connected),User(Suporte REMO : f7258258b3f641e4b75a40883151cd41),False) > [EE] 2012/31/07 11:59:10 xmodmap_util.exec_xmodmap({'LANG': > 'en_US.UTF-8', 'TERM': 'xterm', 'SHELL': '/bin/bash', > 'XDG_SESSION_COOKIE': > 'd4fd079ba37b93c95f1ff27a501002e6-1343746681.747292-97588504', 'SHLVL': > '1', 'SSH_TTY': '/dev/pts/0', 'SSH_CLIENT': '10.1.0.70 52664 22', > 'HISTCONTROL': 'ignoreboth', 'PWD': '/home/neptuno/rogeriobastos', > 'LOGNAME': 'rogeriobastos', 'USER': 'rogeriobastos', 'MAIL': > '/var/mail/rogeriobastos', 'PATH': > '/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games', 'LS_COLORS': > 'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl= 01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:', > 'HOME': '/home/neptuno/rogeriobastos', 'DISPLAY': ':60', '_': > '/usr/bin/winswitch_server', 'SSH_CONNECTION': '10.1.0.70 52664 > 10.1.0.17 22'},-pke) process terminated with error code 1, stdout=, > stderr=No protocol specified/usr/bin/xmodmap: unable to open display ':60' > > Any idea? It's very strange that you are able to connect to the session with NX but somehow the winswitch_server seems to fail to connect to the NX virtual X11 server to set the keymap, etc. Sounds like something is preventing access and generally that means xauth issues. Do you get any SELinux denials? What distro is this? Can you try to specify an alternate XAUTHORITY file? Just out of curiosity, is there anything specific that prevents you from using Xpra instead of NX? Cheers Antoine From antoine at nagafix.co.uk Tue Jul 31 19:12:39 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 01 Aug 2012 01:12:39 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.3.5 / xpra 0.4.1 / xpra 0.5.0-beta1 Message-ID: <50182017.1040906@nagafix.co.uk> Hi, This small update to the 0.3.x and 0.4.x stable branches only fixes one clipboard bug which was causing client application to crash. The 0.4.x branch also gets a fairer delay calculation for small windows. As usual, the source can be found here: https://xpra.org/src/ And links to the binaries/repositories here: https://winswitch.org/downloads/ Those interested in testing the upcoming 0.5 release can find a beta build here: https://xpra.org/beta/ Cheers Antoine From rogeriobastos at dcc.ufba.br Tue Jul 31 19:29:49 2012 From: rogeriobastos at dcc.ufba.br (ROGERIO DE CARVALHO BASTOS) Date: Tue, 31 Jul 2012 15:29:49 -0300 Subject: [winswitch] xmodmap: No protocol specified In-Reply-To: <50181ECA.4060309@nagafix.co.uk> References: <20120731143046.25486scgvpgvzy2u@webmail.dcc.ufba.br> <50181ECA.4060309@nagafix.co.uk> Message-ID: <20120731152949.730870svc0emcrh9@webmail.dcc.ufba.br> Quoting Antoine Martin : > It's very strange that you are able to connect to the session with > NX but somehow the winswitch_server seems to fail to connect to the > NX virtual X11 server to set the keymap, etc. > Sounds like something is preventing access and generally that means > xauth issues. Do you get any SELinux denials? > What distro is this? Can you try to specify an alternate XAUTHORITY file? I'm using Debian 7 without SELinux. > Just out of curiosity, is there anything specific that prevents you > from using Xpra instead of NX? I don't like NX, but we will offer a Desktop Session to users via Internet. -- Rogerio de Carvalho Bastos http://wiki.dcc.ufba.br/Main/RogerioBastos From antoine at nagafix.co.uk Tue Jul 31 19:35:36 2012 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 01 Aug 2012 01:35:36 +0700 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: <50182578.2020800@nagafix.co.uk> On 08/01/2012 01:29 AM, ROGERIO DE CARVALHO BASTOS wrote: > Quoting Antoine Martin : > >> It's very strange that you are able to connect to the session with NX >> but somehow the winswitch_server seems to fail to connect to the NX >> virtual X11 server to set the keymap, etc. >> Sounds like something is preventing access and generally that means >> xauth issues. Do you get any SELinux denials? >> What distro is this? Can you try to specify an alternate XAUTHORITY file? > > I'm using Debian 7 without SELinux. Try manually running xauth commands against that display, ie: DISPLAY=:60 xauth list Also try using your own XAUTHORITY file by setting the environment before starting the server, it might help. >> Just out of curiosity, is there anything specific that prevents you >> from using Xpra instead of NX? > > I don't like NX, but we will offer a Desktop Session to users via Internet. Both Xpra and NX do this... so you haven't really answered my question ;) Antoine