GNOME Bugzilla – Bug 336115
Files/directories with a "Invalid encoding" makes nautilus to crash.
Last modified: 2006-03-26 22:19:57 UTC
Steps to reproduce: 1. I drag'n'dropped a directory containing some sub-directory names tagged with "Invalid encodding" from one vfat drive to the ext3 LVM created by the Ubuntu installation 2. Nautilus Crashed Stack trace: Backtrace was generated from '/usr/bin/nautilus' (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) [Thread debugging using libthread_db enabled] [New Thread -1226237728 (LWP 8115)] [New Thread -1235981392 (LWP 8159)] [New Thread -1235715152 (LWP 8158)] [New Thread -1235448912 (LWP 8157)] [New Thread -1234760784 (LWP 8156)] [New Thread -1229001808 (LWP 8132)] (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) (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67259
Thread 1 (Thread -1226237728 (LWP 8115))
Other information: I filled the bug manually because bug-buddy didn't find sendmail and realised late that the component bug-buddy assigned the bug was "general" instead of "Cut Copy Paste Undo" that I selected (I thougth that drag'n'dropping would be similar to a copy-paste action). This can be workarounded by renaming the directories with a terminal (with the nice autocomplete feature :) ), but to implement one of the following options would be nice: a- Stop the copy process on the first "Invalid encoding" detected file/directory and warn the user of the issue with encodings (instead of crashing nautilus). or: b- Pre-process all the file/directory names to be copied before the copy, and if some issue has been found do not copy any file at all and warn the user about the encoding problem with some files. or: c- Skip the files/directories identified as "Invalid encoding", copying the other files/directories and at the end of the process show a dialog with the "Invalid encoding" files/directories that were found and not copied. Also 'b' or 'c' can display some means to fix it, like a "Select an encoding that displays propperly the flienames" dialog, displaying a list with the encodings, and a list with the filenames affected providing the user with dynamic feedback with the selection of the encoding. This seems related to Bug 318280, Bug 301777 and/or Bug 314538
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 325586 ***