For nautilus-cd-burner this means that:
1. X-GNOME-Bugzilla-Component=general is wrong.. it should be cd-burner
2. It should have version info

Although perhaps the Bug-Buddy info should just go as Bug-Buddy will not tell the difference between nautilus and nautilus-cd-burner (the UI stuff is gone).

====

Starting with Bug-Buddy 2.15.0 all programs wanting to make use of Bug-Buddy must have a .desktop file. Also the .desktop file must contain a few Bug-Buddy headers.

These are:
X-GNOME-Bugzilla-Bugzilla=GNOME <-- Mandatory
X-GNOME-Bugzilla-Product=XXX <--Mandatory
X-GNOME-Bugzilla-Component=YYY <-- Mandatory
X-GNOME-Bugzilla-OtherBinaries=ZZZ <-- Optional, only if you
application has several binaries
X-GNOME-Bugzilla-Version=X.Y.Z <-- Optional, but highly recommended. This should need expansion from configure script, so if you want this you need a
application.desktop.in.in to expand here @VERSION@
(application.desktop.in is used by intltool for translations).

This headers have actually been in use since 2002, except that Bug-Buddy 2.15.0 will now require:
a) A .desktop file containing at least the mandatory information
b) Given product and component MUST exist on bugzilla.gnome.org

Having the X-GNOME-Bugzilla-Version is optional, but highly recommended. The server will automatically change versions like 2.15.90 to 2.15.x, so this doesn't have to be changed in the .desktop file. I recommend keeping the real version in the desktop file as I might put this in a comment.

Users will only be able to fill in their email address and a 'What were you doing when the application crashed?'. Version information will not be possible to select anymore. This is why having the X-GNOME-Bugzilla-Version is highly recommended.

If you want Bug-Buddy support, but do not want your application to show up in the menus, use the following .desktop header:
NoDisplay=true