GNOME Bugzilla – Bug 164894
crash on zip with incorrect filenames
Last modified: 2006-04-04 12:53:40 UTC
Distribution: Debian 3.1 Package: file-roller Severity: normal Version: GNOME2.9.4 unspecified Gnome-Distributor: Ubuntu Synopsis: tried to extract files out of a .zip file with "strange" filenames Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: tried to extract files out of a .zip file with "strange" filenames, meaning the filenames were not depicted on the screen Debugging Information: Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 182970863840 (LWP 14888)] 0x0000002a98e9f9a6 in waitpid () from /lib/libpthread.so.0
+ Trace 54799
Thread 1 (Thread 182970863840 (LWP 14888))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-22 07:34 ------- 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.
what do you call 'strange filename' ? Could you get a backtrace with libglib2.0-0-dbg installed ? Is that file big or can you attach it here or provide a link to download it ?
I happen to have libglib2.0-0-dbg already installed, the filenames may start with Unicode or strangely encoded characters, so file-roller doesnt display the names at all
The submitter gave me an access to the file. The file contains non-correct utf8 names. file-roller doesn't display the name and nautilus '(invalid encoding)' after the filenames. (gdb) bt
+ Trace 54802
Created attachment 36374 [details] bugged filename this archive has a bugged filename. Trying to create a zip containing this file crashes in the same way
*** Bug 165406 has been marked as a duplicate of this bug. ***
*** Bug 165926 has been marked as a duplicate of this bug. ***
*** Bug 166095 has been marked as a duplicate of this bug. ***
*** Bug 167851 has been marked as a duplicate of this bug. ***
*** Bug 167862 has been marked as a duplicate of this bug. ***
*** Bug 169393 has been marked as a duplicate of this bug. ***
*** Bug 172693 has been marked as a duplicate of this bug. ***
*** Bug 172895 has been marked as a duplicate of this bug. ***
*** Bug 300242 has been marked as a duplicate of this bug. ***
*** Bug 300225 has been marked as a duplicate of this bug. ***
*** Bug 300329 has been marked as a duplicate of this bug. ***
*** Bug 300624 has been marked as a duplicate of this bug. ***
*** Bug 300782 has been marked as a duplicate of this bug. ***
fixed in CVS both HEAD and gnome-2-10 branches.
*** Bug 301947 has been marked as a duplicate of this bug. ***
*** Bug 302235 has been marked as a duplicate of this bug. ***
*** Bug 302383 has been marked as a duplicate of this bug. ***
*** Bug 302489 has been marked as a duplicate of this bug. ***
*** Bug 302699 has been marked as a duplicate of this bug. ***
*** Bug 303098 has been marked as a duplicate of this bug. ***
*** Bug 303097 has been marked as a duplicate of this bug. ***
*** Bug 304176 has been marked as a duplicate of this bug. ***
*** Bug 304279 has been marked as a duplicate of this bug. ***
The last dup is 2.10.1 Has this really been fixed? I believe not. Bumping version to 2.10.x
Paolo, should the fix have made it into 2.10.1 ? If yes we need to reopen.
this is fixed since version 2.10.3
*** Bug 305122 has been marked as a duplicate of this bug. ***
*** Bug 306223 has been marked as a duplicate of this bug. ***
*** Bug 306166 has been marked as a duplicate of this bug. ***
*** Bug 306049 has been marked as a duplicate of this bug. ***
*** Bug 305651 has been marked as a duplicate of this bug. ***
*** Bug 306862 has been marked as a duplicate of this bug. ***
*** Bug 307533 has been marked as a duplicate of this bug. ***
*** Bug 307923 has been marked as a duplicate of this bug. ***
*** Bug 322749 has been marked as a duplicate of this bug. ***
*** Bug 332144 has been marked as a duplicate of this bug. ***
*** Bug 321202 has been marked as a duplicate of this bug. ***