From antoine at nagafix.co.uk Wed Feb 1 07:48:22 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 1 Feb 2017 14:48:22 +0700 Subject: [winswitch] [ANNOUNCE] Xpra LTS 0.14.37 EOL (minor fixes) Message-ID: <45d74edd-7f70-b219-3b68-78b6cc72bb76@nagafix.co.uk> Hi, This this the final update to the 0.14.x branch, which has now reached EOL status: there will be no further updates on this branch. The 0.14.x branch was only kept alive for supporting older distros like CentOS 5.x, and for testing for regressions. Release notes: * build fix for gcc 4.1 and older * build fix for python 2.4 * build fix for optimize flag * fix compatibility with ancient pygtk versions (ie: CentOS 5.x) * fix access to window from the wrong thread (can crash) * fix unvalidated malloc in decoder * remove unsafe 24-bit modes in x264 encoder The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Beta: https://xpra.org/beta/ Cheers Antoine From antoine at nagafix.co.uk Wed Feb 1 11:22:29 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 1 Feb 2017 18:22:29 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 1.0.2 LTS (minor fixes) Message-ID: <15841d2b-6fd5-bb84-6603-8e508f42346d@nagafix.co.uk> Hi, This update to the 1.0.x LTS branch fixes a few minor bugs and platform specific issues (MS Windows and Mac OSX). There is no urgency to update if you were not affected. Release notes: - fix OpenGL pixel upload alignment issues - fix hello packet errors when pulseaudio is not installed - fix build handling of optimize flag - fix NVENC version check, update driver version validation - fix handling of bind command line option (replace not append) - fix shadow server screen size on MS Windows for high DPI - fix Events_test.exe (MS Windows) - fix compatibility with the latest version of python-cryptography (MS Windows) - fix Mac OSX clipboard - fix Mac OSX shadow servers: lack of refresh and CPU wastage - fix X bindings wrongly disabled when workspace switching is turned off - more user friendly error message for dbus import errors - print actual display name used when displayfd allocated one - library updates for Mac OSX - workaround for putty plink and nested shell commands (MS Windows) - ignore mmap token errors with desktop mode - add SSH command debug switch The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Beta: https://xpra.org/beta/ Cheers Antoine From lukashaase at gmx.at Thu Feb 2 21:17:48 2017 From: lukashaase at gmx.at (Lukas Haase) Date: Thu, 2 Feb 2017 22:17:48 +0100 Subject: [winswitch] Scrolling with mouse wheel not working Message-ID: Hi, When I use my mouse wheel, the up direction seems to be ignored, scrolling down works. An easy way to reproduce is to start midnight commander (mc) in xterm and go into a large directory. I can scroll down with my mouse wheel but not up. Is this some known issue or an unknown bug? In case it matters: I use xpra client 1.0 (14502) under Win 10 and xpra v1.0.1-r14734 under CentOS 5. Thanks! Luke From antoine at nagafix.co.uk Fri Feb 3 01:21:30 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 3 Feb 2017 08:21:30 +0700 Subject: [winswitch] Scrolling with mouse wheel not working In-Reply-To: References: Message-ID: <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> On 03/02/17 04:17, Lukas Haase via shifter-users wrote: > Hi, > > When I use my mouse wheel, the up direction seems to be ignored, scrolling down works. > An easy way to reproduce is to start midnight commander (mc) in xterm and go into a large directory. I can scroll down with my mouse wheel but not up. > > Is this some known issue or an unknown bug? > > In case it matters: I use xpra client 1.0 (14502) under Win 10 and xpra v1.0.1-r14734 under CentOS 5. Are you sure that you are using the 1.x branch on CentOS 5? I don't see how you could have installed it. In any case, the mouse wheel is known to work on all supported distributions, including CentOS 6.x I suspect that there is something wrong with your setup as mouse event handling is extremely well tested. --- You can try running the client with "-d mouse" and you should see events like those: _button_action(4, ... (4 for up and 5 for down. 6 for left and 7 for right) The same "-d mouse" switch on the server side will show you that we are injecting those button events into the X11 server: xtest_fake_button(4, True) at (256, 240) Your next step would be to run an application like "xev" to verify that the events are seen by the X11 client applications. Cheers Antoine > > Thanks! > Luke > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From lukashaase at gmx.at Fri Feb 3 01:34:36 2017 From: lukashaase at gmx.at (Lukas Haase) Date: Fri, 3 Feb 2017 02:34:36 +0100 Subject: [winswitch] Scrolling with mouse wheel not working In-Reply-To: <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> References: , <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> Message-ID: Hi Antoine, Thanks for your quick response! > On 03/02/17 04:17, Lukas Haase via shifter-users wrote: > > Hi, > > > > When I use my mouse wheel, the up direction seems to be ignored, scrolling down works. > > An easy way to reproduce is to start midnight commander (mc) in xterm and go into a large directory. I can scroll down with my mouse wheel but not up. > > > > Is this some known issue or an unknown bug? > > > > In case it matters: I use xpra client 1.0 (14502) under Win 10 and xpra v1.0.1-r14734 under CentOS 5. > Are you sure that you are using the 1.x branch on CentOS 5? > I don't see how you could have installed it. You are right - it is CentOS 6 ;-) > [...] > You can try running the client with "-d mouse" and you should see events > like those: > _button_action(4, ... > (4 for up and 5 for down. 6 for left and 7 for right) Ok. When I use scroll up using the mouse wheel I get tons of these messages: 2017-02-02 17:28:29,496 mousewheel: orientation=vertical distance=30.0, units=0, new value=0.0, keys=0x0, x=439, y=360, client=gtk2.client, wid=218 When I scrool down (the one that works) the messages are slightly different: 2017-02-02 17:29:41,362 mousewheel: send 1 wheel events to the server for distance=-120, remainder=0 2017-02-02 17:29:41,382 mousewheel: orientation=vertical distance=-30.0, units=-1, new value=-30.0, keys=0x0, x=434, y=375, client=gtk2.client, wid=218 > [...] > Your next step would be to run an application like "xev" to verify that > the events are seen by the X11 client applications. Yes, here seems to be the problem. Scrolling down: ButtonPress event, serial 36, synthetic NO, window 0xc00001, root 0x25d, subw 0x0, time 1389734833, (177,154), root:(445,445), state 0x0, button 5, same_screen YES ButtonRelease event, serial 36, synthetic NO, window 0xc00001, root 0x25d, subw 0x0, time 1389734833, (177,154), root:(445,445), state 0x1000, button 5, same_screen YES Scrolling up: No messages! Do I interpret it correctly that the client does not forward the "up wheel" messages to the server (since there is no "send 1 wheel events to the server ..." for up scrolling? Thanks, Luke From antoine at nagafix.co.uk Fri Feb 3 01:53:37 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 3 Feb 2017 08:53:37 +0700 Subject: [winswitch] Scrolling with mouse wheel not working In-Reply-To: References: <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> Message-ID: (..) > You are right - it is CentOS 6 ;-) > >> [...] >> You can try running the client with "-d mouse" and you should see events >> like those: >> _button_action(4, ... >> (4 for up and 5 for down. 6 for left and 7 for right) > > Ok. When I use scroll up using the mouse wheel I get tons of these messages: > > 2017-02-02 17:28:29,496 mousewheel: orientation=vertical distance=30.0, units=0, new value=0.0, keys=0x0, x=439, y=360, client=gtk2.client, wid=218 > > When I scrool down (the one that works) the messages are slightly different: > > 2017-02-02 17:29:41,362 mousewheel: send 1 wheel events to the server for distance=-120, remainder=0 > 2017-02-02 17:29:41,382 mousewheel: orientation=vertical distance=-30.0, units=-1, new value=-30.0, keys=0x0, x=434, y=375, client=gtk2.client, wid=218 MS Windows clients have extra code for handling scrolling acceleration: https://xpra.org/trac/ticket/1131 The "distance" is accumulated until we reach 120. (this is a MS Windows constant) It looks like your system uses a non-standard vertical acceleration set to just 30 (4 times slower than normal), so it may take 4 wheel scroll steps to generate one scroll event server side. (and up to 7 events if you had already scrolled 3 events in the opposite direction) This code could be improved to tiemout or at least reset the distance when the scrolling changes direction. Feel free to file a ticket for it. (..) > Do I interpret it correctly that the client does not forward the "up wheel" messages to the server (since there is no "send 1 wheel events to the server ..." for up scrolling? Yes. Antoine From lukashaase at gmx.at Fri Feb 3 04:25:42 2017 From: lukashaase at gmx.at (Lukas Haase) Date: Fri, 3 Feb 2017 05:25:42 +0100 Subject: [winswitch] Scrolling with mouse wheel not working In-Reply-To: References: <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> , Message-ID: > Gesendet: Donnerstag, 02. Februar 2017 um 17:53 Uhr > Von: "Antoine Martin" > An: "Lukas Haase" > Cc: shifter-users at lists.devloop.org.uk > Betreff: Re: [winswitch] Scrolling with mouse wheel not working Hi Antoine, I guess I do not completely understand your answer: > (..) > > You are right - it is CentOS 6 ;-) > > > >> [...] > >> You can try running the client with "-d mouse" and you should see events > >> like those: > >> _button_action(4, ... > >> (4 for up and 5 for down. 6 for left and 7 for right) > > > > Ok. When I use scroll up using the mouse wheel I get tons of these messages: > > > > 2017-02-02 17:28:29,496 mousewheel: orientation=vertical distance=30.0, units=0, new value=0.0, keys=0x0, x=439, y=360, client=gtk2.client, wid=218 > > > > When I scrool down (the one that works) the messages are slightly different: > > > > 2017-02-02 17:29:41,362 mousewheel: send 1 wheel events to the server for distance=-120, remainder=0 > > 2017-02-02 17:29:41,382 mousewheel: orientation=vertical distance=-30.0, units=-1, new value=-30.0, keys=0x0, x=434, y=375, client=gtk2.client, wid=218 > MS Windows clients have extra code for handling scrolling acceleration: > https://xpra.org/trac/ticket/1131 > > The "distance" is accumulated until we reach 120. (this is a MS Windows > constant) > > It looks like your system uses a non-standard vertical acceleration set > to just 30 (4 times slower than normal), so it may take 4 wheel scroll > steps to generate one scroll event server side. (and up to 7 events if > you had already scrolled 3 events in the opposite direction) But wouldn't this mean that if I scroll long enough up, it would eventually generate an event? It does not. No matter how long I scroll, xev never generates any output when scrolling upwards. Furthermore: 1.) If I use Xming server and execute "xpra attach :1000" from within SSH session, everything works. (So it works on the same system with a different X server) 2.) It does not work with 4 different mice (2x USB, 1x Bluetooth, 1x RF/USB) 3.) In the control panel under Mouse -> Wheel, the Vertical and Horizontal scrolling setting were the same (3). I set both of them to 1. No difference 4.) Unfortunately (because less reproducible) - it works in Win7 VM in VirtualBox on the same machine. > This code could be improved to tiemout or at least reset the distance > when the scrolling changes direction. Feel free to file a ticket for it. Given 1-3 - do you still think this is the case? I would then create a ticket referencing this conversation. Lukas From antoine at nagafix.co.uk Fri Feb 3 04:36:49 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 3 Feb 2017 11:36:49 +0700 Subject: [winswitch] Scrolling with mouse wheel not working In-Reply-To: References: <4d1c23dd-e131-b96f-511b-fef88e0d1edd@nagafix.co.uk> Message-ID: (snip) >>> Ok. When I use scroll up using the mouse wheel I get tons of these messages: >>> >>> 2017-02-02 17:28:29,496 mousewheel: orientation=vertical distance=30.0, units=0, new value=0.0, keys=0x0, x=439, y=360, client=gtk2.client, wid=218 >>> >>> When I scrool down (the one that works) the messages are slightly different: >>> >>> 2017-02-02 17:29:41,362 mousewheel: send 1 wheel events to the server for distance=-120, remainder=0 >>> 2017-02-02 17:29:41,382 mousewheel: orientation=vertical distance=-30.0, units=-1, new value=-30.0, keys=0x0, x=434, y=375, client=gtk2.client, wid=218 >> MS Windows clients have extra code for handling scrolling acceleration: >> https://xpra.org/trac/ticket/1131 >> >> The "distance" is accumulated until we reach 120. (this is a MS Windows >> constant) >> >> It looks like your system uses a non-standard vertical acceleration set >> to just 30 (4 times slower than normal), so it may take 4 wheel scroll >> steps to generate one scroll event server side. (and up to 7 events if >> you had already scrolled 3 events in the opposite direction) > > But wouldn't this mean that if I scroll long enough up, it would eventually generate an event? > It does not. No matter how long I scroll, xev never generates any output when scrolling upwards. It should. The "distance" should accumulate with every event until it reaches 120. You only provided a single event log message, so we don't know what is happening with those values. > Furthermore: > 1.) If I use Xming server and execute "xpra attach :1000" from within SSH session, everything works. (So it works on the same system with a different X server) I'm not sure exactly what you mean here. The MS Windows client does not use an X11 server at all. > 2.) It does not work with 4 different mice (2x USB, 1x Bluetooth, 1x RF/USB) > 3.) In the control panel under Mouse -> Wheel, the Vertical and Horizontal scrolling setting were the same (3). I set both of them to 1. No difference > 4.) Unfortunately (because less reproducible) - it works in Win7 VM in VirtualBox on the same machine. Works fine here in VM and with a full Windows 7 test system. >> This code could be improved to tiemout or at least reset the distance >> when the scrolling changes direction. Feel free to file a ticket for it. > > Given 1-3 - do you still think this is the case? > I would then create a ticket referencing this conversation. It could be a different issue, difficult to say. In any case, these sort of problems are best tracked using tickets. Cheers Antoine From timothy at hobbs.cz Mon Feb 6 00:50:21 2017 From: timothy at hobbs.cz (Timothy Hobbs) Date: Mon, 6 Feb 2017 01:50:21 +0100 Subject: [winswitch] Keyboard key repetition Message-ID: Hello, I have a weird problem using subuser with the xpra-x11 bridge http://subuser.org/news/0.3.html#the-xpra-x11-bridge. Sometimes, not always, but sometimes, I end up with a situation in firefox, that when I press a key, the key stays down and starts repeating. So if I am backspacing, it will delete the entire line, or I'll get nnnnnnnnnnnnnnnnnnnnn. When this happens, firefox freezes before the repeated keypresses appear. Is it possible, in the xpra api, that you are sending first a key-down and then a key-up, and some sort of delay in the protocol causes the x11 server on the container side of the bridge to think that the key was held down and that repetition should occure? Where would I look in the code to try to fix this bug? Regards, Timothy Hobbs From antoine at nagafix.co.uk Mon Feb 6 06:03:41 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 6 Feb 2017 13:03:41 +0700 Subject: [winswitch] Keyboard key repetition In-Reply-To: References: Message-ID: <91770e01-a82b-d88f-0457-b82b54012500@nagafix.co.uk> On 06/02/17 07:50, Timothy Hobbs via shifter-users wrote: > Hello, > > I have a weird problem using subuser with the xpra-x11 bridge > http://subuser.org/news/0.3.html#the-xpra-x11-bridge. Sometimes, not > always, but sometimes, I end up with a situation in firefox, that when I > press a key, the key stays down and starts repeating. So if I am > backspacing, it will delete the entire line, or I'll get > nnnnnnnnnnnnnnnnnnnnn. When this happens, firefox freezes before the > repeated keypresses appear. That sounds like the whole process is stuck, it may have little to do with the keyboard which may just be a symptom. Can you try running with the clipboard disabled? Some clipboard issues have been reported, clipboard bugs may be able to cause such problems. > Is it possible, in the xpra api, that you > are sending first a key-down and then a key-up, and some sort of delay > in the protocol causes the x11 server on the container side of the > bridge to think that the key was held down and that repetition should > occure? By default, we send key-up and key-down events as they occur. But this can be changed with the "keyboard-sync" switch, see: https://xpra.org/trac/wiki/Keyboard > Where would I look in the code to try to fix this bug? The most important thing is to find the cause first, only then can you start looking at the code. If this is a regression, when did start? Is it platform specific? Do all the processes stall, or just firefox? Or X11? Have you tried enabling debug logging? etc. Cheers Antoine > > Regards, > > Timothy Hobbs > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From dougdoole at gmail.com Tue Feb 7 22:58:41 2017 From: dougdoole at gmail.com (Douglas Doole) Date: Tue, 07 Feb 2017 22:58:41 +0000 Subject: [winswitch] Font troubles with Mac client Message-ID: Hi. I'm having trouble with fonts when using the Mac client. My server is Ubuntu 14.04. Both the client and server are running Xpra 1.0.2. Most of the time I am connected to my Xpra server from my Ubuntu machine in loopback mode (client and server running on the same machine). When I'm working remotely, however, I'll connect from my MacBook Pro. When I connect Xpra, all the windows that are already open are fine. (Generally the windows are terminals and gvim. The text in all the windows is a reasonable size.) However if I create any new windows (such as start a new instance of gvim) the text in the new window is too small to read. Non-text elements (such as icons and window controls) are properly sized, so it's not a general scaling issue. (I've tried other applications as well, such as firefox and eclipse, and the behaviour is consistent - tiny fonts but other elements are properly sized.) Any suggestions on how to fix the fonts for newly created windows from the Mac client? Thanks From antoine at nagafix.co.uk Wed Feb 8 04:22:23 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 8 Feb 2017 11:22:23 +0700 Subject: [winswitch] Font troubles with Mac client In-Reply-To: References: Message-ID: On 08/02/17 05:58, Douglas Doole via shifter-users wrote: > Hi. I'm having trouble with fonts when using the Mac client. > > My server is Ubuntu 14.04. Both the client and server are running Xpra > 1.0.2. > > Most of the time I am connected to my Xpra server from my Ubuntu machine in > loopback mode (client and server running on the same machine). When I'm > working remotely, however, I'll connect from my MacBook Pro. > > When I connect Xpra, all the windows that are already open are fine. > (Generally the windows are terminals and gvim. The text in all the windows > is a reasonable size.) However if I create any new windows (such as start a > new instance of gvim) the text in the new window is too small to read. This tells us that the DPI settings are being applied from the mac and the applications you launch only read these settings when they start. (that's unfortunate, but most applications behave this way) The server log file should have logged it, please include it. > Non-text elements (such as icons and window controls) are properly sized, > so it's not a general scaling issue. (I've tried other applications as > well, such as firefox and eclipse, and the behaviour is consistent - tiny > fonts but other elements are properly sized.) Please see: https://www.xpra.org/trac/wiki/DPI > Any suggestions on how to fix the fonts for newly created windows from the > Mac client? Is the Mac display a high DPI display? What resolution? (actual specifications not Apple's marketing terms) What does the client see it as? (client and server command line output will log it) The output from the "Xpra.app/Contents/Helpers/NativeGUI_info" would be useful too. You can try changing the DPI manually, ie: add {{{--dpi=96}}} to the client command line. If that works, you can stick this setting in "~/.xpra/xpra.conf". Cheers Antoine > > Thanks > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From dougdoole at gmail.com Wed Feb 8 17:48:42 2017 From: dougdoole at gmail.com (Douglas Doole) Date: Wed, 08 Feb 2017 17:48:42 +0000 Subject: [winswitch] Font troubles with Mac client In-Reply-To: References: Message-ID: As always, thanks for your help Antoine. I should have looked for DPI problems, but I dismissed it as an issue since icons looked fine while the fonts were screwy. On Tue, Feb 7, 2017 at 8:22 PM Antoine Martin via shifter-users < shifter-users at lists.devloop.org.uk> wrote: > This tells us that the DPI settings are being applied from the mac and > the applications you launch only read these settings when they start. > (that's unfortunate, but most applications behave this way) > The server log file should have logged it, please include it. > Looking in the server log after connecting from the MacBook I find: 2017-02-08 09:32:54,078 setting keyboard layout to 'us' 2017-02-08 09:32:54,127 DPI set to 17 x 21 (wanted 72 x 72) 2017-02-08 09:32:54,127 you may experience scaling problems, such as huge or small fonts, etc 2017-02-08 09:32:54,127 to fix this issue, try the dpi switch, or use a patched Xorg dummy driver Is the Mac display a high DPI display? What resolution? (actual > specifications not Apple's marketing terms) What does the client see it > as? (client and server command line output will log it) > 2017-02-08 09:32:54,065 client root window size is 1440x900 with 1 display 2017-02-08 09:32:54,065 ddoole-ltm1.internal.salesforce.com (508x317 mm - DPI: 72x72) workarea: 1440x873 at 0x31 2017-02-08 09:32:54,065 monitor 1 2017-02-08 09:32:54,068 server virtual display now set to 1440x900 The output from the "Xpra.app/Contents/Helpers/NativeGUI_info" would be > useful too. > That give a fair bit of output. If you think a ticket is in order, I'll attach it there. > You can try changing the DPI manually, ie: add {{{--dpi=96}}} to the > client command line. > If that works, you can stick this setting in "~/.xpra/xpra.conf". > Forcing DPI to 96 did the trick. From timothy at hobbs.cz Wed Feb 8 17:56:11 2017 From: timothy at hobbs.cz (Timothy Hobbs) Date: Wed, 8 Feb 2017 18:56:11 +0100 Subject: [winswitch] Keyboard key repetition In-Reply-To: <91770e01-a82b-d88f-0457-b82b54012500@nagafix.co.uk> References: <91770e01-a82b-d88f-0457-b82b54012500@nagafix.co.uk> Message-ID: I will try running without the clipboard. However firefox only starts having this problem occasionally, so it might be a long time before I would be sure that running without the clipboard helped. And of course, disabling the clipboard is painful. Perhaps I should try creating some test setup instead, that would send random keyboard events to a firefox running on a test vm... I believe that only the window displaying firefox freezes. On 02/06/2017 07:03 AM, Antoine Martin via shifter-users wrote: > On 06/02/17 07:50, Timothy Hobbs via shifter-users wrote: >> Hello, >> >> I have a weird problem using subuser with the xpra-x11 bridge >> http://subuser.org/news/0.3.html#the-xpra-x11-bridge. Sometimes, not >> always, but sometimes, I end up with a situation in firefox, that when I >> press a key, the key stays down and starts repeating. So if I am >> backspacing, it will delete the entire line, or I'll get >> nnnnnnnnnnnnnnnnnnnnn. When this happens, firefox freezes before the >> repeated keypresses appear. > That sounds like the whole process is stuck, it may have little to do > with the keyboard which may just be a symptom. > Can you try running with the clipboard disabled? > Some clipboard issues have been reported, clipboard bugs may be able to > cause such problems. > >> Is it possible, in the xpra api, that you >> are sending first a key-down and then a key-up, and some sort of delay >> in the protocol causes the x11 server on the container side of the >> bridge to think that the key was held down and that repetition should >> occure? > By default, we send key-up and key-down events as they occur. > But this can be changed with the "keyboard-sync" switch, see: > https://xpra.org/trac/wiki/Keyboard > >> Where would I look in the code to try to fix this bug? > The most important thing is to find the cause first, only then can you > start looking at the code. > If this is a regression, when did start? Is it platform specific? > Do all the processes stall, or just firefox? Or X11? > Have you tried enabling debug logging? > etc. > > Cheers > Antoine > > >> Regards, >> >> Timothy Hobbs >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users From e.berdoncesbonelo at campus.tu-berlin.de Wed Feb 8 16:42:14 2017 From: e.berdoncesbonelo at campus.tu-berlin.de (Berdonces Bonelo, Erik) Date: Wed, 8 Feb 2017 16:42:14 +0000 Subject: [winswitch] HTML start-desktop crash Message-ID: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> Hello, I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? Thanks a lot, and of course, thanks a lot for your great work and for this tool! Best regards, Erik berdonces From antoine at nagafix.co.uk Thu Feb 9 04:53:15 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 9 Feb 2017 11:53:15 +0700 Subject: [winswitch] Font troubles with Mac client In-Reply-To: References: Message-ID: <16e11ce2-c60d-671b-746b-3d8332b5ab0d@nagafix.co.uk> On 09/02/17 00:48, Douglas Doole wrote: > As always, thanks for your help Antoine. > > I should have looked for DPI problems, but I dismissed it as an issue > since icons looked fine while the fonts were screwy. That's exactly what DPI problems look like: icons tend to be fixed size (or at least a fixed bitmap - unless something like SVG is used), whereas fonts are almost always scaled. > On Tue, Feb 7, 2017 at 8:22 PM Antoine Martin via shifter-users > > wrote: > > This tells us that the DPI settings are being applied from the mac and > the applications you launch only read these settings when they start. > (that's unfortunate, but most applications behave this way) > The server log file should have logged it, please include it. > > > Looking in the server log after connecting from the MacBook I find: > > 2017-02-08 09:32:54,078 setting keyboard layout to 'us' > 2017-02-08 09:32:54,127 DPI set to 17 x 21 (wanted 72 x 72) > 2017-02-08 09:32:54,127 you may experience scaling problems, such as > huge or small fonts, etc > 2017-02-08 09:32:54,127 to fix this issue, try the dpi switch, or use a > patched Xorg dummy driver Always look in the server log first! You should use a patched dummy driver. Hard-coding the DPI manually may work, but not in all cases. We have patched dummy drivers in the repository for most distributions now, including Debian and Ubuntu. > Is the Mac display a high DPI display? What resolution? (actual > specifications not Apple's marketing terms) What does the client see it > as? (client and server command line output will log it) > > > 2017-02-08 09:32:54,065 client root window size is 1440x900 with 1 display > 2017-02-08 09:32:54,065 ddoole-ltm1.internal.salesforce.com > (508x317 mm - DPI: 72x72) > workarea: 1440x873 at 0x31 > 2017-02-08 09:32:54,065 monitor 1 > 2017-02-08 09:32:54,068 server virtual display now set to 1440x900 > > The output from the "Xpra.app/Contents/Helpers/NativeGUI_info" would be > useful too. > > > That give a fair bit of output. If you think a ticket is in order, I'll > attach it there. No need, we know what the problem is now. > > > You can try changing the DPI manually, ie: add {{{--dpi=96}}} to the > client command line. > If that works, you can stick this setting in "~/.xpra/xpra.conf". > > > Forcing DPI to 96 did the trick. Your client output says that the client DPI is 72, you may want to use that value instead. The "hardware" DPI can only be set using the patched dummy driver, the DPI xsettings configuration value should have been set to 72 already, so it is a little bit unexpected that using the "--dpi" switch solved things. Maybe there is still another bug in xpra. Cheers Antoine From antoine at nagafix.co.uk Thu Feb 9 05:09:24 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 9 Feb 2017 12:09:24 +0700 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> Message-ID: <466eac8d-d20d-18a3-d27d-5908a162d367@nagafix.co.uk> On 08/02/17 23:42, Berdonces Bonelo, Erik via shifter-users wrote: > Hello, > > I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. > At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). It will interfere with the clipboard if both Xpra and VirtualBox try to synchronize it, this is known to cause system crashes. > I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). > > Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. You can resize it using the regular desktop tools: xrandr and its gui equivalents. The default size of the desktop mode should be 1920x1080. Changing the default is documented here: https://xpra.org/trac/wiki/Desktop For completeness, here are 2 more options: * not recommended: change the xorg configuration and/or the "xvfb" command line option * run the server using: XPRA_DEFAULT_VFB_RESOLUTION=1280x1024 xpra start-desktop --start=fluxbox Note: the resolution chosen must be supported by the server, you use "xrandr" to get the full list. > Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. I don't understand what "won't work" in this case. > Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? The wiki tends to have better documentation than the man page these days. > Thanks a lot, and of course, thanks a lot for your great work and for this tool! Thanks. The title of your email refers to a crash, but I don't see any details on that. Cheers Antoine > > Best regards, > > Erik berdonces > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Mon Feb 13 08:07:51 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 13 Feb 2017 15:07:51 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 1.0.3 LTS : critical fixes Message-ID: <594e5317-b592-773f-b0fd-436b5187cada@nagafix.co.uk> Hi, This update fixes a number of critical bugs, some of those are security related, others fix some long standing race conditions that could lead to crashes and loss of sessions. It is possible that this version will be marginally slower on some memory bandwidth constrained systems, this is the cost to pay to avoid some of the problematic race conditions. We will try to tackle this better in future releases. Updating as soon as possible is strongly recommended. The majority of these bugs have been present for a very long time - including in the old 0.14.x LTS branch, if you are still stuck on an EOLed version, now is a good time to move on. Release notes: - fix memcpy overflow - fix ssh password leak in connection strings - fix race condition in system tray paint updates - fix iconified window coordinates with MS Windows clients - fix "~" directory created by mistake - fix race condition between encoders and X11 destroy events - fix invalid packet header error handler - fix missing build flags, built root stripping - fix out of range quality values sent to pixel encoders - fix scroll debugging log message format - fix scroll encoding sometimes wrongly used - fix scroll encoding fragmentation performance - fix lost wheel events delta with MS Windows clients - fix detected OpenGL size constraints wrongly overruled - fix packet errors with non-string errors (ie: OpenGL) - fix clipboard loops with some greedy clients (ie: MS Windows) - try to prevent X11 crash following keyboard setup - handle non-suid Xorg binary location used in Ubuntu - remove hardcoded DPI option for Debian and Ubuntu (use patched Xdummy) - disable unused and unsafe 24bpp pixel modes with x264 encoder - OSX library updates The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Beta: https://xpra.org/beta/ Cheers Antoine From erik.berdoncesbonelo at tu-berlin.de Mon Feb 13 09:51:18 2017 From: erik.berdoncesbonelo at tu-berlin.de (Berdonces Bonelo, Erik) Date: Mon, 13 Feb 2017 09:51:18 +0000 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> Message-ID: <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> Hi, I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. Errors are as it follows: ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :0 Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 2017-02-13 09:46:02,018 killing xvfb with pid 5842 ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask 0002 This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) Thanks! Best regards, Erik Berdonces Bonelo On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: Hello, I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? Thanks a lot, and of course, thanks a lot for your great work and for this tool! Best regards, Erik berdonces From antoine at nagafix.co.uk Mon Feb 13 10:25:51 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 13 Feb 2017 17:25:51 +0700 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> Message-ID: <12cc2f2e-e150-a0dd-b990-68c38d252f9a@nagafix.co.uk> On 13/02/17 16:51, Berdonces Bonelo, Erik via shifter-users wrote: > Hi, > > I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. > > On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. Removing VirtualBox additions will work but it's a little bit drastic, disabling the clipboard synchronization in your VM settings should be enough. > However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. > > Errors are as it follows: > > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon (snip) > Using display number provided by Xvfb: :0 > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 > 2017-02-13 09:46:02,018 killing xvfb with pid 5842 > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask > 0002 > > This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I'm not seeing this problem at all on Ubuntu 14.04. You may want to retry with xpra 1.0.3 If that doesn't help then I suspect that your setup is different in some crucial way. NFS home perhaps? You can try creating the unix domain sockets in different places until you figure out the ones that work and the ones that don't: xpra start --bind=/tmp/ Or even: xpra start --bind=/tmp/TESTSOCKETFILENAME > I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. The list of *packages* will be identical for both users, and the websockify library should be accessible in both cases. It may not be able to reach the dbus *server* however, if you don't start one. This should not be fatal for xpra, though it may be required by other desktop applications. > If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. > > These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) The websockify package in Ubuntu 14.04 is probably too old. If you are unable to use a newer distribution version, you should be able to upgrade the websockify package manually. Cheers Antoine > > Thanks! > Best regards, > > Erik Berdonces Bonelo > > > On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: > > Hello, > > I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. > At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). > > Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. > > Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. > > Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? > > Thanks a lot, and of course, thanks a lot for your great work and for this tool! > > Best regards, > > Erik berdonces > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From erik.berdoncesbonelo at tu-berlin.de Mon Feb 13 11:19:22 2017 From: erik.berdoncesbonelo at tu-berlin.de (Berdonces Bonelo, Erik) Date: Mon, 13 Feb 2017 11:19:22 +0000 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> Message-ID: <8CCDD46C-91C7-4BA2-94E5-3633126188C5@tu-berlin.de> Hello, As a small update, I?ve been trying with different versions of xPra, and seems that all the 1.X versions do not work with Ubuntu 14.04 LTS. The latest version compatible with ubuntu 14.04 is 0.15.10-1 of Xpra. Best regards, Erik Berdonces On Feb 13, 2017, at 10:51 AM, Berdonces Bonelo, Erik > wrote: Hi, I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. Errors are as it follows: ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :0 Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 2017-02-13 09:46:02,018 killing xvfb with pid 5842 ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask 0002 This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) Thanks! Best regards, Erik Berdonces Bonelo On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: Hello, I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? Thanks a lot, and of course, thanks a lot for your great work and for this tool! Best regards, Erik berdonces From antoine at nagafix.co.uk Mon Feb 13 11:27:42 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 13 Feb 2017 18:27:42 +0700 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <8CCDD46C-91C7-4BA2-94E5-3633126188C5@tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> <8CCDD46C-91C7-4BA2-94E5-3633126188C5@tu-berlin.de> Message-ID: <4bc2c620-dfcb-fd70-c694-640a62105872@nagafix.co.uk> On 13/02/17 18:19, Berdonces Bonelo, Erik via shifter-users wrote: > Hello, > > As a small update, I?ve been trying with different versions of xPra, and seems that all the 1.X versions do not work with Ubuntu 14.04 LTS. All the 1.x versions have been tested with Ubuntu 14.04, including 1.0.3 which was released today. "do not work" is not specific enough, please see: http://xpra.org/trac/wiki/ReportingBugs Cheers Antoine > The latest version compatible with ubuntu 14.04 is 0.15.10-1 of Xpra. > > Best regards, > > Erik Berdonces > > On Feb 13, 2017, at 10:51 AM, Berdonces Bonelo, Erik > wrote: > > Hi, > > I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. > > On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. > However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. > > Errors are as it follows: > > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon > Initializing built-in extension Generic Event Extension > Initializing built-in extension SHAPE > Initializing built-in extension MIT-SHM > Initializing built-in extension XInputExtension > Initializing built-in extension XTEST > Initializing built-in extension BIG-REQUESTS > Initializing built-in extension SYNC > Initializing built-in extension XKEYBOARD > Initializing built-in extension XC-MISC > Initializing built-in extension SECURITY > Initializing built-in extension XINERAMA > Initializing built-in extension XFIXES > Initializing built-in extension RENDER > Initializing built-in extension RANDR > Initializing built-in extension COMPOSITE > Initializing built-in extension DAMAGE > Initializing built-in extension MIT-SCREEN-SAVER > Initializing built-in extension DOUBLE-BUFFER > Initializing built-in extension RECORD > Initializing built-in extension DPMS > Initializing built-in extension Present > Initializing built-in extension DRI3 > Initializing built-in extension X-Resource > Initializing built-in extension XVideo > Initializing built-in extension XVideo-MotionCompensation > Initializing built-in extension SELinux > Initializing built-in extension GLX > [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! > Using display number provided by Xvfb: :0 > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 > 2017-02-13 09:46:02,018 killing xvfb with pid 5842 > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask > 0002 > > This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. > > These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) > > Thanks! > Best regards, > > Erik Berdonces Bonelo > > > On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: > > Hello, > > I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. > At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). > > Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. > > Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. > > Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? > > Thanks a lot, and of course, thanks a lot for your great work and for this tool! > > Best regards, > > Erik berdonces > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From erik.berdoncesbonelo at tu-berlin.de Mon Feb 13 12:44:44 2017 From: erik.berdoncesbonelo at tu-berlin.de (Berdonces Bonelo, Erik) Date: Mon, 13 Feb 2017 12:44:44 +0000 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <8CCDD46C-91C7-4BA2-94E5-3633126188C5@tu-berlin.de> References: <617D1A03-BDFA-4DBD-9B3C-3DC0C0D0837F@campus.tu-berlin.de> <2F8BDE22-5AD8-4BC2-8B7E-97904116876F@tu-berlin.de> <8CCDD46C-91C7-4BA2-94E5-3633126188C5@tu-berlin.de> Message-ID: <19EC7AC2-E718-4640-B90D-D957432A0BB5@tu-berlin.de> Hi again, I?m sorry but I?m not receiving any of your mails in my mailbox. I have to go to the ML archives an read the answers there. When I meant it doesn?t work is that it throws exactly the same error. And I?m not using any funny or strange configuration. It?s just a plain Ubuntu 14.04 server installed with default configuration, just install everything, enable SSH, and install xPra using the remote winswitch repo. 0.15.10-1 works as expected, but any version after this, throws the errors that I sent in the previous message. So procedure to reproduce: 1. Install Ubuntu Server x64 14.04 in VirtualBox (running in MacOS) or any server (I have already tried in both). Simple settings, just enabling SSH server to remote connect and no interface or anything needed. If you want you can install SSH manually later on yourself, but this doesn?t affect the result. No NFS, nothing strange, just a plain installation of ubuntu. 2. Update the packages and install xTerm:`sudo apt-get update && apt-get upgrade -y && apt-get install xterm` 3. Install xPra (via winswitch or deb packages): 3.1Follow the instructions in https://winswitch.org/downloads/debian-repository.html?dist_select=trusty for trusty (14.04). 3.2 I also tried the alternative alternative installing with the deb packages manually from http://xpra.org/dists/trusty/main/binary-amd64/ with dpkg and apt-get install -f (both procedures 3.1 and 3.2 result in the same error later on). I made sure to install websockify, python-xxhash, python-reencode, ffmpeg-xpra when installing deb packages manually. Usually I use the winswitch PPA repo as it?s much easier. Xpra gets installed with version 1.0.3: sturgelose at gilgamesh:~$ xpra --version xpra v1.0.3-r15051 4. Add user ubuntu to Xpra group `sudo usermod -a -G Xpra ubuntu` to avoid problems. 5. Execute `xpra start --bind-tcp=0.0.0.0:14500 --start-child=xterm` (just start a screen with xterm). There is nothing running in port 14500. You can also try with different ports, and will result the same problems. Also tried with `--html=on` option with the HTML5 client, it will happen exactly the same. And I tried different computers as clients. If the command in 5. is ran as default non root user (ubuntu user), which is part of the Xpra group (added in 4.), the server doesn?t start and the daemon ends (mostly the error I sent in previous messages): 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 If run the command (5.) as root user (something I?d like to avoid doing), the socket connects, but then when connecting from the client, it says it can?t find bus package (and other packages), which is installed? still you can try to connect a client but the dbus error will kill the process. _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :1 Xlib: extension "RANDR" missing on display ":1". Xlib: extension "RANDR" missing on display ":1". /home/sturgelose/.xpra/gilgamesh-1 is not responding, waiting for it to timeout before clearing it..... 2017-02-13 13:10:02,461 created unix domain socket: /home/sturgelose/.xpra/gilgamesh-1 2017-02-13 13:10:02,462 Warning: failed to create socket directory '/var/run/xpra' 2017-02-13 13:10:02,463 [Errno 13] Permission denied: '/var/run/xpra' 2017-02-13 13:10:02,463 Warning: cannot create socket '/var/run/xpra/gilgamesh-1' 2017-02-13 13:10:02,464 [Errno 2] No such file or directory 2017-02-13 13:10:02,465 /var/run/xpra does not exist 2017-02-13 13:10:02,465 user 'sturgelose' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra 2017-02-13 13:10:02,551 Warning: menu forwarding is disabled: 2017-02-13 13:10:02,552 cannot load dbus helper: No module named dbus 2017-02-13 13:10:02,932 Warning: libvpx ABI version 5 is too old: 2017-02-13 13:10:02,932 disabling YUV444P support with VP9 2017-02-13 13:10:03,028 Warning: failed to load the mdns avahi publisher: 2017-02-13 13:10:03,029 No module named avahi 2017-02-13 13:10:03,029 either fix your installation or use the 'mdns=no' option 2017-02-13 13:10:03,035 Warning: no X11 RandR support on :1 2017-02-13 13:10:03,953 Error: cannot import websockify connection handler: 2017-02-13 13:10:03,953 cannot import name WebSocketRequestHandler 2017-02-13 13:10:03,954 the html server will not be available 2017-02-13 13:10:04,036 Error: failed to import the virtual video module: 2017-02-13 13:10:04,037 No module named _dbus_bindings 2017-02-13 13:10:04,051 pulseaudio server started with pid 1349 Warning: failed to import GStreamer: GStreamer 1.0: Namespace Gst not available GStreamer 0.10: No module named pygst 2017-02-13 13:10:04,496 Error: failed to query sound subsystem: 2017-02-13 13:10:04,497 query did not return any data 2017-02-13 13:10:04,499 Warning: failed to load or register our dbus notifications forwarder: 2017-02-13 13:10:04,499 No module named dbus.service 2017-02-13 13:10:04,499 if you do not have a dedicated dbus session for this xpra instance, 2017-02-13 13:10:04,500 use the 'notifications=no' option 2017-02-13 13:10:04,501 Warning: cannot load dbus helper: 2017-02-13 13:10:04,502 No module named dbus 2017-02-13 13:10:04,510 Warning: cannot load dbus server: 2017-02-13 13:10:04,511 No module named dbus 2017-02-13 13:10:04,517 started command 'xterm' with pid 1370 2017-02-13 13:10:04,518 xpra X11 version 1.0.3-r15051 64-bit 2017-02-13 13:10:04,519 uid=1000 (sturgelose), gid=1000 (sturgelose) 2017-02-13 13:10:04,519 running with pid 1298 on Linux Ubuntu 14.04 trusty 2017-02-13 13:10:04,520 connected to X11 display :1 2017-02-13 13:10:04,632 xpra is ready. 2017-02-13 13:10:04,635 2.0GB of system memory 2017-02-13 13:10:11,299 New tcp connection received from 130.149.223.41:50452 2017-02-13 13:10:11,302 Warning: client expects a challenge but this connection is unauthenticated 2017-02-13 13:10:11,319 Handshake complete; enabling connection 2017-02-13 13:10:11,424 Warning: xxhash python bindings not found 2017-02-13 13:10:11,425 no scrolling detection 2017-02-13 13:10:11,438 server error processing new connection from Protocol(tcp socket: 130.149.223.55:14500 <- 130.149.223.41:50452): No module named dbus Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 893, in _process_hello self.hello_oked(proto, packet, c, auth_caps) File "/usr/lib/python2.7/dist-packages/xpra/server/server_base.py", line 1115, in hello_oked self.default_speed, self.default_min_speed) File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 357, in __init__ self.dbus_server = dbus_exception_wrap(make_dbus_server, "setting up client dbus instance") File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", line 12, in dbus_exception_wrap v = fn() File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 355, in make_dbus_server from xpra.server.dbus.dbus_source import DBUS_Source File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_source.py", line 7, in from xpra.dbus.helper import dbus_to_native File "/usr/lib/python2.7/dist-packages/xpra/dbus/helper.py", line 7, in import dbus ImportError: No module named dbus 2017-02-13 13:10:11,444 Disconnecting client 130.149.223.41:50452: 2017-02-13 13:10:11,445 server error (error accepting new connection) This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure in Ubuntu 16.04 and it works as expected (no errors nor warnings). In the client I only have one screen (disconnected the second one and rebooted even). I tried with other computers as clients and it?s just the same. The problem is in the xPra server. I attach as well an export of the server configuration done with xPra. From erik.berdoncesbonelo at tu-berlin.de Mon Feb 13 14:24:32 2017 From: erik.berdoncesbonelo at tu-berlin.de (Berdonces Bonelo, Erik) Date: Mon, 13 Feb 2017 14:24:32 +0000 Subject: [winswitch] HTML start-desktop crash References: <19EC7AC2-E718-4640-B90D-D957432A0BB5@tu-berlin.de> Message-ID: <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> Sending again because the attached file is too big. It can be found uploaded in OneDrive in this link: https://1drv.ms/u/s!Ar0lgicIauUbhOQEbXldgJy5H-BMbg Begin forwarded message: From: "Berdonces Bonelo, Erik" > Subject: Re: HTML start-desktop crash Date: February 13, 2017 at 1:44:44 PM GMT+1 To: shifter-users at lists.devloop.org.uk Hi again, I?m sorry but I?m not receiving any of your mails in my mailbox. I have to go to the ML archives an read the answers there. When I meant it doesn?t work is that it throws exactly the same error. And I?m not using any funny or strange configuration. It?s just a plain Ubuntu 14.04 server installed with default configuration, just install everything, enable SSH, and install xPra using the remote winswitch repo. 0.15.10-1 works as expected, but any version after this, throws the errors that I sent in the previous message. So procedure to reproduce: 1. Install Ubuntu Server x64 14.04 in VirtualBox (running in MacOS) or any server (I have already tried in both). Simple settings, just enabling SSH server to remote connect and no interface or anything needed. If you want you can install SSH manually later on yourself, but this doesn?t affect the result. No NFS, nothing strange, just a plain installation of ubuntu. 2. Update the packages and install xTerm:`sudo apt-get update && apt-get upgrade -y && apt-get install xterm` 3. Install xPra (via winswitch or deb packages): 3.1Follow the instructions in https://winswitch.org/downloads/debian-repository.html?dist_select=trusty for trusty (14.04). 3.2 I also tried the alternative alternative installing with the deb packages manually from http://xpra.org/dists/trusty/main/binary-amd64/ with dpkg and apt-get install -f (both procedures 3.1 and 3.2 result in the same error later on). I made sure to install websockify, python-xxhash, python-reencode, ffmpeg-xpra when installing deb packages manually. Usually I use the winswitch PPA repo as it?s much easier. Xpra gets installed with version 1.0.3: sturgelose at gilgamesh:~$ xpra --version xpra v1.0.3-r15051 4. Add user ubuntu to Xpra group `sudo usermod -a -G Xpra ubuntu` to avoid problems. 5. Execute `xpra start --bind-tcp=0.0.0.0:14500 --start-child=xterm` (just start a screen with xterm). There is nothing running in port 14500. You can also try with different ports, and will result the same problems. Also tried with `--html=on` option with the HTML5 client, it will happen exactly the same. And I tried different computers as clients. If the command in 5. is ran as default non root user (ubuntu user), which is part of the Xpra group (added in 4.), the server doesn?t start and the daemon ends (mostly the error I sent in previous messages): 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 If run the command (5.) as root user (something I?d like to avoid doing), the socket connects, but then when connecting from the client, it says it can?t find bus package (and other packages), which is installed? still you can try to connect a client but the dbus error will kill the process. _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :1 Xlib: extension "RANDR" missing on display ":1". Xlib: extension "RANDR" missing on display ":1". /home/sturgelose/.xpra/gilgamesh-1 is not responding, waiting for it to timeout before clearing it..... 2017-02-13 13:10:02,461 created unix domain socket: /home/sturgelose/.xpra/gilgamesh-1 2017-02-13 13:10:02,462 Warning: failed to create socket directory '/var/run/xpra' 2017-02-13 13:10:02,463 [Errno 13] Permission denied: '/var/run/xpra' 2017-02-13 13:10:02,463 Warning: cannot create socket '/var/run/xpra/gilgamesh-1' 2017-02-13 13:10:02,464 [Errno 2] No such file or directory 2017-02-13 13:10:02,465 /var/run/xpra does not exist 2017-02-13 13:10:02,465 user 'sturgelose' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra 2017-02-13 13:10:02,551 Warning: menu forwarding is disabled: 2017-02-13 13:10:02,552 cannot load dbus helper: No module named dbus 2017-02-13 13:10:02,932 Warning: libvpx ABI version 5 is too old: 2017-02-13 13:10:02,932 disabling YUV444P support with VP9 2017-02-13 13:10:03,028 Warning: failed to load the mdns avahi publisher: 2017-02-13 13:10:03,029 No module named avahi 2017-02-13 13:10:03,029 either fix your installation or use the 'mdns=no' option 2017-02-13 13:10:03,035 Warning: no X11 RandR support on :1 2017-02-13 13:10:03,953 Error: cannot import websockify connection handler: 2017-02-13 13:10:03,953 cannot import name WebSocketRequestHandler 2017-02-13 13:10:03,954 the html server will not be available 2017-02-13 13:10:04,036 Error: failed to import the virtual video module: 2017-02-13 13:10:04,037 No module named _dbus_bindings 2017-02-13 13:10:04,051 pulseaudio server started with pid 1349 Warning: failed to import GStreamer: GStreamer 1.0: Namespace Gst not available GStreamer 0.10: No module named pygst 2017-02-13 13:10:04,496 Error: failed to query sound subsystem: 2017-02-13 13:10:04,497 query did not return any data 2017-02-13 13:10:04,499 Warning: failed to load or register our dbus notifications forwarder: 2017-02-13 13:10:04,499 No module named dbus.service 2017-02-13 13:10:04,499 if you do not have a dedicated dbus session for this xpra instance, 2017-02-13 13:10:04,500 use the 'notifications=no' option 2017-02-13 13:10:04,501 Warning: cannot load dbus helper: 2017-02-13 13:10:04,502 No module named dbus 2017-02-13 13:10:04,510 Warning: cannot load dbus server: 2017-02-13 13:10:04,511 No module named dbus 2017-02-13 13:10:04,517 started command 'xterm' with pid 1370 2017-02-13 13:10:04,518 xpra X11 version 1.0.3-r15051 64-bit 2017-02-13 13:10:04,519 uid=1000 (sturgelose), gid=1000 (sturgelose) 2017-02-13 13:10:04,519 running with pid 1298 on Linux Ubuntu 14.04 trusty 2017-02-13 13:10:04,520 connected to X11 display :1 2017-02-13 13:10:04,632 xpra is ready. 2017-02-13 13:10:04,635 2.0GB of system memory 2017-02-13 13:10:11,299 New tcp connection received from 130.149.223.41:50452 2017-02-13 13:10:11,302 Warning: client expects a challenge but this connection is unauthenticated 2017-02-13 13:10:11,319 Handshake complete; enabling connection 2017-02-13 13:10:11,424 Warning: xxhash python bindings not found 2017-02-13 13:10:11,425 no scrolling detection 2017-02-13 13:10:11,438 server error processing new connection from Protocol(tcp socket: 130.149.223.55:14500 <- 130.149.223.41:50452): No module named dbus Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 893, in _process_hello self.hello_oked(proto, packet, c, auth_caps) File "/usr/lib/python2.7/dist-packages/xpra/server/server_base.py", line 1115, in hello_oked self.default_speed, self.default_min_speed) File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 357, in __init__ self.dbus_server = dbus_exception_wrap(make_dbus_server, "setting up client dbus instance") File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", line 12, in dbus_exception_wrap v = fn() File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 355, in make_dbus_server from xpra.server.dbus.dbus_source import DBUS_Source File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_source.py", line 7, in from xpra.dbus.helper import dbus_to_native File "/usr/lib/python2.7/dist-packages/xpra/dbus/helper.py", line 7, in import dbus ImportError: No module named dbus 2017-02-13 13:10:11,444 Disconnecting client 130.149.223.41:50452: 2017-02-13 13:10:11,445 server error (error accepting new connection) This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure in Ubuntu 16.04 and it works as expected (no errors nor warnings). In the client I only have one screen (disconnected the second one and rebooted even). I tried with other computers as clients and it?s just the same. The problem is in the xPra server. I attach as well an export of the server configuration done with xPra. From antoine at nagafix.co.uk Mon Feb 13 16:21:52 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 13 Feb 2017 23:21:52 +0700 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> References: <19EC7AC2-E718-4640-B90D-D957432A0BB5@tu-berlin.de> <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> Message-ID: > I?m sorry but I?m not receiving any of your mails in my mailbox. I have to go to the ML archives an read the answers there. Are you subscribed to the mailing list? (...) > ImportError: No module named dbus Install python-dbus or dbus-python (not sure which one) and this error will go away. Alternatively you may be able to workaround this error by adding "--dbus-control=no" to your xpra server command line. (untested) The next v1.x update will change this into a log error message: http://xpra.org/trac/changeset/15056 (...) > This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure in Ubuntu 16.04 and it works as expected (no errors nor warnings). Ubuntu 16.04 must have the dbus bindings already installed. > In the client I only have one screen (disconnected the second one and rebooted even). I tried with other computers as clients and it?s just the same. The problem is in the xPra server. Yes, your server log says that this is caused by the missing dbus bindings: > Disconnecting client XXX.XXX.XXX.XXX:XXXXX > server error (error accepting new connection) Cheers Antoine From lukashaase at gmx.at Mon Feb 13 23:45:02 2017 From: lukashaase at gmx.at (Lukas Haase) Date: Tue, 14 Feb 2017 00:45:02 +0100 Subject: [winswitch] Xpra crash (Gdk error) Message-ID: Hi, Once in a while xpra crashes with a message like the following: Gdk-ERROR **: The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 30573157 error_code 3 request_code 3 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Abort (core dumped) The X server (Xorg-nosuid /usr/bin/Xorg -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile /home/lukas/.xpra/Xorg-10.log -config /etc/xpra/xorg.conf :2000) as well as the client continue running in the background. I think it is hopeless to debug this and hence do not want to file a bug report because this occurs after working for many days. So debugging/getting this reproducible is hopeless and even if I would enable logging, the log file would probably be GB size. I would rather like to understand what's going on and maybe prevent doing actions that could result in this state. Any idea what could cause a situation like this? Since the error is "BadWindow" I also want to mention that the xpra continuously generates output like this: 2017-02-13 12:36:36,599 failed to manage client : XError: BadWindow Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client self.do_manage_client(gdkwindow) File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ trap._exit(True) File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit raise XError(get_X_error(error)) XError: XError: BadWindow 2017-02-13 12:36:36,609 failed to manage client : XError: BadWindow Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client self.do_manage_client(gdkwindow) File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ trap._exit(True) File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit raise XError(get_X_error(error)) XError: XError: BadWindow as well as: 2017-02-13 15:13:01,663 client 64: unknown string message: 0xc22fL / 49371 / 0 but xpra does not crash - usually for days. However, after a couple of days xpra server will eventually crash with the Gdk error above. It also seems that I can resume the X server/X client with "xpra upgrade" (which mitigates the problem a bit). Thanks, Lukas From antoine at nagafix.co.uk Tue Feb 14 02:59:52 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 14 Feb 2017 09:59:52 +0700 Subject: [winswitch] Xpra crash (Gdk error) In-Reply-To: References: Message-ID: <77e1fbe1-8052-c20c-f811-cf3be51f093c@nagafix.co.uk> On 14/02/17 06:45, Lukas Haase via shifter-users wrote: > Hi, > > Once in a while xpra crashes with a message like the following: > > Gdk-ERROR **: The program 'Xpra' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 30573157 error_code 3 request_code 3 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > aborting... > Abort (core dumped) This GDK error can occur when: 1) xpra fails to synchronize / flush the connection to the X11 server after making a native X11 call 2) xpra calls X11 functions from the wrong thread Both are bugs. > The X server (Xorg-nosuid /usr/bin/Xorg -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile /home/lukas/.xpra/Xorg-10.log -config /etc/xpra/xorg.conf :2000) as well as the client continue running in the background. > > I think it is hopeless to debug this and hence do not want to file a bug report because this occurs after working for many days. So debugging/getting this reproducible is hopeless and even if I would enable logging, the log file would probably be GB size. The log file would still be useful to see: the last few entries in it would tell us what part of the code was potentially doing this illegal access. > I would rather like to understand what's going on and maybe prevent doing actions that could result in this state. Looks like a bug needs fixing in xpra.. > Any idea what could cause a situation like this? > > Since the error is "BadWindow" I also want to mention that the xpra continuously generates output like this: > > 2017-02-13 12:36:36,599 failed to manage client : XError: BadWindow > Traceback (most recent call last): > File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client > self.do_manage_client(gdkwindow) > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ > trap._exit(True) > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit > raise XError(get_X_error(error)) > XError: XError: BadWindow > 2017-02-13 12:36:36,609 failed to manage client : XError: BadWindow > Traceback (most recent call last): > File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client > self.do_manage_client(gdkwindow) > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ > trap._exit(True) > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit > raise XError(get_X_error(error)) > XError: XError: BadWindow It should be harmless and just means that the window disappeared before we could manage it. We probably shouldn't be logging an error here. > as well as: > > 2017-02-13 15:13:01,663 client 64: unknown string message: 0xc22fL / 49371 / 0 This is a message specific to MS Windows clients, we just log the ones we are not expecting to see just in case they provide us a clue for bugs / unusual behaviour. > but xpra does not crash - usually for days. > However, after a couple of days xpra server will eventually crash with the Gdk error above. > > It also seems that I can resume the X server/X client with "xpra upgrade" (which mitigates the problem a bit). Ideally, we could fix that bug and avoid the need for "xpra upgrade". Cheers Antoine > > > Thanks, > Lukas > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From lukashaase at gmx.at Tue Feb 14 05:54:28 2017 From: lukashaase at gmx.at (Lukas Haase) Date: Tue, 14 Feb 2017 06:54:28 +0100 Subject: [winswitch] Xpra crash (Gdk error) In-Reply-To: <77e1fbe1-8052-c20c-f811-cf3be51f093c@nagafix.co.uk> References: , <77e1fbe1-8052-c20c-f811-cf3be51f093c@nagafix.co.uk> Message-ID: Hi Antoine, > [...] > The log file would still be useful to see: the last few entries in it > would tell us what part of the code was potentially doing this illegal > access. What amount of log level would help to identify this problem? Or asked differently, with which "-d" should I start the xpra server? > [...] > > Since the error is "BadWindow" I also want to mention that the xpra continuously generates output like this: > > > > 2017-02-13 12:36:36,599 failed to manage client : XError: BadWindow > > Traceback (most recent call last): > > File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client > > self.do_manage_client(gdkwindow) > > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ > > trap._exit(True) > > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit > > raise XError(get_X_error(error)) > > XError: XError: BadWindow > > 2017-02-13 12:36:36,609 failed to manage client : XError: BadWindow > > Traceback (most recent call last): > > File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client > > self.do_manage_client(gdkwindow) > > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ > > trap._exit(True) > > File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit > > raise XError(get_X_error(error)) > > XError: XError: BadWindow > It should be harmless and just means that the window disappeared before > we could manage it. > We probably shouldn't be logging an error here. Yes, I would really appreciate that. Errors - in particular with stack traces showing some internals always causes me to think about heavy problems. I think many programs draw and quickly remove windows - at least this happens all the time with me. Thanks, Lukas From antoine at nagafix.co.uk Tue Feb 14 05:59:57 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 14 Feb 2017 12:59:57 +0700 Subject: [winswitch] Xpra crash (Gdk error) In-Reply-To: References: <77e1fbe1-8052-c20c-f811-cf3be51f093c@nagafix.co.uk> Message-ID: <97244a0e-5180-2200-c981-324d11bd2b7b@nagafix.co.uk> On 14/02/17 12:54, Lukas Haase wrote: > Hi Antoine, > >> [...] >> The log file would still be useful to see: the last few entries in it >> would tell us what part of the code was potentially doing this illegal >> access. > > What amount of log level would help to identify this problem? Or asked differently, with which "-d" should I start the xpra server? Since we don't know where the error is going to be coming from... "-d all" is the best bet... though it may slow things down quite a bit. And sometimes that's even enough to make the problems go away :/ >> [...] >>> Since the error is "BadWindow" I also want to mention that the xpra continuously generates output like this: >>> >>> 2017-02-13 12:36:36,599 failed to manage client : XError: BadWindow >>> Traceback (most recent call last): >>> File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client >>> self.do_manage_client(gdkwindow) >>> File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ >>> trap._exit(True) >>> File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit >>> raise XError(get_X_error(error)) >>> XError: XError: BadWindow >>> 2017-02-13 12:36:36,609 failed to manage client : XError: BadWindow >>> Traceback (most recent call last): >>> File "/usr/lib64/python2.6/site-packages/xpra/x11/gtk2/wm.py", line 346, in _manage_client >>> self.do_manage_client(gdkwindow) >>> File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 168, in __exit__ >>> trap._exit(True) >>> File "/usr/lib64/python2.6/site-packages/xpra/gtk_common/error.py", line 100, in _exit >>> raise XError(get_X_error(error)) >>> XError: XError: BadWindow >> It should be harmless and just means that the window disappeared before >> we could manage it. >> We probably shouldn't be logging an error here. > > Yes, I would really appreciate that. > Errors - in particular with stack traces showing some internals always causes me to think about heavy problems. Maybe it is related to the problem above? How do I reproduce it? Which particular application / platform / settings / etc. > I think many programs draw and quickly remove windows - at least this happens all the time with me. gtkperf does that, and we use it to stress test - but it has not caused such problems lately - or we would have fixed them. Cheers Antoine From erik.berdoncesbonelo at tu-berlin.de Tue Feb 14 09:16:14 2017 From: erik.berdoncesbonelo at tu-berlin.de (Berdonces Bonelo, Erik) Date: Tue, 14 Feb 2017 09:16:14 +0000 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> References: <19EC7AC2-E718-4640-B90D-D957432A0BB5@tu-berlin.de> <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> Message-ID: <2FBE1786-FD03-4BF7-9264-11F0BE500D2E@tu-berlin.de> Hello, I tried again to enroll into the ML and I hope that now it works well.. Otherwise, I tried with the flag you pointed out (--dbus-control=no), and I can connect using xPra client. Hower, I was expecting to use the html flag to connect using the HTML5 client and it doesn?t work (attaching the logs underneath). As it seems, most of the modules used by xPra can?t be loaded even if they are installed (dbus, websockify, and all the others are installed). I also installed the python-dbus, but seems that the error messages haven?t changed at all?. Also, as I can see, the /var/run/xpra folder is not created, so that might be the problem?.. May it be that the installation is not creating the folder properly? xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon --start-child=xterm --dbus-control=no _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :1 Xlib: extension "RANDR" missing on display ":1". Xlib: extension "RANDR" missing on display ":1". 2017-02-14 10:10:23,124 created unix domain socket: /home/sturgelose/.xpra/gilgamesh-1 2017-02-14 10:10:23,124 Warning: failed to create socket directory '/var/run/xpra' 2017-02-14 10:10:23,125 [Errno 13] Permission denied: '/var/run/xpra' 2017-02-14 10:10:23,125 Warning: cannot create socket '/var/run/xpra/gilgamesh-1' 2017-02-14 10:10:23,126 [Errno 2] No such file or directory 2017-02-14 10:10:23,126 /var/run/xpra does not exist 2017-02-14 10:10:23,127 user 'sturgelose' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra 2017-02-14 10:10:23,182 Warning: menu forwarding is disabled: 2017-02-14 10:10:23,183 cannot load dbus helper: No module named dbus 2017-02-14 10:10:23,397 Warning: libvpx ABI version 5 is too old: 2017-02-14 10:10:23,398 disabling YUV444P support with VP9 2017-02-14 10:10:23,455 Warning: failed to load the mdns avahi publisher: 2017-02-14 10:10:23,456 No module named avahi 2017-02-14 10:10:23,456 either fix your installation or use the 'mdns=no' option 2017-02-14 10:10:23,462 Warning: no X11 RandR support on :1 2017-02-14 10:10:24,237 Error: cannot import websockify connection handler: 2017-02-14 10:10:24,238 cannot import name WebSocketRequestHandler 2017-02-14 10:10:24,238 the html server will not be available 2017-02-14 10:10:24,315 Error: failed to import the virtual video module: 2017-02-14 10:10:24,316 No module named _dbus_bindings 2017-02-14 10:10:24,328 pulseaudio server started with pid 1844 Warning: failed to import GStreamer: GStreamer 1.0: Namespace Gst not available GStreamer 0.10: No module named pygst 2017-02-14 10:10:24,749 Error: failed to query sound subsystem: 2017-02-14 10:10:24,750 query did not return any data 2017-02-14 10:10:24,752 Warning: failed to load or register our dbus notifications forwarder: 2017-02-14 10:10:24,752 No module named dbus.service 2017-02-14 10:10:24,752 if you do not have a dedicated dbus session for this xpra instance, 2017-02-14 10:10:24,753 use the 'notifications=no' option 2017-02-14 10:10:24,754 Warning: cannot load dbus helper: 2017-02-14 10:10:24,755 No module named dbus 2017-02-14 10:10:24,763 started command 'xterm' with pid 1861 2017-02-14 10:10:24,764 xpra X11 version 1.0.3-r15051 64-bit 2017-02-14 10:10:24,764 uid=1000 (sturgelose), gid=1000 (sturgelose) 2017-02-14 10:10:24,765 running with pid 1793 on Linux Ubuntu 14.04 trusty 2017-02-14 10:10:24,766 connected to X11 display :1 2017-02-14 10:10:24,855 xpra is ready. 2017-02-14 10:10:24,868 2.0GB of system memory ^C 2017-02-14 10:10:52,884 got signal SIGINT, exiting 2017-02-14 10:10:52,893 closing TCP socket 0.0.0.0:14500 2017-02-14 10:10:52,898 killing xvfb with pid 1806 2017-02-14 10:10:52,905 removing socket /home/sturgelose/.xpra/gilgamesh-1 Thanks a lot for your time! Best regards, Erik Berdonces On Feb 13, 2017, at 3:24 PM, Berdonces Bonelo, Erik > wrote: Sending again because the attached file is too big. It can be found uploaded in OneDrive in this link: https://1drv.ms/u/s!Ar0lgicIauUbhOQEbXldgJy5H-BMbg Begin forwarded message: From: "Berdonces Bonelo, Erik" > Subject: Re: HTML start-desktop crash Date: February 13, 2017 at 1:44:44 PM GMT+1 To: shifter-users at lists.devloop.org.uk Hi again, I?m sorry but I?m not receiving any of your mails in my mailbox. I have to go to the ML archives an read the answers there. When I meant it doesn?t work is that it throws exactly the same error. And I?m not using any funny or strange configuration. It?s just a plain Ubuntu 14.04 server installed with default configuration, just install everything, enable SSH, and install xPra using the remote winswitch repo. 0.15.10-1 works as expected, but any version after this, throws the errors that I sent in the previous message. So procedure to reproduce: 1. Install Ubuntu Server x64 14.04 in VirtualBox (running in MacOS) or any server (I have already tried in both). Simple settings, just enabling SSH server to remote connect and no interface or anything needed. If you want you can install SSH manually later on yourself, but this doesn?t affect the result. No NFS, nothing strange, just a plain installation of ubuntu. 2. Update the packages and install xTerm:`sudo apt-get update && apt-get upgrade -y && apt-get install xterm` 3. Install xPra (via winswitch or deb packages): 3.1Follow the instructions in https://winswitch.org/downloads/debian-repository.html?dist_select=trusty for trusty (14.04). 3.2 I also tried the alternative alternative installing with the deb packages manually from http://xpra.org/dists/trusty/main/binary-amd64/ with dpkg and apt-get install -f (both procedures 3.1 and 3.2 result in the same error later on). I made sure to install websockify, python-xxhash, python-reencode, ffmpeg-xpra when installing deb packages manually. Usually I use the winswitch PPA repo as it?s much easier. Xpra gets installed with version 1.0.3: sturgelose at gilgamesh:~$ xpra --version xpra v1.0.3-r15051 4. Add user ubuntu to Xpra group `sudo usermod -a -G Xpra ubuntu` to avoid problems. 5. Execute `xpra start --bind-tcp=0.0.0.0:14500 --start-child=xterm` (just start a screen with xterm). There is nothing running in port 14500. You can also try with different ports, and will result the same problems. Also tried with `--html=on` option with the HTML5 client, it will happen exactly the same. And I tried different computers as clients. If the command in 5. is ran as default non root user (ubuntu user), which is part of the Xpra group (added in 4.), the server doesn?t start and the daemon ends (mostly the error I sent in previous messages): 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 If run the command (5.) as root user (something I?d like to avoid doing), the socket connects, but then when connecting from the client, it says it can?t find bus package (and other packages), which is installed? still you can try to connect a client but the dbus error will kill the process. _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :1 Xlib: extension "RANDR" missing on display ":1". Xlib: extension "RANDR" missing on display ":1". /home/sturgelose/.xpra/gilgamesh-1 is not responding, waiting for it to timeout before clearing it..... 2017-02-13 13:10:02,461 created unix domain socket: /home/sturgelose/.xpra/gilgamesh-1 2017-02-13 13:10:02,462 Warning: failed to create socket directory '/var/run/xpra' 2017-02-13 13:10:02,463 [Errno 13] Permission denied: '/var/run/xpra' 2017-02-13 13:10:02,463 Warning: cannot create socket '/var/run/xpra/gilgamesh-1' 2017-02-13 13:10:02,464 [Errno 2] No such file or directory 2017-02-13 13:10:02,465 /var/run/xpra does not exist 2017-02-13 13:10:02,465 user 'sturgelose' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra 2017-02-13 13:10:02,551 Warning: menu forwarding is disabled: 2017-02-13 13:10:02,552 cannot load dbus helper: No module named dbus 2017-02-13 13:10:02,932 Warning: libvpx ABI version 5 is too old: 2017-02-13 13:10:02,932 disabling YUV444P support with VP9 2017-02-13 13:10:03,028 Warning: failed to load the mdns avahi publisher: 2017-02-13 13:10:03,029 No module named avahi 2017-02-13 13:10:03,029 either fix your installation or use the 'mdns=no' option 2017-02-13 13:10:03,035 Warning: no X11 RandR support on :1 2017-02-13 13:10:03,953 Error: cannot import websockify connection handler: 2017-02-13 13:10:03,953 cannot import name WebSocketRequestHandler 2017-02-13 13:10:03,954 the html server will not be available 2017-02-13 13:10:04,036 Error: failed to import the virtual video module: 2017-02-13 13:10:04,037 No module named _dbus_bindings 2017-02-13 13:10:04,051 pulseaudio server started with pid 1349 Warning: failed to import GStreamer: GStreamer 1.0: Namespace Gst not available GStreamer 0.10: No module named pygst 2017-02-13 13:10:04,496 Error: failed to query sound subsystem: 2017-02-13 13:10:04,497 query did not return any data 2017-02-13 13:10:04,499 Warning: failed to load or register our dbus notifications forwarder: 2017-02-13 13:10:04,499 No module named dbus.service 2017-02-13 13:10:04,499 if you do not have a dedicated dbus session for this xpra instance, 2017-02-13 13:10:04,500 use the 'notifications=no' option 2017-02-13 13:10:04,501 Warning: cannot load dbus helper: 2017-02-13 13:10:04,502 No module named dbus 2017-02-13 13:10:04,510 Warning: cannot load dbus server: 2017-02-13 13:10:04,511 No module named dbus 2017-02-13 13:10:04,517 started command 'xterm' with pid 1370 2017-02-13 13:10:04,518 xpra X11 version 1.0.3-r15051 64-bit 2017-02-13 13:10:04,519 uid=1000 (sturgelose), gid=1000 (sturgelose) 2017-02-13 13:10:04,519 running with pid 1298 on Linux Ubuntu 14.04 trusty 2017-02-13 13:10:04,520 connected to X11 display :1 2017-02-13 13:10:04,632 xpra is ready. 2017-02-13 13:10:04,635 2.0GB of system memory 2017-02-13 13:10:11,299 New tcp connection received from 130.149.223.41:50452 2017-02-13 13:10:11,302 Warning: client expects a challenge but this connection is unauthenticated 2017-02-13 13:10:11,319 Handshake complete; enabling connection 2017-02-13 13:10:11,424 Warning: xxhash python bindings not found 2017-02-13 13:10:11,425 no scrolling detection 2017-02-13 13:10:11,438 server error processing new connection from Protocol(tcp socket: 130.149.223.55:14500 <- 130.149.223.41:50452): No module named dbus Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 893, in _process_hello self.hello_oked(proto, packet, c, auth_caps) File "/usr/lib/python2.7/dist-packages/xpra/server/server_base.py", line 1115, in hello_oked self.default_speed, self.default_min_speed) File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 357, in __init__ self.dbus_server = dbus_exception_wrap(make_dbus_server, "setting up client dbus instance") File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", line 12, in dbus_exception_wrap v = fn() File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 355, in make_dbus_server from xpra.server.dbus.dbus_source import DBUS_Source File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_source.py", line 7, in from xpra.dbus.helper import dbus_to_native File "/usr/lib/python2.7/dist-packages/xpra/dbus/helper.py", line 7, in import dbus ImportError: No module named dbus 2017-02-13 13:10:11,444 Disconnecting client 130.149.223.41:50452: 2017-02-13 13:10:11,445 server error (error accepting new connection) This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure in Ubuntu 16.04 and it works as expected (no errors nor warnings). In the client I only have one screen (disconnected the second one and rebooted even). I tried with other computers as clients and it?s just the same. The problem is in the xPra server. I attach as well an export of the server configuration done with xPra. I can?t provide more information from the session, because directly the session doesn?t start! So, there is nothing to do with the encoding or whatsoever, it?s just Xpra not loading any of its dependencies! I?m really not doing anything strange, and I?m totally able to use xPra 1.0.3 in ubuntu 16.04, using exactly the same steps, or Xpra 0.15.10 in ubuntu 14.04. So, there is something wrong with 1.X versions. I hope this time I have redacted everything properly and added all the details... On Feb 13, 2017, at 12:19 PM, Berdonces Bonelo, Erik > wrote: Hello, As a small update, I?ve been trying with different versions of xPra, and seems that all the 1.X versions do not work with Ubuntu 14.04 LTS. The latest version compatible with ubuntu 14.04 is 0.15.10-1 of Xpra. Best regards, Erik Berdonces On Feb 13, 2017, at 10:51 AM, Berdonces Bonelo, Erik > wrote: Hi, I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. Errors are as it follows: ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Using display number provided by Xvfb: :0 Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' xpra initialization error: failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 2017-02-13 09:46:02,018 killing xvfb with pid 5842 ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask 0002 This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) Thanks! Best regards, Erik Berdonces Bonelo On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: Hello, I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? Thanks a lot, and of course, thanks a lot for your great work and for this tool! Best regards, Erik berdonces From antoine at nagafix.co.uk Tue Feb 14 11:36:03 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 14 Feb 2017 18:36:03 +0700 Subject: [winswitch] HTML start-desktop crash In-Reply-To: <2FBE1786-FD03-4BF7-9264-11F0BE500D2E@tu-berlin.de> References: <19EC7AC2-E718-4640-B90D-D957432A0BB5@tu-berlin.de> <054484ED-1F6F-40E0-B2BA-E32F08EE1ACC@tu-berlin.de> <2FBE1786-FD03-4BF7-9264-11F0BE500D2E@tu-berlin.de> Message-ID: <2a8647ae-4012-09a4-0106-be789909e10f@nagafix.co.uk> On 14/02/17 16:16, Berdonces Bonelo, Erik via shifter-users wrote: > Hello, > > I tried again to enroll into the ML and I hope that now it works well.. > > Otherwise, I tried with the flag you pointed out (--dbus-control=no), and I can connect using xPra client. So that's your first problem solved. > Hower, I was expecting to use the html flag to connect using the HTML5 client and it doesn?t work (attaching the logs underneath). Your log sample shows that websockify is either not installed or that the version installed is still too old. > As it seems, most of the modules used by xPra can?t be loaded even if they are installed (dbus, websockify, and all the others are installed). I also installed the python-dbus, but seems that the error messages haven?t changed at all?. I am pretty sure that the numerous dbus related warnings you are posing (which have cut out for brevity) are caused by the missing dbus bindings. You can verify that they are installed properly by running: python -c "import dbus" Until that command runs properly, xpra will warn you about missing dbus. > Also, as I can see, the /var/run/xpra folder is not created, so that might be the problem?.. No, if the directory does not exist or if it is impossible to create a socket there, xpra logs this warning and continues. > May it be that the installation is not creating the folder properly? This folder is normally created by tmpfiles.d, but that's probably not functional in Ubuntu 14.04 > xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon --start-child=xterm --dbus-control=no > 2017-02-14 10:10:23,455 Warning: failed to load the mdns avahi publisher: > 2017-02-14 10:10:23,456 No module named avahi > 2017-02-14 10:10:23,456 either fix your installation or use the 'mdns=no' option Install the "python-avahi" bindings, or use "mdns=no" > 2017-02-14 10:10:24,237 Error: cannot import websockify connection handler: > 2017-02-14 10:10:24,238 cannot import name WebSocketRequestHandler > 2017-02-14 10:10:24,238 the html server will not be available That's what you need to fix to get the html5 client running. (..) > Warning: failed to import GStreamer: > GStreamer 1.0: Namespace Gst not available > GStreamer 0.10: No module named pygst > 2017-02-14 10:10:24,749 Error: failed to query sound subsystem: > 2017-02-14 10:10:24,750 query did not return any data Install the python gstreamer bindings to avoid this warning. (..) Cheers Antoine > > Thanks a lot for your time! > > Best regards, > > Erik Berdonces > > > On Feb 13, 2017, at 3:24 PM, Berdonces Bonelo, Erik > wrote: > > Sending again because the attached file is too big. > It can be found uploaded in OneDrive in this link: https://1drv.ms/u/s!Ar0lgicIauUbhOQEbXldgJy5H-BMbg > > > > Begin forwarded message: > > From: "Berdonces Bonelo, Erik" > > Subject: Re: HTML start-desktop crash > Date: February 13, 2017 at 1:44:44 PM GMT+1 > To: shifter-users at lists.devloop.org.uk > > Hi again, > > I?m sorry but I?m not receiving any of your mails in my mailbox. I have to go to the ML archives an read the answers there. > > When I meant it doesn?t work is that it throws exactly the same error. And I?m not using any funny or strange configuration. It?s just a plain Ubuntu 14.04 server installed with default configuration, just install everything, enable SSH, and install xPra using the remote winswitch repo. 0.15.10-1 works as expected, but any version after this, throws the errors that I sent in the previous message. > > So procedure to reproduce: > > 1. Install Ubuntu Server x64 14.04 in VirtualBox (running in MacOS) or any server (I have already tried in both). Simple settings, just enabling SSH server to remote connect and no interface or anything needed. If you want you can install SSH manually later on yourself, but this doesn?t affect the result. No NFS, nothing strange, just a plain installation of ubuntu. > > 2. Update the packages and install xTerm:`sudo apt-get update && apt-get upgrade -y && apt-get install xterm` > > 3. Install xPra (via winswitch or deb packages): > 3.1Follow the instructions in https://winswitch.org/downloads/debian-repository.html?dist_select=trusty for trusty (14.04). > 3.2 I also tried the alternative alternative installing with the deb packages manually from http://xpra.org/dists/trusty/main/binary-amd64/ with dpkg and apt-get install -f (both procedures 3.1 and 3.2 result in the same error later on). I made sure to install websockify, python-xxhash, python-reencode, ffmpeg-xpra when installing deb packages manually. Usually I use the winswitch PPA repo as it?s much easier. > > Xpra gets installed with version 1.0.3: > > sturgelose at gilgamesh:~$ xpra --version > xpra v1.0.3-r15051 > > 4. Add user ubuntu to Xpra group `sudo usermod -a -G Xpra ubuntu` to avoid problems. > > 5. Execute `xpra start --bind-tcp=0.0.0.0:14500 --start-child=xterm` (just start a screen with xterm). There is nothing running in port 14500. You can also try with different ports, and will result the same problems. Also tried with `--html=on` option with the HTML5 client, it will happen exactly the same. And I tried different computers as clients. > > > If the command in 5. is ran as default non root user (ubuntu user), which is part of the Xpra group (added in 4.), the server doesn?t start and the daemon ends (mostly the error I sent in previous messages): > 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > > If run the command (5.) as root user (something I?d like to avoid doing), the socket connects, but then when connecting from the client, it says it can?t find bus package (and other packages), which is installed? still you can try to connect a client but the dbus error will kill the process. > > _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed > _XSERVTransMakeAllCOTSServerListeners: server already running > Initializing built-in extension Generic Event Extension > Initializing built-in extension SHAPE > Initializing built-in extension MIT-SHM > Initializing built-in extension XInputExtension > Initializing built-in extension XTEST > Initializing built-in extension BIG-REQUESTS > Initializing built-in extension SYNC > Initializing built-in extension XKEYBOARD > Initializing built-in extension XC-MISC > Initializing built-in extension SECURITY > Initializing built-in extension XINERAMA > Initializing built-in extension XFIXES > Initializing built-in extension RENDER > Initializing built-in extension RANDR > Initializing built-in extension COMPOSITE > Initializing built-in extension DAMAGE > Initializing built-in extension MIT-SCREEN-SAVER > Initializing built-in extension DOUBLE-BUFFER > Initializing built-in extension RECORD > Initializing built-in extension DPMS > Initializing built-in extension Present > Initializing built-in extension DRI3 > Initializing built-in extension X-Resource > Initializing built-in extension XVideo > Initializing built-in extension XVideo-MotionCompensation > Initializing built-in extension SELinux > Initializing built-in extension GLX > [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! > Using display number provided by Xvfb: :1 > Xlib: extension "RANDR" missing on display ":1". > Xlib: extension "RANDR" missing on display ":1". > /home/sturgelose/.xpra/gilgamesh-1 is not responding, waiting for it to timeout before clearing it..... > 2017-02-13 13:10:02,461 created unix domain socket: /home/sturgelose/.xpra/gilgamesh-1 > 2017-02-13 13:10:02,462 Warning: failed to create socket directory '/var/run/xpra' > 2017-02-13 13:10:02,463 [Errno 13] Permission denied: '/var/run/xpra' > 2017-02-13 13:10:02,463 Warning: cannot create socket '/var/run/xpra/gilgamesh-1' > 2017-02-13 13:10:02,464 [Errno 2] No such file or directory > 2017-02-13 13:10:02,465 /var/run/xpra does not exist > 2017-02-13 13:10:02,465 user 'sturgelose' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra > 2017-02-13 13:10:02,551 Warning: menu forwarding is disabled: > 2017-02-13 13:10:02,552 cannot load dbus helper: No module named dbus > 2017-02-13 13:10:02,932 Warning: libvpx ABI version 5 is too old: > 2017-02-13 13:10:02,932 disabling YUV444P support with VP9 > 2017-02-13 13:10:03,028 Warning: failed to load the mdns avahi publisher: > 2017-02-13 13:10:03,029 No module named avahi > 2017-02-13 13:10:03,029 either fix your installation or use the 'mdns=no' option > 2017-02-13 13:10:03,035 Warning: no X11 RandR support on :1 > 2017-02-13 13:10:03,953 Error: cannot import websockify connection handler: > 2017-02-13 13:10:03,953 cannot import name WebSocketRequestHandler > 2017-02-13 13:10:03,954 the html server will not be available > 2017-02-13 13:10:04,036 Error: failed to import the virtual video module: > 2017-02-13 13:10:04,037 No module named _dbus_bindings > 2017-02-13 13:10:04,051 pulseaudio server started with pid 1349 > Warning: failed to import GStreamer: > GStreamer 1.0: Namespace Gst not available > GStreamer 0.10: No module named pygst > 2017-02-13 13:10:04,496 Error: failed to query sound subsystem: > 2017-02-13 13:10:04,497 query did not return any data > 2017-02-13 13:10:04,499 Warning: failed to load or register our dbus notifications forwarder: > 2017-02-13 13:10:04,499 No module named dbus.service > 2017-02-13 13:10:04,499 if you do not have a dedicated dbus session for this xpra instance, > 2017-02-13 13:10:04,500 use the 'notifications=no' option > 2017-02-13 13:10:04,501 Warning: cannot load dbus helper: > 2017-02-13 13:10:04,502 No module named dbus > 2017-02-13 13:10:04,510 Warning: cannot load dbus server: > 2017-02-13 13:10:04,511 No module named dbus > 2017-02-13 13:10:04,517 started command 'xterm' with pid 1370 > 2017-02-13 13:10:04,518 xpra X11 version 1.0.3-r15051 64-bit > 2017-02-13 13:10:04,519 uid=1000 (sturgelose), gid=1000 (sturgelose) > 2017-02-13 13:10:04,519 running with pid 1298 on Linux Ubuntu 14.04 trusty > 2017-02-13 13:10:04,520 connected to X11 display :1 > 2017-02-13 13:10:04,632 xpra is ready. > 2017-02-13 13:10:04,635 2.0GB of system memory > 2017-02-13 13:10:11,299 New tcp connection received from 130.149.223.41:50452 > 2017-02-13 13:10:11,302 Warning: client expects a challenge but this connection is unauthenticated > 2017-02-13 13:10:11,319 Handshake complete; enabling connection > 2017-02-13 13:10:11,424 Warning: xxhash python bindings not found > 2017-02-13 13:10:11,425 no scrolling detection > 2017-02-13 13:10:11,438 server error processing new connection from Protocol(tcp socket: 130.149.223.55:14500 <- 130.149.223.41:50452): No module named dbus > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 893, in _process_hello > self.hello_oked(proto, packet, c, auth_caps) > File "/usr/lib/python2.7/dist-packages/xpra/server/server_base.py", line 1115, in hello_oked > self.default_speed, self.default_min_speed) > File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 357, in __init__ > self.dbus_server = dbus_exception_wrap(make_dbus_server, "setting up client dbus instance") > File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", line 12, in dbus_exception_wrap > v = fn() > File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 355, in make_dbus_server > from xpra.server.dbus.dbus_source import DBUS_Source > File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_source.py", line 7, in > from xpra.dbus.helper import dbus_to_native > File "/usr/lib/python2.7/dist-packages/xpra/dbus/helper.py", line 7, in > import dbus > ImportError: No module named dbus > 2017-02-13 13:10:11,444 Disconnecting client 130.149.223.41:50452: > 2017-02-13 13:10:11,445 server error (error accepting new connection) > > This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure in Ubuntu 16.04 and it works as expected (no errors nor warnings). > > In the client I only have one screen (disconnected the second one and rebooted even). I tried with other computers as clients and it?s just the same. The problem is in the xPra server. > > I attach as well an export of the server configuration done with xPra. > > > I can?t provide more information from the session, because directly the session doesn?t start! So, there is nothing to do with the encoding or whatsoever, it?s just Xpra not loading any of its dependencies! > > I?m really not doing anything strange, and I?m totally able to use xPra 1.0.3 in ubuntu 16.04, using exactly the same steps, or Xpra 0.15.10 in ubuntu 14.04. So, there is something wrong with 1.X versions. > > I hope this time I have redacted everything properly and added all the details... > > > On Feb 13, 2017, at 12:19 PM, Berdonces Bonelo, Erik > wrote: > > Hello, > > As a small update, I?ve been trying with different versions of xPra, and seems that all the 1.X versions do not work with Ubuntu 14.04 LTS. The latest version compatible with ubuntu 14.04 is 0.15.10-1 of Xpra. > > Best regards, > > Erik Berdonces > > On Feb 13, 2017, at 10:51 AM, Berdonces Bonelo, Erik > wrote: > > Hi, > > I?m sending it back to this mail, because seems I got a migration in my inbox and I didn?t receive the answer back (no worries, I read it in the online mailman archive), plus I got a new mail address. > > On the desktop size the answers helped a lot, and now I?ve been able to run it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my screen size. > However, I?ve tried to repeat the same process in Ubuntu 14.04, installing the latest version from WinSwitch repository and I?m having some troubles. As it seems it can?t create the socket, even if the .xpra folder gets set a 777 chmod and ubuntu is part of the Xpra group of users. > > Errors are as it follows: > > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon > Initializing built-in extension Generic Event Extension > Initializing built-in extension SHAPE > Initializing built-in extension MIT-SHM > Initializing built-in extension XInputExtension > Initializing built-in extension XTEST > Initializing built-in extension BIG-REQUESTS > Initializing built-in extension SYNC > Initializing built-in extension XKEYBOARD > Initializing built-in extension XC-MISC > Initializing built-in extension SECURITY > Initializing built-in extension XINERAMA > Initializing built-in extension XFIXES > Initializing built-in extension RENDER > Initializing built-in extension RANDR > Initializing built-in extension COMPOSITE > Initializing built-in extension DAMAGE > Initializing built-in extension MIT-SCREEN-SAVER > Initializing built-in extension DOUBLE-BUFFER > Initializing built-in extension RECORD > Initializing built-in extension DPMS > Initializing built-in extension Present > Initializing built-in extension DRI3 > Initializing built-in extension X-Resource > Initializing built-in extension XVideo > Initializing built-in extension XVideo-MotionCompensation > Initializing built-in extension SELinux > Initializing built-in extension GLX > [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! > Using display number provided by Xvfb: :0 > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > 2017-02-13 09:46:02,017 Error: failed to create socket '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 > 2017-02-13 09:46:02,018 killing xvfb with pid 5842 > ubuntu at machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask > 0002 > > This is in a plain Ubuntu Server 14.04 and installing the latest version of xPra and with default configuration. I can run the command with sudo, but then, it complains that it misses the dbus, websockify and many other packages. If I try to install them by hand, it says they are already installed. So, I?m not sure what?s happening that xPra can?t detect the dependencies are already installed.. > > These two things were the ones crashing xPra previously as I see (now running in non-daemon mode seems to keep it running, but still can?t run it in HTML mode and I get lots of warnings) > > Thanks! > Best regards, > > Erik Berdonces Bonelo > > > On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > wrote: > > Hello, > > I?m trying to run a full desktop (I have tried KDE and Unity so far), in order to manage remotely a server. > At the moment I have this running as a VM in VirtualBox + VBox Addons in my computer (I hope it isn?t this interfering somehow?). I?ve been trying with Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I?ve installed the latest release from the Winswitch repository (at the moment 1.0.2). > > Anyways, whenever I start an xpra session, either if I start it from the client or HTML5 client, the transmitted desktop is a window that is much larger than my actual physical screen, and I can?t even resize it down. I?ve tried with the ?desktop-scaling option, but it has no effect. > > Also, I?ve tried to use different desktops (kde, gnome and unity), and to disconnect my physical second screen from my laptop. If I start a simple program as xterm, there are no problems, it?s the proper size. However, doing so with a desktop, it just won?t work. > > Any suggestions on this? I?ve gone through all the xpra manual, but I might have overlooked a setting. Otherwise I don?t know if it can be a bug maybe? > > Thanks a lot, and of course, thanks a lot for your great work and for this tool! > > Best regards, > > Erik berdonces > > > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From stroller at stellar.eclipse.co.uk Wed Feb 15 17:02:32 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Wed, 15 Feb 2017 17:02:32 +0000 Subject: [winswitch] Xpra 1.0.3 won't launch on Mac OS X El Capitan? (10.11.6) Message-ID: Hello, I've just installed the latest Xpra linked on the frontpage of xpra.org and the icon just bounces in the dock a couple of times when I try to run it. In the Console I see: 15/02/2017 16:51:49.242 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 15/02/2017 16:51:49.000 syslogd[42]: ASL Sender Statistics 15/02/2017 16:51:49.390 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 15/02/2017 16:51:49.397 lsd[239]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist 15/02/2017 16:51:49.628 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 15/02/2017 16:51:49.701 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 15/02/2017 16:51:49.714 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 15/02/2017 16:51:51.063 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 15/02/2017 16:51:51.290 com.apple.xpc.launchd[1]: (org.xpra.Xpra.74912[32079]) Service exited with abnormal code: 1 If I go back to the previous version (the one dated 2017-01-31, I think - md5 e87050449cf4b372680eccd0bffb7bdd) it launches fine. Not sure if this is just me doing something stupid, but I thought you might want to know. Stroller. From stroller at stellar.eclipse.co.uk Wed Feb 15 17:29:14 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Wed, 15 Feb 2017 17:29:14 +0000 Subject: [winswitch] xpra - ImportError: No module named client.gtk2.client Message-ID: <0FE9F2AF-3FD7-4400-B485-43AA6151830B@stellar.eclipse.co.uk> Hello, It's been some time since I used xpra (I think I previously primarily used winswitch), so I'm feeling a bit helpless and useless for which I apologise. I've installed xpra through Gentoo's emerge, on a headless HP G7 Microserver (AMD Turion II Neo N54L Dual-Core Processor according to /proc/cpuinfo). Trying to launch it, I initially got this: $ xpra start ssh:localhost --start=xterm /usr/bin/Xorg is suid and not readable, Xdummy support unavailable xpra main error: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main return run_mode(script_file, err, options, args, mode, defaults) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1201, in run_mode return run_remote_server(error_cb, options, args, mode, defaults) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2193, in run_remote_server app = make_client(error_cb, opts) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2110, in make_client toolkit_module = __import__(client_module, globals(), locals(), ['XpraClient']) ImportError: No module named client.gtk2.client $ I reemerged x11-base/xorg-server-1.18.4 with USE="-suid" and the first part of the error has gone away, but the part about a gtk2 client remains: $ xpra start ssh:localhost --start=xterm xpra main error: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main return run_mode(script_file, err, options, args, mode, defaults) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1201, in run_mode return run_remote_server(error_cb, options, args, mode, defaults) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2193, in run_remote_server app = make_client(error_cb, opts) File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2110, in make_client toolkit_module = __import__(client_module, globals(), locals(), ['XpraClient']) ImportError: No module named client.gtk2.client $ Any idea what package or library I'm missing, please? The above is executed with xpra-1.0.2 but I have since upgraded to 1.0.3 and get the same thing. x11-wm/xpra is built with USE="clipboard csc lzo server vpx webp x264 x265 -client -cups -dec_av2 -enc_ffmpeg -libav -lz4 -opengl -pulseaudio -sound -webcam" (for clarity: +server -client). Stroller. From antoine at nagafix.co.uk Thu Feb 16 03:04:06 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 16 Feb 2017 10:04:06 +0700 Subject: [winswitch] xpra - ImportError: No module named client.gtk2.client In-Reply-To: <0FE9F2AF-3FD7-4400-B485-43AA6151830B@stellar.eclipse.co.uk> References: <0FE9F2AF-3FD7-4400-B485-43AA6151830B@stellar.eclipse.co.uk> Message-ID: <9ecaa4a4-b0c8-2c33-e736-760c96f057b4@nagafix.co.uk> On 16/02/17 00:29, Stroller via shifter-users wrote: > Hello, > > It's been some time since I used xpra (I think I previously primarily used winswitch), so I'm feeling a bit helpless and useless for which I apologise. > > I've installed xpra through Gentoo's emerge, on a headless HP G7 Microserver (AMD Turion II Neo N54L Dual-Core Processor according to /proc/cpuinfo). > > Trying to launch it, I initially got this: > > $ xpra start ssh:localhost --start=xterm > /usr/bin/Xorg is suid and not readable, Xdummy support unavailable > xpra main error: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main > return run_mode(script_file, err, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1201, in run_mode > return run_remote_server(error_cb, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2193, in run_remote_server > app = make_client(error_cb, opts) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2110, in make_client > toolkit_module = __import__(client_module, globals(), locals(), ['XpraClient']) > ImportError: No module named client.gtk2.client > > $ > > I reemerged x11-base/xorg-server-1.18.4 with USE="-suid" and the first part of the error has gone away, A note for other gentoo users who may need a suid Xorg installed (to use some proprietary drivers for example), you should be able to use the suid binary in /usr/bin/Xorg just by making it world readable. > but the part about a gtk2 client remains: > > $ xpra start ssh:localhost --start=xterm > xpra main error: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main > return run_mode(script_file, err, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1201, in run_mode > return run_remote_server(error_cb, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2193, in run_remote_server > app = make_client(error_cb, opts) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2110, in make_client > toolkit_module = __import__(client_module, globals(), locals(), ['XpraClient']) > ImportError: No module named client.gtk2.client > > $ > > Any idea what package or library I'm missing, please? > > The above is executed with xpra-1.0.2 but I have since upgraded to 1.0.3 and get the same thing. > > x11-wm/xpra is built with USE="clipboard csc lzo server vpx webp x264 x265 -client -cups -dec_av2 -enc_ffmpeg -libav -lz4 -opengl -pulseaudio -sound -webcam" (for clarity: +server -client). The command you used ("xpra start ssh:...") is a remote start command which is run from the client to start a remote server and connect to it. Maybe you just wanted to run "xpra start" instead? Or you can run that same command but from your client. PS: disabling lz4 is not recommended. I wouldn't bother enabling x265 either - it is too slow. Cheers Antoine > > Stroller. > > > > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From stroller at stellar.eclipse.co.uk Thu Feb 16 19:15:15 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Thu, 16 Feb 2017 19:15:15 +0000 Subject: [winswitch] /run/xpra directory permissions Message-ID: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> I'll respond to my other thread momentarily, but I now have xpra running, and thank Antoine for his help. In the process of this, I got this error: $ xpra start :100 --start-child=xterm $ Entering daemon mode; any further errors will be reported to: /home/stroller/.xpra/:100.log $ tail -n 100 -f /home/stroller/.xpra/\:100.log X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.9.4-gentoo x86_64 Gentoo Current Operating System: Linux alrai 4.9.4-gentoo #2 SMP Fri Jan 20 08:38:04 GMT 2017 x86_64 Kernel command line: BOOT_IMAGE=/kernel-4.9.4-gentoo root=/dev/sda4 ro Build Date: 16 February 2017 06:34:00PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/home/stroller/.xpra/Xorg.:100.log", Time: Thu Feb 16 18:39:49 2017 (++) Using config file: "/etc/xpra/xorg.conf" 2017-02-16 18:39:51,748 Warning: failed to create socket directory '/run/xpra' 2017-02-16 18:39:51,749 [Errno 13] Permission denied: '/run/xpra' 2017-02-16 18:39:51,750 Error: failed to create socket '/run/xpra/alrai-100': 2017-02-16 18:39:51,750 [Errno 2] No such file or directory xpra initialization error: failed to create socket /run/xpra/alrai-100 2017-02-16 18:39:51,752 killing xvfb with pid 31722 (II) Server terminated successfully (0). Closing log file. ^C $ I was able to resolve this by creating a /run/xpra directory and I temporarily gave it permissions 777. As I said before, I'm running Gentoo xpra-1.0.3, installed with the latest x11-wm/xpra ebuild currently in the Portage tree. The ebuild creates an xpra group (in /etc/group) when the package is installed on the system. I'm thinking the install should also create a /run/xpra directory on installation, with permissions that members of the xpra group can write to it (but not other users). Does this sound reasonable? If so, I'll file a bug to this effect with Gentoo. I do appreciate all your hard work, Stroller. From shanew at shanew.net Thu Feb 16 20:40:30 2017 From: shanew at shanew.net (shanew at shanew.net) Date: Thu, 16 Feb 2017 14:40:30 -0600 (CST) Subject: [winswitch] /run/xpra directory permissions In-Reply-To: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> References: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> Message-ID: Do you have the file /usr/lib/tmpfiles.d/xpra.conf on your gentoo installation? This should cause gentoo to create the /run/xpra directory with the appropriate permission at boot time (since /run is a tmpfs thing these days). Note though that users will need to be in the xpra group for this to work. If you don't want that group restriction, you could edit that file so that the permissions get set to 777 (or add an over-riding entry to /etc/tmpfiles.d, since the package installed one will likely get over-written when you update). On Thu, 16 Feb 2017, Stroller via shifter-users wrote: > I'll respond to my other thread momentarily, but I now have xpra running, and thank Antoine for his help. > > In the process of this, I got this error: > > $ xpra start :100 --start-child=xterm > $ Entering daemon mode; any further errors will be reported to: > /home/stroller/.xpra/:100.log > > $ tail -n 100 -f /home/stroller/.xpra/\:100.log > > X.Org X Server 1.18.4 > Release Date: 2016-07-19 > X Protocol Version 11, Revision 0 > Build Operating System: Linux 4.9.4-gentoo x86_64 Gentoo > Current Operating System: Linux alrai 4.9.4-gentoo #2 SMP Fri Jan 20 08:38:04 GMT 2017 x86_64 > Kernel command line: BOOT_IMAGE=/kernel-4.9.4-gentoo root=/dev/sda4 ro > Build Date: 16 February 2017 06:34:00PM > > Current version of pixman: 0.34.0 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (++) Log file: "/home/stroller/.xpra/Xorg.:100.log", Time: Thu Feb 16 18:39:49 2017 > (++) Using config file: "/etc/xpra/xorg.conf" > 2017-02-16 18:39:51,748 Warning: failed to create socket directory '/run/xpra' > 2017-02-16 18:39:51,749 [Errno 13] Permission denied: '/run/xpra' > 2017-02-16 18:39:51,750 Error: failed to create socket '/run/xpra/alrai-100': > 2017-02-16 18:39:51,750 [Errno 2] No such file or directory > xpra initialization error: > failed to create socket /run/xpra/alrai-100 > 2017-02-16 18:39:51,752 killing xvfb with pid 31722 > (II) Server terminated successfully (0). Closing log file. > ^C > $ > > I was able to resolve this by creating a /run/xpra directory and I temporarily gave it permissions 777. > > As I said before, I'm running Gentoo xpra-1.0.3, installed with the latest x11-wm/xpra ebuild currently in the Portage tree. > > The ebuild creates an xpra group (in /etc/group) when the package is installed on the system. > > I'm thinking the install should also create a /run/xpra directory on installation, with permissions that members of the xpra group can write to it (but not other users). Does this sound reasonable? If so, I'll file a bug to this effect with Gentoo. > > I do appreciate all your hard work, > > Stroller. > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > -- Public key #7BBC68D9 at | Shane Williams http://pgp.mit.edu/ | System Admin - UT CompSci =----------------------------------+------------------------------- All syllogisms contain three lines | shanew at shanew.net Therefore this is not a syllogism | www.ischool.utexas.edu/~shanew From stroller at stellar.eclipse.co.uk Fri Feb 17 00:21:22 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Fri, 17 Feb 2017 00:21:22 +0000 Subject: [winswitch] /run/xpra directory permissions In-Reply-To: References: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> Message-ID: > On 16 Feb 2017, at 20:40, shanew--- via shifter-users wrote: > > Do you have the file /usr/lib/tmpfiles.d/xpra.conf on your gentoo > installation? This should cause gentoo to create the /run/xpra > directory with the appropriate permission at boot time (since /run is > a tmpfs thing these days). Yes. I don't think my system has been rebooted since I installed xpra, though (well, maybe when I used xpra before, 2+ years ago). > Note though that users will need to be in the xpra group for this to > work. So I add my user to the xpra group, and then reboot? It seems like you're saying the /run/xpra directory won't be created if no users are in the group? Thanks for your time and help, Stroller. From kc7noa at gmail.com Fri Feb 17 06:26:36 2017 From: kc7noa at gmail.com (Michael Durkin) Date: Thu, 16 Feb 2017 22:26:36 -0800 Subject: [winswitch] error on build Message-ID: Not sure if this is a but yet .. probably more of a Odroid-X2/Ubuntu16.04 fresh install issue .. found gcc version: 5.4.0 Traceback (most recent call last): File "setup.py", line 2449, in ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") File "setup.py", line 688, in exec_pkgconfig raise Exception("ERROR: cannot find a valid pkg-config entry for %s using PKG_CONFIG_PATH=%s" % (" or ".join(options), os.environ.get("PKG_CONFIG_PATH", "(empty)"))) Exception: ERROR: cannot find a valid pkg-config entry for libavformat using PKG_CONFIG_PATH=(empty) im still investigating .... From antoine at nagafix.co.uk Fri Feb 17 06:51:10 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 17 Feb 2017 13:51:10 +0700 Subject: [winswitch] xpra - ImportError: No module named client.gtk2.client In-Reply-To: References: <0FE9F2AF-3FD7-4400-B485-43AA6151830B@stellar.eclipse.co.uk> <9ecaa4a4-b0c8-2c33-e736-760c96f057b4@nagafix.co.uk> Message-ID: (snip) > I can create sessions, add applications and attach and detach from my Mac. > > Well, it works perfectly until I try to close the xrpa shell: > > $ xpra list > Found the following xpra sessions: > /run/xpra: > LIVE session at :0 > $ xpra stop :0 > xpra main error: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main > return run_mode(script_file, err, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1211, in run_mode > return run_stopexit(mode, error_cb, options, args) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2560, in run_stopexit > from xpra.client.gobject_client_base import StopXpraClient > ImportError: No module named client.gobject_client_base > > $ xpra stop --socket-dir=/var/run/xpra/alrai-0 > xpra main error: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 140, in main > return run_mode(script_file, err, options, args, mode, defaults) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 1211, in run_mode > return run_stopexit(mode, error_cb, options, args) > File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 2560, in run_stopexit > from xpra.client.gobject_client_base import StopXpraClient > ImportError: No module named client.gobject_client_base > > $ > > `xpra info` and `xpra version` give similar errors. All these commands are actually clients, they connect to the server and request something. You should be able to run these subcommands from the client, ie: xpra stop ssh:HOST Separating these CLI subcommands from the "real" GUI clients is planned: https://xpra.org/trac/ticket/1253#comment:6 >> Or you can run that same command but from your client. > > I'm using the Mac OS X client, but it's not obvious to me how to run that from the command line. I've just noticed the Xpra_NoDock.app inside the Xpra bundle, but the .app suffix would indicate it's a GUI app, too. Use: /Applications/Xpra.app/Contents/MacOS/Xpra There are a bunch of other executables there and also in: /Applications/Xpra.app/Contents/MacOS/Helpers (those are mostly for debugging purposes) > The Max GUI launcher is lovely, though. Opinions differ on that one: https://xpra.org/trac/ticket/1343 >> PS: disabling lz4 is not recommended. I wouldn't bother enabling x265 >> either - it is too slow. > > I had some USE flags enabled from when I first tried xpra 2 or more years ago, so I'll clear those out. > > Gentoo's default USE flags for this package appear to be: > > client clipboard -csc -cups -dec_av2 -enc_ffmpeg -libav -lz4 -lzo > -opengl -pulseaudio -server -sound -vpx -webcam -webp -x264 -x265 I guess that's what an absolute minimal build would look like. If you care about performance, you need to add lz4 and ideally at least one video+csc codec, ie: vpx and csc. And if you enable "client" then you really should enable "opengl" too. The non-opengl client gets tested less and less with each release and as the opengl drivers mature. It's not clear to me what the "csc" flag does, as there are multiple csc modules in xpra. The one you want to be using is "csc_libyuv". > Is it worth me filling a bug with Gentoo, to suggest making lz4 a default? It seems to pull in only a single dependency, so hardly a burden. Yes. lz4 is tiny yet it provides massive savings. > I do appreciate the assistance you've given me, on this occasion and previously. Thanks! Antoine > > Stroller. > > From antoine at nagafix.co.uk Fri Feb 17 06:57:05 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 17 Feb 2017 13:57:05 +0700 Subject: [winswitch] error on build In-Reply-To: References: Message-ID: <8cd4a953-9aaa-f909-c872-2231a82f1a5c@nagafix.co.uk> On 17/02/17 13:26, Michael Durkin via shifter-users wrote: > Not sure if this is a but yet .. probably more of a Odroid-X2/Ubuntu16.04 > fresh install issue .. > > found gcc version: 5.4.0 > Traceback (most recent call last): > File "setup.py", line 2449, in > ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") > File "setup.py", line 688, in exec_pkgconfig > raise Exception("ERROR: cannot find a valid pkg-config entry for %s > using PKG_CONFIG_PATH=%s" % (" or ".join(options), > os.environ.get("PKG_CONFIG_PATH", "(empty)"))) > Exception: ERROR: cannot find a valid pkg-config entry for libavformat > using PKG_CONFIG_PATH=(empty) You need the libavformat development headers and pkg-config file. I have added more details here: https://www.xpra.org/trac/wiki/Building/Debian Cheers Antoine > > im still investigating .... > _______________________________________________ > 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 Feb 17 07:28:15 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 17 Feb 2017 14:28:15 +0700 Subject: [winswitch] /run/xpra directory permissions In-Reply-To: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> References: <88B5864D-DFA8-4C46-A345-ACADFC2B3464@stellar.eclipse.co.uk> Message-ID: <48ef08f6-f6bf-7738-9057-67ed371a00d5@nagafix.co.uk> On 17/02/17 02:15, Stroller via shifter-users wrote: > I'll respond to my other thread momentarily, but I now have xpra running, and thank Antoine for his help. > > In the process of this, I got this error: > > $ xpra start :100 --start-child=xterm > $ Entering daemon mode; any further errors will be reported to: > /home/stroller/.xpra/:100.log > > $ tail -n 100 -f /home/stroller/.xpra/\:100.log > > X.Org X Server 1.18.4 > Release Date: 2016-07-19 > X Protocol Version 11, Revision 0 > Build Operating System: Linux 4.9.4-gentoo x86_64 Gentoo > Current Operating System: Linux alrai 4.9.4-gentoo #2 SMP Fri Jan 20 08:38:04 GMT 2017 x86_64 > Kernel command line: BOOT_IMAGE=/kernel-4.9.4-gentoo root=/dev/sda4 ro > Build Date: 16 February 2017 06:34:00PM > > Current version of pixman: 0.34.0 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (++) Log file: "/home/stroller/.xpra/Xorg.:100.log", Time: Thu Feb 16 18:39:49 2017 > (++) Using config file: "/etc/xpra/xorg.conf" > 2017-02-16 18:39:51,748 Warning: failed to create socket directory '/run/xpra' > 2017-02-16 18:39:51,749 [Errno 13] Permission denied: '/run/xpra' > 2017-02-16 18:39:51,750 Error: failed to create socket '/run/xpra/alrai-100': > 2017-02-16 18:39:51,750 [Errno 2] No such file or directory > xpra initialization error: > failed to create socket /run/xpra/alrai-100 > 2017-02-16 18:39:51,752 killing xvfb with pid 31722 > (II) Server terminated successfully (0). Closing log file. Failure to write to the "shared socket" folder should not be fatal, we just assumed that this folder was "/var/run/xpra" but it is "/run/xpra" on your system. This is now fixed and will be in the next update: http://xpra.org/trac/changeset/15096/xpra **** Socket issues seem to have bitten a number of people running xpra on the "not officially supported" distributions (or on the ones I fail to test fully before the release...) and is often purely a packaging issue. So here is more information on what is going on. * legacy location: "~/.xpra/" Since the very first version, xpra has been placing its server sockets in "~/.xpra/". It still does, though it may get phased out eventually. * XDG_RUNTIME_DIR (usually "/var/run/user/$UID/xpra/") Then came along the "XDG Base Directory Specification": https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html So we decided to follow the "new and improved" (..) standard location: https://www.xpra.org/trac/ticket/1129 This also fixes problems for those that mount $HOME using network filesystems: https://www.xpra.org/trac/ticket/888 * group sharing (usually "/var/run/xpra/") We also wanted to make it easier to setup session sharing across users via unix group membership, so we added "/var/run/xpra" via tmpfiles.d: https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html This one may fail: you should not be able to write to "/var/run/xpra" if you are not a member of the xpra group for example. (the bug you hit failed to recognise this socket location as optional) So now xpra should create its server sockets in 3 locations. We have to keep the legacy location in the default settings because older clients may not be able to connect to xpra via ssh without it. The XDG_RUNTIME_DIR is also a bit of a mess, especially for users who rely on "sudo" or "su" to launch sessions as most distributions do not create this directory properly (..). Until distributions sort this out - and well after that, we will continue to support the legacy location. Cheers Antoine > I was able to resolve this by creating a /run/xpra directory and I temporarily gave it permissions 777. > > As I said before, I'm running Gentoo xpra-1.0.3, installed with the latest x11-wm/xpra ebuild currently in the Portage tree. > > The ebuild creates an xpra group (in /etc/group) when the package is installed on the system. > > I'm thinking the install should also create a /run/xpra directory on installation, with permissions that members of the xpra group can write to it (but not other users). Does this sound reasonable? If so, I'll file a bug to this effect with Gentoo. > > I do appreciate all your hard work, > > Stroller. > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sat Feb 18 04:38:59 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 18 Feb 2017 11:38:59 +0700 Subject: [winswitch] error on build In-Reply-To: References: <8cd4a953-9aaa-f909-c872-2231a82f1a5c@nagafix.co.uk> Message-ID: Please always keep the list CCed. On 18/02/17 01:43, Michael Durkin wrote: > ok, this error is over my head ... > > building 'xpra.codecs.libav_common.av_log' extension > arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 > -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC > -I/usr/local/include -I/usr/include/python2.7 -c > xpra/codecs/libav_common/av_log.c -o > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall > -Werror -Wno-error=strict-prototypes -fPIC > arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 > -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro > -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > -Werror=format-security > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o > -L/usr/local/lib -lavutil -lm -o > build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall > /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation > R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when > making a shared object; recompile with -fPIC > /usr/local/lib/libavutil.a: error adding symbols: Bad value > collect2: error: ld returned 1 exit status > error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 I think someone hit this error before, but I can't remember the details. This is a toolchain problem, you will need to get someone from Odroid to help you here. This looks relevant: https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448 Or just disable the ffmpeg based codecs (and maybe others too): ./setup.py --without-dec_avcodec2 --without-csc_swcale --without-enc_ffmpeg Cheers Antoine > > > On Fri, Feb 17, 2017 at 9:44 AM, Michael Durkin > wrote: > > Every thing on that page is installed .. or was already part of the > Ubuntu 16.04 HardKernel image ... > > hit this error ... > > error: implicit declaration of function 'avcodec_receive_frame' > > humm .. not quite an error, just not ffmpeg V3 .... > Im not sure what would happen if i remove ffmpeg to anything else ... > Ill try to build ffmpeg from svn/git ... > > On Thu, Feb 16, 2017 at 10:57 PM, Antoine Martin via shifter-users > > wrote: > > On 17/02/17 13:26, Michael Durkin via shifter-users wrote: > > Not sure if this is a but yet .. probably more of a Odroid-X2/Ubuntu16.04 > > fresh install issue .. > > > > found gcc version: 5.4.0 > > Traceback (most recent call last): > > File "setup.py", line 2449, in > > ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") > > File "setup.py", line 688, in exec_pkgconfig > > raise Exception("ERROR: cannot find a valid pkg-config entry for %s > > using PKG_CONFIG_PATH=%s" % (" or ".join(options), > > os.environ.get("PKG_CONFIG_PATH", "(empty)"))) > > Exception: ERROR: cannot find a valid pkg-config entry for libavformat > > using PKG_CONFIG_PATH=(empty) > You need the libavformat development headers and pkg-config file. > I have added more details here: > https://www.xpra.org/trac/wiki/Building/Debian > > > Cheers > Antoine > > > > > im still investigating .... > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > From antoine at nagafix.co.uk Sat Feb 18 05:12:36 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 18 Feb 2017 12:12:36 +0700 Subject: [winswitch] Xpra 1.0.3 won't launch on Mac OS X El Capitan? (10.11.6) In-Reply-To: References: Message-ID: On 16/02/17 00:02, Stroller via shifter-users wrote: > Hello, > > I've just installed the latest Xpra linked on the frontpage of xpra.org and the icon just bounces in the dock a couple of times when I try to run it. FYI: you can find the exact versions available here: http://xpra.org/dists/osx/x86/ The "Xpra.dmg" and "Xpra.pkg" are always linked to the latest version available. > In the Console I see: > > 15/02/2017 16:51:49.242 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 > 15/02/2017 16:51:49.000 syslogd[42]: ASL Sender Statistics > 15/02/2017 16:51:49.390 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 > 15/02/2017 16:51:49.397 lsd[239]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist > 15/02/2017 16:51:49.628 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 > 15/02/2017 16:51:49.701 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 > 15/02/2017 16:51:49.714 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 > 15/02/2017 16:51:51.063 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 > 15/02/2017 16:51:51.290 com.apple.xpc.launchd[1]: (org.xpra.Xpra.74912[32079]) Service exited with abnormal code: 1 I have just tested this on OSX 10.10.x, 10.11.x and 10.12.x and I have not seen any problems at all. I have tested both the DMG (ran directly from the volume and installed into "Applications") and the PKG installer. > If I go back to the previous version (the one dated 2017-01-31, I think - md5 e87050449cf4b372680eccd0bffb7bdd) it launches fine. I see no DMG or PKG with this MD5 checksum. Maybe your download is corrupted, in which case I would have expected the OS to reject the image. > Not sure if this is just me doing something stupid, but I thought you might want to know. Thanks, we do want to know about such problems. Being able to reproduce them would be even better! Cheers Antoine > > Stroller. > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From stroller at stellar.eclipse.co.uk Sat Feb 18 10:05:30 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Sat, 18 Feb 2017 10:05:30 +0000 Subject: [winswitch] Xpra 1.0.3 won't launch on Mac OS X El Capitan? (10.11.6) In-Reply-To: References: Message-ID: <1AC85B6F-9EC8-48A5-B9D1-1DCB718E9342@stellar.eclipse.co.uk> > On 18 Feb 2017, at 05:12, Antoine Martin via shifter-users wrote: > >> In the Console I see: >> >> 15/02/2017 16:51:49.242 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 >> 15/02/2017 16:51:49.000 syslogd[42]: ASL Sender Statistics >> 15/02/2017 16:51:49.390 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 >> 15/02/20rity17 16:51:49.397 lsd[239]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist >> 15/02/2017 16:51:49.628 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 >> 15/02/2017 16:51:49.701 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 >> 15/02/2017 16:51:49.714 launchservicesd[76]: SecTaskLoadEntitlements failed error=22 >> 15/02/2017 16:51:51.063 WindowServer[146]: assertion failed: 15G1217: libxpc.dylib + 22551 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x13 >> 15/02/2017 16:51:51.290 com.apple.xpc.launchd[1]: (org.xpra.Xpra.74912[32079]) Service exited with abnormal code: 1 > I have just tested this on OSX 10.10.x, 10.11.x and 10.12.x and I have > not seen any problems at all. > I have tested both the DMG (ran directly from the volume and installed > into "Applications") and the PKG installer. Well, I've re-downloaded it and it's working now. I think it may have been OS X's "identified developers" Gatekeeper security settings, but I'm not sure. I'm not usually tripped up by that, and run a number of other "unidentified" apps. >> If I go back to the previous version (the one dated 2017-01-31, I think - md5 e87050449cf4b372680eccd0bffb7bdd) it launches fine. > I see no DMG or PKG with this MD5 checksum. Maybe your download is > corrupted, in which case I would have expected the OS to reject the image. That's what I'd have expected, too! And that was the working version. However I can't find that version on your site now, either, so either I must've been having an off day or your build server was. >> Not sure if this is just me doing something stupid, but I thought you might want to know. > Thanks, we do want to know about such problems. > Being able to reproduce them would be even better! Sorry for wasting your time. Stroller. From antoine at nagafix.co.uk Sat Feb 18 10:10:05 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 18 Feb 2017 17:10:05 +0700 Subject: [winswitch] Xpra 1.0.3 won't launch on Mac OS X El Capitan? (10.11.6) In-Reply-To: <1AC85B6F-9EC8-48A5-B9D1-1DCB718E9342@stellar.eclipse.co.uk> References: <1AC85B6F-9EC8-48A5-B9D1-1DCB718E9342@stellar.eclipse.co.uk> Message-ID: <33f054ee-c38c-77f0-3da2-59cac47bf862@nagafix.co.uk> (snip) > I think it may have been OS X's "identified developers" Gatekeeper security settings, but I'm not sure. Yes, it could well be. I had signed version 1.0 and 1.0.1, but since I was told that this made no difference: https://xpra.org/trac/ticket/1340#comment:23 I had not signed version 1.0.3 (the process is a royal pain) (snip) >>> Not sure if this is just me doing something stupid, but I thought you might want to know. >> Thanks, we do want to know about such problems. >> Being able to reproduce them would be even better! > > Sorry for wasting your time. Not at all. I'll make sure to sign 1.0.4 and future versions and hope for the best... Cheers Antoine From stroller at stellar.eclipse.co.uk Sat Feb 18 10:26:27 2017 From: stroller at stellar.eclipse.co.uk (Stroller) Date: Sat, 18 Feb 2017 10:26:27 +0000 Subject: [winswitch] Xpra 1.0.3 won't launch on Mac OS X El Capitan? (10.11.6) In-Reply-To: <33f054ee-c38c-77f0-3da2-59cac47bf862@nagafix.co.uk> References: <1AC85B6F-9EC8-48A5-B9D1-1DCB718E9342@stellar.eclipse.co.uk> <33f054ee-c38c-77f0-3da2-59cac47bf862@nagafix.co.uk> Message-ID: <34C80595-A5B0-4A7F-BEA8-AA1F1A040C82@stellar.eclipse.co.uk> > On 18 Feb 2017, at 10:10, Antoine Martin via shifter-users wrote: > > (snip) >> I think it may have been OS X's "identified developers" Gatekeeper security settings, but I'm not sure. > Yes, it could well be. I had signed version 1.0 and 1.0.1, but since I > was told that this made no difference: > https://xpra.org/trac/ticket/1340#comment:23 > I had not signed version 1.0.3 (the process is a royal pain) Everything about Gatekeeper is a pain! From kc7noa at gmail.com Sat Feb 25 16:11:58 2017 From: kc7noa at gmail.com (Michael Durkin) Date: Sat, 25 Feb 2017 08:11:58 -0800 Subject: [winswitch] error on build In-Reply-To: References: <8cd4a953-9aaa-f909-c872-2231a82f1a5c@nagafix.co.uk> Message-ID: humm .... says to use -fPIC, but it is included in the compile ... building 'xpra.codecs.libav_common.av_log' extension arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/local/include -I/usr/include/python2.7 -c xpra/codecs/libav_common/av_log.c -o build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall -Werror -Wno-error=strict-prototypes -fPIC arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -L/usr/local/lib -lavutil -lm -o build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libavutil.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 On Sat, Feb 25, 2017 at 8:08 AM, Michael Durkin wrote: > does that force usage of internal (that comes with xpra) codec's ? > > On Fri, Feb 17, 2017 at 8:38 PM, Antoine Martin > wrote: > >> Please always keep the list CCed. >> >> On 18/02/17 01:43, Michael Durkin wrote: >> > ok, this error is over my head ... >> > >> > building 'xpra.codecs.libav_common.av_log' extension >> > arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall >> > -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 >> > -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC >> > -I/usr/local/include -I/usr/include/python2.7 -c >> > xpra/codecs/libav_common/av_log.c -o >> > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall >> > -Werror -Wno-error=strict-prototypes -fPIC >> > arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 >> > -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro >> > -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes >> > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat >> > -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro >> > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat >> > -Werror=format-security >> > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o >> > -L/usr/local/lib -lavutil -lm -o >> > build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall >> > /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation >> > R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when >> > making a shared object; recompile with -fPIC >> > /usr/local/lib/libavutil.a: error adding symbols: Bad value >> > collect2: error: ld returned 1 exit status >> > error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 >> I think someone hit this error before, but I can't remember the details. >> This is a toolchain problem, you will need to get someone from Odroid to >> help you here. This looks relevant: >> https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448 >> >> Or just disable the ffmpeg based codecs (and maybe others too): >> ./setup.py --without-dec_avcodec2 --without-csc_swcale >> --without-enc_ffmpeg >> >> Cheers >> Antoine >> >> >> >> > >> > >> > On Fri, Feb 17, 2017 at 9:44 AM, Michael Durkin > > > wrote: >> > >> > Every thing on that page is installed .. or was already part of the >> > Ubuntu 16.04 HardKernel image ... >> > >> > hit this error ... >> > >> > error: implicit declaration of function 'avcodec_receive_frame' >> > >> > humm .. not quite an error, just not ffmpeg V3 .... >> > Im not sure what would happen if i remove ffmpeg to anything else >> ... >> > Ill try to build ffmpeg from svn/git ... >> > >> > On Thu, Feb 16, 2017 at 10:57 PM, Antoine Martin via shifter-users >> > > > > wrote: >> > >> > On 17/02/17 13:26, Michael Durkin via shifter-users wrote: >> > > Not sure if this is a but yet .. probably more of a >> Odroid-X2/Ubuntu16.04 >> > > fresh install issue .. >> > > >> > > found gcc version: 5.4.0 >> > > Traceback (most recent call last): >> > > File "setup.py", line 2449, in >> > > ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") >> > > File "setup.py", line 688, in exec_pkgconfig >> > > raise Exception("ERROR: cannot find a valid pkg-config >> entry for %s >> > > using PKG_CONFIG_PATH=%s" % (" or ".join(options), >> > > os.environ.get("PKG_CONFIG_PATH", "(empty)"))) >> > > Exception: ERROR: cannot find a valid pkg-config entry for >> libavformat >> > > using PKG_CONFIG_PATH=(empty) >> > You need the libavformat development headers and pkg-config >> file. >> > I have added more details here: >> > https://www.xpra.org/trac/wiki/Building/Debian >> > >> > >> > Cheers >> > Antoine >> > >> > > >> > > im still investigating .... >> > > _______________________________________________ >> > > shifter-users mailing list >> > > shifter-users at lists.devloop.org.uk >> > >> > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > >> > > >> > >> > _______________________________________________ >> > shifter-users mailing list >> > shifter-users at lists.devloop.org.uk >> > >> > http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > >> > >> > >> > >> >> > From antoine at nagafix.co.uk Sun Feb 26 06:08:47 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 26 Feb 2017 13:08:47 +0700 Subject: [winswitch] error on build In-Reply-To: References: <8cd4a953-9aaa-f909-c872-2231a82f1a5c@nagafix.co.uk> Message-ID: <86d76137-a472-7c85-f1a4-ed96298b60f0@nagafix.co.uk> On 25/02/17 23:11, Michael Durkin via shifter-users wrote: > humm .... > > says to use -fPIC, but it is included in the compile ... Please see the link I have already posted: https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448 Here's a direct quote: "non-PIC shared libraries were never really deliberately supported for ARM, they just worked by coincidence" Cheers Antoine > > building 'xpra.codecs.libav_common.av_log' extension > arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fstack-protector-strong -Wformat -Werror=format-security -fPIC > -I/usr/local/include -I/usr/include/python2.7 -c > xpra/codecs/libav_common/av_log.c -o > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall -Werror > -Wno-error=strict-prototypes -fPIC > arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g > -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fstack-protector-strong -Wformat -Werror=format-security > -Wl,-Bsymbolic-functions -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fstack-protector-strong -Wformat -Werror=format-security > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o > -L/usr/local/lib -lavutil -lm -o > build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall > /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation > R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making > a shared object; recompile with -fPIC > /usr/local/lib/libavutil.a: error adding symbols: Bad value > collect2: error: ld returned 1 exit status > error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 > > > On Sat, Feb 25, 2017 at 8:08 AM, Michael Durkin wrote: > >> does that force usage of internal (that comes with xpra) codec's ? >> >> On Fri, Feb 17, 2017 at 8:38 PM, Antoine Martin >> wrote: >> >>> Please always keep the list CCed. >>> >>> On 18/02/17 01:43, Michael Durkin wrote: >>>> ok, this error is over my head ... >>>> >>>> building 'xpra.codecs.libav_common.av_log' extension >>>> arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall >>>> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 >>>> -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC >>>> -I/usr/local/include -I/usr/include/python2.7 -c >>>> xpra/codecs/libav_common/av_log.c -o >>>> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall >>>> -Werror -Wno-error=strict-prototypes -fPIC >>>> arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 >>>> -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro >>>> -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes >>>> -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat >>>> -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro >>>> -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat >>>> -Werror=format-security >>>> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o >>>> -L/usr/local/lib -lavutil -lm -o >>>> build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall >>>> /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation >>>> R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when >>>> making a shared object; recompile with -fPIC >>>> /usr/local/lib/libavutil.a: error adding symbols: Bad value >>>> collect2: error: ld returned 1 exit status >>>> error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 >>> I think someone hit this error before, but I can't remember the details. >>> This is a toolchain problem, you will need to get someone from Odroid to >>> help you here. This looks relevant: >>> https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448 >>> >>> Or just disable the ffmpeg based codecs (and maybe others too): >>> ./setup.py --without-dec_avcodec2 --without-csc_swcale >>> --without-enc_ffmpeg >>> >>> Cheers >>> Antoine >>> >>> >>> >>>> >>>> >>>> On Fri, Feb 17, 2017 at 9:44 AM, Michael Durkin >>> > wrote: >>>> >>>> Every thing on that page is installed .. or was already part of the >>>> Ubuntu 16.04 HardKernel image ... >>>> >>>> hit this error ... >>>> >>>> error: implicit declaration of function 'avcodec_receive_frame' >>>> >>>> humm .. not quite an error, just not ffmpeg V3 .... >>>> Im not sure what would happen if i remove ffmpeg to anything else >>> ... >>>> Ill try to build ffmpeg from svn/git ... >>>> >>>> On Thu, Feb 16, 2017 at 10:57 PM, Antoine Martin via shifter-users >>>> >>> > wrote: >>>> >>>> On 17/02/17 13:26, Michael Durkin via shifter-users wrote: >>>> > Not sure if this is a but yet .. probably more of a >>> Odroid-X2/Ubuntu16.04 >>>> > fresh install issue .. >>>> > >>>> > found gcc version: 5.4.0 >>>> > Traceback (most recent call last): >>>> > File "setup.py", line 2449, in >>>> > ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") >>>> > File "setup.py", line 688, in exec_pkgconfig >>>> > raise Exception("ERROR: cannot find a valid pkg-config >>> entry for %s >>>> > using PKG_CONFIG_PATH=%s" % (" or ".join(options), >>>> > os.environ.get("PKG_CONFIG_PATH", "(empty)"))) >>>> > Exception: ERROR: cannot find a valid pkg-config entry for >>> libavformat >>>> > using PKG_CONFIG_PATH=(empty) >>>> You need the libavformat development headers and pkg-config >>> file. >>>> I have added more details here: >>>> https://www.xpra.org/trac/wiki/Building/Debian >>>> >>>> >>>> Cheers >>>> Antoine >>>> >>>> > >>>> > im still investigating .... >>>> > _______________________________________________ >>>> > shifter-users mailing list >>>> > shifter-users at lists.devloop.org.uk >>>> >>>> > http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>> >>>> > >>>> >>>> _______________________________________________ >>>> shifter-users mailing list >>>> shifter-users at lists.devloop.org.uk >>>> >>>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>> >>>> >>>> >>>> >>> >>> >> > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From kc7noa at gmail.com Sun Feb 26 16:32:45 2017 From: kc7noa at gmail.com (Michael Durkin) Date: Sun, 26 Feb 2017 08:32:45 -0800 Subject: [winswitch] error on build In-Reply-To: References: <8cd4a953-9aaa-f909-c872-2231a82f1a5c@nagafix.co.uk> Message-ID: ok .. this did work .... at first i thought it was not ... but after (finally) looking at the log i seen that Xvfb was causing an error ... it was not installed (iv done this mistake more than once in the last few years)... It might be handy to add installing Xvfb to the debian/ubuntu build section ... On Fri, Feb 17, 2017 at 8:38 PM, Antoine Martin wrote: > Please always keep the list CCed. > > On 18/02/17 01:43, Michael Durkin wrote: > > ok, this error is over my head ... > > > > building 'xpra.codecs.libav_common.av_log' extension > > arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall > > -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 > > -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC > > -I/usr/local/include -I/usr/include/python2.7 -c > > xpra/codecs/libav_common/av_log.c -o > > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall > > -Werror -Wno-error=strict-prototypes -fPIC > > arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 > > -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro > > -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes > > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > > -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro > > -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > > -Werror=format-security > > build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o > > -L/usr/local/lib -lavutil -lm -o > > build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall > > /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation > > R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when > > making a shared object; recompile with -fPIC > > /usr/local/lib/libavutil.a: error adding symbols: Bad value > > collect2: error: ld returned 1 exit status > > error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1 > I think someone hit this error before, but I can't remember the details. > This is a toolchain problem, you will need to get someone from Odroid to > help you here. This looks relevant: > https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448 > > Or just disable the ffmpeg based codecs (and maybe others too): > ./setup.py --without-dec_avcodec2 --without-csc_swcale --without-enc_ffmpeg > > Cheers > Antoine > > > > > > > > > On Fri, Feb 17, 2017 at 9:44 AM, Michael Durkin > > wrote: > > > > Every thing on that page is installed .. or was already part of the > > Ubuntu 16.04 HardKernel image ... > > > > hit this error ... > > > > error: implicit declaration of function 'avcodec_receive_frame' > > > > humm .. not quite an error, just not ffmpeg V3 .... > > Im not sure what would happen if i remove ffmpeg to anything else ... > > Ill try to build ffmpeg from svn/git ... > > > > On Thu, Feb 16, 2017 at 10:57 PM, Antoine Martin via shifter-users > > > > wrote: > > > > On 17/02/17 13:26, Michael Durkin via shifter-users wrote: > > > Not sure if this is a but yet .. probably more of a > Odroid-X2/Ubuntu16.04 > > > fresh install issue .. > > > > > > found gcc version: 5.4.0 > > > Traceback (most recent call last): > > > File "setup.py", line 2449, in > > > ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat") > > > File "setup.py", line 688, in exec_pkgconfig > > > raise Exception("ERROR: cannot find a valid pkg-config > entry for %s > > > using PKG_CONFIG_PATH=%s" % (" or ".join(options), > > > os.environ.get("PKG_CONFIG_PATH", "(empty)"))) > > > Exception: ERROR: cannot find a valid pkg-config entry for > libavformat > > > using PKG_CONFIG_PATH=(empty) > > You need the libavformat development headers and pkg-config file. > > I have added more details here: > > https://www.xpra.org/trac/wiki/Building/Debian > > > > > > Cheers > > Antoine > > > > > > > > im still investigating .... > > > _______________________________________________ > > > shifter-users mailing list > > > shifter-users at lists.devloop.org.uk > > > > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > > > > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > > > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > > > > > > >