GNOME Bugzilla – Bug 141355
gnome terminal 2.6 crashed
Last modified: 2005-04-17 19:08:44 UTC
Distribution: Debian testing/unstable Package: gnome-terminal Severity: normal Version: GNOME2.6.1 2.6.1 Gnome-Distributor: Debian Synopsis: gnome terminal 2.6 crashed Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1) Description: Description of the crash: Steps to reproduce the crash: 1. vi something 2. crash 3. Expected Results: How often does this happen? 80% 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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1089220608 (LWP 1220)] (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)...0x40be83ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 46495
Thread 1 (Thread 1089220608 (LWP 1220))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-29 03:30 ------- Unknown version 2.6.1 in product gnome-terminal. Setting version to "1.9.x". 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 cantona@8chi.net. 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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. It'd rock if you got the stack trace using 'bt full' in gdb, btw.
Hmm, looking at these, it is most probably a dup of bug 139441. Reporter, can you tell use what encoding are you using? And/or the output of saying locale on a terminal?
Re-assigning to vte. Looks like a dup of bug 139542.
To provide yet another bug that this could be marked as a duplicate of: The stack trace matches the one in bug 140009, which has been marked as a duplicate of 138886.
Closing this since it's matching reports that are all closed by now. *** This bug has been marked as a duplicate of 138886 ***
Reopening since I don't think you meant to mark this as duplicate of bug #138886.
Was fooled by the typo in #4. bug 138866 is the right one. *** This bug has been marked as a duplicate of 138866 ***