From antoine at nagafix.co.uk Wed Sep 1 08:29:58 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 1 Sep 2021 14:29:58 +0700 Subject: [winswitch] Stop Mobile Keyboard In-Reply-To: <2ff402da-8770-1536-044c-f7e364172a6a@nevets.com.au> References: <2ff402da-8770-1536-044c-f7e364172a6a@nevets.com.au> Message-ID: On 20/08/2021 17:15, Steve Gatenby via shifter-users wrote: > Is it possible to tell xpra to not pass screen touches to mobile os > (android in this case), or is that controlled fully by the phone itself ? I'm sure something can be done, but I'm not so sure that it is possible to satisfy all use-cases by default. Most applications listen for keyboard events and very few actually use read-only windows. By not showing the on-screen keyboard, it would be impossible to use the keyboard with any other application. I guess that we could offer a switch so that xpra's own on-screen keyboard disables the default mobile popup one. Or perhaps the keyboard icon in the top bar could be used to toggle between different modes: no keyboard input at all, on-screen or native. Then there's also the issue of the clipboard, which is somewhat tightly coupled with the keyboard. Perhaps someone else has a better idea? Cheers, Antoine > > I am finding each touch in my app is opening the phone keyboard. > > I have no need for keyboard input in my app, so looking to fully disable > in xpra session ? > > Regards - SteveG > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From ajs1 at cam.ac.uk Thu Sep 2 17:21:30 2021 From: ajs1 at cam.ac.uk (Anthony Stone) Date: Thu, 2 Sep 2021 17:21:30 +0100 Subject: [winswitch] Odd behaviour in xpra Message-ID: <5480e448-6c4e-63bf-5428-44247f83b857@cam.ac.uk> Hello, I'm using xpra v4.2.2-r0 under Ubuntu 18.04 on both server and client. I find that sometimes, when I type a command, the response is just a blank line, with no command output and with the cursor left where the end of the new command prompt would be. Sometimes the command output and a new prompt appear after a pause, over-writing the original blank response. Hitting the return key causes them to appear anyway, with an extra prompt. It's not a serious problem but it's a bit irritating. Anthony From akadanitan at yahoo.com Wed Sep 1 15:46:46 2021 From: akadanitan at yahoo.com (akadanitan at yahoo.com) Date: Wed, 1 Sep 2021 14:46:46 +0000 (UTC) Subject: [winswitch] auto-reattach possible? References: <1707162798.1238413.1630507606944.ref@mail.yahoo.com> Message-ID: <1707162798.1238413.1630507606944@mail.yahoo.com> If I am attached to a remote Xpra session and then my wifi disconnects, the Xpra UI will pop up with the message "Connection lost" in red. Is there a setting whereby it will try to periodically re-attach to the session so that I don't explicitly have to hit the "Connect" button? From luca.manganelli at comune.trento.it Thu Sep 2 10:38:32 2021 From: luca.manganelli at comune.trento.it (Luca Manganelli) Date: Thu, 2 Sep 2021 11:38:32 +0200 Subject: [winswitch] Libreoffice refuses to start after first time Message-ID: Hello, is it normal that Libreoffice doesn't start anymore, after the first time? I killed all relevant processes, but it didn't start after all. -- Comune di Trento? via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 00355870221 tel. +39 0461.884111 | www.comune.trento.it ? From totaam at xpra.org Fri Sep 3 15:34:20 2021 From: totaam at xpra.org (Antoine Martin) Date: Fri, 3 Sep 2021 21:34:20 +0700 Subject: [winswitch] [ANNOUNCE] Xpra HTML5 4.4 Message-ID: Hi, This new release of the HTML5 client comes fairly soon after the 4.3 release because there was a regression which caused a performance degradation due to unnecessary memory copying. Performance should be improved for most platforms thanks to more zero-copy memory transfers and the decoding of screen updates is now in a separate worker thread - this is particularly useful for H264 decoding, which cannot be done "natively" by the browser. There are also improvements to AES encrypted connections: support for CFB and CTR modes was added (requires v4.3 or later of the xpra server), switched to cryptographically secure random numbers. The full release notes can be found here: https://github.com/Xpra-org/xpra-html5/releases/tag/v4.4 Cheers Antoine From antoine at nagafix.co.uk Fri Sep 3 16:06:32 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 3 Sep 2021 22:06:32 +0700 Subject: [winswitch] auto-reattach possible? In-Reply-To: <1707162798.1238413.1630507606944@mail.yahoo.com> References: <1707162798.1238413.1630507606944.ref@mail.yahoo.com> <1707162798.1238413.1630507606944@mail.yahoo.com> Message-ID: <3e6f97e0-ad78-8ae2-8057-b01a198fc062@nagafix.co.uk> On 01/09/2021 21:46, akadanitan--- via shifter-users wrote: > If I am attached to a remote Xpra session and then my wifi disconnects, the Xpra UI will pop up with the message "Connection lost" in red. Is there a setting whereby it will try to periodically re-attach to the session so that I don't explicitly have to hit the "Connect" button? Yes. This feature will finally be included in the upcoming 4.3 release: https://github.com/Xpra-org/xpra/issues/3010 Feel free to test it by using the packages from the beta channel. Cheers, Antoine From totaam at xpra.org Fri Sep 3 16:35:45 2021 From: totaam at xpra.org (Antoine Martin) Date: Fri, 3 Sep 2021 22:35:45 +0700 Subject: [winswitch] Libreoffice refuses to start after first time In-Reply-To: References: Message-ID: <65bc50de-12e0-e943-4a59-85151b372355@xpra.org> On 02/09/2021 16:38, Luca Manganelli via shifter-users wrote: > Hello, > > is it normal that Libreoffice doesn't start anymore, after the first time? > I killed all relevant processes, but it didn't start after all. You haven't specified your versions or OS, so I can't try to reproduce the problem. My guess is that you haven't actually killed *all* the processes that libreoffice had created the first time you ran it and if the display that you ran it on is still active then it may try to spawn the new copy on that same display. This is a "feature" of many applications, especially browsers. If the problem doesn't occur with more simple test applications ('xterm' is always the go-to reference for testing) then it's clearly this particular application's behaviour that is causing the problem, rather than xpra itself. For some applications, there are tricks that can be used to obtain the desired behaviour - that is, to make it start on the new session: * some applications have command line switches for doing that (some browsers have "profiles") * some environment variables can be used to trick the application into believing that it is running for the first time * more advanced tricks can use temporary users, containers and such. But bear in mind that those are tricks and may cause further problems down the line. Cheers, Antoine From totaam at xpra.org Fri Sep 3 16:47:28 2021 From: totaam at xpra.org (Antoine Martin) Date: Fri, 3 Sep 2021 22:47:28 +0700 Subject: [winswitch] Odd behaviour in xpra In-Reply-To: <5480e448-6c4e-63bf-5428-44247f83b857@cam.ac.uk> References: <5480e448-6c4e-63bf-5428-44247f83b857@cam.ac.uk> Message-ID: <65cc8739-ba02-4f29-02f3-31e334763313@xpra.org> On 02/09/2021 23:21, Anthony Stone via shifter-users wrote: > Hello, > > I'm using xpra v4.2.2-r0 under Ubuntu 18.04 on both server and client. I > find that sometimes, when I type a command, the response is just a blank > line, with no command output and with the cursor left where the end of > the new command prompt would be. Sometimes the command output and a new > prompt appear after a pause, over-writing the original blank response. > Hitting the return key causes them to appear anyway, with an extra prompt. > > It's not a serious problem but it's a bit irritating. I can imagine! I have seen this bug in the past, but not recently. OTOH, it could be a number of things: * buggy screen updates that somehow don't end up on screen (ie: decoding errors) - those normally cause error messages in your client's output or in the server log - do you see any? * buggy display drivers / display code - turning off or forcing on the OpenGL acceleration from the system tray may fix that. Terminals should be detected as 'text' applications and therefore not using OpenGL. To debug, you can try a few things: * the "F10" shortcut to toggle paint debugging (on most Linux desktops, that's "Ctrl+Shift+F10" over the window) - the colours should then indicate how it's trying to update the screen, * turning off specific encodings, ie: --encodings=jpeg,rgb,webp and hope to isolate the buggy one * the "refresh window" entry from the tray menu, does this "fix" things? This may give us some clues as to what is going on. Creating a ticket may be the best way to get this resolved: https://github.com/Xpra-org/xpra/issues/new/choose Cheers, Antoine > > Anthony From luca.manganelli at comune.trento.it Sat Sep 4 07:44:12 2021 From: luca.manganelli at comune.trento.it (Luca Manganelli) Date: Sat, 4 Sep 2021 08:44:12 +0200 Subject: [winswitch] Libreoffice refuses to start after first time In-Reply-To: <65bc50de-12e0-e943-4a59-85151b372355@xpra.org> References: <65bc50de-12e0-e943-4a59-85151b372355@xpra.org> Message-ID: Il giorno ven 3 set 2021 alle ore 17:36 Antoine Martin via shifter-users < shifter-users at lists.devloop.org.uk> ha scritto: > You haven't specified your versions or OS, so I can't try to reproduce > the problem. Sorry for incomplete information. My OS is Fedora 33 with Libreoffice 7.0.6. > My guess is that you haven't actually killed *all* the processes that > libreoffice had created the first time you ran it and if the display > that you ran it on is still active then it may try to spawn the new copy > on that same display. I've killed all OO processes, but I discovered that the day after I went to the office, LibreOffice launched on the main monitor, so it never went through xpra. > If the problem doesn't occur with more simple test applications ('xterm' > is always the go-to reference for testing) then it's clearly this > particular application's behaviour that is causing the problem, rather > than xpra itself. I think the same, too. Thank you for the kind answer Luca -- Comune di Trento? via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 00355870221 tel. +39 0461.884111 | www.comune.trento.it ? From xpra at jubileegroup.co.uk Fri Sep 10 19:37:31 2021 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Fri, 10 Sep 2021 19:37:31 +0100 (BST) Subject: [winswitch] First time install of xpra: black screen in all windows. Message-ID: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Hi there, My first use of xpra, for which (I think:) I'm very grateful, and my first post to this list. I built version 4.3 from source (git clone) on two machines. One is a laptop (Debian Buster, Intel i7) and the other is a Raspberry Pi 3B+ (Raspbian Bullseye, ARM): 8<---------------------------------------------------------------------- ged at piplus:~$ uname -a Linux piplus 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 armv7l GNU/Linux ged at piplus:~$ xpra --version xpra v4.3-r29977 (g8a0d2b663) ged at piplus:~$ ssh laptop3 Linux laptop3 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 ... laptop3:~$ >>> xpra --version xpra v4.3-r867 8<---------------------------------------------------------------------- I can start an xpra server on the laptop e.g. with DISPLAY=:101, then start an xterm for that instance, then attach a local xpra client to display 101 on the laptop and everything is fine. However if I attach to the same server from a client on the Pi, I see a window but there's no content displayed in it - it's completely black. Apart from that it's a functioning connection. I can run commands in the black window (blindfold), and they are executed and saved in the command history. Also, if on the laptop I start the browser (palemoon) for display 101, and attach to display 101 from an xpra client on the Pi, three windows are opened on the Pi because I normally run with three windows for various different jobs that I'm working on in the browser. The window titles are correctly displayed in the window borders on the Pi, but like the xterm window, the content is completely black. If there are bits of logs somewhere which might be helpful in tracking down the problem please let me know what to look for. I've searched the list archive but found nothing which quite matched these symptoms. -- 73, Ged. From xpra at jubileegroup.co.uk Sat Sep 11 09:13:26 2021 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Sat, 11 Sep 2021 09:13:26 +0100 (BST) Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: Hello again, On Fri, 10 Sep 2021, G.W. Haywood wrote: > ... > I can start an xpra server on the laptop e.g. with DISPLAY=:101, then > start an xterm for that instance, then attach a local xpra client to > display 101 on the laptop and everything is fine. However if I attach > to the same server from a client on the Pi, I see a window but there's > no content displayed in it - it's completely black. Apart from that > it's a functioning connection. I can run commands in the black window > (blindfold), and they are executed and saved in the command history. More information. I forgot to mention that the window manager on the laptop is fvwm2, which is not negotiable. On the Pi3B+ it is normally Fluxbox. I tried with fvwm on the Pi with exactly the same results. -- 73, Ged. From antoine at nagafix.co.uk Sat Sep 11 10:11:32 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 11 Sep 2021 16:11:32 +0700 Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: On 11/09/2021 15:13, G.W. Haywood via shifter-users wrote: > Hello again, > > On Fri, 10 Sep 2021, G.W. Haywood wrote: > >> ... >> I can start an xpra server on the laptop e.g. with DISPLAY=:101, then >> start an xterm for that instance, then attach a local xpra client to >> display 101 on the laptop and everything is fine.? However if I attach >> to the same server from a client on the Pi, I see a window but there's >> no content displayed in it - it's completely black.? Apart from that >> it's a functioning connection.? I can run commands in the black window >> (blindfold), and they are executed and saved in the command history. > > More information.? I forgot to mention that the window manager on the > laptop is fvwm2, which is not negotiable. I hope that you're talking about the window manager you're using with the laptop's desktop environment, and not that you expect to be able to run a window manager with xpra's seamless mode. You cannot run another window manager in an xpra seamless session as xpra is the window manager. If you want to run a window manager on the server side, then you will need to use desktop mode ("xpra start-desktop") instead of the seamless mode ("xpra start"). > On the Pi3B+ it is normally > Fluxbox.? I tried with fvwm on the Pi with exactly the same results. > I haven't tried it lately on a PI, I've got a 2 and a 3B gathering dust somewhere. This used to work fine but it is possible that something broke in later versions without anyone noticing. The other possibility is that since you've compiled it yourself, you haven't enabled enough picture codecs for it to work properly. The most important one is python pillow, without this library a lot of features just don't work well or not at all. Also, you may want to run the client with --opengl=no (or try forcing it on with 'yes') as I can't remember the state of the client opengl acceleration on PIs, also it may have improved since. If the window is completely blank, I would expect to see some errors in the server log. Cheers, Antoine From xpra at jubileegroup.co.uk Sat Sep 11 11:10:34 2021 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Sat, 11 Sep 2021 11:10:34 +0100 (BST) Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: Hi there, Thanks very much for the speedy and helpful response. On Sat, 11 Sep 2021, Antoine Martin via shifter-users wrote: > On 11/09/2021 15:13, G.W. Haywood via shifter-users wrote: >> On Fri, 10 Sep 2021, G.W. Haywood wrote: >>> ... >>> I can start an xpra server on the laptop e.g. with DISPLAY=:101, then >>> start an xterm for that instance, then attach a local xpra client to >>> display 101 on the laptop and everything is fine.? However if I attach >>> to the same server from a client on the Pi, I see a window but there's >>> no content displayed in it - it's completely black.? Apart from that >>> it's a functioning connection.? I can run commands in the black window >>> (blindfold), and they are executed and saved in the command history. >> >> More information.? I forgot to mention that the window manager on the >> laptop is fvwm2, which is not negotiable. > > I hope that you're talking about the window manager you're using with > the laptop's desktop environment, and not that you expect to be able to > run a window manager with xpra's seamless mode. Yes, of course. The point being that it works fine connecting locally on the laptop using fvwm2 as the laptop's window manager (and using no other window manager at all for the xpra session). > If you want to run a window manager on the server side, then you will > need to use desktop mode ("xpra start-desktop") instead of the seamless > mode ("xpra start"). I understand. When working remotely, I need no window manager (nor even a user's login session) running on the server side. >> On the Pi3B+ it is normally >> Fluxbox.? I tried with fvwm on the Pi with exactly the same results. >> > I haven't tried it lately on a PI, I've got a 2 and a 3B gathering dust > somewhere. This used to work fine but it is possible that something > broke in later versions without anyone noticing. Very possible, in fact this is what I suspect. I was hoping someone on the list might be running this on a Pi. > The other possibility is that since you've compiled it yourself, you > haven't enabled enough picture codecs for it to work properly. Anything like that is very possible. I'm very unfamiliar with Python, I don't even know how to enquire which libraries (modules?) are installed and I find it very confusing that some things seem to be installed using '(pip|pip3) install' and some using 'apt-get install'. > The most important one is python pillow, without this library a lot of > features just don't work well or not at all. I have never heard of pillow, but AFAICT it is installed on both the server and the client. I'm running Debian Buster on the laptop and something approximating to Raspbian Bullseye on the Pi so I suspect that is why the versions are so very different. I say "something approximating" because earlier in the week I ran 'apt-get full-upgrade' on the Pi using the "stable" distribution in the sources.list and it decided that this would be version 11 (Debian's Bullseye). According to my wife (who has delved into this quite a bit) there's been no official announcement from the Raspbery Pi people that Bullseye is available. :( Normally I'm emphatically not on the bleeding edge, I was just trying to get everything up to date before mailing this list. 8<---------------------------------------------------------------------- laptop3:~# >>> pip3 install pillow Requirement already satisfied: pillow in /usr/lib/python3/dist-packages (5.4.1) piplus:~# >>> pip3 install pillow Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple Requirement already satisfied: pillow in /usr/lib/python3/dist-packages (8.1.2) 8<---------------------------------------------------------------------- Again there are confusions resulting largely from the distro packaging, if in doubt I install everything which looks vaguely like something I need. For this exercise that amounted to several hundred pakages on each of the Pi and the laptop... > Also, you may want to run the client with --opengl=no (or try forcing it > on with 'yes') as I can't remember the state of the client opengl > acceleration on PIs, also it may have improved since. Tried both, same result. > If the window is completely blank, I would expect to see some errors in > the server log. Three attempts to connect below. On the laptop: $ xpra start :103 $ DISPLAY=:103 xterm & On the Pi: Try 1: xpra attach ssh://laptop3/103 Try 2: xpra --opengl=yes attach ssh://laptop3/103 Try 3: xpra --opengl=no attach ssh://laptop3/103 In all cases the same result - a black window. Below is laptop3:/tmp/xpra/103/server.log in full for each of the three attempts. Please note that the first line of the log really does have no timestamp, I haven't accidentally truncated it. Just my opinion, but the log would be better without the escape sequences - nothing I see in 'man xpra' makes me think that they might be optional. I do not know what the 'html-xpra package' might be. I have failed to find it using 'apt-cache search' and attempting to install it using pip or pip3 just gives an error that it can't be found. 8<---------------------------------------------------------------------- failure on /tmp/.X11-unix/X103: [Errno 2] No such file or directory: '/tmp/.X11-unix/X103' 2021-09-11 10:38:21,555 cannot use uinput for virtual devices: 2021-09-11 10:38:21,555 [Errno 19] Failed to open the uinput device: No such device 2021-09-11 10:38:23,197 pointer device emulation using XTest 2021-09-11 10:38:23,264 Error: cannot find the html web root 2021-09-11 10:38:23,264 '/usr/local/share/xpra/www' does not exist 2021-09-11 10:38:23,264 install the html-xpra package 2021-09-11 10:38:23,264 wrote pid 21107 to '/tmp/xpra/103/server.pid' 2021-09-11 10:38:23,290 Warning: failed to create socket directory '/run/xpra' 2021-09-11 10:38:23,291 [Errno 13] Permission denied: '/run/xpra' 2021-09-11 10:38:23,291 created unix domain socket '/tmp/xpra/laptop3-103' 2021-09-11 10:38:23,291 cannot create group socket '/run/xpra/laptop3-103' 2021-09-11 10:38:23,291 [Errno 2] No such file or directory 2021-09-11 10:38:23,292 /run/xpra does not exist 2021-09-11 10:38:23,292 created unix domain socket '/home/ged/.xpra/laptop3-103' 2021-09-11 10:38:23,292 xvfb pid=21111 2021-09-11 10:38:23,361 D-Bus notification forwarding is available 2021-09-11 10:38:23,382 pulseaudio server started with pid 21154 2021-09-11 10:38:23,382 private server socket path: 2021-09-11 10:38:23,382 '/tmp/xpra/103/pulse-103/pulse/native' 2021-09-11 10:38:23,489 watching for applications menu changes in: 2021-09-11 10:38:23,489 '/usr/share/applications' 2021-09-11 10:38:23,490 '/usr/local/share/applications' 2021-09-11 10:38:23,504 Warning: webcam forwarding is disabled 2021-09-11 10:38:23,504 the virtual video directory '/sys/devices/virtual/video4linux' was not found 2021-09-11 10:38:23,505 make sure that the 'v4l2loopback' kernel module is installed and loaded 2021-09-11 10:38:23,505 or use the 'webcam=no' option 2021-09-11 10:38:23,505 found 0 virtual video devices for webcam forwarding (Xpra:21107): Gtk-CRITICAL **: 10:38:23.613: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed 2021-09-11 10:38:23,887 waiting for initialization thread to complete 2021-09-11 10:38:23,890 xpra is ready. 2021-09-11 10:38:24,041 GStreamer version 1.14.4 for Python 3.7.3 64-bit 2021-09-11 10:38:24,146 xpra X11 seamless version 4.3-r867 64-bit 2021-09-11 10:38:24,147 uid=1001 (ged), gid=1001 (ged) 2021-09-11 10:38:24,147 running with pid 21107 on Linux Debian 10 buster 2021-09-11 10:38:24,183 connected to X11 display :103 with 24 bit colors 2021-09-11 10:38:27,749 loaded 82 start menu entries from 11 sub-menus in 4.3 seconds 2021-09-11 10:38:31,448 printer forwarding enabled using postscript and pdf 2021-09-11 10:38:31,456 started command '/etc/X11/Xsession true' with pid 21230 2021-09-11 10:38:31,505 3.7GB of system memory 2021-09-11 10:38:31,828 No OpenGL information available 2021-09-11 10:38:51,457 New unix-domain connection received 2021-09-11 10:38:51,457 on '/tmp/xpra/laptop3-103' 2021-09-11 10:38:51,465 Handshake complete; enabling connection 2021-09-11 10:38:51,486 Python/GTK3 Linux Raspbian 11 bullseye tty client version 4.3-r29977 32-bit 2021-09-11 10:38:51,486 OpenGL is disabled 2021-09-11 10:38:51,486 connected from 'piplus' as 'ged' - 'Ged' 2021-09-11 10:38:51,492 setting key repeat rate from client: 660ms delay / 40ms interval 2021-09-11 10:38:51,494 setting keymap: rules=evdev, model=pc105, layout=gb 2021-09-11 10:38:51,527 setting keyboard layout to 'gb' 2021-09-11 10:38:51,647 client root window size is 1600x900 with 1 display: 2021-09-11 10:38:51,647 :0.0 (423x238 mm - DPI: 96x96) workarea: 1600x879  2021-09-11 10:38:52,152 server virtual display now set to 1600x900 2021-09-11 10:38:52,159 automatic picture encoding enabled, also available: 2021-09-11 10:38:52,159 png, png/P, png/L, rgb24, rgb32, jpeg, scroll 2021-09-11 10:38:52,193 DPI set to 96 x 96 2021-09-11 10:38:52,259 client 1 @05.922 Xpra X11 seamless server version 4.3-r867 64-bit 2021-09-11 10:38:52,261 client 1 @05.924 running on Linux Debian 10 buster 2021-09-11 10:38:52,302 client 1 @05.960 Attached to ssh://ged at laptop3/103 2021-09-11 10:38:52,303 client 1 @05.964 (press Control-C to detach) 2021-09-11 10:38:53,287 client 1 @06.949 running, 1 window 2021-09-11 10:38:54,690 client 1 @08.354 Error: cannot access the list of printers 2021-09-11 10:38:54,695 client 1 @08.357 module 'cups' has no attribute 'Connection' 2021-09-11 10:39:01,609 client 1 @15.271 Python/GTK3 Client got signal SIGINT 2021-09-11 10:39:01,610 client 1 @15.274 exiting 2021-09-11 10:39:01,614 client has requested disconnection: exit on signal SIGINT 2021-09-11 10:39:01,614 Disconnecting client /tmp/xpra/laptop3-103: 2021-09-11 10:39:01,615 client request 2021-09-11 10:39:01,617 xpra client 1 disconnected. 2021-09-11 10:39:14,887 New unix-domain connection received 2021-09-11 10:39:14,888 on '/tmp/xpra/laptop3-103' 2021-09-11 10:39:14,894 Handshake complete; enabling connection 2021-09-11 10:39:14,899 Python/GTK3 Linux Raspbian 11 bullseye tty client version 4.3-r29977 32-bit 2021-09-11 10:39:14,899 OpenGL is disabled 2021-09-11 10:39:14,899 connected from 'piplus' as 'ged' - 'Ged' 2021-09-11 10:39:14,901 setting key repeat rate from client: 660ms delay / 40ms interval 2021-09-11 10:39:14,903 keyboard mapping already configured (skipped) 2021-09-11 10:39:14,903 client root window size is 1600x900 with 1 display: 2021-09-11 10:39:14,904 :0.0 (423x238 mm - DPI: 96x96) workarea: 1600x879  2021-09-11 10:39:14,905 best resolution matching 1600x900 is unchanged: 1600x900 2021-09-11 10:39:14,907 automatic picture encoding enabled, also available: 2021-09-11 10:39:14,907 png, png/P, png/L, rgb24, rgb32, jpeg, scroll 2021-09-11 10:39:15,014 client 2 @04.069 Xpra X11 seamless server version 4.3-r867 64-bit 2021-09-11 10:39:15,039 client 2 @04.073 running on Linux Debian 10 buster 2021-09-11 10:39:15,075 client 2 @04.137 Attached to ssh://ged at laptop3/103 2021-09-11 10:39:15,082 client 2 @04.138 (press Control-C to detach) 2021-09-11 10:39:16,038 client 2 @05.089 running, 1 window 2021-09-11 10:39:17,445 client 2 @06.507 Error: cannot access the list of printers 2021-09-11 10:39:17,453 client 2 @06.513 module 'cups' has no attribute 'Connection' 2021-09-11 10:39:21,099 client 2 @10.160 Python/GTK3 Client got signal SIGINT 2021-09-11 10:39:21,106 client 2 @10.168 exiting 2021-09-11 10:39:21,112 client has requested disconnection: exit on signal SIGINT 2021-09-11 10:39:21,112 Disconnecting client /tmp/xpra/laptop3-103: 2021-09-11 10:39:21,112 client request 2021-09-11 10:39:21,114 xpra client 2 disconnected. 2021-09-11 10:39:33,465 New unix-domain connection received 2021-09-11 10:39:33,465 on '/tmp/xpra/laptop3-103' 2021-09-11 10:39:33,468 Handshake complete; enabling connection 2021-09-11 10:39:33,473 Python/GTK3 Linux Raspbian 11 bullseye tty client version 4.3-r29977 32-bit 2021-09-11 10:39:33,473 OpenGL is disabled 2021-09-11 10:39:33,473 connected from 'piplus' as 'ged' - 'Ged' 2021-09-11 10:39:33,476 setting key repeat rate from client: 660ms delay / 40ms interval 2021-09-11 10:39:33,479 keyboard mapping already configured (skipped) 2021-09-11 10:39:33,479 client root window size is 1600x900 with 1 display: 2021-09-11 10:39:33,479 :0.0 (423x238 mm - DPI: 96x96) workarea: 1600x879  2021-09-11 10:39:33,480 best resolution matching 1600x900 is unchanged: 1600x900 2021-09-11 10:39:33,484 automatic picture encoding enabled, also available: 2021-09-11 10:39:33,484 png, png/P, png/L, rgb24, rgb32, jpeg, scroll 2021-09-11 10:39:33,519 client 3 @04.031 Xpra X11 seamless server version 4.3-r867 64-bit 2021-09-11 10:39:33,606 client 3 @04.034 running on Linux Debian 10 buster 2021-09-11 10:39:33,666 client 3 @04.154 Attached to ssh://ged at laptop3/103 2021-09-11 10:39:33,673 client 3 @04.157 (press Control-C to detach) 2021-09-11 10:39:34,638 client 3 @05.151 running, 1 window 2021-09-11 10:39:36,022 client 3 @06.534 Error: cannot access the list of printers 2021-09-11 10:39:36,024 client 3 @06.536 module 'cups' has no attribute 'Connection' 2021-09-11 10:39:37,919 client 3 @08.434 Python/GTK3 Client got signal SIGINT 2021-09-11 10:39:37,922 client 3 @08.437 exiting 2021-09-11 10:39:37,925 client has requested disconnection: exit on signal SIGINT 2021-09-11 10:39:37,925 Disconnecting client /tmp/xpra/laptop3-103: 2021-09-11 10:39:37,925 client request 2021-09-11 10:39:37,927 xpra client 3 disconnected. 8<---------------------------------------------------------------------- Once again, thanks for xpra and for the help. -- 73, Ged. From totaam at xpra.org Thu Sep 16 15:33:36 2021 From: totaam at xpra.org (Antoine Martin) Date: Thu, 16 Sep 2021 21:33:36 +0700 Subject: [winswitch] [ANNOUNCE] Xpra HTML5 4.5 Message-ID: <20a25a61-cde6-d189-50b9-a125f77432bd@xpra.org> Hi, Once again, this new release of the HTML5 client comes fairly soon after the previous one because of another regression (sorry!), this time it was the connect dialog which was preventing connections once AES was selected. Apart from that, there is only one new feature: the client will now prompt for passwords as many times as needed and directly from the main page, without redirecting to the connect dialog. The full release notes can be found here: https://github.com/Xpra-org/xpra-html5/releases/tag/v4.5 Cheers Antoine From totaam at xpra.org Thu Sep 23 16:13:57 2021 From: totaam at xpra.org (Antoine Martin) Date: Thu, 23 Sep 2021 22:13:57 +0700 Subject: [winswitch] [ANNOUNCE] Xpra HTML5 4.5.1 Message-ID: <4e21a18a-c07f-c611-e9c7-8e1132d4bc76@xpra.org> Hi, There are only three changes in this release: * a workaround for a Firefox bug in the image decoder which was causing some windows to show up blank * allow AES and SSL to be combined - for those that need it * support multiple authentication challenge responses as parameters The full release notes can be found here: https://github.com/Xpra-org/xpra-html5/releases/tag/v4.5.1 Cheers Antoine From xpra at jubileegroup.co.uk Tue Sep 28 12:07:05 2021 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Tue, 28 Sep 2021 12:07:05 +0100 (BST) Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: Hello again, Nearly three weeks has elapsed since my post of 11th September at 11:10 BST https://lists.devloop.org.uk/pipermail/shifter-users/2021-September/002873.html which contains descriptions of three connection attempts, all of which fail in the way described in the subject line, and the server log for these attempts. I can trace no reply to my post of 11 September, and my reminder, sent to the list on 19 September at 13:08 BST, does not appear in the archive. To briefly recap, I can run a session 'locally' by starting XPRA and an xterm on the XPRA server and connecting to it from a client on the same machine but when the client is remote, the connection fails to render the screen display. Instead of showing the window content, the screen is completely black. Apart from that the xterm appears to be functional. I can run commands from it and the login session on the server acts upon them - for example I can 'touch' a non-existent file in the user's home directory and it is created as expected. What am I doing wrong? -- 73, Ged. From antoine at nagafix.co.uk Tue Sep 28 13:48:23 2021 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 28 Sep 2021 19:48:23 +0700 Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: On 28/09/2021 18:07, G.W. Haywood via shifter-users wrote: > Hello again, > > Nearly three weeks has elapsed since my post of 11th September at 11:10 BST > > https://lists.devloop.org.uk/pipermail/shifter-users/2021-September/002873.html > > > which contains descriptions of three connection attempts, all of which > fail in > the way described in the subject line, and the server log for these > attempts. > > I can trace no reply to my post of 11 September, This means no-one has had the time or access to the hardware needed for looking into this. I think that opening an issue on github would be a better option: https://github.com/Xpra-org/xpra/issues/new > and my reminder, sent > to the > list on 19 September at 13:08 BST, does not appear in the archive. That's right, I had discarded it. Please accept my apologies for not notifying you directly but I am kinda busy. Posts that simply "bump" another post are not acceptable on most mailing lists, including this one. > To briefly recap, I can run a session 'locally' by starting XPRA and an > xterm > on the XPRA server and connecting to it from a client on the same > machine but > when the client is remote, the connection fails to render the screen > display. > Instead of showing the window content, the screen is completely black. > Apart > from that the xterm appears to be functional.? I can run commands from > it and > the login session on the server acts upon them - for example I can > 'touch' a > non-existent file in the user's home directory and it is created as > expected. > > What am I doing wrong?Answering the questions from the bug reporting guidelines: https://github.com/Xpra-org/xpra/wiki/Reporting-Bugs would got a long way towards identifying the source of the problem. Cheers, Antoine From xpra at jubileegroup.co.uk Tue Sep 28 16:14:58 2021 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Tue, 28 Sep 2021 16:14:58 +0100 (BST) Subject: [winswitch] First time install of xpra: black screen in all windows. In-Reply-To: References: <589f1871-e83-d064-3776-b78e98351957@jubileegroup.co.uk> Message-ID: Hi there, On Tue, 28 Sep 2021, Antoine Martin via shifter-users wrote: > On 28/09/2021 18:07, G.W. Haywood via shifter-users wrote: >> ... >> https://lists.devloop.org.uk/pipermail/shifter-users/2021-September/002873.html >> ... > > I think that opening an issue on github would be a better option: > https://github.com/Xpra-org/xpra/issues/new Done. > ... > Answering the questions from the bug reporting guidelines: > https://github.com/Xpra-org/xpra/wiki/Reporting-Bugs > would got a long way towards identifying the source of the problem. I did try xpra bug-report but I got a slew of error messages like this: 8<---------------------------------------------------------------------- piplus:~$ >>> xpra bug-report Error collecting system bug report data using .get_sys_info at 0x7371ae80> Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/xpra/client/gtk_base/bug_report.py", line 288, in get_data value = value_cb() File "/usr/local/lib/python3.9/dist-packages/xpra/client/gtk_base/bug_report.py", line 125, in get_sys_info "display" : get_display_info(), File "/usr/local/lib/python3.9/dist-packages/xpra/gtk_common/gtk_util.py", line 499, in get_display_info info["screens"] = get_screens_info() File "/usr/local/lib/python3.9/dist-packages/xpra/gtk_common/gtk_util.py", line 242, in get_screens_info info[i] = get_screen_info(display, screen) File "/usr/local/lib/python3.9/dist-packages/xpra/gtk_common/gtk_util.py", line 349, in get_screen_info fo = screen.get_font_options() TypeError: Couldn't find foreign struct converter for 'cairo.FontOptions' Warning: failed to import GStreamer 1.x: Namespace Gst not available 8<---------------------------------------------------------------------- and then no way that I could see to exit the process short of killing it. Would you like to see a bug report about the bug report? :) -- 73, Ged.