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 329552 - Bug Buddy offers to report product it can't name
Bug Buddy offers to report product it can't name
Status: RESOLVED DUPLICATE of bug 164747
Product: bug-buddy
Classification: Deprecated
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-02 02:10 UTC by bucky
Modified: 2006-06-13 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description bucky 2006-02-02 02:10:25 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 offers to report product it can't name
Bugzilla-Product: bug-buddy
Bugzilla-Component: general
Bugzilla-Version: 2.10.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Get: "The Application 'mail-notification' has quit unexpectedly.
Open up Bug Buddy
Bug buddy has no idea what "mail-notification" is.

Steps to reproduce the crash:
1. Get Crash which offers to report via Bug Buddy
2. Try to find the product in the Bug Buddy list.
3. Fail to find product in list.

Expected Results:
I should see "Mail Notification" in the list of Bug Buddy products. 

How often does this happen?
Honestly, I seldom get offers to use Bug Buddy at all, so things really
work well in general. I can't remember the last time I saw a Bug Buddy
window where I was able to match the application named in the error
message with an application in the Bug Buddy list, though.

Additional Information:
The crash belongs to Mail Notification, but clicking on the "inform
developers" button was ultimately futile. I guess what I'm reporting is
really a feature request: if an application launches Bug Buddy but is
not registered, then Bug Buddy could perhaps print out a nice message to
the effect that the crashing application cannot be reported with Bug
Buddy, and that it was rude for the crashing application to suggest
otherwise.


Debugging Information:

Backtrace was generated from '/usr/bin/mail-notification'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208935712 (LWP 3773)]
[New Thread -1221526608 (LWP 3779)]
[New Thread -1211036752 (LWP 3778)]
(no debugging symbols found)
0x001f1402 in __kernel_vsyscall ()

Thread 1 (Thread -1208935712 (LWP 3773))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 main




------- Bug created by bug-buddy at 2006-02-02 02:10 -------

Comment 1 Olav Vitters 2006-02-02 13:44:40 UTC
Bug-Buddy can be made a lot better. See http://gnomerocksmyworld.blogspot.com/2006/01/things-about-gnome-that-su_113867628589513517.html for a list of faults.. scroll down to comment by bkor for my thoughts about it. More suggestions are welcome (#bugs on irc.gnome.org.. use Xchat)

Regarding the crash.. once talked to the mail-notification developer.. There are two known crashers, but caused by other parts of GNOME. This stacktrace doesn't have enough info, but likely the same cause as the other ones.
Comment 2 Olav Vitters 2006-06-13 16:52:06 UTC
Found another bug about it. Btw, lots of issues have been fixed with the release of 2.15.0.

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