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 104599 - bug buddy crashed
bug buddy crashed
Status: RESOLVED FIXED
Product: bug-buddy
Classification: Deprecated
Component: general
2.1.x(GNOME2.x)
Other other
: Normal critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
: 92436 136247 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-01-28 09:21 UTC by David Goodwin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description David Goodwin 2003-01-28 09:18:06 UTC 
Package: bug-buddy
Severity: critical
Version: GNOME2.1.90 2.2.100
Synopsis: bug buddy crashed
Bugzilla-Product: bug-buddy
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.1.90)
Description:
Description of Problem:
Attempted to submit a bug report for gnome-terminal. After selecting the
right stuff on the mail configuration screen it crashed. (Perhaps this
is a result of it saying there was no email address to send
gnome-terminal stuff to earlier?)

Steps to reproduce the problem:
1. Submit bug report for gnome-terminal 
2. 
3. 

Actual Results:

Application "Bug-Buddy" (process 24296) has crashed due to a fatal error
- Seg fault.
Expected Results:

Submit a bug :)
How often does this happen?
Never before.

Additional Information:
Using dropline gnome on Slackware 8.1 system.
Gnome was updated last night (currently using a 2.2 pre build afaik)


Debugging Information:

Backtrace was generated from '/usr/bin/bug-buddy'

[New Thread 1024 (LWP 24296)]
[New Thread 2049 (LWP 24297)]
[New Thread 1026 (LWP 24298)]
0x40823239 in __wait4 () at __wait4:-1
	in __wait4

+ Trace 33230

Thread 1 (Thread 1024 (LWP 24296))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 173
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 generate_email_text
  • #7 druid_set_state
  • #8 on_druid_next_clicked
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_real_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_button_button_release
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #30 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_widget_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #39 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 main
  • #41 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-28 04:18 -------

Reassigning to the default owner of the component, bug-buddy-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-01-28 18:00:27 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.1.x (from version details of
GNOME2.1.90; I hope I can ignore the 2.2.100--?), adding GNOMEVER2.1
and bugsquad keywords, and marking as new.
Comment 2 Fernando Herrera 2003-02-01 18:47:17 UTC 
Thanks for the report. It's fixed in CVS, and I will release 2.2.102 ASAP.
Comment 3 Fernando Herrera 2003-09-26 10:09:03 UTC 
*** Bug 92436 has been marked as a duplicate of this bug. ***
Comment 4 Don Scorgie 2004-03-05 22:44:07 UTC 
*** Bug 136247 has been marked as a duplicate of this bug. ***