Re: maintainer ignores bug
2011/2/27 Osamu Aoki <firstname.lastname@example.org>
I did not quote full dialogue. There were good deal of previous
On Sat, Feb 26, 2011 at 07:41:18PM +0100, Jakub Wilk wrote:
> * Osamu Aoki <email@example.com
>, 2011-02-27, 02:50:
> >>>I've filed a bug on reportbug, but its maintainer ignores it,
> >No maintainer did not ignore it. He responded reasonably.
> He did not. Declaring "it's not a bug in my package" without even
> trying to diagnose the problem is not only unreasonable but also
exchanges. Sandro judged "unreproducible" and " this is something
broken on your machine".
I am not sure what is "omniscient". If it means "crystal clear", yes it
> >One should not report bug to the wrong package.
> Yes, ideally one should also be omniscient...
was very clear and very unlikely reportbug was the root cause of Mr.
Dmitry Baryshev's problem. At least, Mr. Dmitry Baryshev's report was
unconvincing and now he even indicates some other application was likely
Who should do this investigation? I did it because I know how to debug this. If user don't know how to debug this, his bug report will be closed without reassigning to proper package. Hence this investigation should be done by maintainer, not user. Why? Because this problem is reproduced in reportbug, and only in reportbug (at least on my system). In our case maintainer didn't do any diagnostic and closed bugreport without reassigning or investigation. So, user will waste his time to debug this by himself, to communicate with other people in -devel lists, and so on, in other words doing maintaner's job. Most likely he will not do that, and this bug will never be closed.
On Sat, Feb 26, 2011 at 07:50:09PM +0100, Hendrik Sattler wrote:
> Am Samstag 26 Februar 2011, 18:50:41 schrieb Osamu Aoki:
> > > It looks like its an issue with your choice of .gtkrc files.> I really do not recommend the setting in KDE to influence the themes of GTK
> programs. For me, it makes iceweasel using 100% _after_ closing it. It drove
> me almost nuts on my laptop until I found the cause.
"Some KDE application is the root cause" was my impression, too.
I recommend Mr,. Dmitry Baryshev to keep this bug report closed and file
anther bug report on the KDE package he used to create this
configuration after through investigation. (Of course he can use
reopen/reassign of old bug report with method written at
http://www.debian.org/Bugs/server-control but that is an expert option.)