Bug 108598 – gnome-terminal crashed by segmentation fault

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 108598 - gnome-terminal crashed by segmentation fault


Summary:	gnome-terminal crashed by segmentation fault


Status:	RESOLVED DUPLICATE of bug 75076

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Havoc Pennington
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-03-17 14:26 UTC by mshindo
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description mshindo 2003-03-17 14:26:10 UTC

Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: gnome-terminal crashed by segmentation fault
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:


Steps to reproduce the problem:
1. this is not reproducible
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
intermittent

Additional Information:




Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 1177)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34981

Thread 1 (Thread 8192 (LWP 1177))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 strcmp
from /lib/i686/libc.so.6
#7 get_im
from /usr/lib/gtk-2.0/2.0.0/immodules/im-xim.so
#8 gtk_im_context_xim_new
from /usr/lib/gtk-2.0/2.0.0/immodules/im-xim.so
#9 im_module_create
from /usr/lib/gtk-2.0/2.0.0/immodules/im-xim.so
#10 _gtk_im_module_create
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_im_multicontext_get_slave
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_im_multicontext_set_client_window
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_im_context_set_client_window
from /usr/lib/libgtk-x11-2.0.so.0
#14 vte_terminal_realize
from /usr/lib/libvte.so.2
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#22 terminal_window_set_active
#23 notebook_page_switched_callback
#24 _gtk_marshal_VOID__POINTER_UINT
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_notebook_switch_page
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_notebook_insert_page_menu
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_notebook_append_page
from /usr/lib/libgtk-x11-2.0.so.0
#32 terminal_window_add_screen
#33 terminal_app_new_terminal
#34 new_window_callback
#35 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#37 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#39 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_menu_shell_button_release
from /usr/lib/libgtk-x11-2.0.so.0
#43 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#44 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#45 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#46 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#48 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#49 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#51 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#52 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#53 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#54 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#55 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#56 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#57 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#58 main
#59 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-17 09:26 -------

The original reporter (mshindo@mshindo.net) 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-03-17 14:40:05 UTC

This looks like bug #75076, but that's in Nautilus, which is obviously
wrong.

Comment 2 Elijah Newren 2003-03-17 18:08:07 UTC

Owen just changed the product of bug 75076 to be gtk+ instead of
nautilus, so I'm going to mark this as a duplicate of bug 75076.
(Also, note that bug 108604, a bug filed against a more recent version
of nautilus, matches the stack trace of this bug nearly perfectly).

mshindo@mshindo.net: Bug 75076 has been very hard for the developers
to track down because no one can provide them with exact steps on how
to reproduce.  Could you, if possible, tell us:
   1) What version of GTK+ you are using?
   2) Steps to reproduce this crash (if you can figure any
      out--reading bug 75076 may give you some ideas)

I'm marking this as resolved and as a duplicate of 75076, so if you
could add your comments to that bug it'd be appreciated.  I'll add
myself to the cc list, though, in case you for some reason don't want
to add comments to that report.

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