https://bugs.freedesktop.org/show_bug.cgi?id=106557
--- Comment #3 from Tanu Kaskinen <[email protected]> ---
(In reply to Dmitrii Sutiagin from comment #2)
> [dsutyagin@pulsar ~]$ ps -ef | grep [p]ulse
> gdm 2586 1 0 11:42 ? 00:00:00 /usr/bin/pulseaudio --start
> --log-target=syslog
Apparently autospawning is enabled for gdm. That's weird. My impression has
been that Arch disables autospawning (as it should when it's using systemd to
manage pulseaudio), and autospawning seems to be disabled for your own user. Is
there some gdm specific configuration in
/var/lib/gdm/.config/pulse/client.conf? Make sure that /etc/pulse/client.conf
has "autospawn = no". Note that /etc/pulse/client.conf has no effect on gdm if
/var/lib/gdm/.config/pulse/client.conf exists.
> 1. it doesn't work as before, log example can be found here -
> https://pastebin.com/4en37K3L # this is usually the result when I just plug
> in the card while it's on (it's hardware switch)
The log stops rather abruptly in the middle of the probing process after
getting "Input/output error" from snd_pcm_hw_params(). It seems that
snd_pcm_close() is hanging, because otherwise there should be more logs.
To me this seems quite clearly a kernel bug, and I don't think I have much more
to contribute here. You should report the problem to the alsa developers, here
are some instructions: http://alsa-project.org/main/index.php/Bug_Tracking
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
pulseaudio-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
