Tags
|
Size: 13901
Comment:
|
Size: 14033
Comment: Add the needs-artwork tag discussed at UDS
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 30: | Line 30: |
| || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-artwork|`needs-artwork`]] || A bug that needs new artwork to be created || |
|
This page is part of the 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.
Generic
Tag |
Use case |
This bug has a high probability of duplicate reports being filed. |
|
The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) |
|
This bug report includes a screencast of the bug in action! |
|
This bug is easy to fix and suitable for new contributors. |
|
This bug is a string fix (not code) and is great for new contributors. For spelling and grammatic errors. |
|
This bug is about a package's manpage being incorrect. |
|
This bug has been identified as one that could use some additional information and another triager is offering guidance for getting that information. |
|
The bug is likely to be a packaging mistake. |
|
The bug requests the addition/fix of a .desktop file. |
|
Bugs that request new upstream versions - please help reviewing them carefully. |
|
Bugs describing build failures of packages. |
|
Bugs that indicate packages not being installable due to missing dependencies. |
|
Packaging requests - software that isn't packaged for Ubuntu yet |
|
A crash reported by apport - Ubuntu's automated problem reporter |
|
A bug reported using "Report a Problem" in an application's Help menu contains lots of details! |
|
A bug reported by apport when a package failed to install or upgrade |
|
A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release |
|
A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to |
|
A bug that needs new artwork to be created |
|
A bug found when performing iso testing and also tracked at https://iso.qa.ubuntu.com/ |
|
A bug that requires a specific piece of hardware to duplicate |
|
A bug that is Fix Released and should be verified when performing iso testing of daily builds or milestones |
|
Bugs related to Gobuntu |
|
Bugs related to Derivatives |
|
A bug that contains xorg.conf attachments that all passed validation |
|
A bug that contains at least one xorg.conf attachment that failed validation |
Kernel Specific
Tag |
Use case |
With regards to the kernel, this includes things like enabling modules and changing kernel config options |
|
A kernel bug that has a git commit SHA from the upstream kernel |
|
A "BUG:" message output was noted in the logs but it did not contain an Oops |
|
This bug causes a kernel Oops message |
|
This bug was triggered by a suspend/resume failure |
|
This bug was triggered by a hibernate/resume failure |
SRU Specific
See StableReleaseUpdates for more information.
Tag |
Use case |
A Stable Release Update bug with a package in -proposed needing testing |
|
A Stable Release Update bug with a package in -proposed that has been confirmed to fix the bug |
|
A Stable Release Update bug with a package in -proposed that has been verified to not fix the bug |
|
A bug in a stable release of Ubuntu that was found when testing a package from -proposed |
Regression specific
See the regression tracker for a list of these bugs and QATeam/RegressionTracking for more information.
Tag |
Use case |
A bug in the development release that was not present in the stable release. When this bug is a result of a transition in the default application for a task, also use the `default-application` tag. |
|
A bug in a stable release that was not present in a previous stable release |
|
A bug in a stable release that was introduced by a package from -updates |
|
A bug in a stable release of Ubuntu that was found when testing a package from -proposed |
|
An apport crash bug report that was identified by the retracer as having the same characteristics as a fixed crash report |
More specific
Tag |
Use case |
This bug is a LDAP problem. |
|
This bug deals with nscd which is part of the glibc package |
|
This bug is a usability problem. |
|
This bug is an accessibility problem. |
|
This bug is a xinerama problem. Multiple-monitor configuration. |
|
This bug contains Linux firmware kit test results. |
|
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) |
|
This bug is related to the new notification system (notify-osd) introduced in Jaunty |
|
This bug is specifically targeted by Canonical developers, only to be associated with the 'notifications' tag above |
Hardware Specific
Tag |
Use case |
This bug deals with headphone sense for AC'97 based codecs (0401) |
|
This bug deals with headphone sense for HDA based codecs (0403) |
|
Some bug reports are about people running Ubuntu on a Playstation 3 |
|
These bugs deal with Mac Book systems |
|
These bugs deal with Mac Book Pro systems |
|
These bugs deal with Ubuntu Mobile and Embeded systems |
Kubuntu Specific
Tag |
Use case |
This bug needs the report to be forwarded to the upstream project |
|
This bug is reported to the upstream project |
|
This bug has been forwarded to the upstream project which has released a fix that has not been merged yet |
|
This kde-guidance bug is in powermanager |
|
This kde-guidance bug is in displayconfig |
|
This kde-guidance bug is in userconfig |
|
This kde-guidance bug is in mountconfig |
|
This kde-guidance bug is in serviceconfig |
|
This kde-guidance bug is in wineconfig |
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,
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
There is a lot of debugging information available on the GNOME Live wiki: NetworkManager/Debugging.
You can also take a look at Darren Albers' FAQ.
There is additional information on DebuggingNetworkManager/ReasonCodes for disconnection and network changes available.
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
By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:
$ sudo nmcli general logging level DEBUG domains ALL
You do not need to restart NetworkManager to begin seeing debug messages logged to journalctl. You can watch the NetworkManager logs:
$ sudo journalctl -f -u NetworkManager
Getting ModemManager debug logs
Manually run with debug enabled:
$ sudo /usr/sbin/ModemManager --debug $ sudo /usr/sbin/NetworkManager --debug --log-level=DEBUG
See also DebuggingModemmanager.
You do not need to restart ModemManager to begin seeing debug messages logged to journalctl. You can watch the ModemManager logs:
$ sudo journalctl -f -u ModemManager
Getting wpasupplicant debug logs
Change the log level:
$ sudo wpa_cli log_level debug
You do not need to restart wpa_supplicant to begin seeing debug messages logged to journalctl. You can watch the wpa_supplicant logs:
$ sudo journalctl -f -u wpa_supplicant
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
Here are a 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
Captive portal
You can check the status from the cli using:
$ nmcli networking connectivity check
Since 1.38, you can set Environment=NM_LOG_CONCHECK=1 in NetworkManager.service and restart the service to get additional debug logging about connectivity checking.
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 and unload your driver:
$ sudo systemctl stop NetworkManager $ sudo modprobe -r DRIVER
Next, load the driver and start NetworkManager:
$ sudo modprobe DRIVER $ sudo systemctl start NetworkManager
Netplan
A configuration abstraction mechanism has added to NetworkManager as of Ubuntu 23.10, called Netplan. There is a whole library of netplan documentation available. However here is a very basic amount of netplan debugging.
Netplan uses the files in /etc/netplan/*.yaml to generate the running profiles you find at /run/NetworkManager/system-connections/*.nmconnection. If you suspect a feature defined in your /etc/netplan/*.yaml files is not being used, it is a good idea to check that the content matches up.
If you find a netplan bug, please report it here: https://bugs.launchpad.net/netplan/+filebug
Update Manager
Tag |
Use case |
Bugs related to upgrades from Lucid Lynx (10.04) to Precise Pangolin (12.04). |
|
Bugs related to an upgrade from CD-ROM or DVD media. |
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 |
The bug contains a crash report that needs retracing with apport-retrace on amd64 |
|
The bug contains a crash report that needs retracing with apport-retrace on i386 |
|
The bug contains a crash report that needs retracing with apport-retrace on powerpc |
Go back to BugSquad.
CategoryBugSquad
Bugs/Tags (last edited 2020-12-09 16:58:48 by racb)