From antoine at nagafix.co.uk Sun Jun 11 17:49:22 2023 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 11 Jun 2023 23:49:22 +0700 Subject: [winswitch] Xpra start applications as a new session In-Reply-To: <896134415.42482306.1685458000179.JavaMail.zimbra@telenet.be> References: <896134415.42482306.1685458000179.JavaMail.zimbra@telenet.be> Message-ID: On 30/05/2023 21:46, svhb via shifter-users wrote: > Hello, > > I want to use xpra to serve an application from a server to some clients, but everyone has to see a newly started up version of the application. The application is a special calculator for material properties, and to prevent updates on every single system, using Xpra to show the application in a browser can be a perfect solution. > However, if I try to login with a second browser, the first login exits.. To allow multiple clients to connect to *the same* session, use the `sharing` option. When sharing is not enabled, new clients steal the session from the current one which is disconnected. > I need multiple instances, if possible spawned right after connecting > > Are there some settings/configuration I can do the realize this? Yes, many. Which one is right for you depends on a number of things. OTOH: user density, hardware available, security concerns, reliability desired, type of application, etc. If you can manage ports and / or user accounts and give each user a different URL to connect to, then you can simply spawn new instances as needed. (or even have a pool of sessions pre-launched, ready to be used) If you want to use the same URL for all the clients, things are a bit more difficult, but not impossible. You could use some sort of apache or nginx proxy that does the allocation. Or you could use xpra's builtin proxy server to spawn new sessions on demand by configuring it with the `allow` authentication and a matching "start-new-session" URL request. The type of application matters: some applications don't mind running multiple instances under the same user account, others won't work properly, some will just refuse to run that way... Cheers, Antoine > > Thanks in a advance, > > Stefaan. > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From wssddc at wssddc.com Thu Jun 15 06:32:00 2023 From: wssddc at wssddc.com (Bob Babcock) Date: Thu, 15 Jun 2023 01:32:00 -0400 Subject: [winswitch] Xpra shadow with Fedora 38 Message-ID: I did a fresh install of Fedora 38 KDE using nouveau video drivers. (Previously I was running Fedora 37 with 390xx proprietary drivers for my old video card.)? At login, I now have the option of using Plasma X11 or Wayland.? I find xpra shadow doesn't send back anything to Windows 10 even if I picked X11 when logging on to Fedora.? Start also fails, but start-desktop works. Is this expected behavior?? Thanks. From totaam at xpra.org Fri Jun 16 17:23:36 2023 From: totaam at xpra.org (Antoine Martin) Date: Fri, 16 Jun 2023 23:23:36 +0700 Subject: [winswitch] [ANNOUNCE] new Xpra GPG key Message-ID: <8450cbc1-fc8a-6622-9225-477856b1b7f4@xpra.org> Hi, As many of you have noticed, the GPG key used for signing the packages and repositories had expired. Although that key's expiry date was updated to be able to continue to use all the files that had already been signed, it seemed like a good time to use a brand new key: a stronger, better one, and one that belonged to the project rather being tied to my personal keychain. After many delays and false starts, this new key is now live for all the repositories. New installations following the download instructions should be seamless. Here is how you update your systems to use the new key: * Ubuntu and Debian systems using the old "xpra.list" sources.list.d files: wget -qO - https://xpra.org/xpra-2023.asc | sudo apt-key add - * Ubuntu and Debian systems using the new "xpra.sources" sources.list.d files: sudo wget -O "/usr/share/keyrings/xpra.asc" https://xpra.org/xpra.asc * RPM distributions: sudo rpm --import https://xpra.org/xpra.asc If you prefer not to use global rpm import, you can edit your existing repository file to point to: https://xpra.org/xpra-2023.asc (dnf will only download the new key if the key's URL is modified) I have made it coincide with new releases so that this key is only used with the newer packages going forward. All the packages signed using the previous key have been moved to the vault (~150GB): https://xpra.org/vault/ They will be kept around on this read-only storage for a while and eventually moved to offline storage. Following this email, I will be sending release announcements for: * xpra 4.4.6 * xpra 3.1.5 * xpra-html5 8.1 * xpra-html5 5.3 Most of the packages are already available, except for some of the arm64 builds which may take a few more days to complete. If you are still having issues with the GPG, key please see here: https://github.com/Xpra-org/xpra/issues/3863#issuecomment-1589560042 And create new github issues as needed, specifying your full distribution version, installation method, error messages, etc But please wait 24 hours for the full rebuild + repository sync to complete. Cheers Antoine Here is the new key "0x73254CAD17978FAF": pub?? rsa4096 2023-06-10 [SC] [expires: 2033-06-07] ????? B499 3B57 3231 48E3 7977? E5D8 7325 4CAD 1797 8FAF uid????????????????????? Xpra It is available here: https://xpra.org/xpra.gpg https://xpra.org/xpra.asc And on keyservers: https://keyserver.ubuntu.com/pks/lookup?search=0x73254CAD17978FAF&op=index https://pgp.mit.edu/pks/lookup?search=0x73254CAD17978FAF&op=index From totaam at xpra.org Tue Jun 20 16:02:00 2023 From: totaam at xpra.org (Antoine Martin) Date: Tue, 20 Jun 2023 22:02:00 +0700 Subject: [winswitch] [ANNOUNCE] Xpra LTS 3.1.5 : many fixes, at least 2 critical Message-ID: <3b3ad3a3-2565-a32b-48c4-5bc77e5240fa@xpra.org> Hi, This new release from the 3.1.x branch is not just there to ensure that there are binaries signed with the new GPG key available for all supported platforms, there are actually some major fixes in there too: * the same GLib server crash also fixed in the last 4.4.x release * a regression with html5 clients connecting to Python2 servers * system tray and focus fixes * crashes and launch errors on MS Windows * lots of builds fixes, workarounds and tweaks * some visual corruption with delta encoding (now disabled) If you are still stuck on this older branch (ie: RHEL7 and clones), updating is strongly recommended. The more detailed release notes can be found here: https://github.com/Xpra-org/xpra/releases/tag/v3.1.5 Downloads: https://github.com/Xpra-org/xpra/wiki/Download Cheers, Antoine From totaam at xpra.org Tue Jun 20 16:15:41 2023 From: totaam at xpra.org (Antoine Martin) Date: Tue, 20 Jun 2023 22:15:41 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 4.4.6: a few minor client-side issues Message-ID: <8684018b-31b6-c2fa-332e-35b043fa9bef@xpra.org> Hi, This update to the v4.x branch fixes a few issues. These are mostly platform specific and client side, in particular: * an OpenGL sanity check regression introduced in 4.4.5, which caused the clients to run without OpenGL acceleration * an annoying client-side focus issue has finally been solved * missing system tray on Linux and Wayland Everything else is all fairly minor, there is no urgency to update if you were not affected. The detailed release notes can be found here: https://github.com/Xpra-org/xpra/releases/tag/v4.4.6 Downloads: https://github.com/Xpra-org/xpra/wiki/Download Cheers, Antoine