Bug#739294: pulseaudio: should ship a bug script to collect system and config information

[Felipe Sateler]

Control: tags -1 confirmed

On Mon, Feb 17, 2014 at 03:30:10PM +0100, Andreas Beckmann wrote:
> Package: pulseaudio
> Version: 4.0-6
> Severity: normal
> 
> Since reporting bugs about pulseaudio being silent seems to be
> problematic due to lack of reproducability (may require same hardware
> and software setup) and lack of other information, I'd suggest to add a
> bug-script to the pulseaudio packages that tries to collect as much
> information as possible about the system and configuration to help the
> maintainers debug these problems.
> 
> As I'm absolutely clueless about sound (so far it works, I don't care
> whether I'm using alsa or pulseaudio or whatever), I don't know at all
> what this information could be.
> 
> See /usr/share/doc/reportbug/README.developers.gz and dh_bugfiles(1) for
> more information.

I've taken a stab at writing this. It's very easy to include
configuration files and command output.

So far I think we need the contents of:

/etc/default/pulseaudio -> to check if system mode is enabled

/etc/pulse/* -> pulseaudio configuration. Could this include sensitive
information?

`aplay -L` -> if aplay exists, is there anything similar for OSS?

pactl list {cards,sinks} -> what pulseaudio knows exists

pactl list modules -> what pa has loaded

pactl info -> pa defaults, should we exclude the cookie?

Do we need more files to be included? If systemd is running we could
include the logs of the pulseaudio binary. I'm not sure if we can get
this info from regular syslog.


-- 
Saludos,
Felipe Sateler