Summary: | Pulseaudio crashes at volume/mute control of a RAOP device | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | youagree <n3ocort3x> |
Component: | modules | Assignee: | Colin Guthrie <colin> |
Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
Severity: | critical | ||
Priority: | medium | CC: | colin, felix, lennart, n3ocort3x |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | pulseaudio verbose log from its start till crash by trying to set RAOP volume (pulseaudio -vvv --log-target=file:) |
Description
youagree
2011-09-05 10:48:59 UTC
Just FYI, it's generally not polite to change priorities. Everyone's bug is their own most important problem so this is really something the project organisers should set rather than users reporting bugs. I'm going to see if I can plug in my AppleTV that I borrowed shortly and see what happens! Sorry about that, I didn't know. I was thinking the bug can be considered a bug of high importance if it causes the product's main process, i.e. the PulseAudio server to crash completely. But if there was a similar problem with the alsa-sink, I think due to its higher popularity "high" would be more appropriate. (medium OK because not as many people want to use raop devices than alsa devices) -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/333. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.