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 347281 - Bug Buddy doesn't submit bug report correctly
Bug Buddy doesn't submit bug report correctly
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: general
git master
Other All
: Normal blocker
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 356638 (view as bug list)
Depends on:
Blocks: 348827
 
 
Reported: 2006-07-12 06:41 UTC by Alex Smith
Modified: 2015-03-24 13:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Patch fixing gnome-panel bugzilla info (1.96 KB, patch)
2006-07-12 08:26 UTC, Fernando Herrera
none Details | Review

Description Alex Smith 2006-07-12 06:41:23 UTC
Please describe the problem:
When I tried to submit bug #347279 using bug-buddy after gnome-panel crashed, it failed to do so with the error described below.

Steps to reproduce:
1. Submit a bug report on Gnome Panel with bug-buddy


Actual results:
I received this error:

Bug Buddy has encountered an error while submitting your report to the Bugzilla server.  Details of the error are included below.

The component specified doesn't exist or has been renamed.  Please upgrade to the latest version.

Expected results:
Bug Buddy to submit the bug report normally

Does this happen every time?
Yes

Other information:
Frugalware Linux with Gnome 2.15.x
Comment 1 Fernando Herrera 2006-07-12 08:25:28 UTC
Yes, the gnome-panel information about bugzilla is wrong. Every crash on gnome-panel is catched as a Clock crash, with wrong bugzilla product/component.

Can you please try the attached patch?
Comment 2 Fernando Herrera 2006-07-12 08:26:12 UTC
Created attachment 68795 [details] [review]
Patch fixing gnome-panel bugzilla info
Comment 3 Alex Smith 2006-07-12 09:14:48 UTC
OK, I'll test it as soon as I get home and I'll let you know the result
Comment 4 Alex Smith 2006-07-12 19:11:55 UTC
The bug gets submitted now, but it still thinks that it is a Clock crash. Also please close the bug report that I posted when testing this.
Comment 5 Christian Kirbach 2006-07-12 19:43:54 UTC
Can you please state the report number of your "testing" report.
Comment 6 Alex Smith 2006-07-13 06:13:08 UTC
It's #347335
Comment 7 Vincent Untz 2006-07-28 07:32:23 UTC
I committed the change for the clock applet.

Fernando: I think bug-buddy only looks at the server files for applets, so it won't work for the panel. And the panel doesn't ship a desktop file. Is there any other way to tell bug-buddy what to do?
Comment 8 Sergej Kotliar 2006-09-19 16:58:02 UTC
*** Bug 356638 has been marked as a duplicate of this bug. ***
Comment 9 Luca Ferretti 2006-11-16 11:49:01 UTC
(In reply to comment #7)

> And the panel doesn't ship a desktop file. Is there
> any other way to tell bug-buddy what to do?

The latest Bug Buddy shoudl use only .desktop file to identify the crashing module.

You should add a .desktop file for gnome-panel using the NoDisplay key (see http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html) and maybe for applets too.

Try to add a .desktop file like this in your $prefix/share/applications/ directory:

  [Desktop Entry]
  Encoding=UTF-8
  Name=GNOME Panel
  TryExec=gnome-panel
  Exec=gnome-panel
  NoDisplay=true
  Type=Application
  X-GNOME-Bugzilla-Bugzilla=GNOME
  X-GNOME-Bugzilla-Product=gnome-panel
  X-GNOME-Bugzilla-Component=general
  X-GNOME-Bugzilla-Version=2.17.0

then run `killall -s SIGSEGV gnome-panel`. BugBuddy will open itself suggesting to send the crash report to bugzilla.gnome.org.

Now try to run `killall -s SIGSEGV clock-applet`. Bug Buddy will say that the crash come from unknow application and suggest you to save the crash report.

PS I'm not sure Exec and TryExec keys are not needed in Desktop Entry Spec, but could be needed by BugBuddy to identify the crashing application.

PPS maybe Name key should be translatable.
Comment 10 Kjartan Maraas 2007-01-07 15:48:13 UTC
Any news on this? Getting good bugreports for crashes is a priority I guess.
Comment 11 Alex Smith 2007-01-08 07:18:21 UTC
Fixed, forgot to close this. Sorry
Comment 12 Vincent Untz 2007-01-08 17:43:34 UTC
Alex: does it work now? I don't think I fixed this myself and I can't find a changelog entry about this...