This is a very detailed and complete explanation. Thanks for this post.
Didn't search all the pages, but make sure you have included in "Filing a Bug" under Apport that it won't immediately be visible to everyone, as apport filed bugs are automatically marked as private, as they usually contain private data in the report (so only certain people can access).
Also, as I've been semi-alive-ish here, and I've been working towards getting more access to bugs, if there's any basic questions on bugs not explained here, or you want me to include additional information not listed here already, lemme know (I'm on the Bug Squad, so I'm somewhat well versed in bug-fu)
Awesome guide. It makes bug reporting look easier than it seems. The only question is to encounter the bug...
thank you for this great tutorial for people like me it's realy very usefull...hope to see mooe sonn..thank's a lot .respect.
Nothing works. Just want to ask a simple question: Is there a GUI that enables one to do some programming. And by that I don't mean the kids stuff like Glade. GNOME is just too tedious to get under control for a nice GUI.
Thank you for the guide! It cleared up some myths and may help prospective bug reporters!
Remember, you can use, and click on the window of the buggy app if you don't know the package name or for simplicity.Code:
Could the first post please be edited to include the
ubuntu-bug -w command? If it actually works, this is really important.
Another thing to point out is that you can convert Launchpad questions to bug reports, but if you do that, your bug report will probably be closed with a nasty canned note. Should this be clarified in the first post (and in bug-reporting directions everywhere)?