GNOME Bugzilla – Bug 166095
file-roller crashes when extracting files with umlaut characters
Last modified: 2005-02-02 22:20:17 UTC
Distribution: Debian 3.1 Package: file-roller Severity: normal Version: GNOME2.9.90 unspecified Gnome-Distributor: Ubuntu Synopsis: file-roller crashes when extracting files with umlaut characters Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: File-Roller crashes while extracting Steps to reproduce the crash: 1. Open a .zip file that has file with umlaut characters 2. Try to extract the file 3. File-Roller crashes Expected Results: Should show the correct file name instead of blank space How often does this happen? always Additional Information: LANG=de_DE.UFT-8 file-roller 2.9.4 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 -1222850304 (LWP 29140)] [New Thread -1250530384 (LWP 29144)] [New Thread -1249977424 (LWP 29143)] [New Thread -1240835152 (LWP 29142)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 55227
Thread 4 (Thread -1240835152 (LWP 29142))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-02 16:25 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "file-roller". Setting to default milestone for this product, '---' 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 164894 ***