I did a rollback and everything was back to normal. Installed the update again, the issue came back. I checked that pipewire-pulseaudio AND pipewire AND wireplumber were installed and running.
Okay so I know I’m supposed to give logs and stuff but… I don’t know what to give. I typed sudo dmesg but it gave me thousands of incomprehensible lines : 67.2 KB file on MEGA
Then there’s boot.log in /var/log, equally as big and incomprehensible to me : 49.2 KB file on MEGA
To get the audio infos I typed aplay --list-devices and got this:
For comparison, here’s what I get when I run wpctl and systemctl --user status pipewire pipewire-pulse wireplumber from a snapshot where the audio DOES work:
We see that the SINKS provides the correct " 49. Audio interne Stéréo analogique [vol: 0.50]" instead of the incorrect “44. Audio interne Stéréo numérique (HDMI) [vol: 1.00]” that I get from the snapshot after the update.
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-03-12 09:41:02 CET; 2min 51s ago
TriggeredBy: ● pipewire.socket
Main PID: 2244 (pipewire)
Tasks: 4 (limit: 4915)
Memory: 9.4M
CPU: 411ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2244 /usr/bin/pipewire
mars 12 09:41:02 laptopjuju systemd[1894]: Started PipeWire Multimedia Service.
mars 12 09:41:03 laptopjuju pipewire[2244]: [0:00:34.172135448] [2244] WARN IPAManager ipa_manager.cpp:154 No IPA found in '/usr/lib64/libcamera'
mars 12 09:41:03 laptopjuju pipewire[2244]: [0:00:34.172979854] [2244] INFO Camera camera_manager.cpp:284 libcamera v0.2.0
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-03-12 09:41:04 CET; 2min 49s ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 2412 (pipewire-pulse)
Tasks: 3 (limit: 4915)
Memory: 5.4M
CPU: 270ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─2412 /usr/bin/pipewire-pulse
mars 12 09:41:04 laptopjuju systemd[1894]: Started PipeWire PulseAudio.
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-03-12 09:41:02 CET; 2min 51s ago
Main PID: 2247 (wireplumber)
Tasks: 7 (limit: 4915)
Memory: 14.8M
CPU: 930ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2247 /usr/bin/wireplumber
mars 12 09:41:02 laptopjuju systemd[1894]: Started Multimedia Service Session Manager.
mars 12 09:41:02 laptopjuju wireplumber[2247]: [0:00:33.418047723] [2247] WARN IPAManager ipa_manager.cpp:154 No IPA found in '/usr/lib64/libcamera'
mars 12 09:41:02 laptopjuju wireplumber[2247]: [0:00:33.418130087] [2247] INFO Camera camera_manager.cpp:284 libcamera v0.2.0
mars 12 09:41:03 laptopjuju wireplumber[2247]: <WpPortalPermissionStorePlugin:0x558fd2e52a70> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
mars 12 09:41:03 laptopjuju wireplumber[2247]: <WpPortalPermissionStorePlugin:0x558fd2e52a70> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
The inxi output (showing alsa driver and sound server components) seems ok, and the higher-level wireplumber output looks the same for both snapshots at a quick glance.
You can compare with the very first post. It lists the microphone and the speaker as peripherals, whilst in the screenshot of the first post, I have that weird HDMI/DisplayPort that is grayed.
Hi all, for me running this command after having deleted the local files (make sure to back up them) from .local/state/wireplumber/ fixed the issue:
systemctl --user restart pipewire.service
Regards.
TW did find my audio peripherals, it just chose to ignore them by default after the update. In Plasma’s audio setting, I found the unused peripherals and simply click to activate my mic and speaker -_-
I’m very sorry to have disturbed y’all with this bs.
Well, that explains why the terminal output seemed to check out ok. We all make mistakes, so glad that you realised what was needed to get the mic and speaker visible again.