GNOME Bugzilla – Bug 128420
Crashed Gnome Terminal
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gnome-terminal Severity: critical Version: GNOME2.4.0 2.4.x Gnome-Distributor: GNOME.Org Synopsis: Crashed Gnome Terminal Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When close some gnome-terminlas this crashed Steps to reproduce the crash: 1. Close a Gnome-Teminal 2. Close the second Gnome-Terminal 3. Crashed All gnome-terminal Expected Results: How often does this happen? Additional Information: Well, I use gnome terminal gnome-terminal-2.4.0.1-1 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 -1085250912 (LWP 3245)] (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)...0x00ad3c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 42268
Thread 1 (Thread -1085250912 (LWP 3245))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-03 01:26 ------- The original reporter (unimauro@yahoo.com.mx) 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, gnome-terminal-maint@bugzilla.gnome.org.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. (via bug 122245) *** This bug has been marked as a duplicate of 121675 ***
*** Bug 126299 has been marked as a duplicate of this bug. ***