After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 329141 - Bug Buddy refuses to handle Evolution bugs
Bug Buddy refuses to handle Evolution bugs
Status: RESOLVED DUPLICATE of bug 335410
Product: bug-buddy
Classification: Deprecated
Component: general
2.10.x
Other other
: Normal normal
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-29 22:59 UTC by ch
Modified: 2006-06-13 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description ch 2006-01-29 22:59:03 UTC 
Distribution: Fedora Core release 4 (Stentz)
Package: bug-buddy
Severity: normal
Version: GNOME2.10.0 2.10.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Bug Buddy refuses to handle Evolution bugs
Bugzilla-Product: bug-buddy
Bugzilla-Component: general
Bugzilla-Version: 2.10.x
Description:
Description of Problem:
In Evolution, clicking 'Help/Submit Bug Report' takes you to Bugbuddy,
but Bugbuddy doesn't let you submit bugs about Evolution.

Steps to reproduce the problem:
1. Start evolution
2. Click on Help/Submit bug report
3. Click on 'The application does not function correctly', 'Forward'
4. Click on 'Evolution', 'Forward'

Actual Results:
A popup window pops up and says "This Application has bug information,
but Bug Buddy doesn't know about it.  Please choose another application.
(OK)"

Expected Results:
I expected to be able to enter a bug report about evolution.


How often does this happen?
Every time.

Additional Information:
Fedora Core 4 "Install Everything", yum-updated to last month,
bug-buddy-2.10.0-1, evolution-2.2.3-2.fc4 (according to rpm -q bug-buddy
evolution).




------- Bug created by bug-buddy at 2006-01-29 22:59 -------
Comment 1 Olav Vitters 2006-06-13 16:32:08 UTC 
/me bad.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 335410 ***