From schodge at gmail.com Fri Apr 5 02:23:46 2019 From: schodge at gmail.com (Stuart Hodges) Date: Thu, 4 Apr 2019 21:23:46 -0400 Subject: [winswitch] =?utf-8?q?OS_X_Mojave=E2=80=99s__XPRS_server?= Message-ID: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> Hi, I?m trying to use a XPRA server on OS X Mojave. I was unsure if it would work at all with OS X not being native X11 but I have XQuartz running and the documentation seems to suggest it would. I installed the dmg but the server button is not enabled, the shadow button is but if I select it I can?t connect although an additional XPRA process is started. I use XPRA on Linux so have some experience. Should it work. If so how do I start a server ? Thanks From antoine at nagafix.co.uk Fri Apr 5 02:29:46 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 5 Apr 2019 08:29:46 +0700 Subject: [winswitch] =?utf-8?q?OS_X_Mojave=E2=80=99s_XPRS_server?= In-Reply-To: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> References: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> Message-ID: On 05/04/2019 08:23, Stuart Hodges via shifter-users wrote: > Hi, > > I?m trying to use a XPRA server on OS X Mojave. I was unsure if it would work at all with OS X not being native X11 but I have XQuartz running and the documentation seems to suggest it would. Xpra on MacOS does not use X11 at all, so XQuartz is not needed. > I installed the dmg but the server button is not enabled, the shadow button is but if I select it I can?t connect although an additional XPRA process is started. The shadow server should start, but it hasn't been tested on Mojave and I have heard that some new "security" mechanisms may be getting in the way. > I use XPRA on Linux so have some experience. > > Should it work. If so how do I start a server ? The best way would be to install the PKG, if possible, then run the server by hand: Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon Keep an eye on that server log output and try to connect with a browser on that port. Cheers, Antoine > > Thanks > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From lonnie at outstep.com Mon Apr 1 22:38:29 2019 From: lonnie at outstep.com (Lonnie Cumberland) Date: Mon, 1 Apr 2019 17:38:29 -0400 Subject: [winswitch] is windswitch still viable Message-ID: Hello, I am very interested in using Winswitch within a project that I am working on now as it seems to be exactly what I need. With that in mind, I wanted to do a test and just installed it on my Ubuntu 18,04 system as per the instructions, but I cannot seem to tell if it is functional or not as I get no information after starting the program. To have a system that the Unbuntu 18.04 system could talk to, I also tried to install Winswitch on my older WindowsXP (32-bit system) but that may have also not gone well since it seems to depend upon "Bonjour for Windows 1.0.5" and that does not seem to be available. Can someone please help guide me in the right direction? Also, I just wanted to know if the Winswitch project is still active? If not, then perhaps someone will be interested in helping to bring it back to life, as I do not really know of any viable directly competitors or replacement in at my project needs to be able to work on different platforms as well as in seamless mode to have applications from different systems on the same desktop. Any information would be very helpful. Cheers, Lonnie From lonnie at outstep.com Tue Apr 2 00:39:44 2019 From: lonnie at outstep.com (Lonnie Cumberland) Date: Mon, 1 Apr 2019 19:39:44 -0400 Subject: [winswitch] Xpra for linux, windows, osx, Message-ID: Hello, I have recently been looking at Winswitch but think that now maybe Xpra is more of what I need for my project in that I need to be able to use seamless mode to be able to connect windows and linux applications to display seamless on a desktop. I know that Xpra can handle Linux seamless windows but can it handle windows applications in seamless mode as well? Also, I am interested in being able to pass audio and video streaming, too -- Best Regards, Lonnie T. Cumberland, PhD. Email: Lonnie.Cumberland at Outstep.com From lonnie at outstep.com Fri Apr 5 16:57:29 2019 From: lonnie at outstep.com (Lonnie Cumberland) Date: Fri, 5 Apr 2019 11:57:29 -0400 Subject: [winswitch] Interesting thought on Xpra for Windoes Message-ID: Hello All, I am slowly working on a project in which I am going to be using Xpra and have been spending a huge amount of time researching what is currently out there and how it could possibly be used within my project. To that end, what I was looking for is a simple remote protocol seamless-based solution and Xpra seems to be that solution. For my project, I am interested in not only sending windows from Linux hosts to Windows, but also from Windows to Linux while also supporting all of the nice features that Xpra already has available. In my tests, I see that going from Linux to Windows works nicely and even has sound, etc.. The problem seems to be in going from Windows to Linux, but I might have an idea that could work and wanted to see if the group had already thought about it. This idea would be to take the Xpra Windows side and add parts of the code from a project used in rdesktop, and others called "SeamlessRDP" (https://github.com/rdesktop/seamlessrdp). That code is in c/c++ and the part that I am thinking about is the part that gets the actual windows to send back via the RDP protocol, but I do not see why it could not instead just get the windows information and send it back via Xpra. With Python and C/C++ being able to work together, I am trying to see if this type of solution idea might actually be possible. Any thoughts? Best Regards, Lonnie From schodge at gmail.com Sun Apr 7 02:20:44 2019 From: schodge at gmail.com (Stuart Hodges) Date: Sun, 7 Apr 2019 01:20:44 +0000 Subject: [winswitch] =?utf-8?q?OS_X_Mojave=E2=80=99s_XPRS_server?= In-Reply-To: References: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> Message-ID: <259741cd-9eba-e160-0766-25365a21720c@gmail.com> Thanks, The results are quite intersting. When run as you sugest I got : Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon 2019-04-05 20:50:47,908 closing tcp socket 0.0.0.0:14500 xpra initialization error: ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", line 93, in main ??? return run_mode(script_file, err, options, args, mode, defaults) ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", line 421, in run_mode ??? return run_server(error_cb, options, mode, script_file, args, current_display) ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", line 617, in run_server ??? return do_run_server(error_cb, opts, mode, xpra_file, extra_args, desktop_display) ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", line 1054, in do_run_server ??? no_gtk() ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", line 1730, in no_gtk ??? assert gtk.ver is None So I played around for a bit with options to work around that and could not make it go away so I just temporarily modified the /Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py putting a return in as below to see what would happen : def no_gtk(): ??? gtk = sys.modules.get("gtk") or sys.modules.get("gi.repository.Gtk") ??? return It now works when run from the command line : macserver:tmp schodge$ PYTHONPATH=/Applications/Xpra.app/Contents Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: Warning: invalid cast from 'GtkMenuBar' to 'GtkWindow' ? osxapp.set_menu_bar(mh.rebuild()) /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: GtkWarning: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed ? osxapp.set_menu_bar(mh.rebuild()) 2019-04-05 20:42:17,004 created unix domain socket: /Volumes/external/home/schodge/.xpra/macserver.lan-0 2019-04-05 20:42:17,085 serving html content from: /Applications/Xpra.app/Contents/Resources/www 2019-04-05 20:42:17,109 Error setting up system tray Traceback (most recent call last): ? File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/server/shadow/gtk_shadow_server_base.py", line 218, in setup_tray ??? self.tray_menu.append(self.traymenuitem("About Xpra", "information.png", None, about)) AttributeError: 'NoneType' object has no attribute 'append' 2019-04-05 20:42:17,637 GStreamer version 1.14.4 for Python 2.7.16 64-bit 2019-04-05 20:42:17,692 printer forwarding enabled using postscript 2019-04-05 20:42:17,706 xpra GTK2 shadow version 2.5-r22144 64-bit 2019-04-05 20:42:17,707? uid=501 (schodge), gid=20 (staff) 2019-04-05 20:42:17,707? running with pid 1608 on Mac OS X 10.14.3 2019-04-05 20:42:17,707? on display ':0' of size 1920x1080 2019-04-05 20:42:17,749 8.0GB of system memory 2019-04-05 20:42:17,750 xpra is ready. 2019-04-05 20:42:41,359 Handshake complete; enabling connection 2019-04-05 20:42:41,401? automatic picture encoding enabled, also available: 2019-04-05 20:42:41,401?? jpeg, png, rgb32, h264 2019-04-05 20:42:41,431 HTML5 Mac OSX Firefox client version 2.5 2019-04-05 20:42:41,864 shadow server: setting default keymap translation 2019-04-05 20:42:41,864? client root window size is 1280x656 2019-04-05 20:42:42,070 client got hello: server version 2.5 accepted our connection 2019-04-05 20:42:42,139 Error: cannot add printer 'HTML5 client': 2019-04-05 20:42:42,139? the printing system does not support application/pdf 2019-04-05 20:42:42,139 client connection_progress( Session started ,?? ,? 100 ) 2019-04-05 20:42:42,140 client window does not fit in canvas, offsets:? -320 -212 2019-04-05 20:42:42,141 client startup complete 2019-04-05 20:42:42,141 client connection-established The performance is not amazing but that could be to do with the old server I have running the firefox. It also looks like the MAC version was built without server support: Xpra start --bind-tcp=0.0.0.0:14500 --no-daemon xpra initialization error: ?invalid mode 'start' So I'm not realy sure wheat the next step is. I realy want to display back individual windows as opposed to shadowing the whole desktop. Was there a reason for the OSX build the start was not enabled or should I just build it myself on the Mac ? Also my hack of putting the return in is hardly a long term solution :) Any advice, Thanks On 04/05/2019 01:29 AM, Antoine Martin via shifter-users wrote: > On 05/04/2019 08:23, Stuart Hodges via shifter-users wrote: >> Hi, >> >> I?m trying to use a XPRA server on OS X Mojave. I was unsure if it would work at all with OS X not being native X11 but I have XQuartz running and the documentation seems to suggest it would. > Xpra on MacOS does not use X11 at all, so XQuartz is not needed. > >> I installed the dmg but the server button is not enabled, the shadow button is but if I select it I can?t connect although an additional XPRA process is started. > The shadow server should start, but it hasn't been tested on Mojave and > I have heard that some new "security" mechanisms may be getting in the way. > >> I use XPRA on Linux so have some experience. >> >> Should it work. If so how do I start a server ? > The best way would be to install the PKG, if possible, then run the > server by hand: > Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon > Keep an eye on that server log output and try to connect with a browser > on that port. > > Cheers, > Antoine > > >> Thanks >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >> > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From antoine at nagafix.co.uk Sun Apr 7 14:15:33 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 7 Apr 2019 20:15:33 +0700 Subject: [winswitch] Request to work on Android Client for Xpra for GSoC 2019 In-Reply-To: References: Message-ID: <19997395-90ae-7028-52e5-8ebd2d023d30@nagafix.co.uk> On 27/03/2019 23:10, Venkata Rama Koundinya Lanka via shifter-users wrote: > Hi everyone, > > My name is Venkata Rama Koundinya Lanka, a final year engineering student > from India. I have some experience in android programming and interest in > networks. I would like to contribute to xpra android client for GSoC 2019. > I have downloaded the code and I am locally running it in android studio. Which code have you downloaded? There are many ideas already here: https://xpra.org/trac/wiki/Clients/Android and here: https://xpra.org/trac/wiki/ProjectIdeas > Can anyone tell me a good issue to start with? Surely there are issues with the current version of the client. Did you not hit any problems using it? Cheers, Antoine > > Yours sincerely, > Venkata Rama Koundinya Lanka > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sun Apr 7 14:17:55 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 7 Apr 2019 20:17:55 +0700 Subject: [winswitch] is windswitch still viable In-Reply-To: References: Message-ID: <834e5209-1833-3024-32e7-07075b54dad7@nagafix.co.uk> On 02/04/2019 04:38, Lonnie Cumberland via shifter-users wrote: > Hello, > > I am very interested in using Winswitch within a project that I am working > on now as it seems to be exactly what I need. > > With that in mind, I wanted to do a test and just installed it on my Ubuntu > 18,04 system as per the instructions, but I cannot seem to tell if it is > functional or not as I get no information after starting the program. winswitch is meant to be available via its system tray menu. > To have a system that the Unbuntu 18.04 system could talk to, I also tried > to install Winswitch on my older WindowsXP (32-bit system) but that may > have also not gone well since it seems to depend upon "Bonjour for Windows > 1.0.5" and that does not seem to be available. This is not a hard dependency, mdns just makes it easier to find hosts on your LAN. > Can someone please help guide me in the right direction? > > Also, I just wanted to know if the Winswitch project is still active? Not really, I do not have much time for it nowadays. > If > not, then perhaps someone will be interested in helping to bring it back to > life, as I do not really know of any viable directly competitors or > replacement in at my project needs to be able to work on different > platforms as well as in seamless mode to have applications from different > systems on the same desktop. I would gladly help you do that. Cheers, Antoine > > Any information would be very helpful. > Cheers, > Lonnie > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sun Apr 7 14:19:25 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 7 Apr 2019 20:19:25 +0700 Subject: [winswitch] Xpra for linux, windows, osx, In-Reply-To: References: Message-ID: On 02/04/2019 06:39, Lonnie Cumberland via shifter-users wrote: > Hello, > > I have recently been looking at Winswitch but think that now maybe Xpra is > more of what I need for my project in that I need to be able to use > seamless mode to be able to connect windows and linux applications to > display seamless on a desktop. > > I know that Xpra can handle Linux seamless windows but can it handle > windows applications in seamless mode as well? No, not at present. > > Also, I am interested in being able to pass audio and video streaming, too Audio should work fine already. Xpra handles video compression, though this may not work exactly the way you would expect. Cheers, Antoine From antoine at nagafix.co.uk Sun Apr 7 14:24:07 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 7 Apr 2019 20:24:07 +0700 Subject: [winswitch] Interesting thought on Xpra for Windoes In-Reply-To: References: Message-ID: On 05/04/2019 22:57, Lonnie Cumberland via shifter-users wrote: > Hello All, > > I am slowly working on a project in which I am going to be using Xpra and > have been spending a huge amount of time researching what is currently out > there and how it could possibly be used within my project. > > To that end, what I was looking for is a simple remote protocol > seamless-based solution and Xpra seems to be that solution. For my project, > I am interested in not only sending windows from Linux hosts to Windows, > but also from Windows to Linux while also supporting all of the nice > features that Xpra already has available. Seamless mode is not supported with MS Windows servers at present. > In my tests, I see that going from Linux to Windows works nicely and even > has sound, etc.. > > The problem seems to be in going from Windows to Linux, but I might have an > idea that could work and wanted to see if the group had already thought > about it. This idea would be to take the Xpra Windows side and add parts > of the code from a project used in rdesktop, and others called > "SeamlessRDP" (https://github.com/rdesktop/seamlessrdp). Have you tried to use Seamless RDP? The project does not seem very active, and it never worked properly when I tried it. > That code is in c/c++ and the part that I am thinking about is the part > that gets the actual windows to send back via the RDP protocol, but I do > not see why it could not instead just get the windows information and send > it back via Xpra. With Python and C/C++ being able to work together, I am > trying to see if this type of solution idea might actually be possible. Because of the usability problems with SeamlessRDP, I have never looked into this possibility. Assuming that SeamlessRDP can be made to work reliably on Windows-8.1 or later, I can't see any reason why this could not be made to work with xpra. How well remains to be seen. Cheers Antoine > > Any thoughts? > Best Regards, > Lonnie > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Sun Apr 7 14:34:18 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 7 Apr 2019 20:34:18 +0700 Subject: [winswitch] =?utf-8?q?OS_X_Mojave=E2=80=99s_XPRA_server?= In-Reply-To: <259741cd-9eba-e160-0766-25365a21720c@gmail.com> References: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> <259741cd-9eba-e160-0766-25365a21720c@gmail.com> Message-ID: <56809184-7d1a-b905-77e0-f5ed6167c3b4@nagafix.co.uk> On 07/04/2019 08:20, Stuart Hodges via shifter-users wrote: > Thanks, > > The results are quite intersting. > > When run as you sugest I got : > > Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon > 2019-04-05 20:50:47,908 closing tcp socket 0.0.0.0:14500 > xpra initialization error: > > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", > line 93, in main > ??? return run_mode(script_file, err, options, args, mode, defaults) > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", > line 421, in run_mode > ??? return run_server(error_cb, options, mode, script_file, args, > current_display) > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", > line 617, in run_server > ??? return do_run_server(error_cb, opts, mode, xpra_file, extra_args, > desktop_display) > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", > line 1054, in do_run_server > ??? no_gtk() > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", > line 1730, in no_gtk > ??? assert gtk.ver is None This looks like a bug. Try the Python3 / GTK3 builds, those don't seem to have this problem. > So I played around for a bit with options to work around that and could > not make it go away so I just temporarily modified the > /Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py putting > a return in as below to see what would happen : > > def no_gtk(): > ??? gtk = sys.modules.get("gtk") or sys.modules.get("gi.repository.Gtk") > ??? return I'll take a look at this and try to come up with a more correct fix. > It now works when run from the command line : > > macserver:tmp schodge$ PYTHONPATH=/Applications/Xpra.app/Contents Xpra > shadow --bind-tcp=0.0.0.0:14500 --no-daemon > /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: > Warning: invalid cast from 'GtkMenuBar' to 'GtkWindow' > ? osxapp.set_menu_bar(mh.rebuild()) > /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: > GtkWarning: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW > (window)' failed > ? osxapp.set_menu_bar(mh.rebuild()) > 2019-04-05 20:42:17,004 created unix domain socket: > /Volumes/external/home/schodge/.xpra/macserver.lan-0 > 2019-04-05 20:42:17,085 serving html content from: > /Applications/Xpra.app/Contents/Resources/www > 2019-04-05 20:42:17,109 Error setting up system tray > Traceback (most recent call last): > ? File > "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/server/shadow/gtk_shadow_server_base.py", > line 218, in setup_tray > ??? self.tray_menu.append(self.traymenuitem("About Xpra", > "information.png", None, about)) > AttributeError: 'NoneType' object has no attribute 'append' Looks like another minor bug, which may prevent the server system tray control menu from showing up. > 2019-04-05 20:42:17,637 GStreamer version 1.14.4 for Python 2.7.16 64-bit > 2019-04-05 20:42:17,692 printer forwarding enabled using postscript > 2019-04-05 20:42:17,706 xpra GTK2 shadow version 2.5-r22144 64-bit > 2019-04-05 20:42:17,707? uid=501 (schodge), gid=20 (staff) > 2019-04-05 20:42:17,707? running with pid 1608 on Mac OS X 10.14.3 > 2019-04-05 20:42:17,707? on display ':0' of size 1920x1080 > 2019-04-05 20:42:17,749 8.0GB of system memory > 2019-04-05 20:42:17,750 xpra is ready. > 2019-04-05 20:42:41,359 Handshake complete; enabling connection > 2019-04-05 20:42:41,401? automatic picture encoding enabled, also > available: > 2019-04-05 20:42:41,401?? jpeg, png, rgb32, h264 > 2019-04-05 20:42:41,431 HTML5 Mac OSX Firefox client version 2.5 > 2019-04-05 20:42:41,864 shadow server: setting default keymap translation > 2019-04-05 20:42:41,864? client root window size is 1280x656 > 2019-04-05 20:42:42,070 client got hello: server version 2.5 accepted > our connection > 2019-04-05 20:42:42,139 Error: cannot add printer 'HTML5 client': > 2019-04-05 20:42:42,139? the printing system does not support > application/pdf > 2019-04-05 20:42:42,139 client connection_progress( Session started ,?? > ,? 100 ) > 2019-04-05 20:42:42,140 client window does not fit in canvas, offsets:? > -320 -212 > 2019-04-05 20:42:42,141 client startup complete > 2019-04-05 20:42:42,141 client connection-established > > The performance is not amazing but that could be to do with the old > server I have running the firefox. The HTML5 client is always going to be slower than the native one. On top of that, shadow servers are not particularly efficient. > It also looks like the MAC version was built without server support: > > Xpra start --bind-tcp=0.0.0.0:14500 --no-daemon > xpra initialization error: > ?invalid mode 'start' Seamless mode is not supported on MS Windows or MacOS. > So I'm not realy sure wheat the next step is. > > I realy want to display back individual windows as opposed to shadowing > the whole desktop. Was there a reason for the OSX build the start was > not enabled or should I just build it myself on the Mac ? In theory, it should be possible to build an X11 based xpra server for MacOS which would be able to export seamless windows (individual applications rather than the whole desktop), but this would only work for X11 based applications and there aren't many of those on MacOS apart from "xterm", "xeyes" and a few other toy applications. All the other applications use direct rendering and cannot be intercepted to be displayed remotely. > Also my hack of putting the return in is hardly a long term solution :) Will fix. Cheers, Antoine > > Any advice, > > Thanks > > > > On 04/05/2019 01:29 AM, Antoine Martin via shifter-users wrote: >> On 05/04/2019 08:23, Stuart Hodges via shifter-users wrote: >>> Hi, >>> >>> I?m trying to use a XPRA server on OS X Mojave. I was unsure if it >>> would? work at all with OS X not being native X11 but I have XQuartz >>> running and the documentation seems to suggest it would. >> Xpra on MacOS does not use X11 at all, so XQuartz is not needed. >> >>> I installed the dmg but? the server button is not enabled, the shadow >>> button is but if I select it I can?t connect although an additional >>> XPRA process is started. >> The shadow server should start, but it hasn't been tested on Mojave and >> I have heard that some new "security" mechanisms may be getting in the >> way. >> >>> I use XPRA on Linux so have some experience. >>> >>> Should it work. If so how do I start a server ? >> The best way would be to install the PKG, if possible, then run the >> server by hand: >> Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon >> Keep an eye on that server log output and try to connect with a browser >> on that port. >> >> Cheers, >> Antoine >> >> >>> Thanks >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users at lists.devloop.org.uk >>> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >>> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From lonnie at outstep.com Sun Apr 7 18:53:47 2019 From: lonnie at outstep.com (Lonnie Cumberland) Date: Sun, 7 Apr 2019 13:53:47 -0400 Subject: [winswitch] Interesting thought on Xpra for Windoes In-Reply-To: References: Message-ID: Hello all, > > The problem seems to be in going from Windows to Linux, but I might have > an > > idea that could work and wanted to see if the group had already thought > > about it. This idea would be to take the Xpra Windows side and add parts > > of the code from a project used in rdesktop, and others called > > "SeamlessRDP" (https://github.com/rdesktop/seamlessrdp). > Have you tried to use Seamless RDP? > The project does not seem very active, and it never worked properly when > I tried it. > I actually have not had the chance to make it work and also came across "MetaVNC" (http://metavnc.sourceforge.net/) which is a bit dated but is also based upon TightVNC and is meant to be a seamless implementation. Perhaps xpra could find it useful in some way. I may try to build it and see if it will still work. > > That code is in c/c++ and the part that I am thinking about is the part > > that gets the actual windows to send back via the RDP protocol, but I do > > not see why it could not instead just get the windows information and > send > > it back via Xpra. With Python and C/C++ being able to work together, I > am > > trying to see if this type of solution idea might actually be possible. > Because of the usability problems with SeamlessRDP, I have never looked > into this possibility. > Assuming that SeamlessRDP can be made to work reliably on Windows-8.1 or > later, I can't see any reason why this could not be made to work with > xpra. How well remains to be seen. > Actually, I was not thinking to use SeamlessRDP inside of Xpra directly, but mainly just the code parts that grab the active windows and such from an application in Windows. It would then seem reasonable that you could use new small app "SeamlessXPRA.exe notepad.exe" (from within Windows) to serve the application like is done in Linux and then a client could connect. Basically, my thoughts were to see what would be required to strip out the RDP parts in SeamlessRDP and just keep the Windows application hooks so that it can grab the application window and send it via the Xpra protocol. It was just a thought, but it then seemed that it might be possible to offer the same capabilities on Windows as you have on Linux. I have a very specific use in mind for all of this and perhaps we could chat more on it if you are interested, and possibly have time, since I do not know Xpra very well and this might be a side project until it really starts to get going. Have a great weekend, Antoine Cheers, Lonnie > Cheers > Antoine > > > > > > Any thoughts? > > Best Regards, > > Lonnie > > _______________________________________________ > > shifter-users mailing list > > shifter-users at lists.devloop.org.uk > > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > -- Best Regards, Lonnie T. Cumberland, PhD. Email: Lonnie.Cumberland at Outstep.com From Benjamin.Sferrazza at skyworksinc.com Thu Apr 11 23:47:51 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Thu, 11 Apr 2019 22:47:51 +0000 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen Message-ID: <1555022871966.40410@skyworksinc.com> I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works well, but I can't get 'xpra start-desktop' to work. It merely shows a black screen. Similarly, trying to just launch a window such as 'xpra start=gnome-terminal' shows nothing. 'xpra start=xterm' does bring up xterm, but trying to launch something like gnome-terminal from that xterm shows nothing. Verbose logs don't seem to indicate anything is amiss. Any advice on things I can try? Thanks, Ben From schodge at gmail.com Fri Apr 12 00:17:49 2019 From: schodge at gmail.com (Stuart Hodges) Date: Thu, 11 Apr 2019 19:17:49 -0400 Subject: [winswitch] =?utf-8?q?OS_X_Mojave=E2=80=99s_XPRA_server?= In-Reply-To: <56809184-7d1a-b905-77e0-f5ed6167c3b4@nagafix.co.uk> References: <41E89ECA-ACE9-4057-9C12-0C814989A594@gmail.com> <259741cd-9eba-e160-0766-25365a21720c@gmail.com> <56809184-7d1a-b905-77e0-f5ed6167c3b4@nagafix.co.uk> Message-ID: Hi, Thanks for the information on seamless mode. Stuart On 4/7/19 9:34 AM, Antoine Martin via shifter-users wrote: > On 07/04/2019 08:20, Stuart Hodges via shifter-users wrote: >> Thanks, >> >> The results are quite intersting. >> >> When run as you sugest I got : >> >> Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon >> 2019-04-05 20:50:47,908 closing tcp socket 0.0.0.0:14500 >> xpra initialization error: >> >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", >> line 93, in main >> ??? return run_mode(script_file, err, options, args, mode, defaults) >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", >> line 421, in run_mode >> ??? return run_server(error_cb, options, mode, script_file, args, >> current_display) >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", >> line 617, in run_server >> ??? return do_run_server(error_cb, opts, mode, xpra_file, extra_args, >> desktop_display) >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/server.py", >> line 1054, in do_run_server >> ??? no_gtk() >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py", >> line 1730, in no_gtk >> ??? assert gtk.ver is None > This looks like a bug. > Try the Python3 / GTK3 builds, those don't seem to have this problem. > > >> So I played around for a bit with options to work around that and could >> not make it go away so I just temporarily modified the >> /Applications/Xpra.app/Contents/Resources/lib/python/xpra/scripts/main.py putting >> a return in as below to see what would happen : >> >> def no_gtk(): >> ??? gtk = sys.modules.get("gtk") or sys.modules.get("gi.repository.Gtk") >> ??? return > I'll take a look at this and try to come up with a more correct fix. > >> It now works when run from the command line : >> >> macserver:tmp schodge$ PYTHONPATH=/Applications/Xpra.app/Contents Xpra >> shadow --bind-tcp=0.0.0.0:14500 --no-daemon >> /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: >> Warning: invalid cast from 'GtkMenuBar' to 'GtkWindow' >> ? osxapp.set_menu_bar(mh.rebuild()) >> /Applications/Xpra.app/Contents/Resources/lib/python/xpra/platform/darwin/gui.py:104: >> GtkWarning: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW >> (window)' failed >> ? osxapp.set_menu_bar(mh.rebuild()) >> 2019-04-05 20:42:17,004 created unix domain socket: >> /Volumes/external/home/schodge/.xpra/macserver.lan-0 >> 2019-04-05 20:42:17,085 serving html content from: >> /Applications/Xpra.app/Contents/Resources/www >> 2019-04-05 20:42:17,109 Error setting up system tray >> Traceback (most recent call last): >> ? File >> "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/server/shadow/gtk_shadow_server_base.py", >> line 218, in setup_tray >> ??? self.tray_menu.append(self.traymenuitem("About Xpra", >> "information.png", None, about)) >> AttributeError: 'NoneType' object has no attribute 'append' > Looks like another minor bug, which may prevent the server system tray > control menu from showing up. > >> 2019-04-05 20:42:17,637 GStreamer version 1.14.4 for Python 2.7.16 64-bit >> 2019-04-05 20:42:17,692 printer forwarding enabled using postscript >> 2019-04-05 20:42:17,706 xpra GTK2 shadow version 2.5-r22144 64-bit >> 2019-04-05 20:42:17,707? uid=501 (schodge), gid=20 (staff) >> 2019-04-05 20:42:17,707? running with pid 1608 on Mac OS X 10.14.3 >> 2019-04-05 20:42:17,707? on display ':0' of size 1920x1080 >> 2019-04-05 20:42:17,749 8.0GB of system memory >> 2019-04-05 20:42:17,750 xpra is ready. >> 2019-04-05 20:42:41,359 Handshake complete; enabling connection >> 2019-04-05 20:42:41,401? automatic picture encoding enabled, also >> available: >> 2019-04-05 20:42:41,401?? jpeg, png, rgb32, h264 >> 2019-04-05 20:42:41,431 HTML5 Mac OSX Firefox client version 2.5 >> 2019-04-05 20:42:41,864 shadow server: setting default keymap translation >> 2019-04-05 20:42:41,864? client root window size is 1280x656 >> 2019-04-05 20:42:42,070 client got hello: server version 2.5 accepted >> our connection >> 2019-04-05 20:42:42,139 Error: cannot add printer 'HTML5 client': >> 2019-04-05 20:42:42,139? the printing system does not support >> application/pdf >> 2019-04-05 20:42:42,139 client connection_progress( Session started , >> ,? 100 ) >> 2019-04-05 20:42:42,140 client window does not fit in canvas, offsets: >> -320 -212 >> 2019-04-05 20:42:42,141 client startup complete >> 2019-04-05 20:42:42,141 client connection-established >> >> The performance is not amazing but that could be to do with the old >> server I have running the firefox. > The HTML5 client is always going to be slower than the native one. > On top of that, shadow servers are not particularly efficient. > >> It also looks like the MAC version was built without server support: >> >> Xpra start --bind-tcp=0.0.0.0:14500 --no-daemon >> xpra initialization error: >> ?invalid mode 'start' > Seamless mode is not supported on MS Windows or MacOS. > >> So I'm not realy sure wheat the next step is. >> >> I realy want to display back individual windows as opposed to shadowing >> the whole desktop. Was there a reason for the OSX build the start was >> not enabled or should I just build it myself on the Mac ? > In theory, it should be possible to build an X11 based xpra server for > MacOS which would be able to export seamless windows (individual > applications rather than the whole desktop), but this would only work > for X11 based applications and there aren't many of those on MacOS apart > from "xterm", "xeyes" and a few other toy applications. > All the other applications use direct rendering and cannot be > intercepted to be displayed remotely. > >> Also my hack of putting the return in is hardly a long term solution :) > Will fix. > > Cheers, > Antoine > >> Any advice, >> >> Thanks >> >> >> >> On 04/05/2019 01:29 AM, Antoine Martin via shifter-users wrote: >>> On 05/04/2019 08:23, Stuart Hodges via shifter-users wrote: >>>> Hi, >>>> >>>> I?m trying to use a XPRA server on OS X Mojave. I was unsure if it >>>> would? work at all with OS X not being native X11 but I have XQuartz >>>> running and the documentation seems to suggest it would. >>> Xpra on MacOS does not use X11 at all, so XQuartz is not needed. >>> >>>> I installed the dmg but? the server button is not enabled, the shadow >>>> button is but if I select it I can?t connect although an additional >>>> XPRA process is started. >>> The shadow server should start, but it hasn't been tested on Mojave and >>> I have heard that some new "security" mechanisms may be getting in the >>> way. >>> >>>> I use XPRA on Linux so have some experience. >>>> >>>> Should it work. If so how do I start a server ? >>> The best way would be to install the PKG, if possible, then run the >>> server by hand: >>> Xpra shadow --bind-tcp=0.0.0.0:14500 --no-daemon >>> Keep an eye on that server log output and try to connect with a browser >>> on that port. >>> >>> Cheers, >>> Antoine >>> >>> >>>> Thanks >>>> _______________________________________________ >>>> shifter-users mailing list >>>> shifter-users at lists.devloop.org.uk >>>> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>> >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users at lists.devloop.org.uk >>> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From antoine at nagafix.co.uk Fri Apr 12 04:45:23 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 12 Apr 2019 10:45:23 +0700 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <1555022871966.40410@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> Message-ID: <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: > I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works well, but I can't get 'xpra start-desktop' to work. It merely shows a black screen. xpra start-desktop on its own will only start an empty full-window session, you need to start a window manager or some other application to interact with, ie for testing: xpra start-desktop --start=xterm Then you can start a window manager or something else from the xterm. > > Similarly, trying to just launch a window such as 'xpra start=gnome-terminal' shows nothing. 'xpra start=xterm' does bring up xterm, but trying to launch something like gnome-terminal from that xterm shows nothing. Verbose logs don't seem to indicate anything is amiss. > > > Any advice on things I can try? That's odd. I've just tried it and it worked fine. Please create a ticket as per: https://xpra.org/trac/wiki/ReportingBugs Make sure to include "xpra info". And please try connecting from another client (ie: from the Ubuntu system itself) to figure out if the problem is server side or client side. Cheers, Antoine > > > Thanks, > > Ben > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From Benjamin.Sferrazza at skyworksinc.com Fri Apr 12 15:33:00 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Fri, 12 Apr 2019 14:33:00 +0000 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> References: <1555022871966.40410@skyworksinc.com>, <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> Message-ID: <1555079581028.25863@skyworksinc.com> On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: > I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works well, but I can't get 'xpra start-desktop' to work. It merely shows a black screen. xpra start-desktop on its own will only start an empty full-window session, you need to start a window manager or some other application to interact with, ie for testing: xpra start-desktop --start=xterm Then you can start a window manager or something else from the xterm I'm sorry, I should have mentioned I used --start=gnome-session. > > Similarly, trying to just launch a window such as 'xpra start=gnome-terminal' shows nothing. 'xpra start=xterm' does bring up xterm, but trying to launch something like gnome-terminal from that xterm shows nothing. Verbose logs don't seem to indicate anything is amiss. > > > Any advice on things I can try? That's odd. I've just tried it and it worked fine. Please create a ticket as per: https://urldefense.proofpoint.com/v2/url?u=https-3A__xpra.org_trac_wiki_ReportingBugs&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=hYC-Mg4CFDCDDFQQo4OChT_tnXsfnzENzlTSDAvpE1U&s=Sc2p7PKYs3hgrfUuQRTwYpEvhq85BkSMngsHoedlHNQ&e= Make sure to include "xpra info". And please try connecting from another client (ie: from the Ubuntu system itself) to figure out if the problem is server side or client side. OK I'll go ahead and do that. I also forgot to mention that I tried connecting from the Ubuntu localhost and it also just shows a black screen. So it would seem to indicate there's something up with the server. Cheers, Antoine > > > Thanks, > > Ben > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.devloop.org.uk_mailman_listinfo_shifter-2Dusers&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=hYC-Mg4CFDCDDFQQo4OChT_tnXsfnzENzlTSDAvpE1U&s=uUMhfLHNMHnjNupC-xmyCSgR2ZvortCGq0QnpPJ4MIQ&e= > _______________________________________________ shifter-users mailing list shifter-users at lists.devloop.org.uk https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.devloop.org.uk_mailman_listinfo_shifter-2Dusers&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=hYC-Mg4CFDCDDFQQo4OChT_tnXsfnzENzlTSDAvpE1U&s=uUMhfLHNMHnjNupC-xmyCSgR2ZvortCGq0QnpPJ4MIQ&e= From antoine at nagafix.co.uk Fri Apr 12 16:20:39 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 12 Apr 2019 22:20:39 +0700 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <1555079581028.25863@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> <1555079581028.25863@skyworksinc.com> Message-ID: <700d384d-b640-cc45-1944-90f71e900b98@nagafix.co.uk> FYI: whatever email client you are using, it is messing up the inline quoting. On 12/04/2019 21:33, Ben Sferrazza via shifter-users wrote: > On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: >>> I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works well, but I can't get 'xpra start-desktop' to work. It merely shows a black screen. >> xpra start-desktop on its own will only start an empty full-window >> session, you need to start a window manager or some other application to >> interact with, ie for testing: >> xpra start-desktop --start=xterm >> Then you can start a window manager or something else from the xterm > I'm sorry, I should have mentioned I used --start=gnome-session. Well, there is your problem. Try a different window manager, or as per above just an xterm, and you will find that things work just fine. gnome is known to be problematic and may not work without an accelerated X11 server. >>> Similarly, trying to just launch a window such as 'xpra start=gnome-terminal' shows nothing. 'xpra start=xterm' does bring up xterm, but trying to launch something like gnome-terminal from that xterm shows nothing. Verbose logs don't seem to indicate anything is amiss. >>> Any advice on things I can try? >> That's odd. I've just tried it and it worked fine. >> Please create a ticket as per: >> https://xpra.org/trac/wiki/ReportingBugs >> Make sure to include "xpra info". >> And please try connecting from another client (ie: from the Ubuntu >> system itself) to figure out if the problem is server side or client side. > > OK I'll go ahead and do that. I also forgot to mention that I tried connecting from the Ubuntu localhost and it also just shows a black screen. So it would seem to indicate there's something up with the server. Or with gnome-terminal. Cheers, Antoine > > Cheers, > Antoine > > >> >> >> Thanks, >> >> Ben >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.devloop.org.uk_mailman_listinfo_shifter-2Dusers&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=hYC-Mg4CFDCDDFQQo4OChT_tnXsfnzENzlTSDAvpE1U&s=uUMhfLHNMHnjNupC-xmyCSgR2ZvortCGq0QnpPJ4MIQ&e= >> > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.devloop.org.uk_mailman_listinfo_shifter-2Dusers&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=hYC-Mg4CFDCDDFQQo4OChT_tnXsfnzENzlTSDAvpE1U&s=uUMhfLHNMHnjNupC-xmyCSgR2ZvortCGq0QnpPJ4MIQ&e= > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From Benjamin.Sferrazza at skyworksinc.com Tue Apr 16 00:57:19 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Mon, 15 Apr 2019 23:57:19 +0000 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <1555366903559.71595@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> <1555079581028.25863@skyworksinc.com> ,<700d384d-b640-cc45-1944-90f71e900b98@nagafix.co.uk> <1555366903559.71595@skyworksinc.com> Message-ID: <433389a3594e078f225f3eb508e814b7fb07cb90.camel@skyworksinc.com> On Mon, 2019-04-15 at 22:21 +0000, Ben Sferrazza wrote: > FYI: whatever email client you are using, it is messing up the inline > quoting. > > I believe this has something to do with my company filtering emails > that originate from an external source and processing them with added > text. Actually seems to be the fact that I was using the Outlook Web App in Linux. Now using Evolution. > > On 12/04/2019 21:33, Ben Sferrazza via shifter-users wrote: > > On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: > > > > I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The > > > > client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works > > > > well, but I can't get 'xpra start-desktop' to work. It merely > > > > shows a black screen. > > > xpra start-desktop on its own will only start an empty full- > > > window > > > session, you need to start a window manager or some other > > > application to > > > interact with, ie for testing: > > > xpra start-desktop --start=xterm > > > Then you can start a window manager or something else from the > > > xterm > > I'm sorry, I should have mentioned I used --start=gnome-session. > Well, there is your problem. > Try a different window manager, or as per above just an xterm, and > you > will find that things work just fine. > gnome is known to be problematic and may not work without an > accelerated > X11 server. > > OK, ideally wouldn't want to change window managers, but am willing > to give that a try. FYI, I use NIS for login with an NFS mounted > /home directory. I had setup Xpra (successfully) on our Linux servers > that run an old version of CentOS. Now I am attempting to get Xpra to > work on my work PC where I just installed Ubuntu 18.10. There must be > some stale data/configs that could cause issues, as I'm still using > the same /home directory as before. I say that, because after trying > to unsuccessfully get Xpra to work with this Ubuntu install, I went > back just to see how things were working with the setup I had on the > CentOS Linux servers and it was no longer working. Do you have any > suggestions on files/directories to remove to start fresh? ~/.xpra > being an obvious one I suppose. removing ~/.xpra, ~/.local/xpra, and ~/.local/run/xpra seemed to do the trick. At least I can start a gnome-session and have a visible desktop (no more black screen). However, nothing happens on keyboard input and mouse input seems limited. I'll keep debugging. > > > > > Similarly, trying to just launch a window such as 'xpra > > > > start=gnome-terminal' shows nothing. 'xpra start=xterm' does > > > > bring up xterm, but trying to launch something like gnome- > > > > terminal from that xterm shows nothing. Verbose logs don't seem > > > > to indicate anything is amiss. > > > > Any advice on things I can try? > > > That's odd. I've just tried it and it worked fine. > > > Please create a ticket as per: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__xpra.org_trac_wiki_ReportingBugs&d=DwICAg&c=VYRDWu-sKuQrybEAJ2u-dYX_FK6X1lTrDf-PKXUa2P4&r=KUvBUvwZ3xYCa05A5NCXRUdX-yDQhrA_pjQ6in6O-IFVY81yykI4UK_bEOyPBhCw&m=1ry-QExQgmmOByMBK9tpR2G3ZKgDb6cFzeCl0ABhIZQ&s=H_oJFXMfp3dShpPBsIt50P_P-XOlWG2VTdPmK-O66JY&e= > > > Make sure to include "xpra info". > > > And please try connecting from another client (ie: from the > > > Ubuntu > > > system itself) to figure out if the problem is server side or > > > client side. > > > > OK I'll go ahead and do that. I also forgot to mention that I tried > > connecting from the Ubuntu localhost and it also just shows a black > > screen. So it would seem to indicate there's something up with the > > server. > Or with gnome-terminal. > > Cheers, > Antoine From antoine at nagafix.co.uk Tue Apr 16 09:17:26 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 16 Apr 2019 15:17:26 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.5.1: many fixes, none critical Message-ID: Hi, Enough fixes had accumulated to warrant an update. Updating is recommended but none of the bugs fixed are critical. Release notes: * fix sending of icons as premultipled ARGB * fix compatibility with old versions of python-pillow * fix scroll encoding code flow (should be impossible to hit) * fix handling of info requests with Python3 servers * fix missing option for lock argument in man page * fix ssh errors handling authentication failures * fix ssh server connections and support 'none' authentication * fix start new command menu * fix appindicator failures when we fail to locate the default icon * fix command line tools usage under cygwin and terminal emulators * fix pointer position on multi-monitor shadow servers * fix system tray forwarding with python3 servers * fix window icons forwarding (MS Windows and MacOS mostly) * fix detection of splash window types * fix server startup errors when X11 root properties are invalid * fix shadow server startup failures on MacOS * fix system tray errors during shadow server startup on MacOS * fix printing errors with python3 builds and rencode packet encoder * fix parsing of printer options * fix dispatching of printer jobs to clients with python3 servers * fix parsing of key symbol definitions with python3 servers * fix compatibility with older versions of GTK3 * fix proxy video encoders initialization * fix 'missing encodings' server error with python3 * fix spurious clipboard warning when clipboard is disabled * disable modal windows by default (was enabled by default since v2.3) * workaround buggy system trays * try harder to prevent hash collisions in scroll encoding * skip risky opengl probing when the initial check failed * prevent file conflicts with older packages * don't use appindicator with Fedora Gnome * minor packaging fixes (dates) * remove spurious ssh dnssec check logging * bump version in cups backend * DEB package still recommends the python2 builds * don't bundle openssh on MS Windows The source: https://xpra.org/src/ Downloads: https://xpra.org/trac/wiki/Download Cheers Antoine From kmanev073 at gmail.com Tue Apr 16 14:00:08 2019 From: kmanev073 at gmail.com (Kaloyan Manev) Date: Tue, 16 Apr 2019 16:00:08 +0300 Subject: [winswitch] Xpra Implement WebRTC? Message-ID: Hello guys! I love Xpra, so far I've been using it for simple apps and it does the job. Any plans for using WebRTC to transfer data (could be used for nice web client)? Or perhaps improvements in the UDP? Thanks in advance! Regads, Kaloyan Manev From antoine at nagafix.co.uk Tue Apr 16 14:14:07 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 16 Apr 2019 20:14:07 +0700 Subject: [winswitch] Xpra Implement WebRTC? In-Reply-To: References: Message-ID: On 16/04/2019 20:00, Kaloyan Manev via shifter-users wrote: > Hello guys! > > I love Xpra, so far I've been using it for simple apps and it does the job. > Any plans for using WebRTC to transfer data (could be used for nice web > client)? The way xpra handles pixel transfers is quite different from your normal WebRTC video transfer: xpra sends only what has changed, in as small a chunk as possible whereas most WebRTC application usually send a video or audio stream. WebRTC could still be used as a transport, layering xpra's protocol on top of it. (the xpra protocol has a lot more data flowing than just the audio and video) > Or perhaps improvements in the UDP? At present, neither is likely as there just isn't enough time available to work on those features. Cheers, Antoine > > Thanks in advance! > > Regads, > Kaloyan Manev From kmanev073 at gmail.com Tue Apr 16 18:20:58 2019 From: kmanev073 at gmail.com (Kaloyan Manev) Date: Tue, 16 Apr 2019 20:20:58 +0300 Subject: [winswitch] Xpra Protocol Streaming Changes Or Video Message-ID: Hello guys, I've been reading that Xpra server is only sending data about the changes that happened on the screen therefore it should skip a lot of unnecessary packets. If that's true how does it utilize the h.264, VP8 and VP9? They are all video codecs. I a bit confused because the encoders' main idea is to encode one full frame at the beginning and then keep encoding only what has to change in order to get to the next frame. I will be grateful if someone could explain this. Thanks in advance! Regards, Kalyan Manev From antoine at nagafix.co.uk Tue Apr 16 18:42:34 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 17 Apr 2019 00:42:34 +0700 Subject: [winswitch] Xpra Protocol Streaming Changes Or Video In-Reply-To: References: Message-ID: <6a23c01c-7991-fd6c-939b-374b964db0a7@nagafix.co.uk> On 17/04/2019 00:20, Kaloyan Manev via shifter-users wrote: > Hello guys, > > I've been reading that Xpra server is only sending data about the changes > that happened on the screen therefore it should skip a lot of unnecessary > packets. It does. > If that's true how does it utilize the h.264, VP8 and VP9? They > are all video codecs. Yes. Xpra uses all sorts of tricks to figure out when it is appropriate to use a video codec rather than a picture codec. > I a bit confused because the encoders' main idea is to encode one full > frame at the beginning and then keep encoding only what has to change in > order to get to the next frame. The problem is that an application may update many different areas of a window, and not all of those areas are suitable for video compression. So in the end, your screen updates will arrive as a mixture of all sorts of codecs. The best way to visualize this is to enable paint debugging, see XPRA_OPENGL_PAINT_BOX=1 in this ticket: https://xpra.org/trac/ticket/760 Cheers, Antoine > I will be grateful if someone could explain this. Thanks in advance! > > Regards, > > Kalyan Manev > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From Benjamin.Sferrazza at skyworksinc.com Wed Apr 17 23:23:08 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Wed, 17 Apr 2019 22:23:08 +0000 Subject: [winswitch] [EXTERNAL] Re: xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <433389a3594e078f225f3eb508e814b7fb07cb90.camel@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> <1555079581028.25863@skyworksinc.com> ,<700d384d-b640-cc45-1944-90f71e900b98@nagafix.co.uk> <1555366903559.71595@skyworksinc.com> <433389a3594e078f225f3eb508e814b7fb07cb90.camel@skyworksinc.com> Message-ID: <93ffbd97a7184d438f51129c63f992653f6211c1.camel@skyworksinc.com> On Mon, 2019-04-15 at 23:57 +0000, Ben Sferrazza via shifter-users wrote: > > On 12/04/2019 21:33, Ben Sferrazza via shifter-users wrote: > > > On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: > > > > > I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The > > > > > client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works > > > > > well, but I can't get 'xpra start-desktop' to work. It merely > > > > > shows a black screen. > > > > xpra start-desktop on its own will only start an empty full- > > > > window > > > > session, you need to start a window manager or some other > > > > application to > > > > interact with, ie for testing: > > > > xpra start-desktop --start=xterm > > > > Then you can start a window manager or something else from the > > > > xterm > > > I'm sorry, I should have mentioned I used --start=gnome-session. > > Well, there is your problem. > > Try a different window manager, or as per above just an xterm, and > > you > > will find that things work just fine. > > gnome is known to be problematic and may not work without an > > accelerated > > X11 server. Using xfce4 instead of gnome seems to work well. I'm satisfied with that as a solution. The only issue is that I'd like to run 'xpra start- desktop' as a service so that I may be able to remotely login into that session even if my computer were to unexpectedly restart while I'm out of the office. It would also allow me to use the same work PC that Xpra is run on and attach to it locally, treating that Xpra desktop as my main session whether local or remote. I figured this might be a common use case, but didn't find any info regarding using it as a service, much as one would do with a headless Linux VNC setup. I tried following much of the ArchLinux wiki, without success. This is still being run on Ubuntu 18.10. Here's an xpra at .service I created under /etc/systemd/system: [Unit] Description=Xpra Remote Desktop After=syslog.target network.target nfs-home.mount [Service] Type=simple User=%i EnvironmentFile=/etc/conf.d/xpra ExecStart=/usr/bin/xpra --no-daemon start-desktop --start=startxfce4 ${%i} [Install] WantedBy=multi-user.target And the /etc/conf.d/xpra: myusername=:2 I enabled the service by using 'systemctl enable xpra at myusername.service' > From Benjamin.Sferrazza at skyworksinc.com Thu Apr 18 00:25:24 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Wed, 17 Apr 2019 23:25:24 +0000 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <93ffbd97a7184d438f51129c63f992653f6211c1.camel@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> <1555079581028.25863@skyworksinc.com> ,<700d384d-b640-cc45-1944-90f71e900b98@nagafix.co.uk> <1555366903559.71595@skyworksinc.com> <433389a3594e078f225f3eb508e814b7fb07cb90.camel@skyworksinc.com> <93ffbd97a7184d438f51129c63f992653f6211c1.camel@skyworksinc.com> Message-ID: <4146462b659d1a7978088643283e237d3d65226e.camel@skyworksinc.com> On Wed, 2019-04-17 at 15:23 -0700, Ben Sferrazza wrote: On Mon, 2019-04-15 at 23:57 +0000, Ben Sferrazza via shifter-users wrote: On 12/04/2019 21:33, Ben Sferrazza via shifter-users wrote: On 12/04/2019 05:47, Ben Sferrazza via shifter-users wrote: I'm running Xpra 2.5 from the Xpra repo on Ubuntu 18.10. The client is Xpra 3.0 on Windows 10. Using 'xpra shadow' works well, but I can't get 'xpra start-desktop' to work. It merely shows a black screen. xpra start-desktop on its own will only start an empty full- window session, you need to start a window manager or some other application to interact with, ie for testing: xpra start-desktop --start=xterm Then you can start a window manager or something else from the xterm I'm sorry, I should have mentioned I used --start=gnome-session. Well, there is your problem. Try a different window manager, or as per above just an xterm, and you will find that things work just fine. gnome is known to be problematic and may not work without an accelerated X11 server. Using xfce4 instead of gnome seems to work well. I'm satisfied with that as a solution. The only issue is that I'd like to run 'xpra start- desktop' as a service so that I may be able to remotely login into that session even if my computer were to unexpectedly restart while I'm out of the office. It would also allow me to use the same work PC that Xpra is run on and attach to it locally, treating that Xpra desktop as my main session whether local or remote. I figured this might be a common use case, but didn't find any info regarding using it as a service, much as one would do with a headless Linux VNC setup. I tried following much of the ArchLinux wiki, without success. This is still being run on Ubuntu 18.10. Here's an xpra at .service I created under /etc/systemd/system: [Unit] Description=Xpra Remote Desktop After=syslog.target network.target nfs-home.mount [Service] Type=simple User=%i EnvironmentFile=/etc/conf.d/xpra ExecStart=/usr/bin/xpra --no-daemon start-desktop --start=startxfce4 ${%i} [Install] WantedBy=multi-user.target And the /etc/conf.d/xpra: myusername=:2 I enabled the service by using 'systemctl enable xpra at myusername.service' Still not working, but I do see the xpra process running after logging into my Linux box locally. Just cannot attach to it. Reports that it doesn't detect any live xpra sessions. myuserna+ 2554 1.4 0.6 466784 110644 ? SLs 16:15 0:04 /usr/bin/python2 /usr/bin/xpra --no-daemon start-desktop --start=startxfce4 :2 myuserna+ 2794 1.1 1.2 1104644 197308 ? Ssl 16:15 0:03 /usr/lib/xorg/Xorg-for-Xpra-:2 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/myusername/.Xauthority -logfile /tmp/Xorg.:2.log -configdir /run/user/10345/xpra/xorg.conf.d/2554 -config /etc/xpra/xorg.conf -depth 24 :2 The Xorg.:2.log shows a couple of errors that occurred when it started as a service. [ 51.003] (EE) Unable to locate/open config directory: "/run/user/10345/xpra/xorg.conf.d/2554" [ 51.487] (EE) systemd-logind: failed to get session: PID 2794 does not belong to any known session Thanks for any advice on how to debug this issue. Ben From antoine at nagafix.co.uk Thu Apr 18 02:33:45 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 18 Apr 2019 08:33:45 +0700 Subject: [winswitch] xpra shadow works, but start-desktop just shows a black screen In-Reply-To: <4146462b659d1a7978088643283e237d3d65226e.camel@skyworksinc.com> References: <1555022871966.40410@skyworksinc.com> <3a38c33d-d348-43be-cc3d-afe43cdb741a@nagafix.co.uk> <1555079581028.25863@skyworksinc.com> <700d384d-b640-cc45-1944-90f71e900b98@nagafix.co.uk> <1555366903559.71595@skyworksinc.com> <433389a3594e078f225f3eb508e814b7fb07cb90.camel@skyworksinc.com> <93ffbd97a7184d438f51129c63f992653f6211c1.camel@skyworksinc.com> <4146462b659d1a7978088643283e237d3d65226e.camel@skyworksinc.com> Message-ID: <33720bab-776b-4478-c3d8-d95f66c910f0@nagafix.co.uk> Your MUA has completely mashed this email thread. Can you make it not do that? Or switch to something better? > Here's an xpra at .service I created under /etc/systemd/system: > > [Unit] > Description=Xpra Remote Desktop > After=syslog.target network.target nfs-home.mount > > [Service] > Type=simple > User=%i > EnvironmentFile=/etc/conf.d/xpra > ExecStart=/usr/bin/xpra --no-daemon start-desktop --start=startxfce4 > ${%i} > > [Install] > WantedBy=multi-user.target > > And the /etc/conf.d/xpra: > > myusername=:2 > > I enabled the service by using 'systemctl enable > xpra at myusername.service' > > Still not working, but I do see the xpra process running after logging into my Linux box locally. Just cannot attach to it. Reports that it doesn't detect any live xpra sessions. > > myuserna+ 2554 1.4 0.6 466784 110644 ? SLs 16:15 0:04 /usr/bin/python2 /usr/bin/xpra --no-daemon start-desktop --start=startxfce4 :2 > myuserna+ 2794 1.1 1.2 1104644 197308 ? Ssl 16:15 0:03 /usr/lib/xorg/Xorg-for-Xpra-:2 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/myusername/.Xauthority -logfile /tmp/Xorg.:2.log -configdir /run/user/10345/xpra/xorg.conf.d/2554 -config /etc/xpra/xorg.conf -depth 24 :2 > > The Xorg.:2.log shows a couple of errors that occurred when it started as a service. > > > [ 51.003] (EE) Unable to locate/open config directory: "/run/user/10345/xpra/xorg.conf.d/2554" That's harmless. > [ 51.487] (EE) systemd-logind: failed to get session: PID 2794 does not belong to any known session Probably harmless, you can get rid of this problem by starting via the system-wide proxy server. --start-via-proxy=yes > Thanks for any advice on how to debug this issue. You should post the xpra server log output found in the journal. If the process is running by can't be found with "xpra list" then maybe its sockets were not created, or not in the right place. You could always try to bind it to a TCP port and see if you can connect to it that way. Cheers, Antoine > > > Ben From Benjamin.Sferrazza at skyworksinc.com Fri Apr 19 21:19:45 2019 From: Benjamin.Sferrazza at skyworksinc.com (Ben Sferrazza) Date: Fri, 19 Apr 2019 20:19:45 +0000 Subject: [winswitch] Xpra as a systemd service Message-ID: starting a new email thread, since the old one's subject was invalid and the use of OWA was messing up the quoting. Sorry for the trouble. Background: * I have one desktop PC at work with Ubuntu on it and a Windows laptop * /home is an NFS mount and uses NIS * I'd like to have the desktop start an Xpra desktop as a systemd service so that I can both access it from the same desktop and from the laptop when working from home * Ideally it would auto-connect to the existing desktop in the event of power failure or planned maintenance where my desktop PC is powered down when I'm not in the office * I've tried following the ArchLinux wiki on setting Xpra up as a service without success Here's my /etc/systemd/system/xpra at .service file: [Unit] Description=Xpra Remote Desktop After=syslog.target network.target nfs-home.mount gdm.service [Service] Type=simple User=%i EnvironmentFile=/etc/conf.d/xpra Environment="XDG_RUNTIME_DIR=~/.local" ExecStart=/usr/bin/xpra --no-daemon --bind-tcp=0.0.0.0:10000 --socket- dir=~/.xpra start-desktop --start=startxfce4 ${%i} [Install] WantedBy=multi-user.target I enabled the service using 'sudo systemctl enable xpra at myusername.service' The results are as follows: * The Xpra process is running, as shown by 'ps aux | grep xpra' * I cannot simply run 'xpra attach' on the same desktop PC. It reports that no live Xpra sessions are running * I CAN attach to it when explicitly specifying the tcp port by 'xpra attach tcp:localhost:10000' * I cannot attach to it from the Windows laptop Here's the relevant logging from syslog. It complains of XDG_RUNTIME_DIR not being set despite trying to do so within the system unit. Apparently that's not working properly. The ownership of /run is root:root with 755 permissions. Not sure if that needs to be changed for xpra to create the socket there, though using '--socket- dir=~/.xpra' does allow it to create it under my home directory. Apr 19 12:57:00 l-myusername xpra[2562]: 2019-04-19 12:57:00,179 Warning: failed to create socket directory '/run/user/10345/xpra' Apr 19 12:57:00 l-myusername xpra[2562]: 2019-04-19 12:57:00,179 [Errno 2] No such file or directory: '/run/user/10345/xpra' Apr 19 12:57:00 l-myusername xpra[2562]: 2019-04-19 12:57:00,301 Warning: some of the sockets are in an unknown state: Apr 19 12:57:00 l-myusername xpra[2562]: 2019-04-19 12:57:00,301 /home/myusername/.xpra/l-myusername.avnera.com-2 Apr 19 12:57:00 l-myusername xpra[2562]: 2019-04-19 12:57:00,301 please wait as we allow the socket probing to timeout Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,346 created unix domain socket: /home/myusername/.xpra/l- myusername.avnera.com-2 Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,346 Warning: cannot create socket '/run/user/10345/xpra/l- myusername.avnera.com-2': Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,346 [Errno 2] No such file or directory Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,347 ($XDG_RUNTIME_DIR has not been created?) Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,347 cannot create group socket '/run/xpra/l-myusername.avnera.com-2' Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,347 [Errno 13] Permission denied Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,355 user 'myusername' is a member of groups: adm, cdrom, sudo, dip, plugdev, lpadmin, sambashare, xpra, eng Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,355 permissions on directory /run/xpra: 0775 Apr 19 12:57:06 l-myusername xpra[2562]: 2019-04-19 12:57:06,355 ownership root:xpra Apr 19 12:57:07 l-myusername xpra[2562]: 2019-04-19 12:57:07,038 pointer device emulation using XTest Apr 19 12:57:07 l-myusername xpra[2562]: 2019-04-19 12:57:07,112 serving html content from: /usr/share/xpra/www Apr 19 12:57:10 l-myusername xpra[2562]: 2019-04-19 12:57:10,518 OpenGL is supported on display ':2' Apr 19 12:57:10 l-myusername xpra[2562]: 2019-04-19 12:57:10,519 using 'llvmpipe (LLVM 7.0, 256 bits)' renderer Apr 19 12:57:10 l-myusername xpra[2562]: 2019-04-19 12:57:10,860 D-Bus notification forwarding is available Apr 19 12:57:11 l-myusername xpra[2562]: 2019-04-19 12:57:11,989 Warning: webcam forwarding is disabled Apr 19 12:57:11 l-myusername xpra[2562]: 2019-04-19 12:57:11,989 the virtual video directory '/sys/devices/virtual/video4linux' was not found Apr 19 12:57:11 l-myusername xpra[2562]: 2019-04-19 12:57:11,989 make sure that the 'v4l2loopback' kernel module is installed and loaded Apr 19 12:57:11 l-myusername xpra[2562]: 2019-04-19 12:57:11,989 found 0 virtual video devices for webcam forwarding Apr 19 12:57:12 l-myusername xpra[2562]: 2019-04-19 12:57:12,042 pulseaudio server started with pid 3213 Apr 19 12:57:12 l-myusername xpra[2562]: 2019-04-19 12:57:12,043 private server socket path: Apr 19 12:57:12 l-myusername xpra[2562]: 2019-04-19 12:57:12,043 '/home/myusername/.local/xpra/pulse-2/pulse/native' Apr 19 12:57:12 l-myusername xpra[2562]: W: [pulseaudio] pid.c: Stale PID file, overwriting. Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,274 GStreamer version 1.14.4 for Python 2.7.15 64-bit Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,705 xpra GTK2 X11 desktop version 2.5.1-r22431 64-bit Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,707 uid=10345 (myusername), gid=1001 (eng) Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,707 running with pid 2562 on Linux Ubuntu 18.10 cosmic Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,707 connected to X11 display :2 with 24 bit colors Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,708 :2.0 (2167x1084 mm - DPI: 96x95) Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,708 monitor 2 Apr 19 12:57:13 l-myusername xpra[2562]: 2019-04-19 12:57:13,919 xpra is ready. Apr 19 12:57:52 l-myusername xpra[2562]: 2019-04-19 12:57:52,520 printer forwarding enabled using postscript and pdf Apr 19 12:57:52 l-myusername xpra[2562]: /usr/bin/startxfce4: X server already running on display :2 Apr 19 12:57:53 l-myusername xpra[2562]: 2019-04-19 12:57:53,695 15.6GB of system memory Apr 19 12:57:53 l-myusername xpra[2562]: gpg-agent[4015]: WARNING: " --write-env-file" is an obsolete option - it has no effect Apr 19 12:57:54 l-myusername xpra[2562]: gpg-agent: a gpg-agent is already running - not starting a new one Apr 19 12:57:54 l-myusername xpra[2562]: sh: 1: /usr/bin/nvidia- settings: not found Apr 19 12:57:54 l-myusername xpra[2562]: exception: Failed to open /etc/mpd.conf: Permission denied Apr 19 12:57:55 l-myusername xpra[2562]: Indicator stickynotes already running. From tchollingsworth at gmail.com Sat Apr 20 03:49:48 2019 From: tchollingsworth at gmail.com (T.C. Hollingsworth) Date: Fri, 19 Apr 2019 19:49:48 -0700 Subject: [winswitch] Xpra as a systemd service In-Reply-To: References: Message-ID: On Fri, Apr 19, 2019, 6:52 PM Ben Sferrazza via shifter-users < shifter-users at lists.devloop.org.uk> wrote: > Here's the relevant logging from syslog. It complains of > XDG_RUNTIME_DIR not being set despite trying to do so within the system > unit. Apparently that's not working properly. > Add PAMName=login to your [Service] section. Your desktop will run in a full login session as it does locally instead of the minimal systemd environment. And /run/user/$UID will be created. > From ron.eggler at gmail.com Mon Apr 22 19:28:48 2019 From: ron.eggler at gmail.com (Ron Eggler) Date: Mon, 22 Apr 2019 11:28:48 -0700 Subject: [winswitch] get connection timedout: when connectinh from Windows Message-ID: Hi, I have xpra version xpra v0.15.8 on a headless Linux (Ubuntu 16.04.6 LTS) server an am attemting to connect from a Windows client (version 2.5.1) and it does not seem to connect, I get the following in the logs: $ tail -f /home/ron/.xpra/:9999.log 2019-04-22 09:48:32,364 New unix-domain connection received Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 535, in _process_hello auth_caps = self.verify_hello(proto, c) File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 625, in verify_hello authlog.warn("Warning: client expects a challenge but this connection is unauthenticated") NameError: global name 'authlog' is not defined 2019-04-22 09:48:42,366 connection timedout: Protocol(SocketConnection(/home/ron/.xpra/jpax-build07-9999)) 2019-04-22 09:54:43,123 New unix-domain connection received 2019-04-22 09:54:43,129 Connection lost 2019-04-22 11:21:41,075 New unix-domain connection received Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 535, in _process_hello auth_caps = self.verify_hello(proto, c) File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 625, in verify_hello authlog.warn("Warning: client expects a challenge but this connection is unauthenticated") NameError: global name 'authlog' is not defined 2019-04-22 11:21:51,083 connection timedout: Protocol(SocketConnection(/home/ron/.xpra/jpax-build07-9999)) Why is trhis and how can I get around it? Thanks From antoine at nagafix.co.uk Tue Apr 23 02:16:02 2019 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 23 Apr 2019 08:16:02 +0700 Subject: [winswitch] get connection timedout: when connectinh from Windows In-Reply-To: References: Message-ID: <639c25f0-0fc1-398e-6e93-d4146dc5ddb0@nagafix.co.uk> On 23/04/2019 01:28, Ron Eggler via shifter-users wrote: > Hi, > > I have xpra version xpra v0.15.8 on a headless Linux (Ubuntu 16.04.6 LTS) > server an am attemting to connect from a Windows client (version 2.5.1) and > it does not seem to connect, I get the following in the logs: > $ tail -f /home/ron/.xpra/:9999.log > 2019-04-22 09:48:32,364 New unix-domain connection received > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line > 535, in _process_hello > auth_caps = self.verify_hello(proto, c) > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line > 625, in verify_hello > authlog.warn("Warning: client expects a challenge but this connection > is unauthenticated") > NameError: global name 'authlog' is not defined > 2019-04-22 09:48:42,366 connection timedout: > Protocol(SocketConnection(/home/ron/.xpra/jpax-build07-9999)) > 2019-04-22 09:54:43,123 New unix-domain connection received > 2019-04-22 09:54:43,129 Connection lost > 2019-04-22 11:21:41,075 New unix-domain connection received > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line > 535, in _process_hello > auth_caps = self.verify_hello(proto, c) > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line > 625, in verify_hello > authlog.warn("Warning: client expects a challenge but this connection > is unauthenticated") > NameError: global name 'authlog' is not defined > 2019-04-22 11:21:51,083 connection timedout: > Protocol(SocketConnection(/home/ron/.xpra/jpax-build07-9999)) > > Why is trhis and how can I get around it? Those are bugs which have already been fixed many *years* ago. Your distributor is shipping a version with known bugs and serious security vulnerabilities. Make of that what you will. We have a whole wiki page documenting this sad state of affairs: https://xpra.org/trac/wiki/Packaging/DistributionPackages Just install the official packages from xpra.org and everything will work fine. Cheers, Antoine > > Thanks > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > From steve.mckuhr at gmail.com Tue Apr 30 21:54:07 2019 From: steve.mckuhr at gmail.com (Steve McKuhr) Date: Tue, 30 Apr 2019 13:54:07 -0700 Subject: [winswitch] gnome keyring / seahorse Message-ID: <0103e7ac372b7ce2c3d538450f6774b270e828dd.camel@gmail.com> With Linux (Fedora 29) for both client and server when I start Evolution or Chrome the passwords are not to be found i.e. Evolution is asking for password and web login forms normally auto-completed by Chrome are empty. I have tested with starting a desktop session and confirmed that Seahorse shows no passwords. Shadowing :0 works fine. I'm sure I'm missing something obvious but reading the man page and a fair amount of internet read provided no hint. -Steve