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 413401 - crash in Terminal: i pressed CTRL+T to open...
crash in Terminal: i pressed CTRL+T to open...
Status: RESOLVED DUPLICATE of bug 413036
Product: gnome-terminal
Classification: Core
Component: general
2.17.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-01 11:11 UTC by buchomoralez
Modified: 2007-03-01 11:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description buchomoralez 2007-03-01 11:11:10 UTC
Version: 2.17.92

What were you doing when the application crashed?
i pressed CTRL+T to open new window


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc)
BugBuddy Version: 2.17.4

System: Linux 2.6.20-1.2953.fc7 #1 SMP Mon Feb 26 21:30:41 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 97992704 vsize: 97992704 resident: 15261696 share: 10899456 rss: 15261696 rss_rlim: 4294967295
CPU usage: start_time: 1172747431 rtime: 27 utime: 21 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208875296 (LWP 3408)]
[New Thread -1215226992 (LWP 3412)]
(no debugging symbols found)
0x0041d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208875296 (LWP 3408))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libvte.so.9
  • #5 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libvte.so.9
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 gtk_adjustment_value_changed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libvte.so.9
  • #18 ??
    from /usr/lib/libvte.so.9
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 ??
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac10.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Chris Wilson 2007-03-01 11:26:43 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version.

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