Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 224070 - bug-buddy doesn't correctly identify evolution components
bug-buddy doesn't correctly identify evolution components
Product: Fedora
Classification: Fedora
Component: bug-buddy (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
David Lawrence
: 237095 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2007-01-23 16:39 EST by Russell Harrison
Modified: 2008-06-28 23:20 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-18 14:41:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Russell Harrison 2007-01-23 16:39:11 EST
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


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:
Comment 1 Matt McCutchen 2007-02-08 18:39:38 EST
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."
Comment 2 Alexander 2007-04-19 09:00:11 EDT
*** Bug 237095 has been marked as a duplicate of this bug. ***
Comment 3 Alexander 2007-04-19 09:07:01 EDT
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. 
Comment 4 Russell Harrison 2007-04-20 19:01:54 EDT
(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.
Comment 5 Alexander Shopov 2007-06-05 07:19:27 EDT
Similar problem with me
Comment 6 Christopher Beland 2007-08-28 13:18:34 EDT
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.
Comment 7 Ray Strode [halfline] 2008-03-18 14:41:32 EDT

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)
Comment 8 Christopher Beland 2008-06-28 23:20:34 EDT
The "Help" -> "Submit Bug Report" action now correctly identifies the app as
"Evolution Mail and Calendar" in bug-buddy-2.22.0-2.fc9.x86_64.

Note You need to log in before you can comment on or make changes to this bug.