You are not logged in.
Like I said in the title, I had been using Pipewire instead of Pulseaudio as my main sound server for the last few weeks. I had issues with Pulse lately, and Pipewire looked like a nice solution. For most of February everything worked fine with PW, until the microphone went totally silent this evening. I had just finished a phone call (using my rear microphone) at 6, so I went for a short walk and then 30 minutes later, when I unlocked my session, the microphone was totally dead. I didn't reboot, or install anything - it simply stopped working without any warning.
I tried basically everything, with no avail; I got no sound in applications and `arecord` only recorded blank WAVs.
I then tried to kill pipewire, turn up the capture volume in alsamixer for the rear microphone, enable all capture channels, nothing, still empty WAVs. I even tried to run as root in a TTY - nothing. Resetting the ALSA levels accomplished more of the aforementioned nothing. Rebooting was also ineffective; booting Windows helped me diagnosing the issue was indeed on Linux (the microphone worked fine there).
Resigned, I reinstalled pulseaudio and re-enabled it, after disabling and masking Pipewire. I logged back in and poof! The microphone now works fine. Does anybody have any idea what could have wrecked pipewire? Also, arecord works fine now through Pulseaudio, but it weird it didn't work under plain ALSA.
I checked pipewire's journal entries for the last few days, and there are no mentions to recording devices, only spurious playback issues (note that playback never had any issue whatsoever):
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: (alsa_output.pci-0000_09_00.1.pro-output-3-38) start node error -2: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: 'hw:0,3': playback open failed: No such file or directory
Feb 26 23:17:14 Canis pipewire[2473]: (alsa_output.pci-0000_09_00.1.pro-output-3-38) start node error -2: No such file or directoryThe log for pipewire-pulse is instead full of very suspicious errors, starting just around the time the microphone ceased functioning:
Feb 26 19:43:34 Canis pipewire-pulse[5752]: pulse-server 0x55dae9233ce0: [Firefox] UNDERFLOW channel:3 offset:7974912 underrun:4096
Feb 26 19:43:44 Canis pipewire-pulse[5752]: recv client:0x55dae921bf60 res -1: Connection reset by peer
Feb 26 19:43:44 Canis pipewire-pulse[5752]: pulse-server 0x55dae91b84b0: client:0x55dae921bf60 [ALSA plug-in [audacity]] error -104 (Connection reset by peer)
Feb 26 19:43:44 Canis pipewire-pulse[5752]: recv client:0x55dae9c4bfc0 res -1: Connection reset by peer
Feb 26 19:43:44 Canis pipewire-pulse[5752]: pulse-server 0x55dae91b84b0: client:0x55dae9c4bfc0 [ALSA plug-in [audacity]] error -104 (Connection reset by peer)
Feb 26 19:43:44 Canis pipewire-pulse[5752]: recv client:0x55daea6c54e0 res -1: Connection reset by peer
Feb 26 19:43:44 Canis pipewire-pulse[5752]: pulse-server 0x55dae91b84b0: client:0x55daea6c54e0 [ALSA plug-in [audacity]] error -104 (Connection reset by peer)
Feb 26 19:43:44 Canis pipewire-pulse[5752]: recv client:0x55daea3093c0 res -1: Connection reset by peer
[...]
Feb 26 19:48:27 Canis pipewire-pulse[5752]: pulse-server 0x55dae9280130: [Firefox] UNDERFLOW channel:0 offset:11407360 underrun:4096
-- Boot fde52b05494d436285df1ea964beb051 --
Feb 26 19:50:13 Canis pipewire-pulse[5329]: pulse-server 0x55ec7cbfa580: [Firefox] UNDERFLOW channel:0 offset:11288576 underrun:4096
Feb 26 19:51:12 Canis pipewire-pulse[5329]: pulse-server 0x55ec7e92aee0: [libcanberra] ERROR command:18 (PLAY_SAMPLE) tag:6 error:25 (Input/output error)
Feb 26 19:53:55 Canis pipewire-pulse[5329]: 'CHECK_PORT(this, direction, port_id)' failed at ../pipewire/spa/plugins/audioconvert/merger.c:967 impl_node_port_set_param()
Feb 26 19:53:55 Canis pipewire-pulse[5329]: node 0x55ec7ccb3920: error unset format output: Invalid argument
-- Boot a2b8132d5b9a4c4b8674c67fe5590ad0 --
Feb 26 22:12:47 Canis pipewire-pulse[5193]: pulse-server 0x55ab230da990: [Firefox] UNDERFLOW channel:0 offset:11419648 underrun:4096
Feb 26 22:19:11 Canis pipewire-pulse[13278]: pulse-server 0x5566656644b0: failed to connect client: Host is down
Feb 26 22:19:11 Canis pipewire-pulse[13278]: pulse-server 0x5566656677c0: [Thunderbird] ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Feb 26 22:19:11 Canis pipewire-pulse[13278]: pulse-server 0x5566656644b0: failed to connect client: Host is down
Feb 26 22:19:11 Canis pipewire-pulse[13278]: pulse-server 0x556665667dd0: [Firefox] ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Feb 26 22:19:12 Canis pipewire-pulse[13278]: pulse-server 0x5566656644b0: failed to connect client: Host is down
Feb 26 22:19:12 Canis pipewire-pulse[13278]: pulse-server 0x5566656751d0: [Plasma PA] ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Feb 26 22:19:13 Canis pipewire-pulse[13278]: pulse-server 0x5566656644b0: failed to connect client: Host is downAs the logs show, the "Connection reset by peer" errors were replaced by "Host is down" after reboot; the log continues and the errors only cease being recorded when I disabled pipewire. I checked `ps aux` several times and pipewire and pipewire-pulse (and pipewire-media-whatever) were running all times for my user, except when I forcibly killed them.
From this quick analysis, it seems that either pipewire or pipewire-pulse completely broke without any reason. Has anyone had similar experiences with pipewire? Should these kinds of issues be expected given how new the project is?
Last edited by krnlpk (2021-02-26 23:10:07)
Offline