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 90120 - Terminal Crashed During Normal Usage
Terminal Crashed During Normal Usage
Status: RESOLVED DUPLICATE of bug 95615
Product: vte
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Havoc Pennington
Luis Villa
Depends on:
Blocks:
 
 
Reported: 2002-08-07 15:10 UTC by skadz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description skadz 2002-08-07 15:10:35 UTC
Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: Terminal Crashed During Normal Usage
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
I was just using my terminal as I would on a day to day basis and it
crashed.  It MIGHT have been around when I hit the tab key, but I don't
think it was specific to it.

Steps to reproduce the problem:
1. Use a terminal for a while
2. 
3. 

Actual Results:
Crash

Expected Results:
Keep on working

How often does this happen?
Has happened MANY MANY times in the last few days snapshots, this is
only the second time I have actually gotten a bud buddy up, normally it
just freezes.  The previous bud buddy I was not able to fill out, so
this is the first bug report.

Additional Information:
0807 Ximian Snapshot



Debugging Information:

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

[New Thread 1024 (LWP 3064)]
0x40918339 in __wait4 () at __wait4:-1
	in __wait4

Thread 1 (Thread 1024 (LWP 3064))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 620
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 XftGlyphCheck
    from /usr/X11R6/lib/libXft.so.1
  • #7 XftRenderExtents32
    from /usr/X11R6/lib/libXft.so.1
  • #8 XftTextExtents32
    from /usr/X11R6/lib/libXft.so.1
  • #9 vte_terminal_get_char_padding
    at vte.c line 10529
  • #10 vte_terminal_draw_row
    at vte.c line 10919
  • #11 vte_terminal_paint
    at vte.c line 11037
  • #12 vte_terminal_expose
    at vte.c line 11199
  • #13 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #14 g_type_class_meta_marshal
    at gclosure.c line 514
  • #15 g_closure_invoke
    at gclosure.c line 437
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2379
  • #17 g_signal_emit_valist
    at gsignal.c line 2110
  • #18 gtk_signal_emit
    at gtksignal.c line 355
  • #19 gtk_widget_event_internal
    at gtkwidget.c line 3082
  • #20 gtk_main_do_event
    at gtkmain.c line 1296
  • #21 gdk_window_process_updates_internal
    at gdkwindow.c line 2103




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-08-07 11:10 -------

Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Luis Villa 2002-08-07 15:15:42 UTC
Reassigning to vte, though it looks like it could possibly be at a
lower level than that...
Comment 2 Nalin Dahyabhai 2002-08-08 18:59:32 UTC
I'd like to rule out the possibility of a libXft bug -- which
OS/version are you running?  Which version of X or XFree86?
Comment 3 skadz 2002-08-08 19:04:37 UTC
RedHat 7.2
RPM which contains libXft is XFree86-libs-4.1.0-25 (from RH Updates)
Comment 4 Nalin Dahyabhai 2002-10-17 21:16:53 UTC

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