[00:00] <teledyn[m]> interesting. I don't care which it is so long as I can run ardour again
[00:00] <OvenWerks> it has to be user I think
[00:00] <OvenWerks> unless you have set it with sudo in the first place
[00:00] <teledyn[m]> I think it needs to be user, or it would complain
[00:00] <teledyn[m]> but, I am known to be reckless with Linux ...
[00:00] <teledyn[m]> that's how I learned
[00:01] <arraybolt3[m]> I meant to unmask it - if somehow it's still masked after user unmasking, doesn't that sound like it's masked somewhere in an area that requires root to mess with? (I don't know for sure, please be careful with this and someone correct me if i'm wrong)
[00:01] <arraybolt3[m]> I'm thinking maybe you typed wireplumber when you meant pulseaudio when doing the masking.
[00:01] <teledyn[m]> it can replace the symlink with null as user, so it would seem likely it can be unmasked
[00:02] <arraybolt3[m]> Maybe try just starting wireplumber and not restarting it? (Grasping at straws...)
[00:03] <OvenWerks> is wireplumber installed?
[00:03] <OvenWerks> (I guess I shouold ask which distro you are using too)
[00:03] <teledyn[m]> yes, it is, and the sudo didn't help: $ systemctl unmask wireplumber.service
[00:03] <teledyn[m]> Unit wireplumber.service does not exist, proceeding anyway.
[00:03] <teledyn[m]> it prompted for sudo pw
[00:05] <teledyn[m]> I think I had this issue when I was told to mask pa the first time, the symlink was to a system file, but then removed or set to a null file, but I found the original and soft symlinked it back
[00:06] <teledyn[m]> I'll check the other machine, see what it has for these.
[00:07] <teledyn[m]> the other symlink removed was ~/.config/systemd/user/pulseaudio.service which explains why this is a user-space thing.  I think I did compare the contents of that dir, but I don't think I compared where the links go. sec ...
[00:08] <OvenWerks> yeah, wireplumber is odd, I don't have it in /etc/systemd/user/ but config files I set up for wireplumber still work.
[00:09] <teledyn[m]> now this is interesting too: the working machine does not have the .config/systemd directory at all!
[00:10] <OvenWerks> hmm I don't have a .config/systemd/ at all
[00:10] <OvenWerks> .config/systemd/ would override /etc/systemd/user/ though
[00:11] <OvenWerks> I have to go for a bit. Family calls
[00:11] <teledyn[m]> yes that is what I'm thinking, maybe I should delete it, and then compare the two /etc/systemd/user pw/pa files
[00:12] <teledyn[m]> yes, I should have dinner too.  I'll probably be back at this in an hour or two, or while I'm burning dinner (as too often happens, computing and cooking do not mix)
[00:15] <teledyn[m]> thanks so much for all your ideas on this, it is a real puzzle and I expect it could be something really really simple and dumb, like the day Andy and I sat up until 4am trying to figure out why our three SGI machines would boot to a point but then suddenly all of them went down. Turned out, in IRIX, it is bad to nfs mount a subdir of an already mounted disk. I said to Andy next morning (he stayed and found the issue) "Will we EVER
[00:15] <teledyn[m]> know what we're doing in this business?"
[03:07] <teledyn[m]> Made some progress and may have found one of my toxic 'fixes', a symlink in /etc/systemd/user was set to a sibling file instead of to the same name at /lib/systemd/usr - a reinstall restored the /lib file and I fixed the link, and now fuser -v /dev/snd/* shows the devices, as does aplay -L, which lists both a pulseaudio and a pipewire server. even inxi -A gives  Sound Server-2: PipeWire v: 0.3.58 running: yes, but the Plasma config
[03:07] <teledyn[m]> still says there are no devices and the log is still filling with pulseaudio context caput messages. I was following https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995313 until I got to the journalctl -xe and there, curiously, their logs find pipewire entries, mine finds none, but finds these context caput when i grep for pipewire.
[03:07] -ubottu:#ubuntustudio- Launchpad bug 1991934 in pipewire (Ubuntu) "mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic" [Undecided, Confirmed] [duplicate: 1995313]
[03:09] <teledyn[m]> Could this mean somewhere my KDE is set to use pulseaudio instead of pipewire, or the emulation is not running? I did run the systemctl --user status on the pipewire and pipewire-pulse, and both say they are up, although the service does report these two lines that had led me to the above bug
[03:10] <teledyn[m]> Nov 28 19:40:36 strata pipewire-pulse[2638]: mod.rt: Can't find xdg-portal: (null)
[03:10] <teledyn[m]> Nov 28 19:40:36 strata pipewire-pulse[2638]: mod.rt: found session bus but no portal
[03:11] <teledyn[m]> journalctl -xe | grep pulse:
[03:11] <teledyn[m]> Nov 28 22:10:57 strata kdeconnectd[3056]: org.kde.pulseaudio: context kaput
[03:11] <teledyn[m]> Nov 28 22:10:57 strata plasmashell[2968]: org.kde.plasma.pulseaudio: context kaput
[03:27] <teledyn[m]> Followed that trail to an associated bug that suggested reinstall of xdg-portal... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/dbac9272f99c86854549f39d6b6b8b481774cfd6>)
[04:11] <teledyn[m]> I think this will need to wait for tomorrow, but I've now got devices (albeit via pulseaudio) and I installed bluedevil which tells me that I have my Anker connected as "Audio Device" however the Sound config does not show any such device, only the HDMI and laptop speakers/headphones.
[04:16] <teledyn[m]> I didn't find any reference for a pipewire-bluetooth, but I do have pulseaudio-module-bluetooth, however the running pulseaudio is almost certainly a bad idea (step three from that bug report) as my mod.rt errors have been replaced by a string of missing modules
[14:58] <OvenWerks> teledyn[m]: the pipewirepackage for pluetooth would be libspa-0.2-bluetooth
[15:00] <OvenWerks> The actual file(s) it installes is /usr/lib/x86_64-linux-gnu/spa-0.2/bluez5/libspa-bluez5.so and /usr/lib/x86_64-linux-gnu/spa-0.2/bluez5/libspa-codec-bluez5*