Public/private bugreports

Caroline Ford at
Fri Sep 25 22:03:48 BST 2009

I don't know if this was ever implemented but it would be nice if  
upstreams could be given access to private bugs of their own packages.

I no longer have time to be in bug control so I have lost my access to  
private bugs and rely on subscribing to the packages I care about. I  
only get emails on open bugs- I think I would have to check on  
launchpad to see if any crash bugs have been submitted.


(tux4kids hat on)

Sent from a mobile device.

On 25 Sep 2009, at 19:08, Bryce Harrington <bryce at> wrote:

> On Fri, Sep 25, 2009 at 01:58:17PM +0200, Klaus Doblmann wrote:
>> I've been a silent follower of this list for some time now and as  
>> what
>> I'm about to say affects the development of Ubuntu via bugreports  
>> I've
>> decided to post it here - forgive me if I'm wrong.
>> I've submitted a few bugreports of app-crashes in the last few days
>> during my testing of Karmic and before submitting the bug I always  
>> look
>> for duplicates - which launchpad lists. Well, it does so in _some_  
>> cases
>> but not in all.
>> When submitting an application crash the bug report is set to be
>> "private" therefore if somebody else submits the same crash report,  
>> the
>> previous one doesn't shop up in launchpad until after you've  
>> submitted
>> the bug and it's automatically set to be a duplicate.
>> This behaviour leads to many duplicate bugreports and quite a few  
>> hours
>> wasted by the community spent filing these reports.
>> Maybe this behaviour can be changed - or somebody can tell me the  
>> reason
>> for the bugreports being marked as "private" by default?
> There is a chance with crash reports that the data they submit could
> include private data (passwords, etc.).  Since these bugs are
> automatically filed, the reporter may not have the time (or know- 
> how) to
> determine whether it includes personal info, thus the apport  
> developers
> decided the safest approach was to file them all as private.
> You're right that this then requires triagers to do some work to  
> review
> and un-privatize the bugs.  In practice (with Xorg bugs, at least) I
> find it doesn't take me that much time to go through all the private  
> bug
> reports and make them public, but admittedly I don't do it as often  
> as I
> probably should.  Perhaps there is way to automate some of this work
> with launchpadlib.
> Meantime, don't worry at all about filing duplicate bug reports.  On  
> the
> triager end, launchpad makes managing dupe bugs (relatively) cheap.
> Indeed, having a large number of dupes helps flag bug reports that  
> need
> attention.
> Bryce
> -- 
> ubuntu-devel mailing list
> ubuntu-devel at
> Modify settings or unsubscribe at:

More information about the ubuntu-devel mailing list