Mon, 18 Mar 2024 20:59:50 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <3d1390f8-7bc5-404d-b981-21e2e6b51086@telefonica.net> Date & Time: Sun, 17 Mar 2024 16:22:46 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
CER> On 2024-03-17 14:46, Patrick Shanahan wrote: [...] MN>>> In short, there is a bug in the current pipewire.
PS>> wrong attribution, nowhere did is say there is a bug in the current PS>> pipewire
CER> It is not attributed to you. There is a double ">>", albeit with CER> somewhat broken and unusual formatting.
Thanks, Carlos.
I'm sorry if I misled you, Patrick.
Anyway, today I found out two things.
The Audacity problem was caused by the portaudio library of my own build being too new, and I solved it by replacing it with the one provided by openSUSE. Of course, this has nothing to do with pipewire.
However, it has been reported that there can be problems between pipewire and Audacity, and I suspect that Ben's problem is along these lines and is related to the $ pactl info returning an error.
I also had a question about KDE theming, so I checked it out with installing Tumbleweed on my laptop. It turns out that $ pactl info should return results like Patrick showed, and that the absence of /run/user/1000/pulse/native on my PC is an anomaly. I thiink Ben is the same?
By the way, there are pid files under /run/user/1000/pulse as well as native file, and I was surprised to find out that they are from pipewire-pulse by checking with # ps ax | grep pid's value.
I see both of them on my TW