GNOME Bugzilla – Bug 317736
Nautilus crashes when copying files with invalid encoding or special characters like umlauts in their filenames
Last modified: 2005-10-02 18:05:51 UTC
Distribution: Ubuntu 5.10 (breezy) Package: nautilus Severity: Normal Version: GNOME2.12.0 2.12.0 Gnome-Distributor: Ubuntu Synopsis: Nautilus crashes when copying files with invalid encoding or special characters like umlauts in their filenames Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: I copied some files from one folder to another. Nautilus crashed, because of a filename containing '&'. This also happens with filenames that show '(invalid encoding)' which might mean that it's an utf8 <-> iso-8859-1 issue. Steps to reproduce the crash: 1. Choose a file with (invalid encoding) in the filename. 2. Copy it to another folder. 3. Enjoy the sight of nautilus crashing. Expected Results: A clean copy :-). How often does this happen? Every time. Additional Information: I use Ubuntu Breezy with the latest updates from Oct 2 2005 with the following locale(s): LANG=de_DE.UTF-8 LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= Debugging Information: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1226451264 (LWP 12874)] [New Thread -1244488784 (LWP 12939)] [New Thread -1244222544 (LWP 12935)] [New Thread -1241310288 (LWP 12882)] [New Thread -1241044048 (LWP 12881)] [New Thread -1240769616 (LWP 12880)] [New Thread -1240020048 (LWP 12879)] [New Thread -1228833872 (LWP 12875)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63316
Thread 1 (Thread -1226451264 (LWP 12874))
-- "Every thing possible to be believ'd is an image of truth." - William Blake ------- Bug moved to this database by unknown@gnome.bugs 2005-10-02 12:03 UTC ------- Unknown version 2.12.0 in product nautilus. Setting version to "2.12.x".
This is due to nautilus-python
Sebastien: No, it has nothing to do with python.
Christian: But it seems like. I just de-installed the ubuntu python-nautilus package. The bug is not reproducable anymore.
Bastian: There is a patch available under: http://mail.gnome.org/archives/nautilus-list/2005-October/msg00008.html Please check whether it helps.
Created attachment 52938 [details] [review] Proposed patch
Thanks for the extremely verbose stack trace btw. :)
That's a nice thing about ubuntu :-), I just installed the nautilus-dbg package and let nautilus crash again... Btw., Since I don't have any build stuff installed I gotta see whether I can manage to apply the patch. Haven't compiled anything for ages... Schönen Sonntag noch ;-), Bastian
It's as simple as sudo apt-get install fakeroot && apt-get source nautilus && cd nautilus* && gnomevfs-cat "http://bugzilla.gnome.org/attachment.cgi?id=52938&action=view" | patch -p0 && fakeroot dpkg-buildpackage -us -uc && cd .. dpkg -i *nautilus*.deb
Okay, I built the packages, installed a few more dependencies, reinstalled python-nautilus, did a killall nautilus and tried to copy a file affected. As expected, Nautilus crashed. Then I executed sudo dpkg -i *nautilus*.deb and did a killall nautilus. Afterwards I tried to copy, again. Unfortunately, Nautilus crashed with the below pasted stacktrace. Afterwards I de-installed python-nautilus again and tried another copy, which worked. Bastian Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225578816 (LWP 3998)] [New Thread -1240753232 (LWP 4005)] [New Thread -1240486992 (LWP 4004)] [New Thread -1239274576 (LWP 4000)] [New Thread -1228059728 (LWP 3999)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63320
Thread 1 (Thread -1225578816 (LWP 3998))
*** This bug has been marked as a duplicate of 168695 ***