GNOME Bugzilla – Bug 152072
gnome-terminal crashes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-terminal Severity: major Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: gnome-terminal crashes Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: With 28 terminals running, gnome-terminal crashes. I can't see any reason, but this is the second time in a week. Last time, I lost 60 terminals. Both times, it crashed when I came back to my computer in the morning, after running things all night. 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 -150893888 (LWP 32753)] (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)...0x00cff402 in ?? ()
+ Trace 49953
Thread 1 (Thread -150893888 (LWP 32753))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-07 10:54 ------- 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 bill-bugbuddy@uncultured.org. 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 is a duplicate of 151680 (I filed both via bug-buddy).
*** This bug has been marked as a duplicate of 151680 ***