https://bugs.freedesktop.org/show_bug.cgi?id=107037
--- Comment #5 from Alex Henry <tuk...@gmail.com> ---
You are absolutely correct, removing Timidity and reverting my configuration
file has things back to normal. I use Timidity fairly often but as a
command-line tool for one of my projects and I had no idea that it had a daemon
at all, sorry.
That being said though, I still think this report could be acted on by having
module-udev-detect print a big bold error when it tries to access a card that
is being hogged by some other resource. Should I open a new report for this? I
don't remember seeing any such message while browsing logs and could help a lot
for all sorts of troubleshooting.
I can reinstall timidity later on to make sure no such message is already being
printed, but I'm fairly sure it isn't, or at least not as obviously as other
error messages that do pop up on the logs...
Thank you very much for reply and info, Tanu!
--
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
pulseaudio-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs