From thanhnt51 at techcombank.com.vn Tue Sep 13 09:41:20 2022 From: thanhnt51 at techcombank.com.vn (Thanh IT. Nguyen Trung) Date: Tue, 13 Sep 2022 08:41:20 +0000 Subject: [winswitch] High server memory usage for a simple app Message-ID: /usr/bin/python2 /bin/xpra --version xpra v3.1.2-r25 uname -a Linux dev-server 3.10.0-1160.45.1.el7.x86_64 #1 SMP Fri Sep 24 10:17:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server 7.9 (Maipo) I am testing the simple xclock application and find that with each connection to the server, it uses about 400MB of RAM Here is the CLIENT command: xpra start ssh://myuser:mypassword at myserver.com ^ --encoding=jpeg --speaker=disabled --microphone=disabled --env=XPRA_SCROLL_ENCODING=0 --use-display=auto ^ --env=remoteuser=%username% --html=no --dpi=120 --idle-timeout=3600 --exit-with-client=yes ^ --exit-with-children=yes --start-child=xclock--opengl=no --quality=80 --lock=yes What I've tried so far: 1. Disabling microphone and audio 2. Using encoding=jpeg 3. Edit /etc/xpra/xorg.conf to use a smaller value of VideoRam = 256000 instead of the default value of 768000 4. In addition, the manual document says: "The xpra server allocates an over-large framebuffer when using Xvfb; this wastes memory." On our server, it seems that Xpra is using Xdummy (another guy installed this). I don't know how to disable Xvfb and not sure if should I disable it or not. In conclusion, my question is: How can I reduce the amount of RAM that server uses for each connection. Because we have a lot of users need to connect to the server at the same time. Thank you! **************************************************************************************************************************************************************************** This e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. T?nh ri?ng t? c?a th? ?i?n t? n?y c? th? ???c b?o v? v? m?t ph?p l?. N?u qu? v? kh?ng ph?i l? ng??i ch? ??nh ???c nh?n v? ???c s? d?ng, ?? ngh? kh?ng sao ch?p, chuy?n ti?p, ti?t l? ho?c s? d?ng b?t k? n?i dung hay file ??nh k?m n?o trong th? ?i?n t? n?y. N?u qu? v? nh?n ???c th? ?i?n t? n?y do l?i trong qu? tr?nh g?i, ?? ngh? x?a th? ?? v? t?t c? c?c b?n sao trong h? th?ng c?a qu? v?, ??ng th?i th?ng b?o cho ng??i g?i th? ngay l?p t?c. Th?ng tin li?n l?c qua Internet kh?ng th? ??m b?o k?p th?i, an to?n, kh?ng b? l?i hay kh?ng c? virus, do v?y ng??i g?i kh?ng ch?u tr?ch nhi?m ??i v?i b?t k? l?i ho?c thi?u s?t n?o. **************************************************************************************************************************************************************************** **************************************************************************************************************************************************************************** This e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. T?nh ri?ng t? c?a th? ?i?n t? n?y c? th? ???c b?o v? v? m?t ph?p l?. N?u qu? v? kh?ng ph?i l? ng??i ch? ??nh ???c nh?n v? ???c s? d?ng, ?? ngh? kh?ng sao ch?p, chuy?n ti?p, ti?t l? ho?c s? d?ng b?t k? n?i dung hay file ??nh k?m n?o trong th? ?i?n t? n?y. N?u qu? v? nh?n ???c th? ?i?n t? n?y do l?i trong qu? tr?nh g?i, ?? ngh? x?a th? ?? v? t?t c? c?c b?n sao trong h? th?ng c?a qu? v?, ??ng th?i th?ng b?o cho ng??i g?i th? ngay l?p t?c. Th?ng tin li?n l?c qua Internet kh?ng th? ??m b?o k?p th?i, an to?n, kh?ng b? l?i hay kh?ng c? virus, do v?y ng??i g?i kh?ng ch?u tr?ch nhi?m ??i v?i b?t k? l?i ho?c thi?u s?t n?o. **************************************************************************************************************************************************************************** From mcouteau3307 at gmail.com Tue Sep 13 20:46:31 2022 From: mcouteau3307 at gmail.com (Mark Couteau) Date: Tue, 13 Sep 2022 14:46:31 -0500 Subject: [winswitch] public keys Message-ID: <1cd788f9-cf62-6a13-c656-4618cdc64515@twc.com> Hello List: I keep having a failure to update from the xpra software server due to a public key issue. I'm not very familiar with this sort of thing. Here is the error message from the apt update command on Linux Mint 21 Vanessa. Hit:9 https://xpra.org jammy InRelease Err:9 https://xpra.org jammy InRelease ? The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 18ADB31CF18AD6BB Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://xpra.org jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 18ADB31CF18AD6BB W: Failed to fetch https://xpra.org/dists/jammy/InRelease? The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 18ADB31CF18AD6BB W: Some index files failed to download. They have been ignored, or old ones used instead. Any help is appreciated. From totaam at xpra.org Thu Sep 15 15:24:02 2022 From: totaam at xpra.org (Antoine Martin) Date: Thu, 15 Sep 2022 21:24:02 +0700 Subject: [winswitch] High server memory usage for a simple app In-Reply-To: References: Message-ID: <703e4a69-38d6-6761-39d0-6b654f6d3efb@xpra.org> On 13/09/2022 15:41, Thanh IT. Nguyen Trung via shifter-users wrote: > /usr/bin/python2 /bin/xpra --version > xpra v3.1.2-r25 This version is out of date. > uname -a > Linux dev-server 3.10.0-1160.45.1.el7.x86_64 #1 SMP Fri Sep 24 10:17:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > > Red Hat Enterprise Linux Server 7.9 (Maipo) > > I am testing the simple xclock application and find that with each connection to the server, it uses about 400MB of RAM Which process owns this 400MB of RAM? Is it the xpra server or the Xorg process? Assuming that it is the xpra server process, have a look at: xpra info | grep memory And bear in mind that shared memory... is shared. So multiple xpra servers all sharing the same libraries and executables will not be using as much memory as you think. > Here is the CLIENT command: > xpra start ssh://myuser:mypassword at myserver.com ^ > --encoding=jpeg "encoding=jpeg" : don't do that. > --speaker=disabled --microphone=disabled --env=XPRA_SCROLL_ENCODING=0 --use-display=auto ^ "use-display=auto" is not a valid option with xpra 3.x > --env=remoteuser=%username% --html=no --dpi=120 --idle-timeout=3600 --exit-with-client=yes ^ > --exit-with-children=yes --start-child=xclock--opengl=no --quality=80 "quality=80" is a terrible idea, don't do that. Set "min-quality" instead, or just leave it alone. --lock=yes > > What I've tried so far: > 1. Disabling microphone and audio This helps. > 2. Using encoding=jpeg This does not. > 3. Edit /etc/xpra/xorg.conf to use a smaller value of VideoRam = 256000 instead of the default value of 768000 This should help. > 4. In addition, the manual document says: "The xpra server allocates an over-large framebuffer when using Xvfb; this wastes memory." > On our server, it seems that Xpra is using Xdummy (another guy installed this). This is the default. > I don't know how to disable Xvfb and not sure if should I disable it or not. Assuming that the memory belongs to Xorg, try to switch to Xvfb to see if it makes much of a difference. See /etc/xpra/conf.d/55_server_x11.conf > In conclusion, my question is: How can I reduce the amount of RAM that server uses for each connection. Because we have a lot of users need to connect to the server at the same time. Turn off every xpra subsystem and only enable the ones you actually need. In particular, turn off: * video encoders * csc modules * mmap etc The results can be seen in these tickets: * for the client: https://github.com/Xpra-org/xpra/issues/1861#issuecomment-765499403 * for the server: https://github.com/Xpra-org/xpra/issues/1838 Newer versions do this more effectively too, though you won't be able to use them on RHEL 7. If you still cannot find a solution, please create a github issue. Cheers, Antoine > > Thank you! From totaam at xpra.org Thu Sep 15 15:33:29 2022 From: totaam at xpra.org (Antoine Martin) Date: Thu, 15 Sep 2022 21:33:29 +0700 Subject: [winswitch] public keys In-Reply-To: <1cd788f9-cf62-6a13-c656-4618cdc64515@twc.com> References: <1cd788f9-cf62-6a13-c656-4618cdc64515@twc.com> Message-ID: On 14/09/2022 02:46, Mark Couteau via shifter-users wrote: > Hello List: > > I keep having a failure to update from the xpra software server due to a > public key issue. > > I'm not very familiar with this sort of thing. > > Here is the error message from the apt update command on Linux Mint 21 > Vanessa. > > Hit:9 https://xpra.org jammy InRelease > Err:9 https://xpra.org jammy InRelease > ? The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 18ADB31CF18AD6BB > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > All packages are up to date. > W: An error occurred during the signature verification. The repository > is not updated and the previous index files will be used. GPG error: > https://xpra.org jammy InRelease: The following signatures couldn't be > verified because the public key is not available: NO_PUBKEY > 18ADB31CF18AD6BB > W: Failed to fetch https://xpra.org/dists/jammy/InRelease? The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 18ADB31CF18AD6BB > W: Some index files failed to download. They have been ignored, or old > ones used instead. > > Any help is appreciated. You have not specified how you installed xpra or which GPG keys you have imported. Did you follow the instructions here: https://github.com/Xpra-org/xpra/wiki/Download#-for-debian-based-distributions Or something else? The gory details explaining why we now have 2 different sets of keys for signing the packages is explained here: https://github.com/Xpra-org/xpra/issues/3499#issuecomment-1077136429 Cheers, Antoine From mcouteau3307 at gmail.com Thu Sep 15 15:54:50 2022 From: mcouteau3307 at gmail.com (Mark Couteau) Date: Thu, 15 Sep 2022 09:54:50 -0500 Subject: [winswitch] public keys In-Reply-To: References: <1cd788f9-cf62-6a13-c656-4618cdc64515@twc.com> Message-ID: <96dcd748-eaf3-7834-2ca2-e3e12e8613cf@twc.com> Thank you. The detailed instructions on the page fixed it. I did get a configured multiple times warning, but was able to remove xpra from /etc/apt/sources.list.d/additional-repositories.list and it went away. My distro is Jammy. for reference: Step by step example for installing the stable repository on Ubuntu Focal Fossa |DISTRO=jammy #install https support for apt (which may be installed already): sudo apt-get update sudo apt-get install apt-transport-https software-properties-common sudo apt install ca-certificates # add Xpra GPG key(s) sudo wget -O "/usr/share/keyrings/xpra-2022.gpg" https://xpra.org/xpra-2022.gpg # older distributions may also need: # sudo wget -O "/usr/share/keyrings/xpra-2018.gpg" https://xpra.org/xpra-2018.gpg # add Xpra repository wget -O "/etc/apt/sources.list.d/xpra.list" https://xpra.org/repos/$DISTRO/xpra.list # optional beta channel: # wget -O "/etc/apt/sources.list.d/xpra-beta.list" https://xpra.org/repos/$DISTRO/xpra-beta.list # install Xpra package sudo apt-get update sudo apt-get install xpra | For other distributions, simply change |DISTRO| to match your distribution name. MEC On 9/15/22 09:33, Antoine Martin via shifter-users wrote: > On 14/09/2022 02:46, Mark Couteau via shifter-users wrote: > > Hello List: > > > > I keep having a failure to update from the xpra software server due > to a > > public key issue. > > > > I'm not very familiar with this sort of thing. > > > > Here is the error message from the apt update command on Linux Mint 21 > > Vanessa. > > > > Hit:9 https://xpra.org jammy InRelease > > Err:9 https://xpra.org jammy InRelease > >? ? The following signatures couldn't be verified because the public key > > is not available: NO_PUBKEY 18ADB31CF18AD6BB > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > All packages are up to date. > > W: An error occurred during the signature verification. The repository > > is not updated and the previous index files will be used. GPG error: > > https://xpra.org jammy InRelease: The following signatures couldn't be > > verified because the public key is not available: NO_PUBKEY > > 18ADB31CF18AD6BB > > W: Failed to fetch https://xpra.org/dists/jammy/InRelease? The > following > > signatures couldn't be verified because the public key is not > available: > > NO_PUBKEY 18ADB31CF18AD6BB > > W: Some index files failed to download. They have been ignored, or old > > ones used instead. > > > > Any help is appreciated. > You have not specified how you installed xpra or which GPG keys you have > imported. > Did you follow the instructions here: > https://github.com/Xpra-org/xpra/wiki/Download#-for-debian-based-distributions > > Or something else? > > The gory details explaining why we now have 2 different sets of keys for > signing the packages is explained here: > https://github.com/Xpra-org/xpra/issues/3499#issuecomment-1077136429 > > Cheers, > Antoine > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users From lamikr at pilppa.org Mon Sep 19 22:43:49 2022 From: lamikr at pilppa.org (Mika Laitio) Date: Tue, 20 Sep 2022 00:43:49 +0300 (EEST) Subject: [winswitch] new user questions for xpra Message-ID: <8cba75b-ce5a-4692-9f31-eb3df2fde0ce@pilppa.org> Hi I am new user trying the xpra and I have couple of questions. I amd using Mageia Linux 8 and my python version is 3.8.12. I have installed the latest xpra from sources with command: python3 ./setup.py install --user 1) I try to execute the xpra with following command to connect to another computer on ip 192.168.1.31 that is also running the mageia 8: xpra start ssh://lamikr at 192.168.1.31 --start-child=xterm but I am getting following error xpra initialization error: invalid value for sync_xvfb: None int() argument must be a string, a bytes-like object or a number, not 'NoneType' Should I use some different python version. (I know python is very incompatible between different versions) 2) Do I need to install xpra also to computer that I try to connect or is xpra deploying somekind of runtime app to host machine during the connection? https://github.com/Xpra-org/xpra/blob/master/docs/Usage/README.md does not really mention anything about install requirements 3) Will xpra work with wayland + xwayland compination installed or do I need to run either the host or client machine on X11 desktop session? Mika From totaam at xpra.org Tue Sep 20 11:54:58 2022 From: totaam at xpra.org (Antoine Martin) Date: Tue, 20 Sep 2022 17:54:58 +0700 Subject: [winswitch] new user questions for xpra In-Reply-To: <8cba75b-ce5a-4692-9f31-eb3df2fde0ce@pilppa.org> References: <8cba75b-ce5a-4692-9f31-eb3df2fde0ce@pilppa.org> Message-ID: <1d711956-f920-0d95-8ec1-bc559fe42841@xpra.org> On 20/09/2022 04:43, Mika Laitio via shifter-users wrote: > Hi I am new user trying the xpra and I have couple of questions. > I amd using Mageia Linux 8 and my python version is 3.8.12. > I have installed the latest xpra from sources with command: > > ?? python3 ./setup.py install --user I am guessing that you are building from git master? > 1) I try to execute the xpra with following command to connect > to another computer on ip 192.168.1.31 that is also running the mageia 8: > ? xpra start ssh://lamikr at 192.168.1.31 --start-child=xterm > but I am getting following error > > xpra initialization error: > ?invalid value for sync_xvfb: None int() argument must be a string, a > bytes-like object or a number, not 'NoneType' Any of these solutions should work: * specifying "--sync-xvfb=0" * building a stable version instead of git master * "git pull" and install again > Should I use some different python version. (I know python is very > incompatible between different versions) No. There are no compatibility problems with any actively supported Python versions (from 3.6 to 3.11 inclusive) though you may need a fully up to date toolchain for Python 3.11 > 2) Do I need to install xpra also to computer that I try to connect > or is xpra deploying somekind of runtime app to host machine during the > connection? Yes, install xpra at both ends. (you may skip installing the client if you use the html5 client instead) > https://github.com/Xpra-org/xpra/blob/master/docs/Usage/README.md > does not really mention anything about install requirements > > 3) Will xpra work with wayland + xwayland compination installed or do I > need to run either the host or client machine on X11 desktop session? Assuming that you want to run a seamless server ("xpra start") then this session will automatically start an X11 server for you to host the application you want to run. (ie: xterm) On the client side, you can run any window manager / desktop environment you like, including Wayland. (though some features are not available with Wayland clients) https://github.com/Xpra-org/xpra/wiki/Platforms Cheers, Antoine > > Mika