You are not logged in.
As the title states, PulseAudio won't launch when I have my Motu M2 audio interface plugged in. When trying to manually launch from terminal, it outputs the following:
W: [pulseaudio] pid.c: Stale PID file, overwriting.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-MOTU_M2_M2MT18EF8F-00" card_name="alsa_card.usb-MOTU_M2_M2MT18EF8F-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
W: [pulseaudio] cli-command.c: stat('/etc/pulse/default.pa.d'): No such file or directory
fish: Job 1, 'pulseaudio' terminated by signal SIGSEGV (Address boundary error)
Had no problem using this interface on my last machine, and as soon as I unplug it PulseAudio works as excpected.
Never really messed around with Pulse or ALSA, so any help here is greatly appreciated
Last edited by Fisher_D (2022-07-24 05:22:55)
Offline
I just came across this issue with my M2 after a system update. Rolling back to alsa-ucm-conf-1.2.7.1 fixed it for me.
(see https://github.com/alsa-project/alsa-uc … issues/190 and https://gitlab.freedesktop.org/pipewire … sues/2559).
Offline
I just came across this issue with my M2 after a system update. Rolling back to alsa-ucm-conf-1.2.7.1 fixed it for me.
Yeah that did it. Thanks!
Offline
Thanks for this! I had a slightly different issue where pulse wasn't showing any available profiles for my Motu M2. Reverting back to alsa-ucm-conf-1.2.7.1 fixed it for me as well.
Offline
Kindred wrote:I just came across this issue with my M2 after a system update. Rolling back to alsa-ucm-conf-1.2.7.1 fixed it for me.
Yeah that did it. Thanks!
Yes confirm as well! Just downloaded the old version from here https://archive.archlinux.org/packages/a/alsa-ucm-conf/
and it worked. Nothing else. Thank you very much, made my day better
Offline