FindRightPackage

Differences between revisions 54 and 145 (spanning 91 versions)
⇤ ← Revision 54 as of 2009-02-06 08:25:55 →
Size: 9950
Editor: port-213-160-23-156
Comment: Replace the completely wrong suspend/hibernate section
← Revision 145 as of 2022-11-17 15:07:29 → ⇥
Size: 13864
Editor: paulw2u
Comment: Fixed grammatical error
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(BugSquad/Header)>> <<Include(QATeam/Header)>>
Line 4: Line 4:
Finding the right source package for a bug, when submitting or triaging, is essential to ensure that the right people will see the bug. These tricks won't necessarily work in all cases, but will help you most of the time.

A short introductory video, done by Dereck Wonnacott: http://videos.ubuntu.com/qa/assigning-packages-to-bugs.ogg

You can help right away with the [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_contact=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on&search=Search|Bugs with no home]]. Most simply need to be associated with the package name that right in the title.
== When installing Ubuntu, Kubuntu, Edubuntu or Xubuntu ==

If you encounter a bug when '''booting''' the Live CD or the alternate installer, then the bug should be filed about the kernel. The "Kernel related bugs" section contains information on where to file the bug.

If you encounter a bug when '''using''' the Live CD environment, not the install process, and there is no more obvious package to use (e.g. a particular application is failing), then the package used for the bug should be [[https://bugs.launchpad.net/ubuntu/+source/casper/+filebug|casper]].

If you encounter a bug when installing Ubuntu from the Live CD the package used for the bug should be [[https://bugs.launchpad.net/ubuntu/+source/ubiquity/+filebug|ubiquity]]. You can learn more about the proper way to submit a bug about ubiquity by reading [[https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs|debugging ubiquity]].

If you encounter a bug when installing from the Alternate CD installer the package used for the bug should be [[https://bugs.launchpad.net/ubuntu/+source/debian-installer/+filebug|debian-installer]].

== Boot process before login screen ==

When your system is booting and shutting down, before you are presented with a login screen, you may see a static image and messages about the boot or shutdown process. This application is called usplash and bugs regarding it should be filed using the [[https://bugs.launchpad.net/ubuntu/+source/usplash/+filebug|usplash]] package.

== Login Screen ==

The login screen is where you enter your username and password. If you are using Ubuntu the default display manager is gdm and bugs should be filed about the [[https://launchpad.net/ubuntu/+source/gdm/+filebug|gdm]] package. If you are using Kubuntu the default display manager is kdm and bugs should be filed about the [[https://launchpad.net/ubuntu/+source/kdebase/+filebug|kdebase]] package.

== Graphic Environment ==

The X Window system provides the underlying graphic environment of your desktop. It ensures that your video card and monitor work and provides a basis for GNOME or KDE to run on. You can learn more about the proper way to submit a bug regarding the graphic environment, your video card or monitor by reading [[https://help.ubuntu.com/community/DebuggingXAutoconfiguration|debugging X]]. These bugs should be filed using the [[https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug|xorg]] package.

== Printing System ==

The printing system used in Ubuntu is the Common UNIX Printing System (or CUPS). If you encounter a bug dealing with printing it should generally be filed using the [[https://bugs.launchpad.net/ubuntu/+source/cups/+filebug|cups]] package. You can learn more about the proper way to submit a bug regarding CUPS by reading [[https://wiki.ubuntu.com/DebuggingPrintingProblems|debugging printing problems]].

== Sound ==

If you encounter a situation where your sound does not work, is muted, or your headphone jack does not work as expected the correct package depends on the version of the kernel you are using. If you do not know what version of the kernel you are running the command '''uname -r''' will return the kernel release. The "Kernel related bugs" section contains information on where to file the bug. You can learn more about the proper way to submit a bug regarding sound by reading [[https://wiki.ubuntu.com/DebuggingSoundProblems|debugging sound problems]].

== Kernel related bugs ==

The correct package for bugs in the Linux kernel is dependent upon the release of Ubuntu being used. In the event that you do not know what kernel version you are running the command '''uname -r''' will return the kernel release. You can learn about the kernel team's [[https://wiki.ubuntu.com/KernelTeamBugPolicies|bug policies]] and information they need to troubleshoot your bug. Note that it is best to verify if your bug exists against the most recently released kernel and file your bug accordingly.

 * For Dapper (6.06) the correct package is [[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+filebug|linux-source-2.6.15]].
 * For Feisty (7.04) the correct package is [[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+filebug|linux-source-2.6.20]].
 * For Gutsy (7.10) the correct package is [[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+filebug|linux-source-2.6.22]].
 * For Hardy (8.04) the correct package is [[https://bugs.launchpad.net/ubuntu/+source/linux/+filebug|linux]].
 * For Intrepid (8.10) the correct package is [[https://bugs.launchpad.net/ubuntu/+source/linux/+filebug|linux]].

== Suspend / Hibernate ==

Problems with suspend/hibernate/resume on Ubuntu are generally the result of bugs in one of three main components. There is the desktop component ([[https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager|gnome-power-manager]] in the case of Ubuntu), responsible for setting policy on when the system should be suspended or resumed and signalling the system to do so; [[https://bugs.launchpad.net/ubuntu/+source/pm-utils|pm-utils]], which is responsible for getting the system into a state where it can be suspended or hibernated, and handling any cleanup after resume; and the [[https://bugs.launchpad.net/ubuntu/+source/linux|linux kernel]], which implements the actual suspending and resuming and is generally the responsible package when there are any hardware-related failures after resume.

== Find the program executable ==

Sometimes it is not so clear the name of the program or process running, for instance if you start the program through a menu. There are a few ways to try and figure out what it is:

 * Launch the program from the menu and in a terminal execute '''xprop WM_CLASS'''. This will present you with a crosshair cursor with which you should click on the running program. In the terminal you will see a message like '''M_CLASS(STRING) = "konsole", "Konsole"''' from which you can determine the program is konsole.

 * Launch the program from the menu and in a terminal window use the command '''ps ax''' or '''ps aux''' to display all processes running. You can also run '''top''' which by default displays the process using the CPU the most at the top. It is possible to change the order in which processes are displayed, for example pressing "Shift+m" will display the process using the most memory at the top.

If you are not sure you have found the right process, try using ''top'' and ''ps'' before and after starting the program, and see what new processes have appeared.

 * '''apropos <keyword>''' and '''apt-cache search <keyword>''' may also give some clues.

 ''Example: you have problems with System -> Preferences -> Screen Resolution. The process name is gnome-display-properties.''

== Getting more information ==

Sometimes it is possible for an application to silently fail when launched from the program menu. One example of this is VMware Player. If you launch it from the menu and do not have the module versions for your currently running kernel the application will silently fail. However, if you execute 'vmplayer' in a terminal you will receive a more informative error message saying that 'vmware is installed, but it has not been (correctly) configured for this system' followed by steps to fix it. Once you have discovered the program executable name (by following the steps above) try executing it in a terminal to see if you get more information that can help debug your issue.

Some programs also leave error messages in '''~/.xsession-errors'''. Take a look there and see if there is something that can help debug your issue.

== Find the binary package ==

Once you have identified the process name you can try '''type <process_name>''' or '''which <process_name>''' or '''locate <process_name>''' to get the full path of the program.

Then run '''dpkg -S <full path of the program>''' to see which binary package it belongs to.

 ''Example: locate gnome-display-properties''

 ''dpkg -S /usr/bin/gnome-display-properties''

Another useful way to find out what package an application or even a file belongs to is to use [[http://packages.ubuntu.com/#search_packages|packages.ubuntu.com]]. There you can search for files that are parts of packages. This can be very helpful when triaging where you may not have the particular package installed.		 To ensure that the right people see a bug report, every report should identify the software [[Package|package]] related to the bug. When running `ubuntu-bug` (see [[https://help.ubuntu.com/community/ReportingBugs | ReportingBugs]]), one must sometimes specify the package manually. This page contains information to help identify the related package.

== Common Scenarios ==

In most situations, you can identify the problem package based on the scenario in which the bug occurs. Below is a list of common scenarios and instructions to find the related package.

=== Applications ===

Applications in released versions of Ubuntu no longer have a "Report a Problem" menu item. Thus, you must first determine the executable name for the application and then find the package to which the executable belongs.

==== Apport ====

Since Natty Narwhal (11.04) you can call ubuntu-bug with -w or --window which makes it possible for you to click on the window of the application and apport will identify the package name by itself.

==== Determining the Executable Path ====

If you launched the application through the Main Menu, you can use the menu editor to find which command it runs:

===== GNOME =====

 1. Launch System -> Preferences -> Main Menu.
 2. Select the item for the application. (For example, System -> Preferences -> Display.)
 3. Click "Properties" button.
 4. Write down the "Command" value. This is the executable name. (In this case, "gnome-display-properties".)
 5. Open a Terminal (Applications -> Accessories -> Terminal).
 6. In the terminal, type `which [executable name]`. (In this case, `which gnome-display-properties`.)
 7. Write down the value printed on the terminal. This is the full executable path.

 {{attachment:gnome-launcher-props.png}}

===== KDE =====

 1. Open the Menu Editor by clicking on the K button (Kickoff Application Launcher) in the Desktop Panel with the right mouse button and selecting "Menu Editor".
 2. Select the item for the application. (For example, System -> Dolphin (File Manager))
 3. Write down the first value in the "Command" filed in the General tab. This is the executable name. (In this case, "dolphin".)
 4. Open a Terminal with Konsole (K -> Applications -> System -> Terminal).
 5. In the terminal, type `which <executable name>`. (In this case, `which dolphin`)
 6. Write down the value printed on the terminal. This is the full executable path.

 {{attachment:kde-menu-editor-dolphin.png}}

===== Any =====

If you did not launch the application through the Main Menu or cannot use the Menu Editor, you can use ''xprop'' to find the related executable.

 1. Launch the application.
 2. Open a Terminal (GNOME: Applications -> Accessories -> Terminal | KDE: K -> Applications -> System -> Terminal).
 3. In the terminal, type `xprop WM_CLASS`. Your mouse pointer should now turn to crosshairs.
{{attachment:xprop1.png}}
 4. Click anywhere in the application's window.
 5. The terminal will now list a line like `WM_CLASS(STRING) = "deja-dup", "Deja-dup"`. Write down the first value ("deja-dup").
{{attachment:xprop2.png}}
 6. In the terminal, type `locate -b "\[executable name]"`. (In this case, `locate -b "\deja-dup"`.) The backslash (\) is important!
 7. Write down the line printed on the terminal. (If there are multiple lines, use the first one.) This is the full executable path.

==== Finding the Package Name ====

After you have found the executable path, finding the package name is easy. Just run `dpkg -S [full executable path]`. For example, `dpkg -S /usr/bin/gnome-display-properties`. This will print the package name: you're done!

Another tool useful when triaging bugs is '''apt-file''': `apt-file search terminator`. This utility works like `dpkg -S` but searches all packages instead of only those you have installed.

=== When installing Ubuntu (or Derivatives) ===

If you encounter a bug when installing Ubuntu, Kubuntu, Edubuntu, or other derivatives, the bug is probably one of a small set of packages.

 * If you encounter the bug when ''booting'' the Live CD (or alternative installer), file the bug [[#Kernel|against the kernel]].
 * If you encounter the bug when installing Ubuntu from the Desktop CD (most common method), the package is `ubiquity`. (See [[DebuggingUbiquity/AttachingLogs]].)
 * If you encounter the bug when installing from the Alternate or Server CDs, the package is `debian-installer`.

=== When upgrading Ubuntu (or derivatives) ===

If you encounter a bug while upgrading Ubuntu (for example, from 17.04 to 17.10), the problem package is `ubuntu-release-upgrader`. Please attach the log files contained in "/var/log/dist-upgrade/".

=== During boot ===

If you encounter a bug with the boot splash screen (typically an Ubuntu logo displayed during boot), the package is:

 * `plymouth`

If the screen goes blank after the splash screen (about the time the login screen should come up), report the bug against `xorg`.

If the boot errors or freezes even in "recovery mode", the bug should be reported against [[#Kernel|the kernel]].

=== At the login screen ===

If you encounter a bug at the login screen, the package is the display manager:

 * In Ubuntu 11.10 to 17.04, it is `LightDM`. In previous versions of Ubuntu and Edubuntu it was `gdm`.
 * In Ubuntu 17.10 or above it is `gdm3`.
 * In Xubuntu 11.10 or above, it is `LightDM`. In previous versions of Xubuntu it was `gdm`.
 * In Kubuntu 15.04 or above, it is `sddm`. In previous versions of Kubuntu it was `kdm`.
 * In Lubuntu 18.10 or above, it is `sddm`. In Lubuntu 12.04 through 18.04 it was `LightDM`, and prior versions of Lubuntu it was `lxdm`.
 * In Ubuntu GNOME it is `gdm3`.
 * In Ubuntu MATE it is `LightDM`.
 * In Ubuntu Unity it is `LightDM`

=== Graphical Environment ===

The Ubuntu graphical environment is provided by a combination of the Linux kernel and the X Window System (aka X.org).

The following symptoms typically are due to GPU issues in the kernel DRM driver (linux package):

 * Blank or solid-colored screen instead of login screen, or immediately after login
 * System freezes completely
 * Wrong default screen resolution

If you have any of the following symptoms, the issue is with X and the package to report against is `xorg`: (See [[X/Troubleshooting]] if you want to pin-point the problem.)

 * The graphical session terminates and returns to the login screen
 * Fonts extremely big or small

If your problem is with the actual desktop (for example, with desktop icons):

 * In Ubuntu and Edubuntu, the desktop is managed by the file browser, `nautilus`.

If your problem is with window management (for example, focus stealing);

 * If you are using compiz (visual effects), the package is `compiz`.
 * In Ubuntu and Edubuntu, the no-effects window manager is `metacity`.
 * In Xubuntu, the window manager is `xfwm4`.
 * In Kubuntu, the window manager is `kwin`.

If your problem is with the Administration authentication dialog (where you enter your password), the package is:

 * `gksu` in Ubuntu and Edubuntu
 * `kdesudo` in Kubuntu

If your problem is with the Notification System, the package is:

 * `notify-osd` in Ubuntu, Xubuntu and Edubuntu

Lock screen problems:

 * If your problem is with the lock screen itself, the package is gnome-screensaver until 13.10 or unity from 14.04 onwards. For more info, check https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks

=== Printing ===

All printing in Ubuntu is done via the Common UNIX Printing System (CUPS). The package is `cups`. (See also [[DebuggingPrintingProblems]].)

=== Sound ===

See [[DebuggingSoundProblems|Debugging Sound Problems]] for reporting/triage instructions for sound problems.

You might want to try [[https://help.ubuntu.com/community/SoundTroubleshooting|Sound Troubleshooting]] first.

=== Hardware Malfunctions ===

If a piece of hardware is malfunctioning, typically the problem package is [[#Kernel|the kernel]]. ''However'', if the problem is with a storage device (internal or external) in 9.10 Karmic Koala or above, problems should be reported with `ubuntu-bug storage`. (If triaging, see the "Use Storage Symptom" standard reply.)

=== Network ===

Usual candidate packages are the kernel (file bugs under the "linux" package) and network-manager.

=== Suspend and Hibernate ===

Suspend and hibernate are treated as two completely different issues, necessitating one bug report for each. While there are many different packages responsible for :

 * [[#Kernel|The kernel]] implements the actual suspending and resuming and is generally the responsible package when there are any hardware-related failures after resume. Please file all bugs against the package linux first, unless you know exactly the root cause commit in the code for the responsible package. This is how the high majority of suspend/hibernate bugs are due to outdated BIOS, and buggy driver implementations, versus userspace bugs.
 * `gnome-power-manager` (in Ubuntu and Edubuntu) is responsible for setting policy on when the system should be suspended or resumed and signaling the system to do so.
 * `pm-utils` is responsible for getting the system into a state where it can be suspended or hibernated, and handling any cleanup after resume.

If you are unsure which package is causing the problem, a safe bet is the kernel (package 'linux'), ''but make sure the bug title includes "suspend" or "hibernate"''.

=== Hotkeys ===

Hotkey handling, such as volume and suspend keys, involves multiple packages. See [[Hotkeys/Troubleshooting]] for specific packages involved and troubleshooting instructions. If a hotkey does nothing or is mapped to a wrong function, the problem package is likely `udev`.

=== Ubuntu mirror issues ===

Issues with Ubuntu [[Mirrors]] (the servers from which you download packages) should be reported to mirrors@ubuntu.com and ''not'' on Launchpad.

=== Ubuntu Touch ===

Check the guidelines at: https://wiki.ubuntu.com/Touch/Contribute#How_to_report_bugs

== Package-specific instructions ==

Some packages have changed names through versions of ubuntu and others need special care while reporting. This section lists these caveats.

=== Filesystem problems ===

Usual suspects are the kernel, gvfs and mountall.

=== Kernel ===

The correct package for bugs about the kernel is `linux`.

Please read [[KernelTeam/KernelTeamBugPolicies]] when reporting bugs against the kernel.

=== MySQL ===

Please put MySQL bugs in the appropriate package depending on the version of MySQL.

Currently we have:
 * mysql-5.5 - the default version in Trusty (14.04)
 * mysql-5.6
 * mysql-5.7
 * mysql-8.0

=== Incorrectly reported packages ===

The following packages often receive bug reports in error. The correct package is shown after the '->':

 * chromium -> chromium-browser
 * dash -> unity
 * discover -> plasma-discover
 * epiphany -> epiphany-browser ([[https://lists.ubuntu.com/archives/ubuntu-bugsquad/2010-May/002202.html|BugSquad discussion]]).
 * gnome -> gnome-shell or gnome-session
 * kernel-package -> linux
 * snap -> snapd
 * software-center -> gnome software or the 'snap-store-desktop' project if relating to the snap version of 'GNOME Software'
 * ubuntu-settings -> gnome-control-center

also
 * focal - a [[https://wiki.ubuntu.com/FocalFossa|release]] name and not a package against which bugs should currently be reported

Bug reports for these packages should be moved to the correct packages so that they reach those that can investigate and / or fix any reported bugs,
Line 87: Line 224:
Many "binary packages" (that is, packages containing the software you run) may be built from the same "source package" (developers' source code), so bug reports are assigned to ''source'' packages and not binary packages. In rare cases, you must manually identify the source package from a binary package.
Line 90: Line 229:

Alternatively, you can use '''apt-cache show kdm''' and look for the '''Source:''' line to find the source package.

== Assigning already filed bugs ==

A short introductory [[ http://ubuntudevelopers.blip.tv/file/2688450/ | video ]], narrated by Dereck Wonnacott.
  * '''Warning''': This video advises triagers to assign bugs to the {{{acpi-support}}} package. This is wrong! Recent versions of Ubuntu use {{{pm-utils}}} for suspend-resume, {{{acpi-support}}} is not involved in this process. Do not assign bugs to this package, they will only have to be triaged again by a much smaller group of developers. Help is needed to get the above video updated.

You can help right away with the [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_contact=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on&search=Search|bugs with no home]]. Most simply need to be associated with the appropriate package.

To ensure that the right people see a bug report, every report should identify the software package related to the bug. When running ubuntu-bug (see ReportingBugs), one must sometimes specify the package manually. This page contains information to help identify the related package.

Common Scenarios

In most situations, you can identify the problem package based on the scenario in which the bug occurs. Below is a list of common scenarios and instructions to find the related package.

Applications

Applications in released versions of Ubuntu no longer have a "Report a Problem" menu item. Thus, you must first determine the executable name for the application and then find the package to which the executable belongs.

Apport

Since Natty Narwhal (11.04) you can call ubuntu-bug with -w or --window which makes it possible for you to click on the window of the application and apport will identify the package name by itself.

Determining the Executable Path

If you launched the application through the Main Menu, you can use the menu editor to find which command it runs:

GNOME

  1. Launch System -> Preferences -> Main Menu.

  2. Select the item for the application. (For example, System -> Preferences -> Display.)

  3. Click "Properties" button.
  4. Write down the "Command" value. This is the executable name. (In this case, "gnome-display-properties".)

  5. Open a Terminal (Applications -> Accessories -> Terminal).

  6. In the terminal, type which [executable name]. (In this case, which gnome-display-properties.)

  7. Write down the value printed on the terminal. This is the full executable path.

    gnome-launcher-props.png

KDE
  1. Open the Menu Editor by clicking on the K button (Kickoff Application Launcher) in the Desktop Panel with the right mouse button and selecting "Menu Editor".

  2. Select the item for the application. (For example, System -> Dolphin (File Manager))

  3. Write down the first value in the "Command" filed in the General tab. This is the executable name. (In this case, "dolphin".)

  4. Open a Terminal with Konsole (K -> Applications -> System -> Terminal).

  5. In the terminal, type which <executable name>. (In this case, which dolphin)

  6. Write down the value printed on the terminal. This is the full executable path.

    kde-menu-editor-dolphin.png

Any

If you did not launch the application through the Main Menu or cannot use the Menu Editor, you can use xprop to find the related executable.

  1. Launch the application.

  2. Open a Terminal (GNOME: Applications -> Accessories -> Terminal | KDE: K -> Applications -> System -> Terminal).

  3. In the terminal, type xprop WM_CLASS. Your mouse pointer should now turn to crosshairs.

xprop1.png

  1. Click anywhere in the application's window.

  2. The terminal will now list a line like WM_CLASS(STRING) = "deja-dup", "Deja-dup". Write down the first value ("deja-dup").

xprop2.png

  1. In the terminal, type locate -b "\[executable name]". (In this case, locate -b "\deja-dup".) The backslash (\) is important!

  2. Write down the line printed on the terminal. (If there are multiple lines, use the first one.) This is the full executable path.

Finding the Package Name

After you have found the executable path, finding the package name is easy. Just run dpkg -S [full executable path]. For example, dpkg -S /usr/bin/gnome-display-properties. This will print the package name: you're done!

Another tool useful when triaging bugs is apt-file: apt-file search terminator. This utility works like dpkg -S but searches all packages instead of only those you have installed.

When installing Ubuntu (or Derivatives)

If you encounter a bug when installing Ubuntu, Kubuntu, Edubuntu, or other derivatives, the bug is probably one of a small set of packages.

  • If you encounter the bug when booting the Live CD (or alternative installer), file the bug against the kernel.

  • If you encounter the bug when installing Ubuntu from the Desktop CD (most common method), the package is ubiquity. (See DebuggingUbiquity/AttachingLogs.)

  • If you encounter the bug when installing from the Alternate or Server CDs, the package is debian-installer.

When upgrading Ubuntu (or derivatives)

If you encounter a bug while upgrading Ubuntu (for example, from 17.04 to 17.10), the problem package is ubuntu-release-upgrader. Please attach the log files contained in "/var/log/dist-upgrade/".

During boot

If you encounter a bug with the boot splash screen (typically an Ubuntu logo displayed during boot), the package is:

  • plymouth

If the screen goes blank after the splash screen (about the time the login screen should come up), report the bug against xorg.

If the boot errors or freezes even in "recovery mode", the bug should be reported against the kernel.

At the login screen

If you encounter a bug at the login screen, the package is the display manager:

  • In Ubuntu 11.10 to 17.04, it is LightDM. In previous versions of Ubuntu and Edubuntu it was gdm.

  • In Ubuntu 17.10 or above it is gdm3.

  • In Xubuntu 11.10 or above, it is LightDM. In previous versions of Xubuntu it was gdm.

  • In Kubuntu 15.04 or above, it is sddm. In previous versions of Kubuntu it was kdm.

  • In Lubuntu 18.10 or above, it is sddm. In Lubuntu 12.04 through 18.04 it was LightDM, and prior versions of Lubuntu it was lxdm.

  • In Ubuntu GNOME it is gdm3.

  • In Ubuntu MATE it is LightDM.

  • In Ubuntu Unity it is LightDM

Graphical Environment

The Ubuntu graphical environment is provided by a combination of the Linux kernel and the X Window System (aka X.org).

The following symptoms typically are due to GPU issues in the kernel DRM driver (linux package):

  • Blank or solid-colored screen instead of login screen, or immediately after login
  • System freezes completely
  • Wrong default screen resolution

If you have any of the following symptoms, the issue is with X and the package to report against is xorg: (See X/Troubleshooting if you want to pin-point the problem.)

  • The graphical session terminates and returns to the login screen
  • Fonts extremely big or small

If your problem is with the actual desktop (for example, with desktop icons):

  • In Ubuntu and Edubuntu, the desktop is managed by the file browser, nautilus.

If your problem is with window management (for example, focus stealing);

  • If you are using compiz (visual effects), the package is compiz.

  • In Ubuntu and Edubuntu, the no-effects window manager is metacity.

  • In Xubuntu, the window manager is xfwm4.

  • In Kubuntu, the window manager is kwin.

If your problem is with the Administration authentication dialog (where you enter your password), the package is:

  • gksu in Ubuntu and Edubuntu

  • kdesudo in Kubuntu

If your problem is with the Notification System, the package is:

  • notify-osd in Ubuntu, Xubuntu and Edubuntu

Lock screen problems:

Printing

All printing in Ubuntu is done via the Common UNIX Printing System (CUPS). The package is cups. (See also DebuggingPrintingProblems.)

Sound

See Debugging Sound Problems for reporting/triage instructions for sound problems.

You might want to try Sound Troubleshooting first.

Hardware Malfunctions

If a piece of hardware is malfunctioning, typically the problem package is the kernel. However, if the problem is with a storage device (internal or external) in 9.10 Karmic Koala or above, problems should be reported with ubuntu-bug storage. (If triaging, see the "Use Storage Symptom" standard reply.)

Network

Usual candidate packages are the kernel (file bugs under the "linux" package) and network-manager.

Suspend and Hibernate

Suspend and hibernate are treated as two completely different issues, necessitating one bug report for each. While there are many different packages responsible for :

  • The kernel implements the actual suspending and resuming and is generally the responsible package when there are any hardware-related failures after resume. Please file all bugs against the package linux first, unless you know exactly the root cause commit in the code for the responsible package. This is how the high majority of suspend/hibernate bugs are due to outdated BIOS, and buggy driver implementations, versus userspace bugs.

  • gnome-power-manager (in Ubuntu and Edubuntu) is responsible for setting policy on when the system should be suspended or resumed and signaling the system to do so.

  • pm-utils is responsible for getting the system into a state where it can be suspended or hibernated, and handling any cleanup after resume.

If you are unsure which package is causing the problem, a safe bet is the kernel (package 'linux'), but make sure the bug title includes "suspend" or "hibernate".

Hotkeys

Hotkey handling, such as volume and suspend keys, involves multiple packages. See Hotkeys/Troubleshooting for specific packages involved and troubleshooting instructions. If a hotkey does nothing or is mapped to a wrong function, the problem package is likely udev.

Ubuntu mirror issues

Issues with Ubuntu Mirrors (the servers from which you download packages) should be reported to mirrors@ubuntu.com and not on Launchpad.

Ubuntu Touch

Check the guidelines at: https://wiki.ubuntu.com/Touch/Contribute#How_to_report_bugs

Package-specific instructions

Some packages have changed names through versions of ubuntu and others need special care while reporting. This section lists these caveats.

Filesystem problems

Usual suspects are the kernel, gvfs and mountall.

Kernel

The correct package for bugs about the kernel is linux.

Please read KernelTeam/KernelTeamBugPolicies when reporting bugs against the kernel.

MySQL

Please put MySQL bugs in the appropriate package depending on the version of MySQL.

Currently we have:

  • mysql-5.5 - the default version in Trusty (14.04)
  • mysql-5.6
  • mysql-5.7
  • mysql-8.0

Incorrectly reported packages

The following packages often receive bug reports in error. The correct package is shown after the '->':

  • chromium -> chromium-browser

  • dash -> unity

  • discover -> plasma-discover

  • epiphany -> epiphany-browser (BugSquad discussion).

  • gnome -> gnome-shell or gnome-session

  • kernel-package -> linux

  • snap -> snapd

  • software-center -> gnome software or the 'snap-store-desktop' project if relating to the snap version of 'GNOME Software'

  • ubuntu-settings -> gnome-control-center

also

  • focal - a release name and not a package against which bugs should currently be reported

Bug reports for these packages should be moved to the correct packages so that they reach those that can investigate and / or fix any reported bugs,

Find the source package

Many "binary packages" (that is, packages containing the software you run) may be built from the same "source package" (developers' source code), so bug reports are assigned to source packages and not binary packages. In rare cases, you must manually identify the source package from a binary package.

Go to https://launchpad.net/ubuntu/+search where you can search for the source package from which the binary package is compiled. The source package is the package you should select when filing a bug.

  • Example: gnome-control-center belongs to the gnome-system-tools source package

Alternatively, you can use apt-cache show kdm and look for the Source: line to find the source package.

Assigning already filed bugs

A short introductory video, narrated by Dereck Wonnacott.

  • Warning: This video advises triagers to assign bugs to the acpi-support package. This is wrong! Recent versions of Ubuntu use pm-utils for suspend-resume, acpi-support is not involved in this process. Do not assign bugs to this package, they will only have to be triaged again by a much smaller group of developers. Help is needed to get the above video updated.

You can help right away with the bugs with no home. Most simply need to be associated with the appropriate package.

CategoryBugSquad

Bugs/FindRightPackage (last edited 2022-11-17 15:07:29 by paulw2u)