Wireplumber and "Dummy Output"

First off, I’m not sure if this is a Wireplumber issue. The symptom is simply that on a fresh boot, it takes approximately 30 seconds for the sound setting to go from “Dummy Output” to actually finding the default device(s).

Any thoughts?

A bit more info would be great. What is your environment, what hardware etc.

inxi -Fzx output posted as preformated </> text would already help.

1 Like

please

System:
Kernel: 5.18.15-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.37-27.fc36 Desktop: GNOME v: 42.3.1
Distro: Fedora release 36 (Thirty Six)
Machine:
Type: Laptop System: Alienware product: Alienware Area-51m R2 v: 1.17.0
serial:
Mobo: Alienware model: Alienware Area-51m R2 v: A00
serial: UEFI: Alienware v: 1.17.0 date: 06/07/2022
Battery:
ID-1: BAT1 charge: 70.9 Wh (100.0%) condition: 70.9/90.0 Wh (78.8%)
volts: 12.6 min: 11.4 model: COMPAL PABAS0241231 status: full
CPU:
Info: 10-core model: Intel Core i9-10900K bits: 64 type: MT MCP
arch: Comet Lake rev: 5 cache: L1: 640 KiB L2: 2.5 MiB L3: 20 MiB
Speed (MHz): avg: 5096 high: 5115 min/max: 800/5300 cores: 1: 5109
2: 5101 3: 5070 4: 5102 5: 5093 6: 5100 7: 5091 8: 5092 9: 5097 10: 5099
11: 5108 12: 5061 13: 5092 14: 5104 15: 5103 16: 5115 17: 5109 18: 5101
19: 5091 20: 5100 bogomips: 147994
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: Dell driver: N/A
arch: Gen9.5 bus-ID: 00:02.0
Device-2: NVIDIA TU104M [GeForce RTX 2080 SUPER Mobile / Max-Q]
vendor: Dell driver: nvidia v: 515.57 arch: Turing bus-ID: 01:00.0
Device-3: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 1-7:3
Device-4: Tobii AB EyeChip type: USB driver: uvcvideo bus-ID: 1-9:4
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
gpu: nvidia,nvidia-nvswitch resolution: 3840x2160~60Hz
OpenGL: renderer: NVIDIA GeForce RTX 2080 Super/PCIe/SSE2
v: 4.6.0 NVIDIA 515.57 direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3
Device-2: NVIDIA TU104 HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 01:00.1
Sound Server-1: ALSA v: k5.18.15-200.fc36.x86_64 running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi vendor: Rivet Networks
driver: iwlwifi v: kernel bus-ID: 00:14.3
IF: wlo1 state: up mac:
Device-2: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169
v: kernel port: 3000 bus-ID: 07:00.0
IF: enp7s0 state: down mac:
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-14:6
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 4.19 TiB used: 1.58 TiB (37.7%)
ID-1: /dev/nvme0n1 vendor: Samsung model: PM981a NVMe 2048GB
size: 1.86 TiB temp: 49.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: PM981a NVMe 2048GB
size: 1.86 TiB temp: 38.9 C
ID-3: /dev/sda type: USB vendor: Samsung model: Flash Drive FIT
size: 239.02 GiB
ID-4: /dev/sdb type: USB vendor: Samsung model: Flash Drive FIT
size: 239.02 GiB
Partition:
ID-1: / size: 165.29 GiB used: 24.6 GiB (14.9%) fs: ext4
dev: /dev/nvme0n1p3
ID-2: /boot size: 973.4 MiB used: 220.8 MiB (22.7%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 497 MiB used: 412.5 MiB (83.0%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 1.48 TiB used: 232.37 GiB (15.3%) fs: ext4
dev: /dev/nvme0n1p4
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 29.2 MiB (0.4%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 57.0 C pch: 51.0 C mobo: N/A gpu: nvidia
temp: 53 C
Fan Speeds (RPM): N/A
Info:
Processes: 692 Uptime: 3h 31m Memory: 31.1 GiB used: 5.6 GiB (18.0%)
Init: systemd target: graphical (5) Compilers: gcc: 12.1.1 Packages: 27
note: see --pkg Shell: Bash v: 5.1.16 inxi: 3.3.19

Anyone?

Do you really think we are hovering over your problem for an instantaneous answer? Only a paid help desk could be expected to provide that kind of service.

Please be patient and someone may be able to assist when they have the freely given volunteer time to look at it.

Was that helpful, Jeff?

Do you have any custom configurations for sound or any gnome extensions that work with sound?

Nope.

Anyone?

Unfortunately, I can’t reproduce this issue between various machines and docking scenarios. It doesn’t seem like it’s a very common issue, but if someone here is able to reproduce it and has found a workaround, I’m sure they might be happy to give some input. In the meantime, the polling isn’t likely to inspire that to happen. If you do manage to find a workaround, it would be great if you could followup with it here in case it helps the next person.

1 Like

IMHO a 30 second delay for devices to become available is not significant. I also have never noticed that issue and cannot reproduce the problem.

Please do not be discouraged and maybe you can find a solution.

As noted by @vwbusguy it is usually considered bad form for someone to repeatedly bump their own thread to keep it in front of readers. It irritates others when the user exhibits impatience for an answer. With the time yours has been here it seems quite possible that no one has seen similar behavior, or if they have they consider it a non-issue.

Good luck.

1 Like

Jeff, first off, will you PLEASE stop your harangue as to the what’s polite here and what’s not. It’s annoying. If you have nothing constructive to add, then don’t.

That said, a 30-second delay for devices to become available is unusual considering the history and platform cited above.

You might consider that Jeff is trying to do you a favor here. He’s consistently among the most active contributors here and has a pretty good idea of what behavior is likely to get the best results. Generally, responding with what you have tried that may or may not have worked or more relevant log messages are more likely to garner helpful engagement than arguing with the volunteers who have to choose between yours and a number of others to give their attention to. Showing your own initiative to solve it and politely engaging with others will likely get much better results than polling. This is generally true amoung open source forums and support channels.

You might be able to get some clues from the logs: journalctl --boot | grep -e wireplumber -e pipewire. Especially look for any errors related to failure to activate a device, etc.

Scott, I am not arguing with volunteers. And I am not interested in the “feelings” of particular respondents, no matter their forum grease. I am just looking for a solution, or suggestions.

$ journalctl --boot | grep -e wireplumber -e pipewire
Aug 16 18:37:32 boomchicawowwow systemd[2542]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.
Aug 16 18:37:32 boomchicawowwow systemd[2542]: Listening on pipewire.socket - PipeWire Multimedia System Socket.
Aug 16 18:37:32 boomchicawowwow systemd[2542]: Started pipewire.service - PipeWire Multimedia Service.
Aug 16 18:37:32 boomchicawowwow systemd[2542]: Started wireplumber.service - Multimedia Service Session Manager.
Aug 16 18:37:32 boomchicawowwow systemd[2542]: Started pipewire-pulse.service - PipeWire PulseAudio.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2554 of process 2554 (/usr/bin/pipewire-pulse) owned by '1000' high priority at nice level -11.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2552 of process 2552 (/usr/bin/pipewire) owned by '1000' high priority at nice level -11.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2553 of process 2553 (/usr/bin/wireplumber) owned by '1000' high priority at nice level -11.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2582 of process 2553 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2590 of process 2554 (/usr/bin/pipewire-pulse) owned by '1000' RT at priority 20.
Aug 16 18:37:32 boomchicawowwow rtkit-daemon[1046]: Successfully made thread 2591 of process 2552 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
Aug 16 18:37:32 boomchicawowwow pipewire-pulse[2589]: 536870912
Aug 16 18:37:32 boomchicawowwow wireplumber[2553]: Failed to set scheduler settings: Operation not permitted
Aug 16 18:37:32 boomchicawowwow wireplumber[2553]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Aug 16 18:37:32 boomchicawowwow wireplumber[2553]: PipeWire's libcamera SPA missing or broken. libcamera not supported.
Aug 16 18:37:32 boomchicawowwow wireplumber[2553]: reserve-device plugin is not connected to D-Bus, disabling device reservation

Unfortunately, I don’t see anything here that obviously indicates your problem and this is all happening within less than a second. Is there anything within the next 30 seconds or so of the logs that might give some more clues?

Maybe you can use a command like sudo journalctl --since "3 minutes ago" or so because it should not be taken for granted that each relevant line contains the term wireplumber/pipewire. So boot your machine, wait until the devices have been found and then get the logs of the time that has passed since booting. If you think there is something contained in the logs that you consider private, you can hide/replace it.

All I see is this:

Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_intel 0000:00:1f.3: couldn't bind with audio component
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC215: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:      Mic=0x1b
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Aug 17 14:34:29 boomchicawowwow kernel: snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec
Aug 17 14:34:29 boomchicawowwow kernel: hdaudio hdaudioC0D2: Unable to configure, disabling
Aug 17 14:34:29 boomchicawowwow kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Aug 17 14:34:29 boomchicawowwow kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Aug 17 14:34:29 boomchicawowwow systemd[2910]: Reached target sound.target - Sound Card.
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event16)
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) No input driver specified, ignoring this device.
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) This device may have been added with another device file.
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event17)
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) No input driver specified, ignoring this device.
Aug 17 14:34:29 boomchicawowwow /usr/libexec/gdm-x-session[3077]: (II) This device may have been added with another device file.