2009/9/25 Bryce Harrington <span dir="ltr"><<a href="mailto:bryce@canonical.com">bryce@canonical.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Sep 25, 2009 at 01:58:17PM +0200, Klaus Doblmann wrote:<br>
> I've been a silent follower of this list for some time now and as what<br>
> I'm about to say affects the development of Ubuntu via bugreports I've<br>
> decided to post it here - forgive me if I'm wrong.<br>
><br>
> I've submitted a few bugreports of app-crashes in the last few days<br>
> during my testing of Karmic and before submitting the bug I always look<br>
> for duplicates - which launchpad lists. Well, it does so in _some_ cases<br>
> but not in all.<br>
> When submitting an application crash the bug report is set to be<br>
> "private" therefore if somebody else submits the same crash report, the<br>
> previous one doesn't shop up in launchpad until after you've submitted<br>
> the bug and it's automatically set to be a duplicate.<br>
><br>
> This behaviour leads to many duplicate bugreports and quite a few hours<br>
> wasted by the community spent filing these reports.<br>
><br>
> Maybe this behaviour can be changed - or somebody can tell me the reason<br>
> for the bugreports being marked as "private" by default?<br>
<br>
</div>There is a chance with crash reports that the data they submit could<br>
include private data (passwords, etc.). Since these bugs are<br>
automatically filed, the reporter may not have the time (or know-how) to<br>
determine whether it includes personal info, thus the apport developers<br>
decided the safest approach was to file them all as private.<br>
<br>
You're right that this then requires triagers to do some work to review<br>
and un-privatize the bugs. In practice (with Xorg bugs, at least) I<br>
find it doesn't take me that much time to go through all the private bug<br>
reports and make them public, but admittedly I don't do it as often as I<br>
probably should. Perhaps there is way to automate some of this work<br>
with launchpadlib.<br>
<br>
Meantime, don't worry at all about filing duplicate bug reports. On the<br>
triager end, launchpad makes managing dupe bugs (relatively) cheap.<br>
Indeed, having a large number of dupes helps flag bug reports that need<br>
attention.<br>
<font color="#888888"><br>
Bryce<br></font></blockquote><div><br></div><div><div>Thanks for your answer, Bryce!<br></div><div><br></div><div>I've got one suggestion from a user's point of view: When one submits a crashlog that gets marked as a duplicate due to the reasons now explained, you obviously can't view the duplicate bugreport because it's set as private which is confusing to the average user committing a crash report. It would be a good idea to change the error message telling the user he can't access the bugreport because it is set temporarily set as private due to security-reasons until it gets reviewed. The current "you don't have permission to access this page" (it's something along these lines) is too non-descriptive and confusing to the average user - at least that's the way I see it.</div>
<div><br></div></div>Klaus<br clear="all"><br>-- <br>Klaus Doblmann<br>SIP: <a href="mailto:klaus.doblmann@ekiga.net">klaus.doblmann@ekiga.net</a><br>Web: <a href="http://www.doblmann.de">www.doblmann.de</a> - wo der gute Film ein Zuhause findet <br>
Blog: <a href="http://www.straightrazorguy.net">http://www.straightrazorguy.net</a><br><br>Associate Member of the Free Software Foundation (#7570)<br>OpenPGP-Key: <a href="http://www.doblmann.de/pgp_key.asc">http://www.doblmann.de/pgp_key.asc</a><br>
<br>Bitte vermeiden Sie es, mir Dokumente im Word- oder Powerpoint-Format zu senden!<br>Nutzen Sie eine kostenlose, freie Alternative zu Word&Co: <a href="http://de.openoffice.org/">http://de.openoffice.org/</a><br>