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 329131 - Evolution/Help/Submit Bug Report fails
Evolution/Help/Submit Bug Report fails
Status: RESOLVED DUPLICATE of bug 335410
Product: evolution
Classification: Applications
Component: general
2.4.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
: 329130 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-29 21:59 UTC by pfudd
Modified: 2006-04-09 11:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pfudd 2006-01-29 21:59:36 UTC 
Please describe the problem:
In Evolution 2.2.3, as found in Fedora Core 4 (evolution-2.2.3-2.fc4), the
help/submit bug report option calls Bugbuddy (bug-buddy-2.10.0-1), but Bugbuddy
says that it doesn't know about Evolution's bug information.

Steps to reproduce:
1. Start Evolution
2. Go to Help/Submit bug report
3. In BugBuddy, pick 'The application does not function correctly', hit forward
4. Pick Evolution from the list, hit forward

Actual results:
You get a popup window that says: "This application has bug information, but Bug
Buddy doesn't know about it.  Please choose another application."

Expected results:
I'd expect to be able to enter a bug for Evolution.  Entering a bug for another
application sounds like a goofy idea: "Hey, let's submit this Evolution bug as a
bug for the Gimp!"

Does this happen every time?
Yes.

Other information:
Fedora Core 4 "Install Everything", fully updated with yum last month.  And I
use KDE, not Gnome.
Comment 1 pfudd 2006-01-29 22:01:16 UTC 
*** Bug 329130 has been marked as a duplicate of this bug. ***
Comment 2 Thierry Moisan 2006-01-30 21:43:00 UTC 
even happens in evolution 2.4.1
Comment 3 André Klapper 2006-04-09 11:27:39 UTC 
sounds like a dup of bug 335410, at least i guess that it is the same reason.

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