Ubuntu

Why Must We Identify A Package When Reporting A Bug?

Asked by Anthony

For some bugs it is very difficult to track down the appropriate package(s) leaving you with little else but a description of the bug's symptoms. In these cases being able to identify the package is half the solution, and trying to I.D the package is in fact part of the very help we're seeking.

For example, I reported a bug where my Num Lock light turns off the first time I press Ctrl or Shift after a system Reboot. How am I supposed to even begin trying to find the package containing the problem? Meanwhile, when I reported this bug there was so much importance placed on naming the package that out of desperation I listed "numlockx" which wasn't even installed, leading to readers' confusion.

Why can't we report bugs using symptom categories instead? In this case a category called "Num Lock" or "Keyboard" would help, and then from there we can try to branch off into package I.D. troubleshooting.

Question information

Language:
English Edit question
Status:
Needs information
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Just log a bug, it will be moved by the maintainers if necessary.

Revision history for this message
Anthony (danthonyd) said : 		#2

Sorry actionparsnip, 15 days later and no movement.
Please see bug #1600478 as I listed above. Maybe you can help me by telling me what I need to do with it now :)

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

see also https://wiki.ubuntu.com/Bugs/FindRightPackage

Revision history for this message
Manfred Hampl (m-hampl) said : 		#4

If you are completely unable to identify the package, you can report it against "Ubuntu", but please don't be astonished when you get a replay like https://wiki.ubuntu.com/Bugs/Responses#Bugs_without_a_package

Revision history for this message
Anthony (danthonyd) said : 		#5

Here's another example:

I filed a bug for the window manager, called Nautilus, right? Wrong!

It's called "Files", actually "'GNOME Files". Nope, wrong again, according to apt-cache pkgnames it's Nautilus. How much time did I waste trying to find the name, the REAL name in order for ubuntu-bug to work?
It would be so much easier to comply with this obsessive "supply the package name" fetish if there was a system in place to help us actually find the name, AND if the name of the package was actually the name of the package, not some other name. I mean, why? Why call it "Files" if that's not what it's called???

Eye of Gnome is another rant-worthy one.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#6

I do not understand what your problem is with Eye of Gnome.

Package names must not contain space characters, so "Eye of Gnome" is not suitable as package name.
On the other hand presenting the user with a name like "eog" is not a good idea either.
So there are desktop files for translating one name into the other.

If you have "Eye of Gnome" open and you use the "xprop WM_CLASS" command as shown in the document linked above, you will immediately find the name eog (which is the name of both the executable and the package itself).

For a program that you start yourself from the dash or any other starter, there should not be a problem in identifying the package.
I agree with you that for bugs with system functionality (like the numlock indicator) it will be harder to identify the correct package. In such cases please follow the "find right package" instructions linked above, or (if you are absolutely unable to identify a package) file the bug against "Ubuntu" as such, or the kernel. The bug team will then try helping to re-route the bug to the correct package.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#7

And for the reason that a package has to be identified:

For each package there is a person or group responsible for bug maintenance. To be able to trigger the right person or group, the related package has to be identified.

Revision history for this message
Anthony (danthonyd) said : 		#8

Manfred, open Eye Of Gnome and try finding the words "Eye Of Gnome" or "eog".
What you are presented with are terms like "Image Viewer", "The GNOME Image Viewer", "About Image Viewer" and other very, very helpful identification labels. If you're persistent you might accidentally stumble across the correct name in Help->Contents.

A consistent naming scheme, and a reasonably simple and accessible process for finding those names is needed. It would help people reporting a bug have assurance that the convoluted acronym they are typing is indeed reporting the correct application, and it would just look more professional and organized.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#9

Have you tried "xprop WM_CLASS" for the windows of Eye of Gnome?
What do you get?

Can you help with this problem?

Provide an answer of your own, or ask Anthony for more information if necessary.

To post a message you must log in.