Results 1 to 2 of 2

Thread: Best practice for reporting bugs

  1. #1
    Join Date
    Dec 2004
    Location
    Utah, USA
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Best practice for reporting bugs

    This is a great e-mail posted to the ubuntu-devel mailing list about best practices for reporting bugs in Ubuntu by Matt Zimmerman (CTO of Canonical, Head of Ubuntu Tech Board).

    Please consider the suggestions given in this e-mail before making bug reports in Jaunty Beta.

    https://lists.ubuntu.com/archives/ub...ch/027868.html

    Quote Originally Posted by MDZ
    I've noticed that, even among Ubuntu devleopers, not everyone is applying our best practices for reporting bugs. In particular, reporting bugs directly to Launchpad is usually *NOT* the best approach. This should only be done if there is no better option.

    In almost all cases, it is preferable to report the bug using Apport. This can be done in one of the following ways:

    1. If the bug is a crash, apport should automatically generate a report and guide you in filing it. Copies of the crash reports are stored in /var/crash in case you need to refer to them directly.

    2. The "Help" menu in many applications includes an entry "Report a problem..." which will invoke Apport manually.

    3. On the command line, you can run "ubuntu-bug <package>" (or "ubuntu-bug <PID>") to invoke Apport manually. Kernel bugs should be reported with "ubuntu-bug linux".

    Using this method will automatically attach the relevant version information, log files, etc. where available. This saves you time in filing the bug, and saves others time in analyzing it. For example, filing a bug on the kernel will automatically include dmesg, lspci and so on.

    We're about to get flooded with bug reports from the beta, so please start using this method immediately, and encourage everyone else who reports bugs to do the same.

    More instructions for filing bugs can be found in the community documentation at https://help.ubuntu.com/community/ReportingBugs

    Note that if someone files a bug without using apport, you can still take
    advantage of it to add the information later (assuming it's still relevant), by using apport-collect(1). See https://lists.ubuntu.com/archives/ub...ry/000535.html for details.

    If you'd like to enhance your packages to take better advantage of apport by attaching relevant data, please ask for help. It's very simple once you know how to do it. The basics can be found at https://wiki.ubuntu.com/Apport/DeveloperHowTo

    - mdz
    Some graphical examples of this can be found on Jonathan Carter's blog.
    http://jonathancarter.co.za/2009/03/...ugs-in-ubuntu/

    Rocket2DMn also has a great beginners guide for bug reporting:
    http://ubuntuforums.org/showthread.php?t=1011078
    Last edited by Technoviking; March 25th, 2009 at 05:44 PM.
    Mike: "The hardest questions in life are the ones worth answering"
    E-Mail | Blog | Gmail | technoviking on irc.freenode.net, identi.ca , and Twitter

  2. #2
    Join Date
    Dec 2004
    Location
    Utah, USA
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Best practice for reporting bugs

    I'm locking the thread to keep this a informational thread and not a debate on bug reporting practices. Please feel free to create a separate thread for discussion of this topic.

    T-V
    Last edited by Technoviking; March 25th, 2009 at 05:38 PM.
    Mike: "The hardest questions in life are the ones worth answering"
    E-Mail | Blog | Gmail | technoviking on irc.freenode.net, identi.ca , and Twitter

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •