From antoine at nagafix.co.uk Fri Dec 1 01:35:36 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 1 Dec 2017 08:35:36 +0700 Subject: [winswitch] Question about Xpra, OpenGL, and Xming-Mesa In-Reply-To: References: Message-ID: <22d99820-e2a7-aae6-4b97-5fc3635f5443@nagafix.co.uk> On 01/12/17 01:11, Michael Segev via shifter-users wrote: > Hello, > > My situation is as follows: > > I'm currently on a Windows 10 machine that has Xpra, Xming-Mesa (Xming with > OpenGL support), and PuTTY installed. I am trying to run a GUI java app > that uses OpenGL on a remote Linux (Ubuntu 16.04) machine and have it > display back on my PC using Xpra. > > I can successfully run the application when I just use Xming-mesa. However, > when I add Xpra into the equation, the GUI java app fails to start and > throws this error: > > OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current > thread > > But if i shut down the Xpra server and just connect using Xming-mesa, the > application starts fine; so I'm somehow inclined to believe that there is > some conflict here involving Xpra and OpenGL. > > Any advice you could provide to fix this would be greatly appreciated. The easiest way is to add "+extension GLX" to your xvfb command line in /etc/xpra/conf.d/55_server_x11.conf This will be the default for Ubuntu 16.04 in the upcoming 2.2 release. This solution is not accelerated. For more options, including OpenGL acceleration see: https://xpra.org/trac/wiki/Usage/OpenGL Cheers Antoine > > Thank you. > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From michael.sgv at gmail.com Fri Dec 1 17:32:30 2017 From: michael.sgv at gmail.com (Michael Segev) Date: Fri, 1 Dec 2017 12:32:30 -0500 Subject: [winswitch] Question about Xpra, OpenGL, and Xming-Mesa In-Reply-To: <22d99820-e2a7-aae6-4b97-5fc3635f5443@nagafix.co.uk> References: <22d99820-e2a7-aae6-4b97-5fc3635f5443@nagafix.co.uk> Message-ID: Hi Antoine, Thank you for the prompt response. I added the "+extension GLX" to the command line, so now my command in the file looks like this: xvfb = Xvfb +extension GLX +extension Composite -screen 0 5760x2560x24+32 -dpi #96 -nolisten tcp -noreset -auth $XAUTHORITY Unfortunately, the application is still refusing to start and gives me the same "no OpenGL found in context" error. Yesterday I was digging around the Xpra site and I saw that there seems to be an issue with nvidia graphics cards and OpenGL ( https://xpra.org/trac/wiki/Xdummy). The graphics card for my local windows PC (which, in X terminology, I guess would be called the "server"?) is an Nvidia GeForce 960M, and I saw on the Xpra site that VirtualGL is a potential solution for this. I just spent the past 6 hours reading the documentation for VirtualGL on their site ( https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html), but the documentation was incredibly confusing. For instance, I could not for the life of my figure out this image: https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/vgltransport.png. Shouldn't the "application" be sitting in on the "client "side, since in X terminology the client side is the remote server where I'm running the application? And, following the X terminology, shouldn't I have to download VirtualGL for the "server" side--in this case, my local Windows PC? There was no "server" downloads on the OpenGL site for Windows PC's, only for "client" software which linked to a software called "Exceed", of what *I think *is a commercialized version of Xming? And in fact, on the latest download files for VirtualGL, the client software for Windows was completely gone--there was just a "VirtualGLUtils" package that seemed to just provide benchmarking tools. Terminology confusion aside, I tried installing VirtualGL for my remote Ubuntu 16.04 linux box (the "client"?) just because I had no idea what to do at this point, and then tried running the following (with Xming and X11 tunnelling enabled over Putty): "vglrun java -jar MyApp.jar" but then VirtualGL gave me the error: "[VGL] ERROR: Could not open display 0." So at this point, I'm, completely confused. Any help/clarification you could provide would be greatly appreciated; perhaps I should also ask over at the VirtualGL support thread and see if they say anything. Thank you for your time, Michael On Thu, Nov 30, 2017 at 8:35 PM, Antoine Martin via shifter-users < shifter-users at lists.devloop.org.uk> wrote: > On 01/12/17 01:11, Michael Segev via shifter-users wrote: > > Hello, > > > > My situation is as follows: > > > > I'm currently on a Windows 10 machine that has Xpra, Xming-Mesa (Xming > with > > OpenGL support), and PuTTY installed. I am trying to run a GUI java app > > that uses OpenGL on a remote Linux (Ubuntu 16.04) machine and have it > > display back on my PC using Xpra. > > > > I can successfully run the application when I just use Xming-mesa. > However, > > when I add Xpra into the equation, the GUI java app fails to start and > > throws this error: > > > > OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the > current > > thread > > > > But if i shut down the Xpra server and just connect using Xming-mesa, the > > application starts fine; so I'm somehow inclined to believe that there is > > some conflict here involving Xpra and OpenGL. > > > > Any advice you could provide to fix this would be greatly appreciated. > The easiest way is to add "+extension GLX" to your xvfb command line in > /etc/xpra/conf.d/55_server_x11.conf > This will be the default for Ubuntu 16.04 in the upcoming 2.2 release. > This solution is not accelerated. > > For more options, including OpenGL acceleration see: > https://xpra.org/trac/wiki/Usage/OpenGL > > Cheers > Antoine > > > > > Thank you. > > _______________________________________________ > > 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 Fri Dec 1 18:50:15 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 2 Dec 2017 01:50:15 +0700 Subject: [winswitch] Question about Xpra, OpenGL, and Xming-Mesa In-Reply-To: References: <22d99820-e2a7-aae6-4b97-5fc3635f5443@nagafix.co.uk> Message-ID: On 02/12/17 00:32, Michael Segev wrote: > Hi Antoine, > > Thank you for the prompt response. I added the "+extension GLX" to the > command line, so now my command in the file looks like this: > > xvfb = Xvfb +extension GLX +extension Composite -screen 0 > 5760x2560x24+32 -dpi #96 -nolisten tcp -noreset -auth $XAUTHORITY Looks OK. > Unfortunately, the application is still refusing to start and gives me > the same "no OpenGL found in context" error. Can you run simple test applications like "glxgears" or "glxinfo"? > Yesterday I was digging around the Xpra site and I saw that there seems > to be an issue with nvidia graphics cards and OpenGL > (https://xpra.org/trac/wiki/Xdummy). Not the graphics card itself, but the proprietary nvidia driver. glvnd is the future solution to this particular problem. (but I don't recommend you go down that route if you are struggling already) > The graphics card for my local > windows PC (which, in X terminology, I guess would be called the > "server"?) is an Nvidia GeForce 960M, and I saw on the Xpra site that > VirtualGL is a potential solution for this. I just spent the past 6 > hours reading the documentation for VirtualGL on their site? > (https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html), but > the documentation was incredibly confusing. For instance, I could not > for the life of my figure out this > image:?https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/vgltransport.png. > Shouldn't the "application" be sitting in on the "client "side, since in > X terminology the client side is the remote server where I'm running the > application? And, following the X terminology, shouldn't I have to > download VirtualGL for the "server" side--in this case, my local Windows > PC? There was no "server" downloads on the OpenGL site for Windows PC's, > only for "client" software which linked to a software called "Exceed", > of what /I think /is a commercialized?version of Xming? And in fact, on > the latest download files for VirtualGL, the client software for Windows > was completely gone--there was just a "VirtualGLUtils" package that > seemed to just provide benchmarking tools. VirtualGL is expected to run on your xpra server's display, on Linux. xpra does not use Xming or anything like it, it is a native application and all the OpenGL rendering will happen on the xpra server side. > Terminology confusion aside, I tried installing VirtualGL for my remote > Ubuntu 16.04 linux box (the "client"?) just because I had no idea what > to do at this point, and then tried running the following (with Xming > and X11 tunnelling enabled over Putty): > > "vglrun java -jar MyApp.jar" > > but then VirtualGL gave me the error: > > "[VGL] ERROR: Could not open display 0." VirtualGL delegates OpenGL calls to an existing accelerated X11 display. Looks like you don't have one running on :0, or you don't have access to it. If you have one, but it's not on :0, then you need to use the "-d" switch. If you don't have an X11 display running, then you might be able to remove the nvidia driver and then use software rendering. Or you can start one to be able to use VirtualGL with it. > So at this point, I'm, completely confused. Any help/clarification you > could provide would be greatly appreciated; perhaps I should also ask > over at the VirtualGL support thread and see if they say anything. Their answer is likely to be what I said above, or "RTFM". Cheers Antoine > > Thank you for your time, > Michael > > On Thu, Nov 30, 2017 at 8:35 PM, Antoine Martin via shifter-users > > wrote: > > On 01/12/17 01:11, Michael Segev via shifter-users wrote: > > Hello, > > > > My situation is as follows: > > > > I'm currently on a Windows 10 machine that has Xpra, Xming-Mesa (Xming with > > OpenGL support), and PuTTY installed. I am trying to run a GUI java app > > that uses OpenGL on a remote Linux (Ubuntu 16.04) machine and have it > > display back on my PC using Xpra. > > > > I can successfully run the application when I just use Xming-mesa. However, > > when I add Xpra into the equation, the GUI java app fails to start and > > throws this error: > > > >? OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current > > thread > > > > But if i shut down the Xpra server and just connect using Xming-mesa, the > > application starts fine; so I'm somehow inclined to believe that there is > > some conflict here involving Xpra and OpenGL. > > > > Any advice you could provide to fix this would be greatly appreciated. > The easiest way is to add "+extension GLX" to your xvfb command line in > /etc/xpra/conf.d/55_server_x11.conf > This will be the default for Ubuntu 16.04 in the upcoming 2.2 release. > This solution is not accelerated. > > For more options, including OpenGL acceleration see: > https://xpra.org/trac/wiki/Usage/OpenGL > > > Cheers > Antoine > > > > > Thank you. > > _______________________________________________ > > 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 Dec 2 09:52:11 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 2 Dec 2017 16:52:11 +0700 Subject: [winswitch] Question about Xpra, OpenGL, and Xming-Mesa In-Reply-To: References: <22d99820-e2a7-aae6-4b97-5fc3635f5443@nagafix.co.uk> Message-ID: <83734cbb-45f9-1494-8883-a2e969df8923@nagafix.co.uk> Please always keep the mailing list CCed. On 02/12/17 03:12, Michael Segev wrote: > Hi Antoine, > > Thanks again for the response, I really appreciate it.? > > Can you run simple test applications like "glxgears" or "glxinfo"? > > > Yes, I can run both with the Xpra server running no problems. I can send > you over a pastebin of glxinfo output if you'd like. > > VirtualGL delegates OpenGL calls to an existing accelerated X11 display. > Looks like you don't have one running on :0, or you don't have > access to it. > If you have one, but it's not on :0, then you need to use the "-d" > switch. > If you don't have an X11 display running, then you might be able to > remove the nvidia driver and then use software rendering. Or you can > start one to be able to use VirtualGL with it. > > > I do have an accelerated X11 display running on my local windows machine > on :0 (through Xming), and it's set in Putty so that the server should > be forwarding to use it. As I said previously, xpra uses a native client that does not need or use any client-side X11 server at all. Do not use putty's X11 forwarding either. The fact that you are even mentioning it makes me think that you may be misunderstanding how this is supposed to work. I'll assume that you've tested your application when running against a regular X11 server on your Linux system. If that's working fine but refuses to work when running against Xvfb then you should consider switching to Xdummy (see wiki for details) as this option is no different from a regular X11 server. Cheers Antoine > > On Fri, Dec 1, 2017 at 1:50 PM, Antoine Martin > wrote: > > On 02/12/17 00:32, Michael Segev wrote: > > Hi Antoine, > > > > Thank you for the prompt response. I added the "+extension GLX" to the > > command line, so now my command in the file looks like this: > > > > xvfb = Xvfb +extension GLX +extension Composite -screen 0 > > 5760x2560x24+32 -dpi #96 -nolisten tcp -noreset -auth $XAUTHORITY > Looks OK. > > > Unfortunately, the application is still refusing to start and gives me > > the same "no OpenGL found in context" error. > Can you run simple test applications like "glxgears" or "glxinfo"? > > > Yesterday I was digging around the Xpra site and I saw that there seems > > to be an issue with nvidia graphics cards and OpenGL > > (https://xpra.org/trac/wiki/Xdummy ). > Not the graphics card itself, but the proprietary nvidia driver. > glvnd is the future solution to this particular problem. (but I don't > recommend you go down that route if you are struggling already) > > > The graphics card for my local > > windows PC (which, in X terminology, I guess would be called the > > "server"?) is an Nvidia GeForce 960M, and I saw on the Xpra site that > > VirtualGL is a potential solution for this. I just spent the past 6 > > hours reading the documentation for VirtualGL on their site? > > (https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html > ), but > > the documentation was incredibly confusing. For instance, I could not > > for the life of my figure out this > > image:?https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/vgltransport.png . > > Shouldn't the "application" be sitting in on the "client "side, since in > > X terminology the client side is the remote server where I'm running the > > application? And, following the X terminology, shouldn't I have to > > download VirtualGL for the "server" side--in this case, my local Windows > > PC? There was no "server" downloads on the OpenGL site for Windows PC's, > > only for "client" software which linked to a software called "Exceed", > > of what /I think /is a commercialized?version of Xming? And in > fact, on > > the latest download files for VirtualGL, the client software for Windows > > was completely gone--there was just a "VirtualGLUtils" package that > > seemed to just provide benchmarking tools. > VirtualGL is expected to run on your xpra server's display, on Linux. > xpra does not use Xming or anything like it, it is a native application > and all the OpenGL rendering will happen on the xpra server side. > > > Terminology confusion aside, I tried installing VirtualGL for my remote > > Ubuntu 16.04 linux box (the "client"?) just because I had no idea what > > to do at this point, and then tried running the following (with Xming > > and X11 tunnelling enabled over Putty): > > > > "vglrun java -jar MyApp.jar" > > > > but then VirtualGL gave me the error: > > > > "[VGL] ERROR: Could not open display 0." > VirtualGL delegates OpenGL calls to an existing accelerated X11 display. > Looks like you don't have one running on :0, or you don't have > access to it. > If you have one, but it's not on :0, then you need to use the "-d" > switch. > If you don't have an X11 display running, then you might be able to > remove the nvidia driver and then use software rendering. Or you can > start one to be able to use VirtualGL with it. > > > So at this point, I'm, completely confused. Any help/clarification you > > could provide would be greatly appreciated; perhaps I should also ask > > over at the VirtualGL support thread and see if they say anything. > Their answer is likely to be what I said above, or "RTFM". > > Cheers > Antoine > > > > > Thank you for your time, > > Michael > > > > On Thu, Nov 30, 2017 at 8:35 PM, Antoine Martin via shifter-users > > > > >> wrote: > > > >? ? ?On 01/12/17 01:11, Michael Segev via shifter-users wrote: > >? ? ?> Hello, > >? ? ?> > >? ? ?> My situation is as follows: > >? ? ?> > >? ? ?> I'm currently on a Windows 10 machine that has Xpra, > Xming-Mesa (Xming with > >? ? ?> OpenGL support), and PuTTY installed. I am trying to run a > GUI java app > >? ? ?> that uses OpenGL on a remote Linux (Ubuntu 16.04) machine > and have it > >? ? ?> display back on my PC using Xpra. > >? ? ?> > >? ? ?> I can successfully run the application when I just use > Xming-mesa. However, > >? ? ?> when I add Xpra into the equation, the GUI java app fails to > start and > >? ? ?> throws this error: > >? ? ?> > >? ? ?>? OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found > in the current > >? ? ?> thread > >? ? ?> > >? ? ?> But if i shut down the Xpra server and just connect using > Xming-mesa, the > >? ? ?> application starts fine; so I'm somehow inclined to believe > that there is > >? ? ?> some conflict here involving Xpra and OpenGL. > >? ? ?> > >? ? ?> Any advice you could provide to fix this would be greatly > appreciated. > >? ? ?The easiest way is to add "+extension GLX" to your xvfb > command line in > >? ? ?/etc/xpra/conf.d/55_server_x11.conf > >? ? ?This will be the default for Ubuntu 16.04 in the upcoming 2.2 > release. > >? ? ?This solution is not accelerated. > > > >? ? ?For more options, including OpenGL acceleration see: > >? ? ?https://xpra.org/trac/wiki/Usage/OpenGL > > >? ? ? > > > > >? ? ?Cheers > >? ? ?Antoine > > > >? ? ?> > >? ? ?> Thank you. > >? ? ?> _______________________________________________ > >? ? ?> 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 mailinglist__shifter-users at compeuphoria.com Sat Dec 9 18:31:23 2017 From: mailinglist__shifter-users at compeuphoria.com (WireRydr) Date: Sat, 09 Dec 2017 13:31:23 -0500 Subject: [winswitch] client failed to provide any keycodes (XPRA client win10 2.2-r17577 against XPRA server 2.2-0.20171206r17578.fc27) Message-ID: <94c4f5b758a290f2ca758b906fab9e92@compeuphoria.com> Hello all; I've posted this as a question to the mailing-list instead of as a bug-report because I cannot rule out the possibility of mis-configuration. However, given that this problem doesn't happen with an older client, I suspect it's a regression. Operating Environment --------------------- Host OS: Fedora 27 (x86_64) XPRA Server: 2.2-0.20171206r17578.fc27 XPRA Client: Python/Gtk2 Microsoft Windows 10 aero client version 2.2-r17577 64-bit I've pasted two logging outputs below: 1) When I attempt to connect to a running XPRA server with a Win10 client 2.2-r17577, and 2) When I connect to the same XPRA server with a Win10 client 2.2-r17538. In the first attempt the resulting child xterm doesn't respond properly to keyboard input, and the server log includes an error and traceback. In the second attempt (same server but older client), the xterm responds properly and there's no server error/traceback. Any advice/guidance you can provide to assist with better troubleshooting this would be greatly appreciated. Thanks! SERVER LOG WITH CLIENT 2.2-r17577 --------------------------------- 2017-12-08 15:52:31,479 wrote pid 9938 to '/run/user/1000/xpra.pid' Failed to rename log file "/run/user/1000/xpra/Xorg.S9938.log" to "/run/user/1000/xpra/Xorg.S9938.log": No such file or directory X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: 4.12.9-300.fc26.x86_64 Current Operating System: Linux studio-f27.example.com 4.13.16-302.fc27.x86_64 #1 SMP Thu Nov 30 15:33:36 UTC 2017 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.16-302.fc27.x86_64 root=UUID=ef51d839-3eed-4629-a7d2-95d56065e1e7 ro rhgb quiet LANG=en_CA.UTF-8 systemd.legacy_systemd_cgroup_controller=1 systemd.unified_cgroup_hierarchy=0 Build Date: 12 October 2017 07:35:27PM Build ID: xorg-x11-server 1.19.5-1.fc27 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: "/run/user/1000/xpra/Xorg.S9938.log", Time: Fri Dec 8 15:52:31 2017 (++) Using config file: "/etc/xpra/xorg-uinput.conf" (++) Using config directory: "/run/user/1000/xpra/xorg.conf.d/9938" (==) Using system config directory "/usr/share/X11/xorg.conf.d" 2017-12-08 15:52:34,020 cannot access uinput: [Errno 19] Failed to open the uinput device: No such device 2017-12-08 15:52:34,238 pointer device emulation using XTest 2017-12-08 15:52:34,538 serving html content from: /usr/share/xpra/www 2017-12-08 15:52:34,675 GStreamer version 1.12.3 for Python 2.7.14 64-bit 2017-12-08 15:52:34,680 D-Bus notification forwarding is available 2017-12-08 15:52:34,682 Warning: no local sockets defined, 2017-12-08 15:52:34,682 disabling printer forwarding 2017-12-08 15:52:34,682 xpra X11 version 2.2-r17577 64-bit 2017-12-08 15:52:34,683 uid=1000 (someuser), gid=1000 (someuser) 2017-12-08 15:52:34,683 running with pid 9938 on Linux Fedora 27 Twenty Seven 2017-12-08 15:52:34,683 connected to X11 display :0 with 24 bit colors 2017-12-08 15:52:34,765 xpra is ready. 2017-12-08 15:52:34,783 2.0GB of system memory 2017-12-08 15:53:25,411 New tcp connection received from 192.168.240.120:59339 on studio-f27.example.com:14500 2017-12-08 15:53:25,414 Authentication required by allow authenticator module 2017-12-08 15:53:25,415 sending challenge for username 'someuser' using hmac+sha512 digest 2017-12-08 15:53:25,446 Handshake complete; enabling connection 2017-12-08 15:53:25,455 Python/Gtk2 Microsoft Windows 10 aero client version 2.2-r17577 64-bit 2017-12-08 15:53:25,455 connected from 'einstein' as 'someuser' 2017-12-08 15:53:25,455 automatic picture encoding enabled, also available: 2017-12-08 15:53:25,455 h264, vp9, vp8, png, webp, rgb24, jpeg, rgb32 2017-12-08 15:53:25,456 client root window size is 3840x1200 with 1 display: 2017-12-08 15:53:25,461 Default (1016x317 mm - DPI: 96x96) 2017-12-08 15:53:25,461 DISPLAY1 1920x1200 at 1920x0 (518x324 mm - DPI: 94x94) workarea: 1920x1200 2017-12-08 15:53:25,461 DISPLAY2 1920x1080 at 0x120 (531x298 mm - DPI: 91x92) workarea: 1920x1080 2017-12-08 15:53:25,577 server virtual display now set to 3840x1200 2017-12-08 15:53:25,578 setting key repeat rate from client: 500ms delay / 33ms interval 2017-12-08 15:53:25,579 setting keyboard layout to 'us' 2017-12-08 15:53:25,594 Error setting X11 keyboard modifier map Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xpra/x11/server_keyboard_config.py", line 292, in set_keymap assert has_keycodes, "client failed to provide any keycodes!" AssertionError: client failed to provide any keycodes! 2017-12-08 15:53:25,602 started command 'xterm' with pid 9992 2017-12-08 15:53:25,603 DPI set to 96 x 96 xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1" 2017-12-08 15:53:25,993 sound source pipeline warning: Failed to connect: Connection refused 2017-12-08 15:53:25,993 sound source pulsesrc.c(1015) 2017-12-08 15:53:25,993 sound source gst_pulsesrc_open () 2017-12-08 15:53:25,993 sound source /GstPulseSrc 2017-12-08 15:53:25,993 sound source src-actual-src-puls ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not open audio device for playback. Additional debug info: gstalsasink.c(865): gst_alsasink_open (): /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Playback open error on device 'default': No such file or directory 2017-12-08 15:53:26,495 sound source using audio codec opus SERVER LOG WITH CLIENT 2.2-r17538 --------------------------------- 2017-12-08 20:06:33,926 wrote pid 10292 to '/run/user/1000/xpra.pid' Failed to rename log file "/run/user/1000/xpra/Xorg.S10292.log" to "/run/user/1000/xpra/Xorg.S10292.log": No such file or directory X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: 4.12.9-300.fc26.x86_64 Current Operating System: Linux studio-f27.example.com 4.13.16-302.fc27.x86_64 #1 SMP Thu Nov 30 15:33:36 UTC 2017 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.16-302.fc27.x86_64 root=UUID=ef51d839-3eed-4629-a7d2-95d56065e1e7 ro rhgb quiet LANG=en_CA.UTF-8 systemd.legacy_systemd_cgroup_controller=1 systemd.unified_cgroup_hierarchy=0 Build Date: 12 October 2017 07:35:27PM Build ID: xorg-x11-server 1.19.5-1.fc27 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: "/run/user/1000/xpra/Xorg.S10292.log", Time: Fri Dec 8 20:06:33 2017 (++) Using config file: "/etc/xpra/xorg-uinput.conf" (++) Using config directory: "/run/user/1000/xpra/xorg.conf.d/10292" (==) Using system config directory "/usr/share/X11/xorg.conf.d" 2017-12-08 20:06:37,190 cannot access uinput: [Errno 19] Failed to open the uinput device: No such device 2017-12-08 20:06:37,403 pointer device emulation using XTest 2017-12-08 20:06:37,752 serving html content from: /usr/share/xpra/www 2017-12-08 20:06:37,878 GStreamer version 1.12.3 for Python 2.7.14 64-bit 2017-12-08 20:06:37,880 D-Bus notification forwarding is available 2017-12-08 20:06:37,881 Warning: no local sockets defined, 2017-12-08 20:06:37,881 disabling printer forwarding 2017-12-08 20:06:37,881 xpra X11 version 2.2-r17577 64-bit 2017-12-08 20:06:37,881 uid=1000 (someuser), gid=1000 (someuser) 2017-12-08 20:06:37,881 running with pid 10292 on Linux Fedora 27 Twenty Seven 2017-12-08 20:06:37,882 connected to X11 display :0 with 24 bit colors 2017-12-08 20:06:37,980 xpra is ready. 2017-12-08 20:06:37,982 2.0GB of system memory 2017-12-08 20:06:50,508 New tcp connection received from 192.168.240.120:60938 on studio-f27.example.com:14500 2017-12-08 20:06:50,510 Authentication required by allow authenticator module 2017-12-08 20:06:50,510 sending challenge for username 'someuser' using hmac+sha512 digest 2017-12-08 20:06:50,544 Handshake complete; enabling connection 2017-12-08 20:06:50,552 Python/Gtk2 Microsoft Windows 10 aero client version 2.2-r17538 64-bit 2017-12-08 20:06:50,552 connected from 'einstein' as 'someuser' - 'someuser' 2017-12-08 20:06:50,553 automatic picture encoding enabled, also available: 2017-12-08 20:06:50,553 h264, vp9, vp8, png, webp, rgb24, jpeg, rgb32 2017-12-08 20:06:50,554 client root window size is 3840x1200 with 1 display: 2017-12-08 20:06:50,554 Default (1016x317 mm - DPI: 96x96) 2017-12-08 20:06:50,554 DISPLAY1 1920x1200 at 1920x0 (518x324 mm - DPI: 94x94) workarea: 1920x1200 2017-12-08 20:06:50,554 DISPLAY2 1920x1080 at 0x120 (531x298 mm - DPI: 91x92) workarea: 1920x1080 2017-12-08 20:06:50,648 server virtual display now set to 3840x1200 2017-12-08 20:06:50,651 setting key repeat rate from client: 500ms delay / 33ms interval 2017-12-08 20:06:50,653 setting keyboard layout to 'us' 2017-12-08 20:06:50,687 started command 'xterm' with pid 10345 2017-12-08 20:06:50,689 DPI set to 96 x 96 xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1" 2017-12-08 20:06:51,052 sound source pipeline warning: Failed to connect: Connection refused 2017-12-08 20:06:51,053 sound source pulsesrc.c(1015) 2017-12-08 20:06:51,053 sound source gst_pulsesrc_open () 2017-12-08 20:06:51,053 sound source /GstPulseSrc 2017-12-08 20:06:51,053 sound source src-actual-src-puls ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not open audio device for playback. Additional debug info: gstalsasink.c(865): gst_alsasink_open (): /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Playback open error on device 'default': No such file or directory 2017-12-08 20:06:51,555 sound source using audio codec opus From antoine at nagafix.co.uk Sun Dec 10 08:13:50 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 10 Dec 2017 15:13:50 +0700 Subject: [winswitch] client failed to provide any keycodes (XPRA client win10 2.2-r17577 against XPRA server 2.2-0.20171206r17578.fc27) In-Reply-To: <94c4f5b758a290f2ca758b906fab9e92@compeuphoria.com> References: <94c4f5b758a290f2ca758b906fab9e92@compeuphoria.com> Message-ID: <7f4363db-8ffb-02fd-2845-bbb87e15635e@nagafix.co.uk> On 10/12/17 01:31, WireRydr via shifter-users wrote: > Hello all; > > I've posted this as a question to the mailing-list instead of as a > bug-report because I cannot rule out the possibility of > mis-configuration.? However, given that this problem doesn't happen with > an older client, I suspect it's a regression. It is. > Operating Environment > --------------------- > ? Host OS:????? Fedora 27 (x86_64) > ? XPRA Server:? 2.2-0.20171206r17578.fc27 > ? XPRA Client:? Python/Gtk2 Microsoft Windows 10 aero client version > 2.2-r17577 64-bit > > I've pasted two logging outputs below:? 1) When I attempt to connect to > a running XPRA server with a Win10 client 2.2-r17577, and? 2) When I > connect to the same XPRA server with a Win10 client 2.2-r17538. > > In the first attempt the resulting child xterm doesn't respond properly > to keyboard input, and the server log includes an error and traceback.? > In the second attempt (same server but older client), the xterm responds > properly and there's no server error/traceback. > > Any advice/guidance you can provide to assist with better > troubleshooting this would be greatly appreciated.? Thanks! This bug has been fixed, for details see here: http://xpra.org/trac/ticket/1665#comment:6 And you can find updated builds in the usual location: https://xpra.org/beta/ Sorry for the inconvenience. For future reference, keyboard debugging is documented here: https://xpra.org/trac/wiki/Keyboard But I have to say that your bug report is one of the best I have seen. Cheers Antoine From antoine at nagafix.co.uk Mon Dec 11 20:12:52 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 12 Dec 2017 03:12:52 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.2 Message-ID: <7c7d0c5b-fa91-e601-3100-7f35b1513cc2@nagafix.co.uk> Hi, The areas that have seen the most important changes in this release are: * the network layer now supports UDP connections and VNC clients in desktop mode, it handles challenging network performance much more smoothly, with more options to configure all the connection types * the Python3 + GTK3 port is now almost on par with the GTK2 client, and even has some advantages on MS Windows: support for transparent windows. * keyboard layout improvements, support for fine grained scrolling, etc For more detailed information, including links to the documentation and tickets, see: http://xpra.org/trac/wiki/News#a2.2ImportantFeatures The source: https://xpra.org/src/ Downloads: http://xpra.org/trac/wiki/Download Cheers Antoine From nikolausr at google.com Wed Dec 13 12:22:09 2017 From: nikolausr at google.com (Nikolaus Rath) Date: Wed, 13 Dec 2017 12:22:09 +0000 Subject: [winswitch] Unable to start - "unknown format for display name" Message-ID: Hi, I'm trying to use xpra for the first time on two new systems, but it gives me an error that I haven't seen before: $ xpra start ssh:niratiquity.fra.corp.google.com --start=xfce4-terminal 2017-12-13 12:14:09,386 Xpra gtk2 client version 0.17.6-r14322 2017-12-13 12:14:09,386? running on Linux Debian rodete rodete 2017-12-13 12:14:09,386 Warning: failed to import opencv: 2017-12-13 12:14:09,386? No module named cv2 2017-12-13 12:14:09,387? webcam forwarding is disabled 2017-12-13 12:14:09,567 GStreamer version 1.12 for Python 2.7 2017-12-13 12:14:09,912 PyOpenGL warning: missing accelerate module 2017-12-13 12:14:09,914 OpenGL enabled with Quadro K1200/PCIe/SSE2 2017-12-13 12:14:09,998? detected keyboard: rules=evdev, model=pc105, layout=us 2017-12-13 12:14:09,999? desktop size is 4000x2560 with 1 screen: 2017-12-13 12:14:09,999?? :0.0 (1058x677 mm - DPI: 96x96) 2017-12-13 12:14:09,999???? monitor 1 2560x1440 at 0x438 (597x336 mm - DPI: 108x108) 2017-12-13 12:14:09,999???? monitor 2 1440x2560 at 2560x0 (597x336 mm - DPI: 61x193) 2017-12-13 12:14:09,999? upscaled by 167%, virtual screen size: 2400x1536 2017-12-13 12:14:10,000?? :0.0 (1058x677 mm - DPI: 57x57) 2017-12-13 12:14:10,000???? monitor 1 1536x864 at 0x263 (597x336 mm - DPI: 65x65) 2017-12-13 12:14:10,000???? monitor 2 864x1536 at 1536x0 (597x336 mm - DPI: 36x116) Entering daemon mode; any further errors will be reported to: ? /home/nikolausr/.xpra/S7666.log Actual log file name is now: /home/nikolausr/.xpra/:0.log 2017-12-13 12:14:33,060 xpra initialization error: 2017-12-13 12:14:33,060? unknown format for display name: S7663 2017-12-13 12:14:33,060 2017-12-13 12:14:33,062 Error: printing disabled: 2017-12-13 12:14:33,063? No module named cups 2017-12-13 12:14:33,069 Connection lost The logs on the remote system don't show anything suspicious either: $ cat /home/nikolausr/.xpra/:0.log Failed to rename log file "/home/nikolausr/.xpra/Xorg.S7666.log" to "/home/nikolausr/.xpra/Xorg.S7666.log": No such file or directory X.Org X Server 1.19.3 Release Date: 2017-03-15 [...] Using display number provided by /usr/lib/xorg/Xorg: :0 failed to rename Xorg log file from '/home/nikolausr/.xpra/Xorg.S7666.log' to '/home/nikolausr/.xpra/Xorg.:0.log' ?[Errno 2] No such file or directory 2017-12-13 13:14:18,304 created unix domain socket: /home/nikolausr/.xpra/niratiquity.fra.corp.google.com-0 2017-12-13 13:14:18,733 Pillow error saving jpeg with quality=50, speed=50, alpha=True 2017-12-13 13:14:18,733? cannot write mode RGBA as JPEG Traceback (most recent call last): ? File "/usr/lib/python2.7/dist-packages/xpra/codecs/pillow/encode.py", line 157, in selftest ??? v = encode(encoding, img, q, s, alpha) ? File "/usr/lib/python2.7/dist-packages/xpra/codecs/pillow/encode.py", line 89, in encode ??? im.save(buf, coding.upper(), **kwargs) ? File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 1893, in save ??? save_handler(self, fp, filename) ? File "/usr/lib/python2.7/dist-packages/PIL/JpegImagePlugin.py", line 604, in _save ??? raise IOError("cannot write mode %s as JPEG" % im.mode) IOError: cannot write mode RGBA as JPEG 2017-12-13 13:14:18,835 Warning: failed to load the mdns avahi publisher: 2017-12-13 13:14:18,836? No module named avahi 2017-12-13 13:14:18,836? either fix your installation or use the 'mdns=no' option 2017-12-13 13:14:19,243 Warning: webcam forwarding is disabled 2017-12-13 13:14:19,243? the virtual video directory '/sys/devices/virtual/video4linux' was not found 2017-12-13 13:14:19,243? make sure that the 'v4l2loopback' kernel module is installed and loaded 2017-12-13 13:14:19,243 found 0 virtual video devices 2017-12-13 13:14:19,257 pulseaudio server started with pid 7702 2017-12-13 13:14:19,470 GStreamer version 1.12 for Python 2.7 Someone able to help? Best, -Nikolaus From totaam at gmail.com Wed Dec 13 12:33:47 2017 From: totaam at gmail.com (Antoine Martin) Date: Wed, 13 Dec 2017 19:33:47 +0700 Subject: [winswitch] Unable to start - "unknown format for display name" In-Reply-To: References: Message-ID: > > > $ xpra start ssh:niratiquity.fra.corp.google.com --start=xfce4-terminal > 2017-12-13 12:14:09,386 Xpra gtk2 client version 0.17.6-r14322 Easy: you're using an outdated and buggy version. See here for details: https://www.xpra.org/trac/wiki/Packaging/DistributionPackages Cheers Antoine From nikolausr at google.com Wed Dec 13 13:02:23 2017 From: nikolausr at google.com (Nikolaus Rath) Date: Wed, 13 Dec 2017 13:02:23 +0000 Subject: [winswitch] Unable to start - "unknown format for display name" In-Reply-To: References: Message-ID: <6dbdebb5-dbca-a2e5-6e74-6ecfc5123a81@google.com> On 12/13/2017 12:33 PM, Antoine Martin wrote: > > > $ xpra start ssh:niratiquity.fra.corp.google.com > --start=xfce4-terminal > 2017-12-13 12:14:09,386 Xpra gtk2 client version 0.17.6-r14322 > > Easy: you're using an outdated and buggy version. > See here for details: > https://www.xpra.org/trac/wiki/Packaging/DistributionPackages > > Ah, got it. Thanks, and sorry for not checking myself first! Best, -Nikolaus From antoine at nagafix.co.uk Thu Dec 21 04:51:34 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 21 Dec 2017 11:51:34 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.2.1: minor fixes Message-ID: Hi, This update fixes some minor issues, mostly regressions in the 2.2 branch related to the keyboard, system tray and webp encoding. Release notes: * fix MacOS keyboard detection crash * fix system proxy not starting due to missing SSL certificate (DEB) * fix typo in per-user config file location example * fix error in fakeXinerama error handler * fix non-systemd system service files * fix automatic bandwidth limit underestimated * fix application crash caused by KDE systray API * fix system tray forwarding, size miscalculation on MS Windows * fix "delay-tray" command line option * fix system tray command line test scripts * fix key mapping regression with X11 clients and non-us layouts * fix auto-refresh handling error * fix webp encoding with OpenGL rendering disabled * don't enable webp on platforms with outdated libraries * handle rfb-upgrade parsing failures more gracefully * check for uinput permissions early (avoid using uinput configuration unnecessarily) * support older versions of python-lz4 (as used on Ubuntu and Debian) * add missing webp RPM dependencies Source: https://xpra.org/trac/wiki/Source Downloads: https://xpra.org/trac/wiki/Download Cheers Antoine From max at knirz.de Thu Dec 28 18:13:42 2017 From: max at knirz.de (Max Kubierschky) Date: Thu, 28 Dec 2017 19:13:42 +0100 Subject: [winswitch] xpra initialization error: failed to identify the new server display! Message-ID: Hello everybody, I try to set up a remote pair programming environment with xpra. Development takes place on a cloud server. Both programmers are connected via xpra. The idea is, that in this way we don't need much bandwidth on upload (only the keystrokes and mouseclicks). The bigger data volume (screen content) is only on download and thus less problematic. As an example, I want to run a terminal window on the server and share it on both clients. All involved machines run debian strech (yet). On the server I start a session with $ xpra start :30 --sharing=yes then I start mate-terminal on that server. On the first client, I attach with $ xpra attach ssh:max at xxxxx.org:30 --desktop-scaling=off --quality=100 --sharing=yes This works as expected, I see and can use the terminal. On the second client, I try to share with $ xpra shadow ssh:max at xxxxx.org:30 and get no connection. Error messages are below. Whats wrong? Any hints? --------------------------------------------- output from: xpra shadow ssh:max at xxxxx.org:30 --------------------------------------------- 2017-12-28 19:07:28,614 Xpra gtk2 client version 0.17.6-r14322 2017-12-28 19:07:28,615? running on Linux debian 9.3 2017-12-28 19:07:28,616 Warning: failed to import opencv: 2017-12-28 19:07:28,616? No module named cv2 2017-12-28 19:07:28,616? webcam forwarding is disabled 2017-12-28 19:07:29,128 GStreamer version 1.10 for Python 2.7 2017-12-28 19:07:31,004 PyOpenGL warning: missing accelerate module 2017-12-28 19:07:31,689? detected keyboard: rules=evdev, model=pc105, layout=de 2017-12-28 19:07:31,692? desktop size is 1920x1080 with 1 screen: 2017-12-28 19:07:31,699?? :0.0 (508x286 mm - DPI: 96x95) workarea: 1888x1080 at 32x0 2017-12-28 19:07:31,711???? monitor 1 (531x298 mm - DPI: 91x92) xpra initialization error: ?failed to identify the new server display! 2017-12-28 18:07:48,639 server failure: disconnected before the session could be established 2017-12-28 18:07:48,639 server requested disconnect: server error (failed to start a new session) Warning: cannot use the system proxy for 'shadow' subcommand, ?FAILURE Entering daemon mode; any further errors will be reported to: ? /home/max/.xpra/:30.log xpra initialization error: ?failed to identify the new server display! 2017-12-28 18:08:04,139 server failure: disconnected before the session could be established 2017-12-28 18:08:04,139 server requested disconnect: server error (failed to start a new session) Warning: cannot use the system proxy for 'shadow' subcommand, ?FAILURE Entering daemon mode; any further errors will be reported to: ? /home/max/.xpra/:30.log xpra initialization error: ?failed to identify the new server display! 2017-12-28 19:08:19,979 The SSH process has terminated with exit code 0 2017-12-28 19:08:19,980? the command line used was: 2017-12-28 19:08:19,980? ssh -x -l max -T xxxxx.org xpra initenv;~/.xpra/run-xpra _shadow_start :30 || $XDG_RUNTIME_DIR/xpra/run-xpra _shadow_start :30 || xpra _shadow_start :30 From antoine at nagafix.co.uk Thu Dec 28 18:24:39 2017 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 29 Dec 2017 01:24:39 +0700 Subject: [winswitch] xpra initialization error: failed to identify the new server display! In-Reply-To: References: Message-ID: (..) > As an example, I want to run a terminal window on the server and share > it on both clients. All involved machines run debian strech (yet). > > On the server I start a session with > > $ xpra start :30 --sharing=yes > > then I start mate-terminal on that server. > On the first client, I attach with > > $ xpra attach ssh:max at xxxxx.org:30 --desktop-scaling=off --quality=100 > --sharing=yes > > This works as expected, I see and can use the terminal. > On the second client, I try to share with > > $ xpra shadow ssh:max at xxxxx.org:30 Don't use shadow for the second user, just use attach with --sharing=yes > and get no connection. Error messages are below. > Whats wrong? Any hints? > > --------------------------------------------- > output from: xpra shadow ssh:max at xxxxx.org:30 > --------------------------------------------- > > 2017-12-28 19:07:28,614 Xpra gtk2 client version 0.17.6-r14322 That version is buggy as hell and full of security issues, do not use. Cheers Antoine