GNOME Bugzilla – Bug 169393
File-roller crach unicode in filename
Last modified: 2005-03-06 16:08:19 UTC
Distribution: Debian 3.1 Package: file-roller Severity: normal Version: GNOME2.9.91 2.9.91 Gnome-Distributor: Ubuntu Synopsis: File-roller crach unicode in filename Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 2.9.91 BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: If there is a unicode character in the filename of one of the tobe extracted files. The app crashed Tested multiple times Steps to reproduce the crash: 1. Extract a file with a unicode in its name. 2. 3. Expected Results: How often does this happen? Every time a unicode is in a filename Additional Information: Zipfile was created using winzip 8 under win2ksp4 Debugging Information: Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1222776576 (LWP 13980)] [New Thread -1233974352 (LWP 13984)] [New Thread -1224877136 (LWP 13983)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 56503
Thread 3 (Thread -1224877136 (LWP 13983))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-06 11:00 ------- Unknown version 2.9.91 in product file-roller. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "file-roller". 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 rene@pangia.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. Matches the stack trace in bug 167862, which has been marked as a duplicate of 164894. *** This bug has been marked as a duplicate of 164894 ***