Re: maintainer ignores bug
2011/2/27 Osamu Aoki os...@debian.org Hi, On Sat, Feb 26, 2011 at 07:41:18PM +0100, Jakub Wilk wrote: * Osamu Aoki os...@debian.org, 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 rude. I did not quote full dialogue. There were good deal of previous exchanges. Sandro judged unreproducible and this is something broken on your machine. One should not report bug to the wrong package. Yes, ideally one should also be omniscient... I am not sure what is omniscient. If it means crystal clear, yes it 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 cause. 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.) Osamu -- Regards, Krasu
Re: maintainer ignores bug
2011/2/26 Osamu Aoki os...@debian.org Hi, On Sat, Feb 26, 2011 at 11:45:46AM -0500, Michael Gilbert wrote: On Sat, 26 Feb 2011 17:52:02 +0200 Dmitry Baryshev wrote: Hello guys. I've filed a bug on reportbug, but its maintainer ignores it, No maintainer did not ignore it. He responded reasonably. and continues to close it without any troubleshooting or debug. I did a simple troubleshooting by myself, but maintainer ignored it and closed the bug again. With whom I can talk about this strange situation? The bug itself: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599476 Has Mr. Mr. Dmitry Baryshev read all the responses by Sandro Tosi. I think Sandro made it very clear (typo corrected): | Really, stop this game, it's not a bug in reportbug but in *something | else* of your system. Please CC any comments. Thanks! Here is CC for Mr. Dmitry Baryshev. It looks like its an issue with your choice of .gtkrc files. Tahoma is a microsoft font and will not be on a debian system by default, so that may be the problem itself. You can just remove or back up those files, and you should be fine. This can happen due to broken font renderer or broken font itself. In KDE this font works fine, so, it's a broken font renderer in GTK or python-gtk or reportbug or something. No one even tried to diagnose this I mean. Anyway, if I trust Mr. Dmitry Baryshev, he has pure squeeze. What ever application he used to create this situation may be the cause. He needs to file a bug report to the package which is causing problem. (I do not know how he created this ~/.gtkrc which he claims to be the cause.) reportbug has nothing to do with this. One may file a general bug report if he does not know which package is causing problem. But that is usually a least useful kind of bug report. One should not report bug to the wrong package. If it is not immediately clear to DD which package is causing problem from a vague bug report which seems to be caused by user miss configuration, DD will close such useless bug report. It serves nothing. Please think about this. Osamu -- Regards, Krasu
maintainer ignores bug
Hello guys. I've filed a bug on reportbug, but its maintainer ignores it, and continues to close it without any troubleshooting or debug. I did a simple troubleshooting by myself, but maintainer ignored it and closed the bug again. With whom I can talk about this strange situation? The bug itself: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599476 Please CC any comments. Thanks! -- Regards, Krasu
Re: maintainer ignores bug
On Sat, 26 Feb 2011 17:52:02 +0200 Dmitry Baryshev wrote: Hello guys. I've filed a bug on reportbug, but its maintainer ignores it, and continues to close it without any troubleshooting or debug. I did a simple troubleshooting by myself, but maintainer ignored it and closed the bug again. With whom I can talk about this strange situation? The bug itself: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599476 Please CC any comments. Thanks! It looks like its an issue with your choice of .gtkrc files. Tahoma is a microsoft font and will not be on a debian system by default, so that may be the problem itself. You can just remove or back up those files, and you should be fine. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110226114546.146f5aa9.michael.s.gilb...@gmail.com
Re: maintainer ignores bug
Hi, On Sat, Feb 26, 2011 at 11:45:46AM -0500, Michael Gilbert wrote: On Sat, 26 Feb 2011 17:52:02 +0200 Dmitry Baryshev wrote: Hello guys. I've filed a bug on reportbug, but its maintainer ignores it, No maintainer did not ignore it. He responded reasonably. and continues to close it without any troubleshooting or debug. I did a simple troubleshooting by myself, but maintainer ignored it and closed the bug again. With whom I can talk about this strange situation? The bug itself: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599476 Has Mr. Mr. Dmitry Baryshev read all the responses by Sandro Tosi. I think Sandro made it very clear (typo corrected): | Really, stop this game, it's not a bug in reportbug but in *something | else* of your system. Please CC any comments. Thanks! Here is CC for Mr. Dmitry Baryshev. It looks like its an issue with your choice of .gtkrc files. Tahoma is a microsoft font and will not be on a debian system by default, so that may be the problem itself. You can just remove or back up those files, and you should be fine. Anyway, if I trust Mr. Dmitry Baryshev, he has pure squeeze. What ever application he used to create this situation may be the cause. He needs to file a bug report to the package which is causing problem. (I do not know how he created this ~/.gtkrc which he claims to be the cause.) reportbug has nothing to do with this. One may file a general bug report if he does not know which package is causing problem. But that is usually a least useful kind of bug report. One should not report bug to the wrong package. If it is not immediately clear to DD which package is causing problem from a vague bug report which seems to be caused by user miss configuration, DD will close such useless bug report. It serves nothing. Please think about this. Osamu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110226175041.ga10...@debian.org
Re: maintainer ignores bug
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. HS -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201102261950.09670.p...@hendrik-sattler.de
Re: maintainer ignores bug
* Osamu Aoki os...@debian.org, 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 rude. One should not report bug to the wrong package. Yes, ideally one should also be omniscient... -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110226184117.ga7...@jwilk.net
Re: maintainer ignores bug
Hi, On Sat, Feb 26, 2011 at 07:41:18PM +0100, Jakub Wilk wrote: * Osamu Aoki os...@debian.org, 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 rude. I did not quote full dialogue. There were good deal of previous exchanges. Sandro judged unreproducible and this is something broken on your machine. One should not report bug to the wrong package. Yes, ideally one should also be omniscient... I am not sure what is omniscient. If it means crystal clear, yes it 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 cause. 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.) Osamu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110227020518.ga31...@debian.org
Re: maintainer ignores bug
On Sat, 26 Feb 2011 21:05:19 -0500 (EST), Osamu Aoki wrote: On Sat, Feb 26, 2011 at 07:41:18PM +0100, Jakub Wilk wrote: Yes, ideally one should also be omniscient... I am not sure what is omniscient. ... I hope this does not sound too patronizing, Osamu; but since English is not your first language, I will tell you that omniscient means knowing everything, a term which, in it's strictest sense, applies only to God himself. I believe that this was Mr. Wilk's way of saying that he would have to know everything in order to know which package he should file the bug report against. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1361907891.1091567.1298776386245.javamail.r...@md01.wow.synacor.com
