GNOME Bugzilla – Bug 153543
gnome-terminal crash after changing directory to a UTF-8 encoded directory
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: gnome-terminal Severity: normal Version: GNOME2.6.1 2.6.1 Gnome-Distributor: Debian Synopsis: gnome-terminal crash after changing directory to a UTF-8 encoded directory Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: When I change directory to a UTF-8 (Hebrew language) directory, which is on a fat filesystem, gnome-terminal crashes. 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/i686/cmov/libthread_db.so.1". (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1073894944 (LWP 12717)] [New Thread 1089870768 (LWP 12720)] [Thread debugging using libthread_db enabled] [New Thread 1073894944 (LWP 12717)] [New Thread 1089870768 (LWP 12720)] [Thread debugging using libthread_db enabled] [New Thread 1073894944 (LWP 12717)] [New Thread 1089870768 (LWP 12720)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 50416
Thread 1 (Thread 1073894944 (LWP 12717))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-23 09:41 ------- 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 he3@bezeqint.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. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 107262 ***