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 110379 - Spontaneous Combustion of gnome-terminal
Spontaneous Combustion of gnome-terminal
Status: RESOLVED DUPLICATE of bug 107007
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-09 13:13 UTC by x
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description x 2003-04-09 13:44:02 UTC
Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: Spontaneous Combustion of gnome-terminal
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
gnome-terminal crashes after time

Steps to reproduce the problem:
1. Launch gnome-terminal
2. Open a few tabs
3. Wait.. (a long time)

Actual Results:
gnome-terminal crashes with a segmentation fault

Expected Results:
gnome-terminal stays up

How often does this happen?
Very rare

Additional Information:
I was not even using the terminal at the time this happened. Indeed, the
terminal was almost completely obscured by other windows.



Debugging Information:

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

(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)...[New
Thread 1087391456 (LWP 2401)]

(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)...0xffffe002 in ?? ()

Thread 1 (Thread 1087391456 (LWP 2401))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_false
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-09 09:44 -------

The original reporter (x@xman.org) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 John Fleck 2003-04-09 14:34:30 UTC
Another random app crashing in gtk_widget_get_toplevel(). See also bug
107007 and bug 108854.
Comment 2 Elijah Newren 2003-05-06 20:48:49 UTC
...and also bug 111980.

I have a suspicion that this is related to bug 105745, but in any
event, we need a better stack trace.

[If you're using RedHat 9, you can do so with the following easy
method; otherwise this will require recompiling from source:

  Install
  http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm
  and if the problem occurs again, submit the backtrace you get.
  Installing the debuginfo package will make the backtrace much more
  useful.]

I am adding myself to the cc and marking as needinfo for now.
Comment 3 Elijah Newren 2003-07-07 02:09:29 UTC
marking as a dup of 107007.  Please feel free to provide a stack trace
with debugging symbols if you can get one...

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