Pitfalls of the Ubuntu bug tracker - Was: volume past 100% and vol control

[Ralf Mardorf]

On Tue, 09 Feb 2016 13:16:55 +0100, Oliver Grawert wrote:
>Am Montag, den 08.02.2016, 21:01 +0000 schrieb Colin Law:
>
>> 
>> ... The only part which can be
>> tricky is deciding which package to assign it to.  If I do not know
>> which to use then I ask here and usually someone will know the
>> package, or at least suggest one in the general area so that whoever
>> looks at it will probably be able to re-assign it to the correct
>> one.  
>
>and since ubuntu has a wikipage for everything ... 
>https://wiki.ubuntu.com/Bugs/FindRightPackage#Any ...might be helpful
>if you cant send mails to ask the community while debugging :)

You expect users to know this hidden tool?

The OP wasn't aware of this tool.

Beyond that the tool might work for packages you build on your own. I
for example have one package for claws-mail installed.

[root at archlinux rocketmouse]# systemd-nspawn -qD /mnt/moonstudio 
[root at moonstudio ~]# dpkg -l claws* | grep ii
ii  claws-mail-git          3.13.2-1-geb0880-1 amd64
                            A GTK+ based e-mail client - git checkout

However, the official package is split into many, many packages.

http://packages.ubuntu.com/search?keywords=claws&searchon=names&suite=wily&section=all

Assumed claws-mail shouldn't filter spam correctly and I would click on
claws, how does the command line tool recognise that the buggy package
is claws-mail-bogofilter?

As somebody with years of experiences, who never used Unity and never
used pulseaudio, even while my domain is audio (pro-audio), I couldn't
tell the OP if the culprit is the package "indicator-sound" or the
package "pavucontrol" and actually I was the only one who at least
mentioned that it likely is one of those packages, nobody else of the
community mentioned that it definitively is not the package
"ubuntu-wallpapers".

In this case your assumption is proved to be wrong. Even if it would be
correct, it would require to use this mailing list in combination with
auto-bug-reporting tools that check your mobo ID for absolutely no good
reason, that might collect passwords unencrypted, in plain text.

If you take a look at good bug trackers, then you would notice that it's
less complicated and that they ask a novice to post a log file, but
first to to remove all passwords, let alone that nobody is interested
in you mobos ID.

Regards,
Ralf