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 413893 - crash in Terminal: Starting gnome terminal ...
crash in Terminal: Starting gnome terminal ...
Status: RESOLVED DUPLICATE of bug 412717
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-02 15:34 UTC by chris
Modified: 2007-03-02 15:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description chris 2007-03-02 15:34:24 UTC 
Version: 2.17.92

What were you doing when the application crashed?
Starting gnome terminal with the --geometry=100x30 parameter.  Without it it is OK.


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: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 42094592 vsize: 42094592 resident: 14204928 share: 10387456 rss: 14204928 rss_rlim: 4294967295
CPU usage: start_time: 1172849567 rtime: 67 utime: 22 stime: 45 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 -1208760608 (LWP 2829)]
[New Thread -1215521904 (LWP 2834)]
(no debugging symbols found)
0x002c5402 in __kernel_vsyscall ()

+ Trace 115225

Thread 1 (Thread -1208760608 (LWP 2829))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libvte.so.9
  • #5 ??
    from /usr/lib/libvte.so.9
  • #6 ??
    from /usr/lib/libvte.so.9
  • #7 ??
    from /usr/lib/libvte.so.9
  • #8 ??
    from /usr/lib/libvte.so.9
  • #9 g_cclosure_marshal_VOID__OBJECT
    from /lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #11 g_cclosure_marshal_VOID__OBJECT
    from /lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(gnome-terminal:2829): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:2829): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:2829): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:2829): 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-02 15:43:04 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. You may want to check for a software upgrade.


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