Page MenuHomeLubuntu

Bugs
Updated 16 Days AgoPublic

Software inevitably has bugs. Sometimes despite the most rigorous testing, bugs still get through. Luckily, bug reporting is an easy way to alert developers to the need to solve an issue. Additionally, it's easier to troubleshoot bugs in a single place than it is on a mailing list or IRC.

It is a common misconception that reporting bugs is an extremely difficult task, but as long as you clearly explain the problem, someone with more experience can guide you in getting any additional information. New people reporting bugs are very strongly encouraged to read How To Write Bugs Effectively to help with wording their bug report.

Getting started

  • Before you can report bugs, you will need a Launchpad account.
  • To use the reporting tools, you will need to make sure to install apport (sudo apt install apport) and ensure it is enabled.

Essential components

The more complete you can make your bug report, the more likely it is to be fixed. Here's the pieces you should consider essential:

  1. The report is filed against an appropriate package. See below.
  2. The report has a clear title.
  3. The report description includes the following pieces:
    1. Steps to reproduce (this is the most important thing; if it's not reproducible, it's nearly impossible to fix).
    2. Expected results.
    3. Actual results.
    4. Affected versions.
    5. Optionally, any other notes concerning conditions required to reproduce the bug, testing information, log files, etc.
  4. The report includes appropriate tags, but especially "lubuntu."

General guidelines

  • Ideally, it's good to do a little web search or ask around to see if your bug is really a support issue.
  • One quick way to ensure you have a real bug is to set up a virtual machine with the version of Lubuntu you're using and see if you can repeat the behavior. If you can't, you might still have a bug, but the issue will be related to some specific aspect of your system, which will need to be tracked down.
  • If you do have a bug, it's a good idea to do a search on Launchpad to see if you find a duplicate bug. If you do, work to add to and triage that bug report instead of reporting a new one.
  • MOST IMPORTANTLY: if you're not sure if you should report a bug, report it anyway!

Additional documentation

How to report bugs

The best way to report a bug is to simply open a terminal and run:

ubuntu-bug name_of_the_affected_package

Example: if you had a problem with the web browser, you'd use:

ubuntu-bug firefox

When in doubt, please file against lubuntu-desktop.

Common packages

Lubuntu specific

componentpackage
settingslubuntu-default-settings
artworklubuntu-artwork
installer settingscalamares-settings-lubuntu
splash screen logoplymouth-theme-lubuntu-logo
splash screen textplymouth-theme-lubuntu-text
display manager settingssddm-theme-lubuntu
metapackagelubuntu-desktop

Core desktop environment

componentLXDE (≤18.04)LXQt (≥18.10)
window manageropenboxopenbox
display managerlightdmsddm
session managerlxsessionlxqt-session
application launcherlxqt-runnerlxpanel has run dialog
taskbarlxpanellxqt-panel
file managerpcmanfmpcmanfm-qtalso manages desktop
notification daemonxfce4-notifydlxqt-notificationd
authentication agentlxpolkitlxqt-policykit
screen lockerlight-lockerxscreensaver
Bluetooth managerbluemanbluedevil

Configuration

componentLXDE (≤18.04)LXQt (≥18.10)
window manager configurationobconfobconf-qt
hot key configurationlxhotkey-gtklxqt-globalkeys
theme configurationlxappearancelxqt-config
monitor settingslxrandrlxqt-config
input settingslxinputlxqt-config

Default applications

componentLXDE (≤18.04)LXQt (≥18.10)
installerubiquitycalamares
software centergnome-softwareplasma-discover
archive toolfile-rollerark
task managerlxtaskqps
partition toolgnome-disk-utilitypartitionmanager
disc burnerxfburnk3b
terminallxterminalqterminal
text editorleafpadfeatherpad
music playeraudaciousvlc
video playergnome-mpvvlc
image viewergpicviewlximage-qt
drawing programmtpaintlibreoffice-draw
web browserfirefoxfirefox
emailsylpheedtrojita
calculatorgcalculatorkcalc
document viewerevinceqpdf
word processorabiwordlibreoffice-writer
spreadsheetgnumericlibreoffice-calc

Triage: making bug reports better

An important part of QA is not only making bug reports, but making them in such a way that they can be worked on by developers. Additionally, triage should be something that QA considers part of their workload. Bug reports are there to help developers know what to work on next. The only way development happens is if these bug reports are clear and clearly marked.

The work here is making sure all of the essential components above are set up appropriately. Additionally, the following components are done:

  1. The bug is reproduced by the triager and marked as confirmed.
  2. An upstream bug report is created and links to the downstream bug and vice versa.
  3. It is given a status of triaged.
  4. It is given a reasonable priority.

Advice to these ends are provided by the Ubuntu Bug Squad team which has an open membership. Their documentation is a valuable reference, but they are available by IRC and email for additional questions. Or you can contact the friendly Lubuntu Development/QA teams!

You will also need to contact the aforementioned folks to set statuses and priorities. Alternately, you can submit an application to the Ubuntu Bug Control team. The more well-equipped triagers we have on this team, the better, so please do so!

Example

Here's an example of a complete, well-triaged bug report:

it has the following qualities:

  1. It has been marked as confirmed.
  2. It is linked to an upstream bug report. If you follow the link to the tracker, you'll find it links back to the downstream bug.
  3. It is marked as triaged.
  4. It is given a reasonable priority.
  5. It has clear steps to reproduce, expected results, actual results, and any other additional notes detailing the version numbers and other conditions that apply and don't apply.
  6. It has the Lubuntu Packages Team subscribed.
  7. It's given appropriate tags, but especially the lubuntu one.

Contents of this page originated from the Ubuntu Wiki, all copyright goes to the respective authors.

Last Author
wxl
Last Edited
Sat, Dec 1, 11:10 PM

Event Timeline

wxl created this document.Oct 7 2018, 1:57 AM
wxl edited the content of this document. (Show Details)
wxl added a project: QA.
wxl added a subscriber: tsimonq2.
wxl edited the content of this document. (Show Details)Oct 7 2018, 2:10 AM
wxl edited the content of this document. (Show Details)Oct 17 2018, 1:51 AM
wxl edited the content of this document. (Show Details)Oct 17 2018, 10:57 AM
wxl edited the content of this document. (Show Details)
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:07 AM
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:10 AM
wxl edited the content of this document. (Show Details)
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:16 AM
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:30 PM
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:43 PM
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:46 PM
wxl edited the content of this document. (Show Details)
wxl edited the content of this document. (Show Details)Oct 17 2018, 11:57 PM
wxl edited the content of this document. (Show Details)
wxl edited the content of this document. (Show Details)Oct 18 2018, 12:19 AM
tsimonq2 edited the content of this document. (Show Details)Oct 19 2018, 4:14 PM
tsimonq2 edited the content of this document. (Show Details)Oct 19 2018, 4:20 PM
tsimonq2 edited the content of this document. (Show Details)
tsimonq2 edited the content of this document. (Show Details)Oct 19 2018, 11:51 PM
wxl edited the content of this document. (Show Details)Sat, Dec 1, 11:10 PM