GNOME Bugzilla – Bug 146893
gnome-terminal crashes on strartup
Last modified: 2005-09-30 19:28:27 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-terminal Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gnome-terminal crashes on strartup Bugzilla-Product: gnome-terminal Bugzilla-Component: docs Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: When starting the terminal I get ths error: The Application "gnome-terminal" has quit unexpectedly. Steps to reproduce the crash: 1. Attempt to start gnome-terminal 2. get error message Expected Results: The terminal should start. How often does this happen? every time I try to start it Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -150750496 (LWP 6093)] (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)...0x00aa9402 in ?? ()
+ Trace 48247
Thread 1 (Thread -150750496 (LWP 6093))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 08:28 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was fire7earth@yahoo.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This stack trace is broken, as vte_terminal_get_emulation does not call vte_terminal_set_emulation... Moving to vte, as this is deep inside it: maybe nalin knows where it broke.
No new information here and no duplicates. Closing as INCOMPLETE.