From xpra at zellners.com Tue Jun 7 06:18:11 2022 From: xpra at zellners.com (xpra at zellners.com) Date: Mon, 06 Jun 2022 22:18:11 -0700 Subject: [winswitch] HTML Client - howto and problems Message-ID: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> Using Xpra 4.3.3 on Kubuntu 20.04....both server and client. I am testing out the HTML client to possibly allow for use case when SSH and X11 is not available, but a web browser is... but I run into some issues 1) Proper server startup ?? Following the wiki, man page and numerous sites adding --bind-tcp=0.0.0.0:14500 --html=on should do the trick, correct? No joy, UNLESS I REMOVE the --bind-tcp option... then the Xpra server will start. otherwise get an error about already in use on 0.0.0.0 ... So has this changed and the bind is automatic by default????? Or???? So I add --html=on to the startup xpra start --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 --start=/home/theprogramIstartup That works.... everything starts... I can use xpra-connect and connect.. good to go on my normal mode... 2) Access THE SESSION ABOVE VIA THE HTML5 client goto https://1.2.3.4:14500/connect.html OK.. get the login box....ok.. a) First issue: Connect option: "NO SESSIONS FOUND" in red I am taking this "connect" option would be what I do via the xpra_connect setup I have, already, connect up to the running XPRA on :100 let me see what its doing, etc., disconnect come back to it as needed.. Thats my use case mostly, check up on a program that runs long term... Is that correct for this connect option??????? b) Second issue: Using the SHADOW OPTION and it gives a drop down, :0, obviously the desktop thats there.. and then :100 which is the session I STARTED ABOVE... OK... select shadow and :100 from the drop down... Connects up, and after the initial transfer, I get session :0, NOT :100.. Doesn't matter how many times I change the dropdown from :0 to :100 it will NOT CONNECT TO THAT :100 session in shadow UMMMM???????? c) Infinite loop connection IF you try the connection LOCALLY ON THE SAME BOX as the server via HTML5 client in browser, because it is shadowing :0 it just causes an infinite loop where the browser window just shows that toolbar and just keeps redrawing it infinitely d) The process that won't die! This shadow connection starts another xpra server for :0, and it just WON'T DIE! You can tell it to shutdown via the HTML5 client option, it doesn't shut down, and when you disconnect you will have 2 XPRA processes running, the original :100 and this new :0 process, and sudo kill -9 pid will kill it and then it RESPAWNS... the only way to kill that is to HARD REBOOT the box! e) Password entry issues Seems to get things to connect the first time, I have to enter the password twice, even if its saved and auto entered by the browser, and hitting the eye to show it, it is correct, will connect, FAIL VALIDATION, and then enter it again, or let browser fill in again, and 2nd time works. shrug Comments, insights, welcome... Thanks! From antoine at nagafix.co.uk Tue Jun 7 12:52:07 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 7 Jun 2022 18:52:07 +0700 Subject: [winswitch] The application window turns gray if I want to move the work window to a new location In-Reply-To: <18e8cacf-dd24-de42-f029-ad866792941b@dussan.org> References: <18e8cacf-dd24-de42-f029-ad866792941b@dussan.org> Message-ID: <0f5ec351-c75b-7cc2-ba42-417c8ea93ebf@nagafix.co.uk> On 10/05/2022 18:32, Du?an Vejnovi? via shifter-users wrote: > Xpra version: 4.3.3 > OS version: Debian 11 > > How to reproduce: > - install Eclipse IDE on xpra server (from > https://www.eclipse.org/downloads/) > - run Eclipse IDE on xpra server (e.g. xpra start :10000 > --bind-tcp=0.0.0.0:10000 --systemd-run=no --exit-with-children=yes > --start-child="eclipse") > - connect to xpra server with Xpra HTML client > - create new project > - place the mouse cursor on the title bar of any window inside the > Eclipse IDE, press and hold the left mouse button for a few seconds > - all Eclipse IDE window turns gray I'm not seeing gray windows but I do see some very odd behaviour with a flashing top level window that comes and goes. That's par for the course with Java applications and eclipse IDE in particular. > > Must I make an error report? Yes please. Cheers, Antoine > > > Bye, Du?an. > _______________________________________________ > 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 Tue Jun 7 14:18:45 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 7 Jun 2022 20:18:45 +0700 Subject: [winswitch] run_scaled runs command but nothing shows up In-Reply-To: References: Message-ID: <9d45d1aa-002e-327a-53ff-e7630e7754c5@nagafix.co.uk> On 12/05/2022 04:29, Ben Pearre via shifter-users wrote: > Hi! > > Fully up-to-date manjaro, running xpra 4.3.3 just downloaded from github. Beware: github only hosts source snapshots, so you must have installed it manually - which may or may not have installed all the components required correctly. There are build and installation for some distributions here: https://github.com/Xpra-org/xpra/tree/master/docs/Build but not for Manjaro. > Nvidia Xorg driver. Please let me know what other version info you might > need. > > Since I couldn't find anything like this in the xpra issue tracker, I'll > assume I'm doing something stupid...? No, you just found a regression in the 4.3.x series. The trivial fix has been committed: https://github.com/Xpra-org/xpra/commit/9bebd86bfda4a3696818e81a6effec4ba8497687 The next releases will include it. In the meantime, you can run from git master, patch manually, or perhaps downgrade until the next stable release is out. > "run_scaled xterm" produces no errors, detaches, and then does nothing > obvious. > > Running "xpra" pops up a control window, browsing reveals that the xterm is > there, and I can attach to it. I'd thought that run_scaled did this > automatically---it did with the 4.2.x that someone packaged for > Manjaro---but this is encouraging. > > Problem is, it's not scaled. The scaling occurs when attaching so when you use the default GUI to attach, it won't use any scaling by default. But you can still change the scaling at runtime once attached: * via the system tray menu - which you can also activate over any xpra window, usually using the shortcut [Control Shift F1] * using the scaling key shortcuts, on most Linux DEs those are [Control Shift +] and [Control Shift -] > I assume this might have something to do with the line "DPI set to 32 x 33 > (wanted 288 x 288)"? No. That's a different problem - one which will be going away very soon as RandR support has been added to the dummy driver. This will be the most important feature of xpra 4.4: https://github.com/Xpra-org/xpra/issues/56 > The desired screen resolution is indeed about 288 > (EDID reports correctly, visible in the log I've attached). Almost this > error message was a bug back in 4.2.x (where it said "DPI set to 8x8 [...]" > or something, so 2.9 cheers for hillclimbing optimisation) but darnit? > > There are a bunch of errors and warnings. Do I have to add the user to > group xpra? Running as root doesn't seem to fix anything, so that's > probably not it... Most of these harmless warnings are documented here: https://github.com/Xpra-org/xpra/blob/master/docs/FAQ.md > > I'd be surprised if errors with html or cuda or webcam etc would result in > no scaling, but I could be wrong? > > Does this have anything to do with the fact that there are around a dozen > pieces of Manjaro / xfce / X11 that keep trying to override the EDID > resolution with the 96 x 96 lie? I think this lie is exactly why we need > run_scaled, so I bet all that nonsense is ignored...? No, that's unrelated. > > Pointers? What am I failing to do correctly? Nothing... it was just a bug. Sorry. Cheers, Antoine > Many thanks! > _______________________________________________ > 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 Tue Jun 7 14:27:38 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 7 Jun 2022 20:27:38 +0700 Subject: [winswitch] Desktop mode In-Reply-To: References: Message-ID: <69137d12-545a-8271-0d49-fa19e7bd815e@nagafix.co.uk> On 25/05/2022 01:14, carl langlois via shifter-users wrote: > Hi, > > Is it possible to have multiple virtual displays when running in Desktop > mode? Like having multiple screens. Yes: https://github.com/Xpra-org/xpra/issues/3524 With some usage examples here: https://github.com/Xpra-org/xpra/issues/3524#issuecomment-1107521099 Until xpra 4.4 is released, you can use the beta builds to test this feature. > Also not sure why the Alt-Tab is not caught when the desktop is having the > focus. This requires grabbing the keyboard and GTK is not cooperating: https://github.com/Xpra-org/xpra/issues/3059#issuecomment-804239253 To make matters worse on Wayland, xpra was not allowed on the whitelist: https://github.com/Xpra-org/xpra/issues/2613 Cheers, Antoine > > Thanks & regards > > Cl > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From yonatan.zaken at gmail.com Thu Jun 9 20:29:19 2022 From: yonatan.zaken at gmail.com (yonatan zaken) Date: Thu, 9 Jun 2022 22:29:19 +0300 Subject: [winswitch] [xpra] xpra-html how to Message-ID: Hi, xpra v4.3-r40 Ubuntu 18.04.6 LTS I cloned xpra-html5 to my home directory and installed as mentioned: https://github.com/Xpra-org/xpra-html5 And I run the following in terminal: xpra start --start=xterm --bind-tcp=127.0.0.1:10000 Standard output shows: ================================================= Entering daemon mode; any further errors will be reported to: /run/user/1000/xpra/S23615.log Actual display used: :2 Actual log file name is now: /run/user/1000/xpra/:2.log ================================================= Then I run in terminal: xdg-open http://localhost:10000 And a chrome window opens with the following: ================================================== Server Error Error code 400. Message: this port does not support HTTP requests. Error code explanation: 400 = Bad request syntax or unsupported method. ================================================== This is my log output: Quite hard to follow, *Is it the uinput missing module that might cause the issue?* *There is a line mentioning "install the html-xpra package" even though it's installed.* *Any suggestions how to proceed?* ================================================================= ailure on /tmp/.X11-unix/X100: [Errno 2] No such file or directory: '/tmp/.X11-unix/X100' 2022-06-09 22:15:35,050 cannot access python uinput module: 2022-06-09 22:15:35,050 No module named 'uinput' Unable to create /home/username123/.dbus/session-bus 2022-06-09 22:15:36,209 pointer device emulation using XTest 2022-06-09 22:15:36,268 Error: cannot find the html web root 2022-06-09 22:15:36,269 '/usr/local/share/xpra/www' does not exist 2022-06-09 22:15:36,269 install the html-xpra package 2022-06-09 22:15:36,281 Warning: failed to create socket directory '/run/xpra' 2022-06-09 22:15:36,281 [Errno 13] Permission denied: '/run/xpra' 2022-06-09 22:15:36,281 created unix domain socket '/run/user/1000/xpra/y10-100' 2022-06-09 22:15:36,282 cannot create group socket '/run/xpra/y10-100' 2022-06-09 22:15:36,282 [Errno 2] No such file or directory 2022-06-09 22:15:36,282 /run/xpra does not exist 2022-06-09 22:15:36,282 created unix domain socket '/home/username123/.xpra/y10-100' 2022-06-09 22:15:36,293 Warning: failed to load the mdns publisher 2022-06-09 22:15:36,293 No module named 'zeroconf' 2022-06-09 22:15:36,293 either install the 'python-avahi' module 2022-06-09 22:15:36,293 or use the 'mdns=no' option 2022-06-09 22:15:36,306 D-Bus notification forwarding is available 2022-06-09 22:15:36,316 pulseaudio server started with pid 24681 2022-06-09 22:15:36,316 private server socket path: 2022-06-09 22:15:36,316 '/run/user/1000/xpra/pulse-100/pulse/native' (Xpra:24639): Gtk-CRITICAL **: 22:15:36.354: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed 2022-06-09 22:15:36,484 xpra is ready. 2022-06-09 22:15:36,485 xpra X11 seamless version 4.3-r40 64-bit 2022-06-09 22:15:36,498 watching for applications menu changes in: 2022-06-09 22:15:36,498 '/usr/share/ubuntu/applications' 2022-06-09 22:15:36,498 '/usr/local/share/applications' 2022-06-09 22:15:36,498 '/usr/share/applications' 2022-06-09 22:15:36,498 '/var/lib/snapd/desktop/applications' 2022-06-09 22:15:36,516 Warning: webcam forwarding is disabled 2022-06-09 22:15:36,516 the virtual video directory '/sys/devices/virtual/video4linux' was not found 2022-06-09 22:15:36,517 make sure that the 'v4l2loopback' kernel module is installed and loaded 2022-06-09 22:15:36,517 or use the 'webcam=no' option 2022-06-09 22:15:36,517 found 0 virtual video devices for webcam forwarding 2022-06-09 22:15:36,525 printer forwarding enabled using postscript and pdf 2022-06-09 22:15:36,529 started command 'ibus-daemon --xim -v -r --panel=disable' with pid 24693 2022-06-09 22:15:36,540 started command '/etc/X11/Xsession true' with pid 24694 2022-06-09 22:15:36,550 started command 'xterm' with pid 24704 2022-06-09 22:15:36,561 15.6GB of system memory 2022-06-09 22:15:36,585 uid=1000 (username123), gid=1000 (username123) 2022-06-09 22:15:36,585 running with pid 24639 on Linux Ubuntu 18.04 bionic 2022-06-09 22:15:36,586 connected to X11 display :100 with 24 bit colors 2022-06-09 22:15:36,793 No OpenGL information available 2022-06-09 22:15:37,562 loaded 96 start menu entries from 12 sub-menus in 1.1 seconds 2022-06-09 22:15:37,562 Warning: found 1 large icon: 2022-06-09 22:15:37,562 '/snap/code/97/meta/gui/com.visualstudio.code.png' (215 KB) 2022-06-09 22:15:37,562 more bandwidth will be used by the start menu data ====================================================================== *Cheers,* *Yonatan* From antoine at nagafix.co.uk Tue Jun 7 14:45:22 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 7 Jun 2022 20:45:22 +0700 Subject: [winswitch] HTML Client - howto and problems In-Reply-To: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> References: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> Message-ID: <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> On 07/06/2022 12:18, xpra--- via shifter-users wrote: > > Using Xpra 4.3.3 on Kubuntu 20.04....both server and client. > > I am testing out the HTML client to possibly allow for use case when SSH > and X11 is not available, but a web browser is... but I run into some > issues > > 1) Proper server startup ?? > > Following the wiki, man page and numerous sites adding Can you please specify the wiki page so that I can amend it? > --bind-tcp=0.0.0.0:14500 --html=on should do the trick, correct? The html5 client documentation uses port 10000, which is usually free: https://github.com/Xpra-org/xpra-html5#usage > No joy, UNLESS I REMOVE the --bind-tcp option... then the Xpra server > will start. otherwise get an error about already in use on 0.0.0.0 ... That's because the xpra package runs a proxy server on port 14500 so you cannot start another server on the same port. Connecting via the proxy is possible and it should work, but you may want to skip it altogether to simplify things - especially when encountering issues. > So has this changed and the bind is automatic by default????? Or???? > > So I add --html=on to the startup That doesn't make any difference, it is the default. > > xpra start --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 > --start=/home/theprogramIstartup "--env=XPRA_VAAPI=0" is also the default. > That works.... everything starts... I can use xpra-connect and connect.. > good to go on my normal mode... > > 2) Access THE SESSION ABOVE VIA THE HTML5 client > > goto https://1.2.3.4:14500/connect.html > > OK.. get the login box....ok.. > > a) First issue: > > ?Connect option:? "NO SESSIONS FOUND" in red > > > ?I am taking this "connect" option would be what I do via the > xpra_connect setup I have, already, connect up to the running XPRA on > :100 let me see what its doing, etc., disconnect come back to it as > needed.. Thats my use case mostly, check up on a program that runs long > term... > > Is that correct for this connect option??????? This option is similar to what can be done via "xpra sessions". But if the proxy server doesn't see the server you started, it is unlikely to work. > b) Second issue: > > Using the SHADOW OPTION and it gives a drop down, :0, obviously the > desktop thats there.. and then :100 which is the session I STARTED > ABOVE... OK... select shadow and :100 from the drop down... > > Connects up, and after the initial transfer, I get session :0,? NOT > :100.. Doesn't matter how many times I change the dropdown from :0 to > :100 it will NOT CONNECT TO THAT :100 session in shadow > > UMMMM???????? Sounds like a bug. The "xpra start" session on ":100" should have shown up in the "connect" list, not in the "shadow" list. > c) Infinite loop connection > > IF you try the connection LOCALLY ON THE SAME BOX as the server via > HTML5 client in browser, because it is shadowing :0 it just causes an > infinite loop where the browser window just shows that toolbar and just > keeps redrawing it infinitely I'm not 100% sure I understand, but shadowing your own local display does create a sort of nested paint loop. That's expected. > d) The process that won't die! > > This shadow connection starts another xpra server for :0, and it just > WON'T DIE! You can tell it to shutdown via the HTML5 client option, it > doesn't shut down, and when you disconnect you will have 2 XPRA > processes running, the original :100 and this new :0 process, and sudo > kill -9 pid will kill it and then it RESPAWNS... the only way to kill > that is to HARD REBOOT the box! shadow servers don't re-spawn, perhaps it is the proxy server that you're killing - this one is managed as a systemd service and will be re-spawned. > e) Password entry issues > > Seems to get things to connect the first time, I have to enter the > password twice, even if its saved and auto entered by the browser, and > hitting the eye to show it, it is correct, will connect, FAIL > VALIDATION, and then enter it again, or let browser fill in again, and > 2nd time works. shrug It isn't clear what command lines / port / (no?)proxy configuration triggers this, but I haven't seen this particular problem. Connections via the proxy do usually require authentication and the default is to use system authentication. After that, the session itself may also require authentication depending on how you configured it, but I can't remember if those authentication requests can be forwarded through the proxy. > Comments, insights, welcome... Thanks! Cheers, Antoine > > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From xpra at zellners.com Wed Jun 15 13:47:15 2022 From: xpra at zellners.com (xpra at zellners.com) Date: Wed, 15 Jun 2022 05:47:15 -0700 Subject: [winswitch] HTML Client - howto and problems In-Reply-To: <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> References: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> Message-ID: <20220615054715.Horde.LHcqlOOYHeE0P_Oeb49ZgEy@lv-shared03.cpanelplatform.com> Quoting Antoine Martin via shifter-users : > Can you please specify the wiki page so that I can amend it? I used about 10 so or web sites from the GitHub to the xpra.org site, to piece together what should be used... > The html5 client documentation uses port 10000, which is usually free: > https://github.com/Xpra-org/xpra-html5#usage Yeah, that was one of them and then comparing to the numerous other sites saying how to do this.. > That's because the xpra package runs a proxy server on port 14500 so > you cannot start another server on the same port. Is this documented??? Its defeinitely is not something I was aware of that XPRA started this "proxy" And all the other sites around various search results all point to use 14500 and theres even a results which says XPRA got a NANA port officially of 14500, so I take that to mean that the HTML server defaults to 14500, and the tcp bind fails as it starts automaticly... so I remove it from the startup >> xpra start --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 >> :100 --start=/home/theprogramIstartup > "--env=XPRA_VAAPI=0" is also the default. The VAPI may be the default, back when I first started with XPRA this was a requirement to get it work, due to Video card issues.. on the this server.... so I leave it to ensure that things start with what I know works. > > But if the proxy server doesn't see the server you started, it is > unlikely to work. Ok... I have perfect storm where things collide on me using this setup and some changes with that setup... but.. any way... I use: xpra start --bind-tcp=0.0.0.0:10000 --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 --start=/home/TheProgram Start up works.. its running... xpra connect via my xpra_launcher on my desktop -- GOOD! XPRA HTML ---- SUCESS! Glitch... no SSL! Ok... looking at the /var/log... it needs something else for SSL " no certificate paths specified 2022-06-14 13:47:36,069 you must specify an 'ssl-cert' file to use ssl sockets " OK... I don't remember seeing that listed on the HTML examples....no biggie... so based on some digging I think that this startup then would be xpra start --bind-tcp=0.0.0.0:10000 --ssl-cert=/etc/xpra/ssl-cert.pem --ssl=on --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 --start=/home/TheProgram > Sounds like a bug. > The "xpra start" session on ":100" should have shown up in the > "connect" list, not in the "shadow" list. Connecting to the PROXY on 14500 only thing I get is the list in the SHADOW list.. the CONNECT shows: no connections found... I guess I should file a issue/bug at the github on it???? I don't want to file a bug, if there is more a issue with the user as in the startup command.... >> c) Infinite loop connection > I'm not 100% sure I understand, but shadowing your own local display > does create a sort of nested paint loop. That's expected. Yeah... I figure the same.. I included for completeness... and since I missed this whole proxy thing... to start.. just ignore it.. that as you said expected behavior, I agree when you take that into account. > shadow servers don't re-spawn, perhaps it is the proxy server that > you're killing - this one is managed as a systemd service and will > be re-spawned. pgrep gives me two processes when I connect via that proxy.. and after disconnection its still there... I get kill happy when I close out a program and it still has lingering processes... so thats likely the case... it won't be an issue since I know the proxy exists... and I won't be using it any way... >> e) Password entry issues >> I think that is related to the whole proxy thing... using the HTML client things connect... takes the user/pass .. PLBKC Just curious... does the whole AUDIO MISSING pass through to the HTML client from that bug that is fixed in 4.4??? I enabled it in the ADVANCED OPTIONS.. webm:opus... I will play with it some more if should be coming through in the HTML V5.0 client.. maybe I need to find the right codex to use.. I just used the default real quick..... opus, as that I know was used in the regular client... THANKS FOR THE REPLY! Biggest thing is the conflicting info I got.. and use conflated to wrong setup command.. ok... resolved... I can't touch this too much now (MY ISSUE) so I will restart it to enforce SSL use later with the command above... as once I do that, I can forward through the firewall and to the client to access this remotely since I don't have X11 on that one setup I want to use... and I've yet to find any X11 server that is worth anything for Android sadly... From xpra at zellners.com Wed Jun 15 16:15:51 2022 From: xpra at zellners.com (xpra at zellners.com) Date: Wed, 15 Jun 2022 08:15:51 -0700 Subject: [winswitch] HTML Client - howto and problems In-Reply-To: <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> References: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> Message-ID: <20220615081551.Horde.pP9Xle_E0S8N40FXRelA2bD@lv-shared03.cpanelplatform.com> Quoting Antoine Martin via shifter-users : >> 1) Proper server startup ?? >> >> Following the wiki, man page and numerous sites adding > Can you please specify the wiki page so that I can amend it? > >> --bind-tcp=0.0.0.0:14500 --html=on should do the trick, correct? > The html5 client documentation uses port 10000, which is usually free: > https://github.com/Xpra-org/xpra-html5#usage >> xpra start --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 >> :100 --start=/home/theprogramIstartup > "--env=XPRA_VAAPI=0" is also the default. SSL issue now.... Server: 4.3.3 Kubuntu 20.04 XPRA HTML 5.0 Client: 4.3.3 Kubuntu 20.04 w/FF 100.0 using: xpra start --bind-tcp=0.0.0.0:10000 --html=on --ssl-cert=/etc/xpra/ssl-cert.pem --ssl=on --env=XPRA_VAAPI=0 .... FF refuses to connect, doesn't give the option to accept the self signed cert, Check the /var/log.... from tcp socket: 2022-06-15 10:36:04,273 no certificate paths specified 2022-06-15 10:36:04,273 [Errno 13] Permission denied 2022-06-15 10:36:04,281 Error: failed to create SSL socket 2022-06-15 10:36:04,281 from tcp socket: 2022-06-15 10:36:04,281 no certificate paths specified 2022-06-15 10:36:04,282 [Errno 13] Permission denied Ummm, but yes I did spec a path for the cert checking /etc/xpra/ /etc/xpra$ ls -larth total 364K -rw-r--r-- 1 root root 734 May 18 2021 xpra.conf -rw-r--r-- 1 root root 151K May 18 2021 xorg-uinput.conf -rw-r--r-- 1 root root 674 May 18 2021 cuda.conf -rw------- 1 root root 3.2K Jul 3 2021 key.pem -rw-r--r-- 1 root root 2.0K Jul 3 2021 cert.pem -rw------- 1 root root 5.2K Jul 3 2021 ssl-cert.pem -rw-r--r-- 1 root root 151K Aug 9 2021 xorg.conf drwxr-xr-x 2 root root 4.0K Jun 1 15:32 html5-client drwxr-xr-x 2 root root 4.0K Jun 1 15:39 conf.d drwxr-xr-x 2 root root 4.0K Jun 1 15:39 content-categories drwxr-xr-x 2 root root 4.0K Jun 1 15:39 content-type drwxr-xr-x 2 root root 4.0K Jun 1 15:39 http-headers drwxr-xr-x 7 root root 4.0K Jun 1 15:39 . drwxr-xr-x 138 root root 12K Jun 1 15:40 .. Yes, ssl-cert.pem has a cert in it, not posting it for obvious reasons... Should this stuff really be owned by root???????? Shrug????? From antoine at nagafix.co.uk Fri Jun 17 13:10:05 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 17 Jun 2022 19:10:05 +0700 Subject: [winswitch] FAO gmail users Message-ID: <9d9cb2e1-e5c0-5af4-4143-549822db7cbc@nagafix.co.uk> Hi, gmail had bounced this list reply which was quite interesting: https://lists.devloop.org.uk/pipermail/shifter-users/2022-June/002921.html The response from gmail's support system is only mildly amusing however: https://github.com/Xpra-org/xpra/issues/3555 The mailing list has been in "emergency moderation" since one spammy message got through a few years ago. This will continue and messages will be throttled to prevent triggering gmail's oversensitive filters. Please be patient when posting or waiting for replies. Cheers, Antoine From xpra at jubileegroup.co.uk Fri Jun 17 17:09:21 2022 From: xpra at jubileegroup.co.uk (G.W. Haywood) Date: Fri, 17 Jun 2022 17:09:21 +0100 (BST) Subject: [winswitch] FAO gmail users In-Reply-To: <9d9cb2e1-e5c0-5af4-4143-549822db7cbc@nagafix.co.uk> References: <9d9cb2e1-e5c0-5af4-4143-549822db7cbc@nagafix.co.uk> Message-ID: Hi there, On Fri, 17 Jun 2022, Antoine Martin via shifter-users wrote: > gmail had bounced this list reply which was quite interesting: > https://lists.devloop.org.uk/pipermail/shifter-users/2022-June/002921.html Google is amongst the top three spam sources I have to deal with (one significant other being Microsoft). Avoid. > The response from gmail's support system is only mildly amusing however: > https://github.com/Xpra-org/xpra/issues/3555 Quoting you, from that page: > On two more occasions, they asked again that I talked to my "email > provider". Either this was a different person who had not read the > earlier discussion, or just forgotten about it? I doubt that Google considers you suffucuently important for them to spend money on letting you talk to a person. -- 73, Ged. From antoine at nagafix.co.uk Sun Jun 19 15:38:03 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 19 Jun 2022 21:38:03 +0700 Subject: [winswitch] [xpra] xpra-html how to In-Reply-To: References: Message-ID: <92b63624-1b48-0b19-700e-fe6239c94d13@nagafix.co.uk> On 10/06/2022 02:29, yonatan zaken via shifter-users wrote: > Hi, > > xpra v4.3-r40 That versions is too old. > Ubuntu 18.04.6 LTS > > I cloned xpra-html5 to my home directory and installed as mentioned: > https://github.com/Xpra-org/xpra-html5 The very next line on that page states: "On Linux, this will install the html5 client in /usr/share/xpra/www which is where the xpra server expects to find it." > And I run the following in terminal: > xpra start --start=xterm --bind-tcp=127.0.0.1:10000 > Standard output shows: > ================================================= > Entering daemon mode; any further errors will be reported to: > /run/user/1000/xpra/S23615.log > Actual display used: :2 > Actual log file name is now: /run/user/1000/xpra/:2.log > ================================================= > > Then I run in terminal: > xdg-open http://localhost:10000 > And a chrome window opens with the following: > ================================================== > Server Error > > Error code 400. > > Message: this port does not support HTTP requests. > > Error code explanation: 400 = Bad request syntax or unsupported method. > ================================================== > > This is my log output: > Quite hard to follow, Most of these messages are documented in the FAQ: https://github.com/Xpra-org/xpra/blob/master/docs/FAQ.md > *Is it the uinput missing module that might cause the issue?* No. > *There is a line mentioning "install the html-xpra package" even though > it's installed.* > *Any suggestions how to proceed?* Yes, see below > ================================================================= > ailure on /tmp/.X11-unix/X100: [Errno 2] No such file or directory: > '/tmp/.X11-unix/X100' > 2022-06-09 22:15:35,050 cannot access python uinput module: > 2022-06-09 22:15:35,050 No module named 'uinput' > Unable to create /home/username123/.dbus/session-bus > 2022-06-09 22:15:36,209 pointer device emulation using XTest > 2022-06-09 22:15:36,268 Error: cannot find the html web root > 2022-06-09 22:15:36,269 '/usr/local/share/xpra/www' does not exist > 2022-06-09 22:15:36,269 install the html-xpra package Solutions: * install xpra from an official package, which will put it in the correct place and look for the html5 client in "/usr/share/xpra/www". * install xpra-html5 manually in `/usr/local`: ./setup.py install / /usr/local/share/xpra/www/ * just copy /usr/share/xpra/www to /usr/local/share/xpra/www (or symlink it there) (..) Cheers, Antoine From antoine at nagafix.co.uk Mon Jun 20 06:05:11 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 20 Jun 2022 12:05:11 +0700 Subject: [winswitch] HTML Client - howto and problems In-Reply-To: <20220615054715.Horde.LHcqlOOYHeE0P_Oeb49ZgEy@lv-shared03.cpanelplatform.com> References: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> <20220615054715.Horde.LHcqlOOYHeE0P_Oeb49ZgEy@lv-shared03.cpanelplatform.com> Message-ID: On 15/06/2022 19:47, xpra--- via shifter-users wrote: > > Quoting Antoine Martin via shifter-users > : > > >> Can you please specify the wiki page so that I can amend it? > > I used about 10 so or web sites from the GitHub to the xpra.org site, to > piece together what should be used... Most of the web sites out there contain instructions that are either completely out of date (ie: using `DISPLAY=:7 xterm`) or just plain wrong. >> That's because the xpra package runs a proxy server on port 14500 so >> you cannot start another server on the same port. > > Is this documented??? Its defeinitely is not something I was aware of > that XPRA started this "proxy" https://github.com/Xpra-org/xpra/blob/master/docs/Usage/Proxy-Server.md > And all the other sites around various search results all point to use > 14500 and theres even a results which says XPRA got a NANA port > officially of 14500, so I take that to mean that the HTML server > defaults to 14500, and the tcp bind fails as it starts automaticly... > so I remove it from the startup 14500 has been the default port for the xpra service since 2016: https://github.com/Xpra-org/xpra/issues/731#issuecomment-765427947 (..) >> But if the proxy server doesn't see the server you started, it is >> unlikely to work. > > Ok... I have perfect storm where things collide on me using this setup > and some changes with that setup... but.. any way... > > I use: > > xpra start --bind-tcp=0.0.0.0:10000 --html=on --env=XPRA_VAAPI=0 > --env=CUTTER_THRESHOLD=0 :100 --start=/home/TheProgram > > Start up works.. its running... > xpra connect via my xpra_launcher on my desktop -- GOOD! > XPRA HTML ---- SUCESS! > Glitch... no SSL! > > Ok... looking at the /var/log... it needs something else for SSL > > " no certificate paths specified > 2022-06-14 13:47:36,069? you must specify an 'ssl-cert' file to use ssl > sockets > " > > OK... I don't remember seeing that listed on the HTML examples....no > biggie... No, it is not listed. The examples given are designed to be as simple as possible. (and SSL generally isn't really "simple") > so based on some digging I think that this startup then would be > > xpra start --bind-tcp=0.0.0.0:10000 --ssl-cert=/etc/xpra/ssl-cert.pem > --ssl=on --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 > --start=/home/TheProgram This should not work as the SSL key installed with the packages should only be readable by root. (see next reply) >> Sounds like a bug. >> The "xpra start" session on ":100" should have shown up in the >> "connect" list, not in the "shadow" list. > > Connecting to the PROXY on 14500 only thing I get is the list in the > SHADOW list.. the CONNECT shows: no connections found... I guess I > should file a issue/bug at the github on it???? I don't want to file a > bug, if there is more a issue with the user as in the startup command.... Any session started should be visible to the proxy server and should be exposed through the html5 UI. (..) >> shadow servers don't re-spawn, perhaps it is the proxy server that >> you're killing - this one is managed as a systemd service and will be >> re-spawned. > > pgrep gives me two processes when I connect via that proxy.. and after > disconnection its still there... I get kill happy when I close out a > program and it still has lingering processes... so thats likely the > case... it won't be an issue since I know the proxy exists... and I > won't be using it any way... Then you may want to just turn it off. The proxy server is a socket activated process which will remain available once it is stated. The other is likely to be the proxy instance for the connection you're making. It should terminate when the connection is closed. >>> e) Password entry issues >>> > > I think that is related to the whole proxy thing... using the HTML > client things connect... takes the user/pass .. PLBKC > > Just curious... does the whole AUDIO MISSING pass through to the HTML > client from that bug that is fixed in 4.4??? I enabled it in the > ADVANCED OPTIONS.. webm:opus... I will play with it some more if should > be coming through in the HTML V5.0 client.. maybe I need to find the > right codex to use.. I just used the default real quick..... opus, as > that I know was used in the regular client... There is an audio bug in the 4.3.x series which is fixed in the upcoming 4.3.4 release. Perhaps try the 4.4 or 4.3.4 builds from the beta channel. > > THANKS FOR THE REPLY! > > Biggest thing is the conflicting info I got.. and use conflated to wrong > setup command.. ok... resolved... Sadly, this is not the first time people get misled by invalid instructions. Cheers, Antoine > I can't touch this too much now (MY ISSUE) so I will restart it to > enforce SSL use later with the command above... as once I do that, I can > forward through the firewall and to the client to access this remotely > since I don't have X11 on that one setup I want to use... and I've yet > to find any X11 server that is worth anything for Android sadly... > > > _______________________________________________ > 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 Mon Jun 20 08:39:28 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 20 Jun 2022 14:39:28 +0700 Subject: [winswitch] SSL issue (was HTML Client - howto and problems) In-Reply-To: <20220615081551.Horde.pP9Xle_E0S8N40FXRelA2bD@lv-shared03.cpanelplatform.com> References: <20220606221811.Horde.0-v8rAmgPhsR8pxei9oVW0E@lv-shared03.cpanelplatform.com> <16df77b3-42fe-a070-8e18-b29b3d850f61@nagafix.co.uk> <20220615081551.Horde.pP9Xle_E0S8N40FXRelA2bD@lv-shared03.cpanelplatform.com> Message-ID: >>> --bind-tcp=0.0.0.0:14500 --html=on should do the trick, correct? >> The html5 client documentation uses port 10000, which is usually free: >> https://github.com/Xpra-org/xpra-html5#usage >>> xpra start --html=on --env=XPRA_VAAPI=0 --env=CUTTER_THRESHOLD=0 :100 >>> --start=/home/theprogramIstartup >> "--env=XPRA_VAAPI=0" is also the default. > > SSL issue now.... > > Server: 4.3.3 Kubuntu 20.04 XPRA HTML 5.0 > Client: 4.3.3 Kubuntu 20.04 w/FF 100.0 > > > using: > > xpra start --bind-tcp=0.0.0.0:10000 --html=on > --ssl-cert=/etc/xpra/ssl-cert.pem --ssl=on --env=XPRA_VAAPI=0 .... You're trying to use the SSL certificate which is generated for the system wide proxy service, which runs as root. Making this certificate world readable would allow anyone with access to the file to decrypt all SSL traffic used by this service. > FF refuses to connect, doesn't give the option to accept the self signed > cert, > > Check the /var/log.... > > ?from tcp socket: type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.0.z', 10000), > raddr=('192.168.0.z', 39584)> > 2022-06-15 10:36:04,273? no certificate paths specified > 2022-06-15 10:36:04,273? [Errno 13] Permission denied > 2022-06-15 10:36:04,281 Error: failed to create SSL socket > 2022-06-15 10:36:04,281? from tcp socket: family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, > laddr=('192.168.0.z', 10000), raddr=('192.168.0.z', 39586)> > 2022-06-15 10:36:04,281? no certificate paths specified > 2022-06-15 10:36:04,282? [Errno 13] Permission denied > > Ummm, but yes I did spec a path for the cert Yes, but not a valid one. "Permission denied" > checking /etc/xpra/ > > /etc/xpra$ ls -larth (..) > -rw-------?? 1 root root 5.2K Jul? 3? 2021 ssl-cert.pem (..) > > Yes, ssl-cert.pem has a cert in it, not posting it for obvious reasons... > > Should this stuff really be owned by root???????? Yes. Users should not share SSL certificates. More information here: https://github.com/Xpra-org/xpra/blob/master/docs/Network/SSL.md Cheers, Antoine > > Shrug????? > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From totaam at xpra.org Tue Jun 21 16:55:59 2022 From: totaam at xpra.org (Antoine Martin) Date: Tue, 21 Jun 2022 22:55:59 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 4.3.4 - many bugs, some important Message-ID: Hi, A number of major bug fixes are included in this release, but those all required quite specific commands, clients or steps to trigger. So unless you were affected by these issues, there is no urgency to update. (though it is still strongly recommended) The more detailed release notes can be found here: https://github.com/Xpra-org/xpra/releases/tag/v4.3.4 Downloads: https://github.com/Xpra-org/xpra/wiki/Download Cheers Antoine From totaam at xpra.org Mon Jun 27 14:27:54 2022 From: totaam at xpra.org (Antoine Martin) Date: Mon, 27 Jun 2022 20:27:54 +0700 Subject: [winswitch] [ANNOUNCE] Xpra LTS 3.1.3 : accumulated fixes Message-ID: <32af55df-892d-112d-9c56-de040ab4d71e@xpra.org> Hi, This update to the LTS+1 branch includes all the fixes that had accumulated over the past 8 months since the 3.1.2 release. There are a lot of fixes in there and some are quite important. But please bear in mind that unless your OS is unable to run newer versions (ie: Python2 systems like CentOS 7.x), you should not be running this version in production. The MacOS builds are still in reasonably good shape since we control the full set of libraries used on that platform. The MS Windows builds are now locked with whatever library versions were available during the last MSYS2 update that was still compatible with this branch. Only the "client" builds can still be generated on MS Windows. I chose to continue to include these builds because they can still be useful when checking for regressions. A new LTS version will replace this branch, hopefully by the end of the year, at which point the 3.x series will be abandoned. The more detailed release notes can be found here: https://github.com/Xpra-org/xpra/releases/tag/v3.1.3 Downloads: https://github.com/Xpra-org/xpra/wiki/Download Cheers, Antoine From totaam at xpra.org Mon Jun 27 15:00:47 2022 From: totaam at xpra.org (Antoine Martin) Date: Mon, 27 Jun 2022 21:00:47 +0700 Subject: [winswitch] RHEL / CentOS 8 and the clones Message-ID: <016f087d-59cb-74e6-b017-35e8ef884192@xpra.org> Hi, The xpra build system can now generate packages for most of the clones / derived distributions: * OracleLinux * AlmaLinux * RockyLinux * CentOS stream8 The last two xpra releases (4.3.4 and 3.1.3) included packages for all of the above, including some arm64 builds. The first three do generate identical binaries which is comforting. For the time being, the "RedHat" download link continues to be a symbolic link to the CentOS packages. The problem with this is that there are no CentOS 8.6 builds. At present, the packages we rely on in RHEL 8.6 are still ABI compatible with 8.5 so this is not a big problem, yet. So rather than choosing which distribution to use as a replacement for the now defunct CentOS 8, I have left things unchanged. But this may have to be changed when 8.7 (or later) is released. Which clone should replace CentOS as the "one true clone" is not clear at this point and would only be changed for the ">=8.6" series and perhaps also "9.x", but not the "7" and older builds. (making the repository link maintenance more difficult than it already is) If you have suggestions or opinions on what should be done, feel free to chime in - here, on IRC or on github issues. Cheers, Antoine