GNOME Bugzilla – Bug 106586
gnome-terminal crashes on startup
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-terminal Severity: normal Version: 2.2.1 Synopsis: gnome-terminal crashes on startup Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: gnome-terminal crashes on startup Steps to reproduce the problem: 1. Start it How often does this happen? Every time. Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (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)...(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)... (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)...(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)... (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)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 6400)] (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)...(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)... (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)...(no debugging symbols found)... 0x40b38b89 in wait4 () from /lib/libc.so.6
+ Trace 34043
Thread 1 (Thread 16384 (LWP 6400))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-19 22:33 ------- The original reporter (sandra@python.ca) 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.
Appears to be a unique stack trace, according to the simple-dup-finder. Setting version->2.2.x, marking priority->high & severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad keywords, and marking as new.
If it happens every time I would strongly suspect a miscompilation or other local system issue. Where did you get your g-t packages and what OS do you run?
The package came from Debian unstable gnome-terminal_2.2.1-1_i386.deb.
Need symbols, and be sure you aren't using unstable vte 0.11.x *** This bug has been marked as a duplicate of 110263 ***