Summary: | qpaeq: DBus error on start | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Jan Alexander Steffens (heftig) <jan.steffens> |
Component: | tools | Assignee: | pulseaudio-bugs |
Status: | RESOLVED FIXED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | colin, hhielscher, lennart, luis |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | triaged | ||
i915 platform: | i915 features: |
Description
Jan Alexander Steffens (heftig)
2011-06-27 18:03:40 UTC
Have you got any equaliser sinks loaded? Does it still crash if you do? (It obviously shouldn't crash either way - just trying to narrow down the cause :D) Indeed, loading module-equalizer-sink allows qpaeq to run. Either we need to have qpaeq load the module, or error out gracefully. Adding "triaged" to the whiteboard. We don't currently have definitions for any whiteboard content. I think it would make sense to have such documentation. I'd define "triaged" as: The root cause has been found. Now fix it! Assigning it to myself, to dive into PulseAudio development. Please have some patience and give me a few days to have a patch ready. Just needs to have graceful handling of missing dbus path saying "you haven't got module-equalizer-sink loaded, so bye" (In reply to comment #5) > Assigning it to myself, to dive into PulseAudio development. Please have some > patience and give me a few days to have a patch ready. Sounds great! It's been a while since your message - has there been any process? If not, that's perfectly fine, but I think in that case the bug status should moved back to NEW. Back to NEW state due to lack of activity. There is a patch for this (partially) on the ML: http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/12723 Therefore removing the "love" keyword. I'm going to close this for now, since the patch has been merged and no further work to beautify qpaeq is currently happening. :) |
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.