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 116065 - mysterious gnome-terminal crash
mysterious gnome-terminal crash
Status: RESOLVED DUPLICATE of bug 105745
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other other
: Normal critical
: ---
Assigned To: gtk-bugs
GNOME Terminal Maintainers
: 124118 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-06-26 23:19 UTC by lindahl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description lindahl 2003-06-26 23:20:05 UTC 
Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: mysterious gnome-terminal crash
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

I wasn't doing anything much, and gnome-terminal crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




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

0x40a11567 in waitpid () from /lib/i686/libpthread.so.0

+ Trace 38212

Thread 1 (Thread 16384 (LWP 1101))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 gdk_event_apply_filters
    at gdkevents-x11.c line 299
  • #6 gdk_event_translate
    at gdkevents-x11.c line 814
  • #7 _gdk_events_queue
    at gdkevents-x11.c line 1952
  • #8 gdk_event_dispatch
    at gdkevents-x11.c line 2012
  • #9 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    at gtkmain.c line 1092
  • #14 main
  • #15 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 waitpid
    from /lib/i686/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-26 19:20 -------

The original reporter (lindahl@keyresearch.com) 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 Elijah Newren 2003-07-03 19:41:48 UTC 
This looks like it may be a duplicate of bug 114929.  I'm not sure
because of the gdk_event_apply_filters.  It may be a duplicate of
105745, but the first couple functions doesn't quite match there either.

I think this is a gtk+ problem, so I'm reassigning.
Comment 2 Kjartan Maraas 2003-07-08 07:29:28 UTC 
Should this be marked as duplicate of #114929?
Comment 3 Owen Taylor 2003-08-13 22:15:24 UTC 
Pretty sure this is another dup of bug 105745, one way or the
other.

*** This bug has been marked as a duplicate of 105745 ***
Comment 4 Mariano Suárez-Alvarez 2003-10-11 23:51:41 UTC 
*** Bug 124118 has been marked as a duplicate of this bug. ***