BugZappers/CorrectComponent

From FedoraProject

< BugZappers(Difference between revisions)
Jump to: navigation, search
(Which RPM is it?: You should include the full name and version number of this RPM in your bug report.)
(Which program is it?: how to figure out what program a menu item runs)
 
(3 intermediate revisions by 2 users not shown)
Line 4: Line 4:
  
 
If you started the program from the command line, the name of the program is the first "word" of the command (everything before the first space, which might include dashes or underscores).
 
If you started the program from the command line, the name of the program is the first "word" of the command (everything before the first space, which might include dashes or underscores).
 +
 +
If you want to find out exactly what command a specific menu item will run, in Gnome you can do the following:
 +
* Right-click on the menu item and select "Add this launcher to panel"
 +
* Right-click on the icon that appears on your panel and select "Properties"
 +
* Record the "Command" field, then close the Properties window.
 +
* Right-click on the panel icon again and select "Remove from panel" to put things back the way they were when you started.
  
 
==Which file is it?==
 
==Which file is it?==
Line 9: Line 15:
 
If you know which command was run, but don't know the exact file name this corresponds to, try this on the command line:
 
If you know which command was run, but don't know the exact file name this corresponds to, try this on the command line:
  
<pre>
 
 
  which <command-name>
 
  which <command-name>
</pre>
 
  
 
or if you are running tcsh:
 
or if you are running tcsh:
  
<pre>
 
 
  where <command-name>
 
  where <command-name>
</pre>
 
  
 
The first line in the results is the one you want.
 
The first line in the results is the one you want.
  
 
For example:
 
For example:
<pre>
+
 
 
  $ which ssh
 
  $ which ssh
 
  /usr/bin/ssh
 
  /usr/bin/ssh
</pre>
 
  
 
==Which RPM is it?==
 
==Which RPM is it?==
Line 31: Line 32:
 
Once you have the name of a file or directory, you can determine which RPM owns it using "rpm -qf".  For example:
 
Once you have the name of a file or directory, you can determine which RPM owns it using "rpm -qf".  For example:
  
<pre>
 
 
  $ rpm -qf /usr/bin/nautilus-file-management-properties
 
  $ rpm -qf /usr/bin/nautilus-file-management-properties
 
  nautilus-2.25.91-2.fc11.x86_64
 
  nautilus-2.25.91-2.fc11.x86_64
</pre>
 
  
 
You should include the full name and version number of this RPM in your bug report.
 
You should include the full name and version number of this RPM in your bug report.
Line 41: Line 40:
  
 
In Fedora, a given "source" RPM can produce multiple RPMs in the distribution.  Bugzilla groups bugs according to the "source" RPMs only.  Once you have the RPM name, you can get the "source" RPM name (which might be different) using "rpm -qi".  For example, run "rpm -qi glibc-common" and then look for the line that says "Source RPM:"  In this case, it's glibc-2.9.90-7.src.rpm, which means the component name to use in Bugzilla is "glibc" (everything before the dash before the version number).
 
In Fedora, a given "source" RPM can produce multiple RPMs in the distribution.  Bugzilla groups bugs according to the "source" RPMs only.  Once you have the RPM name, you can get the "source" RPM name (which might be different) using "rpm -qi".  For example, run "rpm -qi glibc-common" and then look for the line that says "Source RPM:"  In this case, it's glibc-2.9.90-7.src.rpm, which means the component name to use in Bugzilla is "glibc" (everything before the dash before the version number).
 +
 +
<pre>
 +
$ rpm -qi glibc-common
 +
...
 +
Group      : System Environment/Base      Source RPM: glibc-2.11-2.src.rpm
 +
...
 +
</pre>
  
 
Note that if the "Vendor:" line does not say "Fedora Project", you may need to report the bug to a different bugzilla.
 
Note that if the "Vendor:" line does not say "Fedora Project", you may need to report the bug to a different bugzilla.
 +
 +
==If you don't have package installed==
 +
 +
For packages which you have NOT installed you can use <code>repoquery</code>:
 +
 +
repoquery -qf /usr/bin/kdm
 +
 +
will find you which ''binary'' package contains this file.
 +
 +
repoquery -q --qf="%{sourcerpm}\n" kdm
 +
 +
will tell you which ''component'' provides this binary package.
  
 
==Embedded components==
 
==Embedded components==
  
 
Sometimes it can be unclear whether a bug is in the main application or a plugin or library.  In these cases, just make your best guess.  A triager or developer will reassign the bug if necessary.
 
Sometimes it can be unclear whether a bug is in the main application or a plugin or library.  In these cases, just make your best guess.  A triager or developer will reassign the bug if necessary.

Latest revision as of 01:44, 9 March 2010

Contents

[edit] Which program is it?

If you started the program from the GNOME menu, you can usually find the name of the program by going to "Help -> About" in the program's internal menus. You can also go to "System -> Preferences -> Personal -> Sessions" on the GNOME menu. Click on the "Current Session" tab to see a list of programs running on your desktop.

If you started the program from the command line, the name of the program is the first "word" of the command (everything before the first space, which might include dashes or underscores).

If you want to find out exactly what command a specific menu item will run, in Gnome you can do the following:

  • Right-click on the menu item and select "Add this launcher to panel"
  • Right-click on the icon that appears on your panel and select "Properties"
  • Record the "Command" field, then close the Properties window.
  • Right-click on the panel icon again and select "Remove from panel" to put things back the way they were when you started.

[edit] Which file is it?

If you know which command was run, but don't know the exact file name this corresponds to, try this on the command line:

which <command-name>

or if you are running tcsh:

where <command-name>

The first line in the results is the one you want.

For example:

$ which ssh
/usr/bin/ssh

[edit] Which RPM is it?

Once you have the name of a file or directory, you can determine which RPM owns it using "rpm -qf". For example:

$ rpm -qf /usr/bin/nautilus-file-management-properties
nautilus-2.25.91-2.fc11.x86_64

You should include the full name and version number of this RPM in your bug report.

[edit] Which component is it?

In Fedora, a given "source" RPM can produce multiple RPMs in the distribution. Bugzilla groups bugs according to the "source" RPMs only. Once you have the RPM name, you can get the "source" RPM name (which might be different) using "rpm -qi". For example, run "rpm -qi glibc-common" and then look for the line that says "Source RPM:" In this case, it's glibc-2.9.90-7.src.rpm, which means the component name to use in Bugzilla is "glibc" (everything before the dash before the version number).

$ rpm -qi glibc-common
...
Group       : System Environment/Base       Source RPM: glibc-2.11-2.src.rpm
...

Note that if the "Vendor:" line does not say "Fedora Project", you may need to report the bug to a different bugzilla.

[edit] If you don't have package installed

For packages which you have NOT installed you can use repoquery:

repoquery -qf /usr/bin/kdm

will find you which binary package contains this file.

repoquery -q --qf="%{sourcerpm}\n" kdm

will tell you which component provides this binary package.

[edit] Embedded components

Sometimes it can be unclear whether a bug is in the main application or a plugin or library. In these cases, just make your best guess. A triager or developer will reassign the bug if necessary.