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 135283 - Unknown crash
Unknown crash
Status: RESOLVED INCOMPLETE
Product: gnome-terminal
Classification: Core
Component: general
2.5.x
Other other
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-24 12:45 UTC by Trent "Lathiat" Lloyd
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Trent "Lathiat" Lloyd 2004-02-24 12:46:46 UTC
Distribution: Debian testing
Package: gnome-terminal
Severity: normal
Version: GNOME2.5.5 2.5.4
Gnome-Distributor: GNOME.Org
Synopsis: Unknown crash
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.5.4
BugBuddy-GnomeVersion: 2.0 (2.5.4)
Description:
This was a random crash, debugging isnt enabled but I provide the
bugbuddy collected debug info just in case its usefull. (tho i doubt it
somehow)

I just alt-tabbed off gnome-terminal everything slowed down for a second
then it crashed.


Debugging Information:

Backtrace was generated from '/usr/local/bin/gnome-terminal'

[New Thread 16384 (LWP 31917)]
0x40b52bd8 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 31917))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/local/lib/libgnomeui-2.so.0
  • #2 libgnomeui_segv_setup
    at gnome-ui-init.c line 689
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 g_type_check_class_is_a
    at gtype.c line 2763
  • #6 gail_widget_connect_widget_destroyed
    at gailwidget.c line 237
  • #7 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 63
  • #8 g_closure_invoke
    at gclosure.c line 423
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2505
  • #10 g_signal_emit_valist
    at gsignal.c line 2216
  • #11 g_signal_emit_valist
    at gsignal.c line 2136
  • #12 gtk_notebook_reorder_child
    at gtknotebook.c line 5435
  • #13 gtk_widget_create_pango_context
    at gtkwidget.c line 4960
  • #14 g_object_run_dispose
    at gobject.c line 599
  • #15 gtk_notebook_reorder_child
    at gtknotebook.c line 5419
  • #16 gtk_widget_class_init
    at gtkwidget.c line 700
  • #17 gtk_box_set_child_packing
    at gtkbox.c line 616
  • #18 _gtk_container_queue_resize
    at gtkcontainer.c line 1124
  • #19 gtk_container_child_set
    at gtkcontainer.c line 672
  • #20 ??
  • #21 ??
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-24 07:46 -------

Unknown version 2.5.4 in product gnome-terminal. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.

Comment 1 Theodore Randall 2004-02-24 20:10:12 UTC
Appears to be a unique stack trace accoreding to simple-dup-finder.
Adding keywords GNOMEVER2.5, STACKTRACE, bugsquad. Priority->High,
Severity->Critical.

I couldn't confirm with alt-tab.
Comment 2 Mariano Suárez-Alvarez 2004-06-28 14:21:23 UTC
Adding the accessibility keyword, as this happened in gail.
Comment 3 padraig.obriain 2004-07-07 07:50:25 UTC
It does look like accessibility is enabled. However there seems to be
inconsistencies in the stack trace.

There is not enough information here to determine tyhe cause of the problem.