Over time I gathered more than 10 launchpad bug reports that were reported with apport, initially marked as private and never responded to.

There was one I've discussed additionally on IRC and that's the only one I can remember being processed.

What should I do with them? How can I make sure they don't contain anything really private before making those bugs public?

  • 1
    int_ua, as a member of Bug Control myself, I've provided guidelines here. I have also removed the list of bugs you have identified as "private" here, because until those bugs are public, the bug numbers should only be discussed with Bug Controllers or people who can see those private bugs. I've copied the bug list to my clipboard, and if you would like me to assist you with looking at these bugs (assuming i can see them), please join me in the chat system so you and I can discuss these. Or on IRC, whichever you prefer. – Thomas Ward Nov 6 '13 at 18:58
  • 1
    However, I would prefer to work with you on private bugs over IRC, because we can coordinate with other bugcontrollers on it, but I can try and answer any other questions you have via the chat channel I've linked in my previous comment. :) – Thomas Ward Nov 6 '13 at 19:10

As a member of Bug Control, I've had to work with these private bugs on occasion. There is a specific policy on handling private bugs, and checking for specific information.

For crash bugs, the general thing you have to look for in the private bugs are core dumps and any stacktraces that may be on the bug. If a core dump is attached, remove it. If there's stacktraces attached, look through them and identify any possibly private data in the stack trace. If there looks to be private data, then what you have to do is download the stacktrace, edit out the private data, upload the edited version, then remove the old version.

As well, find any other Personally Identifiable Information, or private information, such as social security numbers, account numbers, passwords, etc., and try and edit those out as well.

For other private bugs, it depends, since there are separate policies for private security bugs which I am not privy to as those are handled by the Security team, and it likely would only be "Private Security" marked if the bug was legitimately a security risk that they could not publicize the information for.

There can also be private bugs that are not against the Ubuntu packages but are against other projects on Launchpad (i.e. not the Ubuntu project or an Ubuntu package). For those bugs, the managers of that project will be setting forth the policies for those bugs.

Additional information on how to triage Apport crash reports and other private bugs in Ubuntu can be found on the Ubuntu Wiki, in the How to Triage guide, as part of the Bug Squad's knowledge base. The link will automatically point you to the "Apport reports" section, however for the most up to date information on triage guidelines you should refer to that wiki document.

| improve this answer | |
  • 1
    Nice answer. Bookmarked. – 23 93 26 35 19 57 3 89 Nov 6 '13 at 19:05
  • What is the recommended period after which I should make a bug report public myself? Week? Month? – int_ua Nov 7 '13 at 7:13
  • 2
    @int_ua As far as I am aware there is no specific recommended time period for when you should make a private bug public. – Thomas Ward Nov 7 '13 at 13:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.