On 8/13/23 15:59, Neal Gompa wrote:

On Sun, Aug 13, 2023 at 3:18 PM Joe Salmeri wrote:

...

After Tumbleweed switched from pulseaudio to pipewire, remote desktop sessions ( XRDP ) no longer had sound because that support was based on pulseaudio.

The developers have been working on a solution for quite a while now and it appears they have it working again using a new module.

https://github.com/matt335672/pipewire-module-xrdp

Can we get this new module included in TW ?

What desktop are you using? For example, if you're using GNOME, you can use its built-in support for RDP through gnome-remote-desktop.

I am using KDE but clients are Linux as well as Windows which both worked fine with xrdp until pulseaudio was replaced by pipewire. I don't have any issues with pipewire on my desktop, but apparently xrdp was originally written to work with pulseaudio. That new module allows it to work with pipewire. Does gnome-remote-desktop provide the server/service or is it client only ?    If it is the server side, can it support Windows clients connecting via rdp ? -- Regards, Joe

On 8/13/23 16:19, Neal Gompa wrote:

On Sun, Aug 13, 2023 at 4:06 PM Joe Salmeri wrote:

...

Does gnome-remote-desktop provide the server/service or is it client only ? If it is the server side, can it support Windows clients connecting via rdp ?

It is the server software, and yes Windows clients can connect to it.

That said, KDE Plasma 6 will include support for RDP too when using Plasma Wayland.

More details are in this blog post: https://quantumproductions.info/articles/2023-08/remote-desktop-using-rdp-pr...

Hopefully Plasma 6 will arrive later this year. :)

Interesting, I wonder whether gnome-remote-desktop would work with KDE instead of Gnome? Thanks for the link and info on KDE Plasma 6, I just read the article you sent. One comment in the article raises a concern: However, the current implementation is fairly limited, only allowing you to choose to accept or reject a remote desktop request. That sounds like how Windows RDP works on the non server products where you cannot be logged in locally and have a RDP session as another user at the same time. That functionality requires Windows Server. Windows Pro allows 1 RDP session but you cannot be logged on locally at the same time, but there have been various hacks over the years to make it bypass that restriction on Windows Pro. Windows Home only has the RDP client and no RDP server at all. With the xrdp package, I have multiple clients using RDP into the linux box at the same time that I am using the desktop locally so no need to prompt to accept or reject the request as they each have their own session. That functinonlity is critical for me. Does gnome-remote-desktop allow multiple RDP sessions to co-exist at the same time as well as a user logged on locally ? -- Regards, Joe

On 8/13/23 22:25, Masaru Nomiya wrote:

JS>     https://github.com/matt335672/pipewire-module-xrdp

JS> Can we get this new module included in TW ?

MN> The WM Enlightenment has been also developed with the assumption that MN> it would use the pulseaudio sound server, but I get sound with pipewire MN> without problems. MN> This is thanks to the pipewire-pulseaudio module, xrdp should be able MN> to do the same.

MN> Please have a look;

MN> http://c-nergy.be/blog/?p=18449

Hi Masaru, Thanks, I have seen that Ubuntu link before but those instructions are for disabling PipeWire and re-installing and enabling PulseAudio. The new module that I wrote about is a new module which modifies xrdp so that it can work with pipewire. Although, the pipewire-pulseaudio module is "supposed" to allow apps written for pulseaudio to work with pipewire, that does not seem to work for xrdp. However, I carefully went through your module list to make sure that I had everything which you mentioned.

I don't know about Ubuntu, but the method described here is too complicated, but in openSUSE, it is much simpler.

All you need is these files;

1. pipewire files

pipewire-module-x11-0_3-0.3.77-1.2.x86_64 gstreamer-plugin-pipewire-0.3.77-1.2.x86_64 pipewire-lang-0.3.77-1.2.noarch pipewire-devel-0.3.77-1.2.x86_64 pipewire-media-session-lang-0.4.1+git.f71506321.20220128-2.31.noarch pipewire-alsa-0.3.77-1.2.x86_64 pipewire-spa-plugins-0_2-0.3.77-1.2.x86_64 pipewire-spa-tools-0.3.77-1.2.x86_64 pipewire-alsa-32bit-0.3.77-1.2.x86_64 libpipewire-0_3-0-32bit-0.3.77-1.2.x86_64 pipewire-doc-0.3.77-1.2.x86_64 pipewire-pulseaudio-0.3.77-1.2.x86_64 pipewire-spa-plugins-0_2-32bit-0.3.77-1.2.x86_64 pipewire-0.3.77-1.2.x86_64 pipewire-media-session-0.4.1+git.f71506321.20220128-2.31.x86_64 pipewire-modules-0_3-0.3.77-1.2.x86_64 pipewire-tools-0.3.77-1.2.x86_64 pipewire-modules-0_3-32bit-0.3.77-1.2.x86_64 libpipewire-0_3-0-0.3.77-1.2.x86_64 pipecontrol-0.2.10-4.12.x86_64

2. pulseaudo files

apulse-0.1.13-37.58.x86_64 pulseaudio-utils-16.1-4.2.x86_64 system-user-pulse-16.1-4.2.noarch pulseaudio-utils-32bit-16.1-4.2.x86_64 pulseaudio-zsh-completion-16.1-4.2.x86_64 libpulse-devel-16.1-4.2.x86_64 libpulse0-16.1-4.2.x86_64 pulseaudio-setup-16.1-4.2.x86_64 pulseaudio-bash-completion-16.1-4.2.x86_64 alsa-plugins-pulse-1.2.7.1-173.0.x86_64 libpulse-mainloop-glib0-16.1-4.2.x86_64 libpulse0-32bit-16.1-4.2.x86_64

With these files, just do this;

$ systemctl --user daemon-reload $ systemctl --user start pipewire pipewire-pulse pipewire-media

In the above, pipewire-media module can be replaced with wireplumber module.

The following summarizes the status of the packages you specified on my system     I       = Installed package because it was NOT installed     NF   = Package NOT found     Y      = Package was already installed     SK   = Package skipped ( I don't use zsh )     NI   = Package NOT installed because it conflicts     1. pipewire files     I  pipewire-module-x11-0_3-0.3.77-1.2.x86_64     I  gstreamer-plugin-pipewire-0.3.77-1.2.x86_64     I  pipewire-lang-0.3.77-1.2.noarch     I  pipewire-devel-0.3.77-1.2.x86_64     NF pipewire-media-session-lang-0.4.1+git.f71506321.20220128-2.31.noarch     Y  pipewire-alsa-0.3.77-1.2.x86_64     Y  pipewire-spa-plugins-0_2-0.3.77-1.2.x86_64     Y  pipewire-spa-tools-0.3.77-1.2.x86_64     Y  pipewire-alsa-32bit-0.3.77-1.2.x86_64     Y  libpipewire-0_3-0-32bit-0.3.77-1.2.x86_64     I  pipewire-doc-0.3.77-1.2.x86_64     Y  pipewire-pulseaudio-0.3.77-1.2.x86_64     Y  pipewire-spa-plugins-0_2-32bit-0.3.77-1.2.x86_64     Y  pipewire-0.3.77-1.2.x86_64     NF pipewire-media-session-0.4.1+git.f71506321.20220128-2.31.x86_64     Y  pipewire-modules-0_3-0.3.77-1.2.x86_64     Y  pipewire-tools-0.3.77-1.2.x86_64     Y  pipewire-modules-0_3-32bit-0.3.77-1.2.x86_64     Y  libpipewire-0_3-0-0.3.77-1.2.x86_64     NF pipecontrol-0.2.10-4.12.x86_64     2. pulseaudo files     I  apulse-0.1.13-37.58.x86_64     Y  pulseaudio-utils-16.1-4.2.x86_64     I  system-user-pulse-16.1-4.2.noarch     Y  pulseaudio-utils-32bit-16.1-4.2.x86_64     SK pulseaudio-zsh-completion-16.1-4.2.x86_64     I  libpulse-devel-16.1-4.2.x86_64     Y  libpulse0-16.1-4.2.x86_64                 * NOTE: It installed 11 other pkgs too     Y  pulseaudio-setup-16.1-4.2.x86_64     I  pulseaudio-bash-completion-16.1-4.2.x86_64     NI alsa-plugins-pulse-1.2.7.1-173.0.x86_64     * NOTE: Cannot be installed because it conflicts with pipewire-alsa which is already installed     Y  libpulse-mainloop-glib0-16.1-4.2.x86_64     Y  libpulse0-32bit-16.1-4.2.x86_64     With these files, just do this;     $ systemctl --user daemon-reload     $ systemctl --user start pipewire pipewire-pulse pipewire-media MN: In the above, pipewire-media module can be replaced with wireplumber module. JS:    The libwireplumber-0_4-0, wireplumber, and wireplumber-audio packages are ALREADY installed After logging into the user via RDP I verified that the 3 services are started     systemctl --user status pipewire pipewire-pulse wireplumber         ALL 3 services are running Checking the Audio Volume reports "No output or input devices found" for the xrdp session. If that user logs in locally then sound works fine so the issue is just with pipewire and sound redirection for xrdp. Here is the discussion that I have been following about pipewire and xrdp from the upstream website for xrdp     https://github.com/neutrinolabs/xrdp/discussions/2023 Both Matt and Hiero32 seem to be key people with regard to xrdp and getting it to work with pipewire. This link talks about early testing for pipewire sound redirection for xrdp     http://c-nergy.be/blog/?p=18772 This link talks about the new pipewire-module-xrdp which was created to allow xrdp to generate sound on a pipewire based system and the one I was asking to be added to Tumbleweed.     https://github.com/neutrinolabs/pipewire-module-xrdp Maybe you could join that discussion to explain what you sent to me ? Thanks, Joe

On 8/14/23 14:04, Jan Engelhardt wrote:

On Monday 2023-08-14 19:16, Joe Salmeri wrote:

...

On 8/13/23 22:25, Masaru Nomiya wrote:

...

JS>     https://github.com/matt335672/pipewire-module-xrdp Although, the pipewire-pulseaudio module is "supposed" to allow apps written for pulseaudio to work with pipewire, that does not seem to work for xrdp. But *why* is the question.

Hi Jan, I don't know the answer and it is outside of my experience. If I had to guess, I suspect that pipewire-pulseaudio works fine with apps that a user logs on locally and runs which were written for pulseaudio. In the case of xrdp, the sound is redirected from the host ( xrdp server ) back to the client ( which in my cause could be Linux or Windows - the same issue exists on both ). When the user logs in via xrdp the Audio Volume applet does not even see the sound device. Possibly if that problem was addressed then pipewire-pulse might actually work but that is beyond my debugging ability. If you review the links I included in my other msg, you may gain more insight if you read those 2 developers messages. -- Regards, Joe

On 8/14/23 14:24, Andrei Borzenkov wrote:

On 14.08.2023 21:04, Jan Engelhardt wrote:

...

On Monday 2023-08-14 19:16, Joe Salmeri wrote:

...

On 8/13/23 22:25, Masaru Nomiya wrote:

...

JS> https://github.com/matt335672/pipewire-module-xrdp

Although, the pipewire-pulseaudio module is "supposed" to allow apps written for pulseaudio to work with pipewire, that does not seem to work for xrdp.

But *why* is the question.

AFAIU xrdp support is implemented as PA server module.

Yes, which I think is the "Why" answer and the new module I mentioned earlier in the thread is implemented using pipewire which is why I was asking about getting it packaged up for TW because it "appears" to me that it will be a separate package instead of just part of the xrdp package ( but I could be misunderstanding ). -- Regards, Joe

Hello, In the Message; Subject : Re: xrdp and sound Message-ID : Date & Time: Mon, 14 Aug 2023 13:16:49 -0400 [JS] == Joe Salmeri has written: [...] JS> After logging into the user via RDP I verified that the 3 JS> services are started JS>     systemctl --user status pipewire pipewire-pulse wireplumber JS>         ALL 3 services are running JS> Checking the Audio Volume reports "No output or input devices found" for the JS> xrdp session. [...] JS> added to Tumbleweed. JS>     https://github.com/neutrinolabs/pipewire-module-xrdp JS> Maybe you could join that discussion to explain what you sent to me ? Thank you very much for your kind and detailed explanation. As a matter of fact, as soon as I looked at the web to find out what xrdp is, I understood everything. I mean, since I migrated to Tumbleweed last March, I have not been able to hear the sound on my guest Windows (10 & 11) with VMwareWorkstaion and ViratulBox, and I thought the cause might be pipewire. I say "might" because I think I could hear the sound under pipewire until I migrated to Tumbleweed. Maybe I'm wrong. ....... Since I retired, I use Windows only once or twice a year for government work, so I'm not complaining about the current situation. In any case, I am sorry for the trouble. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ " Hassabis says that no one really knows for sure that AI will become a major danger. But he is certain that if progress continues at its current pace, there isn’t much time to develop safeguards. "I can see the kinds of things we're building into the Gemini series right, and we have no reason to believe that they won't work," he says." -- "Google DeepMind's CEO Says Its Next Algorithm Will Eclipse ChatGPT" --

Hello, In the Message; Subject : Re: xrdp and sound Message-ID : Date & Time: Wed, 16 Aug 2023 09:49:16 -0400 [JS] == Joe Salmeri has written: JS> On 8/15/23 21:09, Masaru Nomiya wrote: [...] MN> > I mean, since I migrated to Tumbleweed last March, I have not been MN> > able to hear the sound on my guest Windows (10 & 11) with MN> > VMwareWorkstaion and ViratulBox, and I thought the cause might be MN> > pipewire. JS> FWIW, I am using VMWare and have many Linux guest VMs ( different distros and JS> also Tumbleweed VMs ) and also have Windows 10 and 11 guests which have sound JS> working fine. JS> Feel free to reach me off list if you want. Thanks, but you gave me a BIG clue! I have an idea of the change to a wireless keyboard, so I checked around USB and changed USB Compatibility to 3,1 and now I get sound on all of them. But I couldn't hear the Windows system sound. I checked and found that, strangely enough, it was set to disable. I wonder why ..... (_ _? Anyway, many thanks indeed! I have read that some companies use virtual machines for security reasons, but is it possible that they use such a wide variety of virtual machines? Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --

On 8/16/23 21:20, Jason Craig wrote:

On 8/13/2023 13:18, Joe Salmeri wrote:

...

After Tumbleweed switched from pulseaudio to pipewire, remote desktop sessions ( XRDP ) no longer had sound because that support was based on pulseaudio.

The developers have been working on a solution for quite a while now and it appears they have it working again using a new module.

     https://github.com/matt335672/pipewire-module-xrdp

Can we get this new module included in TW ?

You can try this (fair warning: I just built it, I haven't tried it): https://build.opensuse.org/package/show/home:jacraig:xrdp/pipewire-module-xr...

Comments/improvements welcomed on package.

-- Jason Craig

Thanks Jason that's awesome! I just installed on my test TW machine which is running 20230809 and it is working perfectly! Now we just need to get it into the TW repos -- Regards, Joe