alsa apport hook (Re: It is 2009 and I am still hearing my pc speaker)
Bryce Harrington
bryce at canonical.com
Wed Apr 8 20:19:01 BST 2009
On Wed, Apr 08, 2009 at 07:48:56PM +0100, Matt Zimmerman wrote:
> Indeed, I realize these packages don't actually contain the drivers we ship,
> though I thought it made more sense to ship the hook with alsa-base than
> in the kernel package. It's easier to change there, and it can still be
> used by any package.
>
> Do you think that all kernel bugs should include the ALSA info as well? If
> so, that's easy to add to the kernel package hook. If not, I think
> apport-collect -p alsa-base is probably the best we can do for now, since we
> don't know which bugs are ALSA-related until they get reviewed by a human.
>
> There's some talk of adding more interactivity to ubuntu-bug in Karmic, so
> we could ask enough questions to know what information to attach.
It might be slick to have a means to file a bug based on "symptom".
ubuntu-bug -s sound
ubuntu-bug -s keyboard
ubuntu-bug -p xorg -s resolution
I've noticed with using apport with X, that there is a stronger
correlation between files I want and the generic symptom, then there is
between them and the source package. E.g., both "X crash" and "Big
fonts" are usually xorg-server bugs, however I need completely different
sets of files for each case.
I imagine the situation is probably even more extreme with the kernel.
Currently, I just pile everything I might possibly want into the generic
xorg package hook. Being able to file based on symptom might enable
being more precise in what is collected, and save some bandwidth.
Bryce
More information about the ubuntu-devel
mailing list