https://bugs.freedesktop.org/show_bug.cgi?id=97627
--- Comment #17 from Tanu Kaskinen <[email protected]> ---
Yes, a server hang would have been the most obvious explanation. I expected to
see some alsa call to be blocking or something like that.
pulseaudio4.log shows also an error from a timed out dbus call. It looks like
the dbus daemon tried to start bluetoothd, but that took a long time. I don't
think bluetooth is to blame, since I don't think we try to talk to bluetoothd
after the initial failure, and you experience the problem also at other times
than just after starting pulseaudio. But whatever is causing the problem seems
to affect other parts of the system too.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
pulseaudio-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
