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 494112 - Fault code returned by Bugzilla is not recognised.
Fault code returned by Bugzilla is not recognised.
Status: RESOLVED WONTFIX
Product: bug-buddy
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
gnome[unmaintained]
: 494108 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-11-06 11:51 UTC by Dr Alan J Bartlett
Modified: 2018-07-16 08:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dr Alan J Bartlett 2007-11-06 11:51:17 UTC
Steps to reproduce:
1. Impossible to say.
2. 
3. 


Stack trace:
Impossible to do so. See below.

Other information:
Was viewing /var/log/cups/access_log via the System Log Viewer when this application crashed. Bug Buddy executed. Having reviewed the data to be sent and inserted what I was doing & my email address, clicked on Send. Bug Buddy returned this message:

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

The fault code returned by Bugzilla is not recognised. Please report the following information to bugzilla.gnome.org manually:

          999:not_accepting_crashers
<end quote>

So this is my manual report!
Comment 1 Dr Alan J Bartlett 2007-11-06 11:55:15 UTC
Possibly this should be regarded as two separate events (1) crash of System Log Viewer (2) failure of Bug Buddy
Comment 2 Paul Parker 2007-12-28 05:24:43 UTC
Bug Buddy has encountered an error while submitting your report to the Bugzilla server.  Details of the error are included below.

The fault code returned by Bugzilla is not recognized. Please report the following information to bugzilla.gnome.org manually:

999:not_accepting_crashers


Comment: 
1.  Am very new to Linux !

2.  Happened several times, so copy and paste below information into an error information file.

3.  zmd  is what System Monitor calls application trying to check for updates (has big world icon on desktop).

4. Bug Report Information
4.a My bug report Fri 28 December 2007  at 15:55  
4.b Earlier bug report (perhaps earlier today) 





4.a My bug report Fri 28 December 2007  at 15:55  
--start my cut and paste---
DETAILS : 

Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 43618304 vsize: 0 resident: 43618304 share: 0 rss: 2965504 rss_rlim: 0
CPU usage: start_time: 1198817411 rtime: 0 utime: 135 stime: 0 cutime:97 cstime: 0 timeout: 38 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/bin/gnome-system-monitor'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226553664 (LWP 9212)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f3e410 in ?? ()

--end my cut and paste---


hope it helps..
Comment 3 Kevin Cozens 2008-02-04 19:08:33 UTC
*** Bug 494108 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2018-07-16 08:26:01 UTC
bug-buddy is not under active development anymore and had its last code changes
many years ago. Its codebase has been archived:
https://gitlab.gnome.org/Archive/bug-buddy/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality (see bug 796784). Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.