Description of problem:
Whenever evolution crashes bug buddy identifies the components individually
rather than linking them to evolution.
Version-Release number of selected component (if applicable):
$ rpm -q bug-buddy
bug-buddy-2.16.0-3.fc6
How reproducible:
Crash evolution calendar, and allow bug buddy to catch it
Actual results:
bug buddy seems to have caught the crash and is building a bug report to post to
gnome. However when you go to send the bug report it claims the application is
not tracked in the Gnome bugzilla.
Expected results:
bug buddy should post the bug entry to the Evolution project.
Additional info:

I ran into this problem too. I was annoyed that I spent some time writing a
good bug report, only for Bug Buddy to refuse to send it.
Here's the exact text of the error: "Unable to create the bug report:
Application does not track its bugs in the GNOME Bugzilla."

(In reply to comment #3)
> I've got this bug too. I spent some time making my report about evolution crash
> more informative and then was saddened when bug-buddy refused to send the report.
It is pretty frustrating when it just exits like that. I wish it would at least
let you save the stack trace before it quit.

This may still be a problem in the Fedora 7 release. When I go to "Help" ->
"Submit Bug Report" in the Evolution mail window, bug-buddy starts using the
name "Tasks". I would have expected "Mailer" though "Evolution" is probably
what is needed for the bug report to actually go through.

Hi,
We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)