Tags

Differences between revisions 174 and 175
Revision 174 as of 2011-03-14 22:14:34
Size: 19931
Editor: 71-209-55-185
Comment: should not have been renamed to linex
Revision 175 as of 2011-03-14 22:17:35
Size: 19990
Editor: c-98-246-63-231
Comment: page was renamed from https:/wiki.ubuntu.com/Bugs/Tags
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from https:/wiki.ubuntu.com/Bugs/Tags

information_little.png This page is part of the Bug Squad’s KnowledgeBase - pages with information about how to triage bugs.

Tags provide us ways to group bugs across packages, easily find certain types of bugs or divide a package's bug reports into smaller parts.

Below are some standard tags and information about when to use the tag when working on bug reports about Ubuntu.

The vast majority of these tags are included in a greasemonkey script which is part of the Launchpad Greasemonkey Scripts project. These are also made available in a Firefox extension from a PPA.

Different ways you can help

Tag

Use case

`bitesize`

This bug is easy to fix and suitable for new contributors.

`needs-artwork`

A bug that needs new artwork to be created

`needs-coding`

A bug that needs new source code to be written

`needs-design`

A bug that needs UI design done first

`needs-packaging`

Packaging requests - software that isn't packaged for Ubuntu yet

`needs-sound`

A bug that needs new sound to be created

Generic bug tags

Tag

Use case

`apport-bug`

A bug reported using "Report a Problem" in an application's Help menu contains lots of details!

`apport-collected`

A bug that has had apport-collect ran against it which will contain additional information

`apport-crash`

A crash reported by apport - Ubuntu's automated problem reporter

`apport-package`

A bug reported by apport when a package failed to install or upgrade

`derivatives`

Bugs related to Derivatives

`desktop-file`

The bug requests the addition/fix of a .desktop file.

`fix-to-verify`

A bug that is Fix Released and should be verified when performing iso testing of daily builds or milestones

`ftbfs`

Bugs describing build failures of packages.

`gobuntu`

Bugs related to Gobuntu

`hw-specific`

A bug that requires a specific piece of hardware to duplicate

`iso-testing`

A bug found when performing iso testing and also tracked at https://iso.qa.ubuntu.com/

`likely-dup`

The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.)

`manpage`

This bug is about a package's manpage being incorrect.

`metabug`

This bug has a high probability of duplicate reports being filed.

`nautilus-desktop-icons`

Bugs related to the Nautilus desktop, especially the alignment, display and grid of icons.

`needs-devrelease-testing`

A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release

`needs-reassignment`

A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to

`packaging`

The bug is likely to be a packaging mistake.

`screencast`

This bug report includes a screencast of the bug in action!

`string-fix`

This bug is a string fix (not code) and is great for new contributors. For spelling and grammatical errors.

`touch`

an issue with touch support in applications or X

`triage-mentoring-available`

This bug has been identified as one that could use some additional information and another triager is offering guidance for getting that information.

`units-policy`

A bug that violates the UnitsPolicy

`unmetdeps`

Bugs that indicate packages not being installable due to missing dependencies.

`upgrade-software-version`

Bugs that request new software versions - please help reviewing them carefully.

`work-intensive`

triaging requires intensive work to validate/reproduce

Application Specific Tags

Open Office

Network Manager

Include: Nothing found for "== Bug Tags =="!

Include: Nothing found for "^The previously described tags are specific"!

Available languages: Italiano,

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

Bug Summary

If a network-manager bug report is about not being able to connect the title or summary should be in the format:

"[CHIPSET] cannot connect to (ENCRYPT_METHOD)"

where the CHIPSET is the wireless driver used and ENCRYPT_METHOD is the encryption method used by your wireless network.

Understanding your bug and getting more information

Getting debug logs

You can then follow developers' intructions on a bug report for the exact command line to use; or run it directly as such:

Getting NetworkManager debug logs

sudo /usr/lib/NetworkManager/debug-helper.py --nm debug

Then get the logs which will be written to /var/log/syslog. To disable it, pass info instead of debug in the above command, or reboot.

Getting ModemManager debug logs

sudo /usr/lib/NetworkManager/debug-helper.py --mm debug

Then get the logs which will be written to /var/log/syslog. To disable it, pass info instead of debug in the above command, or reboot.

See also DebuggingModemmanager.

Getting wpasupplicant debug logs

sudo /usr/lib/NetworkManager/debug-helper.py --wpa msgdump

Then get the logs which will be written to /var/log/syslog. To disable it, pass info instead of debug in the above command, or reboot.

Getting a capture of syslog

Mixing and mashing the above is perfectly acceptable as well if you want to see how NetworkManager and other parts of the stack interact together.

In order to understand whats going on and track down issues, its good to have a full log. To do so, capture the complete test case and submit the whole file (don't cut out what you think is important). Please add markers in the log file so the bug triager can easily see what actions the user takes at what point of time (this isn't essential, but helps a lot).

To capture the syslog, do:

 tail -n0 -f /var/log/syslog > /tmp/syslog

and to stop capturing do Ctrl-C (you will have to type your other commands in an other window or tab)

Adding markers is just like adding new lines with an editor that show the triager what happened at what point of time. You can also do this on the fly as you test with the command logger "[ clicked on wireless network 'ubuntu']" .

Example marker:

Sep  6 08:12:30 ...

[ clicked on wireless network 'ubuntu']

Sep  6 08:12:31 ...
...

Handling 3G / modem issues

An few extra things that are very helpful to add in case of issues with 3G:

The output of udevadm for tty devices, and output of lsusb:

$ udevadm info --query=all --path=/sys/class/tty/... --attribute-walk

$ lsusb

A Testcase

A good testcase is a step by step instruction to reproduce your bug starting with driver unloaded and NetworkManager stopped.

First, stop NetworkManager:

sudo service network-manager stop

Then unload your driver:

sudo modprobe -r DRIVER

Next, load the driver:

sudo modprobe DRIVER

and finally start NetworkManager:

sudo service network-manager start

Update Manager

Tag

Use case

lucid2precise

Bugs related to upgrades from Lucid Lynx (10.04) to Precise Pangolin (12.04).

cdrom-upgrade

Bugs related to an upgrade from CD-ROM or DVD media.

Firefox/Xulrunner Stable Upgrade Regressions

`ffox36-hardy`

Regressions on Hardy due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2

`ffox36-jaunty`

Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2

`ffox36-karmic`

Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2

Other specific bug tags

Ayatana

Specific bugs concerning parts of the Ayatana project.

Tag

Use case

`app-menu`

Bugs related to the App Menu that will be used for the first time in the Ubuntu Maverick Netbook Edition.

`indicator-applet`

Bugs related to the use of the Indicator Applet that are not in the 'indicator-applet' package (no Application Indicators!)

`indicator-application`

Bugs related to the use of Indicator Application that are not in the 'indicator-application' package

`trayaway`

Bugs related to the Notification Area transition.

Hardware Specific

Tag

Use case

`ac97-jack-sense`

This bug deals with headphone sense for AC'97 based codecs (0401)

`hda-jack-sense`

This bug deals with headphone sense for HDA based codecs (0403)

`macbook`

These bugs deal with Mac Book systems

`macbookpro`

These bugs deal with Mac Book Pro systems

`ps3`

Some bug reports are about people running Ubuntu on a Playstation 3

`ume`

These bugs deal with Ubuntu Mobile and Embeded systems

`armel`

These bugs deal with Ubuntu arm systems

Historical Tags

These tags were relevant previously for Ubuntu bugs and may still appear in some bugs. The needs retracing tags are added automatically for Gutsy.

Tag

Use case

`need-amd64-retrace`

The bug contains a crash report that needs retracing with apport-retrace on amd64

`need-i386-retrace`

The bug contains a crash report that needs retracing with apport-retrace on i386

`need-powerpc-retrace`

The bug contains a crash report that needs retracing with apport-retrace on powerpc

Kernel Specific

Tag

Use case

`apport-kerneloops`

This Kernel Oops was reported using apport.

`bitesize`

With regards to the kernel, this includes things like enabling modules and changing kernel config options

`cherry-pick`

A kernel bug that has a git commit SHA from the upstream kernel

`hibernate resume`

This bug was triggered by a hibernate/resume failure

`kernel-bug`

A "BUG:" message output was noted in the logs but it did not contain an Oops

`kernel-oops`

This bug causes a kernel Oops message

`needs-upstream-testing`

This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds

`suspend resume`

This bug was triggered by a suspend/resume failure

`xorg-needs-kernel-fix`

This is an xorg bug which is dependent on a kernel patch

For more tags see Kernel/Tagging.

Kubuntu Specific

Tag

Use case

`guidance-powermanager`

This kde-guidance bug is in powermanager

`kde-guidance-displayconfig`

This kde-guidance bug is in displayconfig

`kde-guidance-mountconfig`

This kde-guidance bug is in mountconfig

`kde-guidance-serviceconfig`

This kde-guidance bug is in serviceconfig

`kde-guidance-userconfig`

This kde-guidance bug is in userconfig

`kde-guidance-wineconfig`

This kde-guidance bug is in wineconfig

`needs-upstream-report`

This bug needs the report to be forwarded to the upstream project

`needs-upstream-sync`

This bug has been forwarded to the upstream project which has released a fix that has not been merged yet

`upstream`

This bug is reported to the upstream project

More specific

Tag

Use case

`a11y`

This bug is an accessibility problem.

`dxteam`

This bug is specifically targeted by Canonical developers, only to be associated with the 'notifications' tag.

`ec2-images`

This bug is related to Ubuntu on EC2.

`java-headless`

This bug is related to a Java program or library that could run headless but depends on a full Java environment (including graphics and sound)

`ldap`

This bug is a LDAP problem.

`linuxfirmwarekit`

This bug contains Linux firmware kit test results.

`ngo`

This bug affects NGOs.

`notifications`

This bug is related to the new notification system (notify-osd) introduced in Jaunty

`nscd`

This bug deals with nscd which is part of the glibc package

`usability`

This bug is a usability problem.

`rtl`

This bug is a right-to-left problem.

`uec-images`

This bug is related to the Ubuntu Enterprise Cloude (UEC) images

`xinerama`

This bug is a xinerama problem. Multiple-monitor configuration.

Patch specific

`patch`

This bug has a patch attached to it

`patch-accepted-debian`

This bug has a patch attached to it that has been accepted by Debian

`patch-accepted-upstream`

This bug has a patch attached to it that has been accepted by upstream

`patch-forwarded-debian`

This bug has a patch attached to it that has been forwarded to Debian.

`patch-forwarded-upstream`

This bug has a patch attached to it that has been forwarded upstream

`patch-needswork`

This bug has a patch attached to it that needs some work done on it

`patch-rejected`

This bug has a patch attached to it that was not included in Ubuntu

`patch-rejected-debian`

This bug has a patch attached to it that has been rejected by Debian

`patch-rejected-upstream`

This bug has a patch attached to it that has been rejected by upstream

`patch-upstreaminput`

This bug has a patch attached to it that has been forwarded upstream and requires their input or incorporation

Regression specific

See the regression tracker for a list of these bugs and QATeam/RegressionTracking for more information.

Tag

Use case

`regression-release`

A bug in a release that was not present in a previous release. Should be used together with a separate tag for the release the regression was found in.

`regression-update`

A bug in a stable release that was introduced by a package from -updates

`regression-proposed`

A bug in a stable release of Ubuntu that was found when testing a package from -proposed

`regression-retracer`

An apport crash bug report that was identified by the retracer as having the same characteristics as a fixed crash report

`regression-potential`

DEPRECATED, do not use

SRU Specific

See StableReleaseUpdates for more information.

Tag

Use case

`regression-proposed`

A bug in a stable release of Ubuntu that was found when testing a package from -proposed

`verification-done`

A Stable Release Update bug with a package in -proposed that has been confirmed to fix the bug

`verification-failed`

A Stable Release Update bug with a package in -proposed that has been verified to not fix the bug

`verification-needed`

A Stable Release Update bug with a package in -proposed needing testing

X Specific

For X tags please check X Tagging with all the official X tags


Go back to BugSquad.
CategoryBugSquad

Bugs/Tags (last edited 2020-12-09 16:58:48 by racb)