From xpra at zellners.com Wed Feb 9 21:36:54 2022 From: xpra at zellners.com (xpra at zellners.com) Date: Wed, 09 Feb 2022 13:36:54 -0800 Subject: [winswitch] Growing Lethargy over time with use... Message-ID: <20220209133654.Horde.yacXzkp1-IBaQFLENXmoZN0@lv-shared03.cpanelplatform.com> Use/problem: Over time the connection setup to the XPRA SERVER grows lethargic, and eventually fails, with some features that work ie: audio, quit working. XPRA Version: 4.2.2 on both server and client OS's: Server - 20.04 Client 20.04 Kernels: 5.8.0.53-Client 5.4.0.80-Server Connection is an SSH connection that I setup via the XPRA-Launcher Connecting via local LAN, all 1Gbps xpra_launcher /home/ME/MyXPRA.xpra So heres the situation... Start up the server: xpra start --env=XPRA_VAAPI=0 :100 --start=/home/server/dir/dir2/bin/program This is a Java based program, not that I think that really is relevant, but maybe... Any way... all things start up and things go fine... I connect up to the server a few times a day to check the program, check a few things on the program yadda yadda... all is well ... the gist is that over time things will take longer and longer to connect. From connecting up quickly and the screen showing snappily.... eventually it gets to the point it will not connect at all. Gradually over time the time to connect, bring up the screen, and get the "beep" for audio connection grows longer and longer and longer. Eventually the XPRA server needs to be shut down and then restarted. And all is back to normal, connect starts up snappy, screen shows up, beep audio...and then the cycle starts.. it may be weeks till this starts to grow lethargic... I am open to any comments to look to where this might be creeping in be it the program being run to elsewhere... Comments?? Ideas??? More data wanted? ? ? Thanks in advance. From ajs1 at cam.ac.uk Thu Feb 10 19:46:33 2022 From: ajs1 at cam.ac.uk (Anthony Stone) Date: Thu, 10 Feb 2022 19:46:33 +0000 Subject: [winswitch] Growing Lethargy over time with use... In-Reply-To: <20220209133654.Horde.yacXzkp1-IBaQFLENXmoZN0@lv-shared03.cpanelplatform.com> References: <20220209133654.Horde.yacXzkp1-IBaQFLENXmoZN0@lv-shared03.cpanelplatform.com> Message-ID: <6d9512bc-aeb8-0f3a-1b50-72c948263aea@cam.ac.uk> I have noticed the same problem. xpra versions 4.3.2 on both server and client Ubuntu 18.04 fully up to date on both server and client Connecting using xpra start ssh/ --start ... I usually leave the connection up for several days at a time and it gets very sluggish. There are occasional complaints that the network is struggling to keep up, but after stopping the connection and reconnecting it becomes much more responsive. Anthony On 09/02/2022 21:36, xpra--- via shifter-users wrote: > Use/problem: Over time the connection setup to the XPRA SERVER grows > lethargic, and eventually fails, with some features that work ie: audio, > quit working. > > XPRA Version: 4.2.2 on both server and client > > OS's: Server - 20.04 Client 20.04 > Kernels: 5.8.0.53-Client 5.4.0.80-Server > > Connection is an SSH connection that I setup via the XPRA-Launcher > > Connecting via local LAN, all 1Gbps > > xpra_launcher /home/ME/MyXPRA.xpra > > So heres the situation... > > Start up the server: > xpra start --env=XPRA_VAAPI=0 :100 > --start=/home/server/dir/dir2/bin/program > > This is a Java based program, not that I think that really is relevant, > but maybe... > > Any way... all things start up and things go fine... > > I connect up to the server a few times a day to check the program, check > a few things on the program yadda yadda... all is well ... the gist is > that over time things will take longer and longer to connect. From > connecting up quickly and the screen showing snappily.... eventually it > gets to the point it will not connect at all. Gradually over time the > time to connect, bring up the screen, and get the "beep" for audio > connection grows longer and longer and longer. > > Eventually the XPRA server needs to be shut down and then restarted. And > all is back to normal, connect starts up snappy, screen shows up, beep > audio...and then the cycle starts.. it may be weeks till this starts to > grow lethargic... > > I am open to any comments to look to where this might be creeping in be > it the program being run to elsewhere... > > Comments?? Ideas??? More data wanted? ? ? > > Thanks in advance. > > > _______________________________________________ > 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 Feb 16 06:18:38 2022 From: xpra at zellners.com (xpra at zellners.com) Date: Tue, 15 Feb 2022 22:18:38 -0800 Subject: [winswitch] No audio on upgrade to 4.3.2 Message-ID: <20220215221838.Horde.dFmNY-m9nDfbYwG58jQImlx@lv-shared03.cpanelplatform.com> After upgrading my client during my recent OS updates, got XPRA 4.3.2 for the client. Ran that to see if any change in re the "lethargic" startup in previous mention.... But noticed immediately, NO AUDIO. Do not get the "audible beep" on startup. Connection status shows Audio: "ready" Client will show "audio connection using opus codec" Tried a toggle via xpra|speaker| off/on.. no joy. Still no audio from the server. Ubuntu 20.04..on server and client... Tried on an older client 4.2.? something.... on the connections status it shows "ready" and then it will go to "disabled" toggle off/on/off etc.. it will stick for a few seconds, "ready" and then "disabled", no audio here either. Any anything else to investigate? Server startup: Start up the server: xpra start --env=XPRA_VAAPI=0 :100 --start=/home/server/dir/dir2/bin/program 100/socket 2022-02-16 00:52:20,815 please wait as we allow the socket probing to timeout 2022-02-16 00:52:26,827 created unix domain socket '/run/user/1000/xpra/rec9140-SDRBox-100' 2022-02-16 00:52:26,827 cannot create group socket '/run/xpra/rex-SDRBox-100' 2022-02-16 00:52:26,827 [Errno 13] Permission denied 2022-02-16 00:52:26,829 created unix domain socket '/home/rex0/.xpra/rx40-SDRBox-100' 2022-02-16 00:52:26,830 created unix domain socket '/run/user/1000/xpra/100/socket' 2022-02-16 00:52:26,830 xvfb pid=1421 2022-02-16 00:52:27,021 D-Bus notification forwarding is available 2022-02-16 00:52:27,059 pulseaudio server started with pid 2795 2022-02-16 00:52:27,061 private server socket path: 2022-02-16 00:52:27,061 '/run/user/1000/xpra/100/pulse/pulse/native' (Xpra:2779): Gtk-CRITICAL **: 00:52:27.197: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed 2022-02-16 00:52:27,524 waiting for initialization thread to complete 2022-02-16 00:52:27,571 xpra is ready. 2022-02-16 00:52:27,581 watching for applications menu changes in: 2022-02-16 00:52:27,581 '/usr/share/applications' 2022-02-16 00:52:27,595 Warning: webcam forwarding is disabled 2022-02-16 00:52:27,596 the virtual video directory '/sys/devices/virtual/video4linux' was not found 2022-02-16 00:52:27,596 make sure that the 'v4l2loopback' kernel module is installed and loaded 2022-02-16 00:52:27,597 or use the 'webcam=no' option 2022-02-16 00:52:27,597 found 0 virtual video devices for webcam forwarding 2022-02-16 00:52:27,699 GStreamer version 1.16.2 for Python 3.8.10 64-bit 2022-02-16 00:52:28,869 xpra X11 seamless version 4.3.2-r0 64-bit 2022-02-16 00:52:28,870 uid=1000 (rec9140), gid=1000 (rx140) 2022-02-16 00:52:28,871 running with pid 2779 on Linux Ubuntu 20.04 focal 2022-02-16 00:52:28,878 connected to X11 display :100 with 24 bit colors 2022-02-16 00:52:37,532 Warning: initialization thread is still active 2022-02-16 00:52:37,565 started command 'ibus-daemon --xim --verbose --replace --panel=disable --desktop=xpra --daemonize' with pid 2852 2022-02-16 00:52:39,011 loaded 56 start menu entries from 10 sub-menus in 11.4 seconds 2022-02-16 00:52:39,141 printer forwarding enabled using postscript and pdf 2022-02-16 00:52:39,155 started command '/home/ From antoine at nagafix.co.uk Wed Feb 16 13:42:25 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 16 Feb 2022 20:42:25 +0700 Subject: [winswitch] Growing Lethargy over time with use... In-Reply-To: <6d9512bc-aeb8-0f3a-1b50-72c948263aea@cam.ac.uk> References: <20220209133654.Horde.yacXzkp1-IBaQFLENXmoZN0@lv-shared03.cpanelplatform.com> <6d9512bc-aeb8-0f3a-1b50-72c948263aea@cam.ac.uk> Message-ID: <0f951781-df60-4528-8264-872da3412c23@nagafix.co.uk> On 11/02/2022 02:46, Anthony Stone via shifter-users wrote: > I have noticed the same problem. > > xpra versions 4.3.2 on both server and client > Ubuntu 18.04 fully up to date on both server and client > > Connecting using xpra start ssh/ --start ... > > I usually leave the connection up for several days at a time and it gets > very sluggish. There are occasional complaints that the network is > struggling to keep up, but after stopping the connection and > reconnecting it becomes much more responsive. OTOH, this could be caused by a resource leak that ends up making the session sluggish - though other applications would be affected by that too, or it could be some kind of miscalculation somewhere. The first step would normally be to turn most features off to see if that makes any difference: no audio, no opengl, clipboard, etc.. It sounds like you have a way of reproducing it so this should not be too hard to fix. Please collect `xpra info` when the session becomes sluggish and once when it's not and attach it to a new github issue. Cheers, Antoine > > Anthony > > On 09/02/2022 21:36, xpra--- via shifter-users wrote: >> Use/problem: Over time the connection setup to the XPRA SERVER grows >> lethargic, and eventually fails, with some features that work ie: >> audio, quit working. >> >> XPRA Version: 4.2.2 on both server and client >> >> OS's: Server - 20.04 Client 20.04 >> Kernels: 5.8.0.53-Client 5.4.0.80-Server >> >> Connection is an SSH connection that I setup via the XPRA-Launcher >> >> Connecting via local LAN, all 1Gbps >> >> xpra_launcher /home/ME/MyXPRA.xpra >> >> So heres the situation... >> >> Start up the server: >> xpra start --env=XPRA_VAAPI=0 :100 >> --start=/home/server/dir/dir2/bin/program >> >> This is a Java based program, not that I think that really is >> relevant, but maybe... >> >> Any way... all things start up and things go fine... >> >> I connect up to the server a few times a day to check the program, >> check a few things on the program yadda yadda... all is well ... the >> gist is that over time things will take longer and longer to connect. >> From connecting up quickly and the screen showing snappily.... >> eventually it gets to the point it will not connect at all. Gradually >> over time the time to connect, bring up the screen, and get the "beep" >> for audio connection grows longer and longer and longer. >> >> Eventually the XPRA server needs to be shut down and then restarted. >> And all is back to normal, connect starts up snappy, screen shows up, >> beep audio...and then the cycle starts.. it may be weeks till this >> starts to grow lethargic... >> >> I am open to any comments to look to where this might be creeping in >> be it the program being run to elsewhere... >> >> Comments?? Ideas??? More data wanted? ? ? >> >> Thanks in advance. >> >> >> _______________________________________________ >> shifter-users mailing list >> shifter-users at lists.devloop.org.uk >> https://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ > 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 Wed Feb 16 13:49:03 2022 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 16 Feb 2022 20:49:03 +0700 Subject: [winswitch] No audio on upgrade to 4.3.2 In-Reply-To: <20220215221838.Horde.dFmNY-m9nDfbYwG58jQImlx@lv-shared03.cpanelplatform.com> References: <20220215221838.Horde.dFmNY-m9nDfbYwG58jQImlx@lv-shared03.cpanelplatform.com> Message-ID: <78aa7192-65b6-cfca-c10b-68e2b97cc797@nagafix.co.uk> On 16/02/2022 13:18, xpra--- via shifter-users wrote: > After upgrading my client during my recent OS updates, got XPRA 4.3.2 > for the client. > > Ran that to see if any change in re the "lethargic" startup in previous > mention.... > > But noticed immediately, NO AUDIO. There were no updates or fixes to the audio subsystem for quite some time. > > Do not get the "audible beep" on startup. > > Connection status shows Audio: "ready" > > Client will show "audio connection using opus codec" > > Tried a toggle via xpra|speaker| off/on.. no joy. Still no audio from > the server. > > Ubuntu 20.04..on server and client... > > Tried on an older client 4.2.? something.... on the connections status > it shows "ready" and then it will go to "disabled" toggle off/on/off > etc.. it will stick for a few seconds, "ready" and then "disabled", no > audio here either. > > Any anything else to investigate? The "-d sound,gstreamer" command line option will dump a huge amount of information to your terminal, it should show us what the client and server think they are doing. Please don't forward it here and use a github issue instead. Cheers, Antoine