GNOME Bugzilla – Bug 153615
ssh to one opteron linux, start vim prog , terminal crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-terminal Severity: critical Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: ssh to one opteron linux, start vim prog , terminal crash Bugzilla-Product: gnome-terminal Bugzilla-Component: docs Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 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 -151144672 (LWP 2580)] (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)...0x001b87a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50434
Thread 1 (Thread -151144672 (LWP 2580))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-24 03:10 ------- 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 zhbcnn@163.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.
Marking as a dup of bug 139542 via bug 146217. *** This bug has been marked as a duplicate of 139542 ***