ddnn
October 17, 2026, 4:17pm
21
I see.
This could also be KDE-specific, since kpipewire was updated in the 6.8 update. So there is a possible mismatch not accounted for, especially since I don’t remember seeing a pipewire/wireplumber (upstream) update. Maybe just downgrading kpipewire would work, but I’m almost sure it won’t downgrade without downgrading all of KDE, so check this as well.
grep -E "upgraded (pipewire|libpipewire|wireplumber|alsa-ucm-conf|alsa-lib|alsa-utils|plasma-pa|plasma-desktop|plasma-workspace|kpipewire)" /var/log/pacman.log | tail -40
The last update I have for pipewire was back in September, and wireplumber on Oct 1.
And officially from the Arch repos, they were Sep 23 and Sep 30 respectively. It’s possible that kpipewire is the issue.
Do you have another window manager or DE installed to test?
R121
October 17, 2026, 4:29pm
22
well i did, before the update
x11, the thing they removed in this update, because its old and it sucks and would frequently crash n freeze as a window manager
but yeah it would be that since as mentioned way at the top, this started because a big major update to nearly everything happened
anyway
-utils|plasma-pa|plasma-desktop|plasma-workspace|kpipewire)" /var/log/pacman.log | tail -40
[2026-06-25T07:14:23-0500] [ALPM] upgraded plasma-desktop (6.7.0-1 -> 6.7.1-1)
[2026-06-25T07:14:23-0500] [ALPM] upgraded plasma-pa (6.7.0-1 -> 6.7.1-1)
[2026-07-02T06:21:49-0500] [ALPM] upgraded kpipewire (6.7.1-1 -> 6.7.2-1)
[2026-07-02T06:21:49-0500] [ALPM] upgraded plasma-workspace (6.7.1-1 -> 6.7.2-1)
[2026-07-02T06:21:50-0500] [ALPM] upgraded plasma-desktop (6.7.1-1 -> 6.7.2-1)
[2026-07-02T06:21:50-0500] [ALPM] upgraded plasma-pa (6.7.1-1 -> 6.7.2-1)
[2026-07-16T21:22:47-0500] [ALPM] upgraded libpipewire (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:47-0500] [ALPM] upgraded pipewire (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:47-0500] [ALPM] upgraded pipewire-audio (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:47-0500] [ALPM] upgraded pipewire-jack (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:50-0500] [ALPM] upgraded kpipewire (6.7.2-1 -> 6.7.3-1)
[2026-07-16T21:22:50-0500] [ALPM] upgraded plasma-workspace (6.7.2-1 -> 6.7.3-1)
[2026-07-16T21:22:57-0500] [ALPM] upgraded pipewire-alsa (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:57-0500] [ALPM] upgraded pipewire-pulse (1:1.6.7-1 -> 1:1.6.8-1)
[2026-07-16T21:22:57-0500] [ALPM] upgraded plasma-desktop (6.7.2-1 -> 6.7.3-1)
[2026-07-16T21:22:57-0500] [ALPM] upgraded plasma-pa (6.7.2-1 -> 6.7.3-1)
[2026-08-15T11:08:02-0500] [ALPM] upgraded kpipewire (6.7.3-1 -> 6.7.4-5)
[2026-08-15T11:08:02-0500] [ALPM] upgraded plasma-workspace (6.7.3-1 -> 6.7.4-1)
[2026-08-15T11:08:08-0500] [ALPM] upgraded plasma-desktop (6.7.3-1 -> 6.7.4-1)
[2026-08-15T11:08:09-0500] [ALPM] upgraded plasma-pa (6.7.3-1 -> 6.7.4-1)
[2026-08-24T18:21:50-0500] [ALPM] upgraded plasma-workspace (6.7.4-1 -> 6.7.4-3)
[2026-08-31T11:00:32-0500] [ALPM] upgraded wireplumber (0.5.15-1 -> 0.5.16-1)
[2026-09-09T08:23:11-0500] [ALPM] upgraded wireplumber (0.5.16-1 -> 0.5.17-1)
[2026-09-09T08:23:12-0500] [ALPM] upgraded kpipewire (6.7.4-5 -> 6.7.5-1)
[2026-09-09T08:23:13-0500] [ALPM] upgraded plasma-workspace (6.7.4-3 -> 6.7.5-1)
[2026-09-09T08:23:16-0500] [ALPM] upgraded plasma-desktop (6.7.4-1 -> 6.7.5-1)
[2026-09-09T08:23:16-0500] [ALPM] upgraded plasma-pa (6.7.4-1 -> 6.7.5-1)
[2026-09-23T08:22:28-0500] [ALPM] upgraded libpipewire (1:1.6.8-1 -> 1:1.6.9-1)
[2026-09-23T08:22:28-0500] [ALPM] upgraded pipewire (1:1.6.8-1 -> 1:1.6.9-1)
[2026-09-23T08:22:28-0500] [ALPM] upgraded pipewire-audio (1:1.6.8-1 -> 1:1.6.9-1)
[2026-09-23T08:22:28-0500] [ALPM] upgraded wireplumber (0.5.17-1 -> 0.5.17-2)
[2026-09-23T08:22:28-0500] [ALPM] upgraded pipewire-jack (1:1.6.8-1 -> 1:1.6.9-1)
[2026-09-23T08:22:30-0500] [ALPM] upgraded pipewire-alsa (1:1.6.8-1 -> 1:1.6.9-1)
[2026-09-23T08:22:30-0500] [ALPM] upgraded pipewire-pulse (1:1.6.8-1 -> 1:1.6.9-1)
[2026-10-01T11:27:28-0500] [ALPM] upgraded wireplumber (0.5.17-2 -> 0.5.18-1)
[2026-10-08T07:27:39-0500] [ALPM] upgraded plasma-workspace (6.7.5-1 -> 6.7.5-3)
[2026-10-16T07:02:44-0500] [ALPM] upgraded kpipewire (6.7.5-1 -> 6.8.0-1)
[2026-10-16T07:02:45-0500] [ALPM] upgraded plasma-workspace (6.7.5-3 -> 6.8.0-1)
[2026-10-16T07:02:47-0500] [ALPM] upgraded plasma-desktop (6.7.5-1 -> 6.8.0-1)
[2026-10-16T07:02:47-0500] [ALPM] upgraded plasma-pa (6.7.5-1 -> 6.8.0-1)
ddnn
October 17, 2026, 4:34pm
23
You might have to try forcing a downgrade of only kpipewire then. Try this first:
sudo downgrade kpipewire
You should get a list. Choose 6.7.5, then tell me what happens. It should give you a dependency error.
R121
October 17, 2026, 4:37pm
24
id take a screenshot but now spectacle broke, fun
it didnt give me any error actually, it just worked
@R121 @ddnn Just a heads-up: The forum will be down any moment now.
ddnn
October 17, 2026, 4:38pm
26
Try a reboot then. And if it doesn’t work, your next -Syu will re-upgrade it automatically, unless you set to ignore.
@Bryanpwo Thanks for the heads-up.
ddnn
October 17, 2026, 4:43pm
28
There were two other versions that were skipped, maybe pipewire works better with one of them. Try them: 6.7.90 and 6.7.91.
Oh, and each time, it would be a good idea to rename the wireplumber folder before rebooting.
.local/state/wireplumber`
R121
October 17, 2026, 4:51pm
29
still no change
btw all renaming that folder does is reset my volume sliders it doesnt do anything else for audio
ddnn
October 17, 2026, 4:57pm
30
Sad.
It actually does more than that, though. But unfortunately, in this case, the only change you can perceive is the volume change.
Will look into things a bit more. I’m using the links on the page below for info related to pipewire and such, if you wanna try to find something yourself.
ddnn
October 17, 2026, 8:14pm
31
Try the following while playing the same audio/video.
journalctl --user -u wireplumber -b | tail -50
journalctl --user -u pipewire -b | tail -50
It might say no entries.
R121
October 17, 2026, 8:16pm
32
no it has a lot actually
Oct 17 11:50:42 EOSWS-R121 systemd[1601]: Started Multimedia Service Session Manager.
Oct 17 11:50:43 EOSWS-R121 wireplumber[1881]: spa.bluez5: BlueZ system service is not available
Oct 17 11:50:43 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 11:50:43 EOSWS-R121 wireplumber[1881]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Oct 17 11:50:43 EOSWS-R121 wireplumber[1881]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Oct 17 12:04:01 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1c26a8d0> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 12:09:46 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 12:33:21 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1c225db0> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 12:49:17 EOSWS-R121 wireplumber[1881]: wp-properties: wp_properties_get: assertion 'self != NULL' failed
Oct 17 13:07:38 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1c132b50> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 13:29:06 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1bd70c20> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 13:47:56 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1c17f490> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 13:50:44 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 14:12:50 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 14:12:51 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 14:53:04 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be46800> failed: <WpSiStandardLink:0x555b1c16eb80> link failed: 1 of 1 PipeWire links failed to activate
Oct 17 14:53:58 EOSWS-R121 wireplumber[1881]: wp-event-dispatcher: <WpAsyncEventHook:0x555b1be69000> failed: failed to activate item: Object activation aborted: proxy destroyed
Oct 17 11:50:42 EOSWS-R121 systemd[1601]: Started PipeWire Multimedia Service.
ddnn
October 17, 2026, 9:15pm
33
Okay, this helps. Do these commands return anything?
speaker-test -D plughw:Audio,1 -c 2 -t wav -l 3
speaker-test -D pulse -c 2 -t wav -l 3
R121
October 17, 2026, 9:19pm
34
speaker-test 1.2.16
Playback device is plughw:Audio,1
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 32 to 96000
Period size range from 16 to 48000
Periods = 4
was set period_size = 12000
was set buffer_size = 48000
0 - Front Left
1 - Front Right
Time per period = 2.235205
0 - Front Left
1 - Front Right
Time per period = 3.000142
0 - Front Left
1 - Front Right
Time per period = 2.999942
speaker-test 1.2.16
Playback device is pulse
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 1048576
Period size range from 32 to 349526
Periods = 4
was set period_size = 12000
was set buffer_size = 48000
0 - Front Left
1 - Front Right
Time per period = 2.056755
0 - Front Left
1 - Front Right
Time per period = 3.071952
0 - Front Left
1 - Front Right
Time per period = 3.072044
ok i actually heard the second test going on in my headphones
ddnn
October 17, 2026, 9:23pm
35
Didn’t hear anything from the first?
Try this:
systemctl --user stop wireplumber pipewire pipewire-pulse
mv .local/state/wireplumber/ .local/state/wireplumber-bkp
rm -rf ~/.cache/wireplumber/
systemctl --user start wireplumber pipewire pipewire-pulse
Then wait 10 seconds, then run:
wpctl status
Finally, re-run the previous two tests.
speaker-test -D plughw:Audio,1 -c 2 -t wav -l 3
speaker-test -D pulse -c 2 -t wav -l 3
If you don’t hear anything, reboot, then run the tests.
R121
October 17, 2026, 10:03pm
36
PipeWire 'pipewire-0' [1.6.9, ribbons0121r121@EOSWS-R121, cookie:2166252023]
└─ Clients:
32. kwin_wayland [1.6.9, ribbons0121r121@EOSWS-R121, pid:1744]
33. WirePlumber [1.6.9, ribbons0121r121@EOSWS-R121, pid:1881]
42. WirePlumber [client] [1.6.9, ribbons0121r121@EOSWS-R121, pid:1881]
44. Steam Voice Settings [1.6.9, ribbons0121r121@EOSWS-R121, pid:3993]
46. plasmashell [1.6.9, ribbons0121r121@EOSWS-R121, pid:1757]
93. xdg-desktop-portal-kde [1.6.9, ribbons0121r121@EOSWS-R121, pid:2840]
94. xdg-desktop-portal [1.6.9, ribbons0121r121@EOSWS-R121, pid:2508]
95. wpctl [1.6.9, ribbons0121r121@EOSWS-R121, pid:93070]
98. [1.6.9, ribbons0121r121@EOSWS-R121, pid:1757]
99. [1.6.9, ribbons0121r121@EOSWS-R121, pid:1749]
100. Firefox [1.6.9, ribbons0121r121@EOSWS-R121, pid:2569]
101. Steam [1.6.9, ribbons0121r121@EOSWS-R121, pid:3993]
102. libcanberra [1.6.9, ribbons0121r121@EOSWS-R121, pid:1757]
103. libcanberra [1.6.9, ribbons0121r121@EOSWS-R121, pid:1749]
111. pipewire [1.6.9, ribbons0121r121@EOSWS-R121, pid:92975]
Audio
├─ Devices:
│ 48. GA104 High Definition Audio Controller [alsa]
│ 49. HD Webcam C615 [alsa]
│ 50. USB Audio [alsa]
│ 51. Built-in Audio [alsa]
│
├─ Sinks:
│ * 59. GA104 High Definition Audio Controller Digital Stereo (HDMI) [VA26LHDTV10T] [vol: 0.40]
│ 61. USB Audio S/PDIF Output [vol: 0.40]
│ 62. USB Audio Speakers [vol: 0.40]
│ 63. USB Audio Front Headphones [vol: 0.60]
│ 66. Built-in Audio Digital Stereo (HDMI) [VE228] [vol: 0.40]
│
├─ Sources:
│ * 45. HD Webcam C615 Mono [vol: 1.00]
│ 64. USB Audio Line Input [vol: 1.00]
│ 65. USB Audio Microphone [vol: 1.50]
│
├─ Filters:
│
└─ Streams:
Video
├─ Devices:
│ 55. HD Webcam C615 [v4l2]
│ 60. HD Webcam C615 [v4l2]
│
├─ Sinks:
│
├─ Sources:
│ * 96. HD Webcam C615 (V4L2)
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
0. Audio/Sink alsa_output.pci-0000_01_00.1.hdmi-stereo
i only heard something on the second again, but now its more delayed
ddnn
October 17, 2026, 10:09pm
37
Are you sure you’ve gone through all the KDE/pavucontrol GUI-based settings while playing audio/video? This is really looking like the issue is settings-based.
And yes, it was working before the update, but settings can become incompatible with updates, so really can’t rule it out.
Maybe try pavucontrol directly.
sudo pacman -Syu pavucontrol-qt
Play something with audio and check both the “Output Devices” and “Playback” tabs for inconsistencies, while also changing devices to see if they make a difference.
Could it be that the audio plays from the headphones, then somehow get slowly transferred to another device? Maybe that’s why it sounds further away?
Try running this two times while playing audio:
pactl list sink-inputs | grep -E "Sink:|application.name|node.name|State:"
Once when things sound as they should, and once when it doesn’t.
R121
October 17, 2026, 10:25pm
38
ahead of time post, that command you gave me for pauvcontrol, it shows another system wide upgrade queued in it, and there might be a 2% chance thatll magically fix the problem without explanation
ddnn
October 17, 2026, 10:26pm
39
Yes it might - the kernel and mesa updates in particular.
You should always run -Syu when installing a package.
I mean, I don’t, but most people should.
R121
October 17, 2026, 10:37pm
40
yeah it did, i wonder whats broken instead
i will say tho, ive never messed with other settings besides volume balanced and latency, because the codecs ui is entirely new to me
it was genuinely just that before in the menu, theres new options now
thanks?