Bug 76774 - Bad unicode breaks nautilus open application
Bad unicode breaks nautilus open application
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: nautilus (Show other bugs)
8.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Alexander Larsson
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-26 06:00 EDT by Need Real Name
Modified: 2015-01-07 19:01 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-12 09:05:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Tar of file with "bad unicode" name that crashes nautilus eventually (10.00 KB, application/x-tar)
2002-10-28 03:40 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-10-26 06:00:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
I had a filename with bad unicode (from vfat partition).  Once a nautilus window
on the directory containing this bad filename, then doubleclicking on ANY
openoffice document ANYWHERE to open the document caused nautilus to consume all
memory and swap and then crash and restart.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a filename with bad unicide (nautilus will report (Invalid Unicode)
below the filename.  My filename had character 0xD0 as one charater
2. Use nautilus to navigate to the directory containing this bad file
3. Double click on any open Office document anywhere (even on the deskto)
4. Watch nautilus die
5. All is well again until that folder is shown by nautilus again
	

Actual Results:  Nautilus crashes consuming all memory when opening ocuments

Expected Results:  Nothing much

Additional info:
Comment 1 Havoc Pennington 2002-10-26 11:07:17 EDT
Can you get us the exact filename?

I'm not thinking of a _great_ way to upload the filename; you could make a tar 
archive of the single file, but that would include the file contents.
Maybe just "echo filename > foo.txt" and attach foo.txt would work, 
maybe instead of typing "filename" type the first letter and push tab so 
the shell escapes it for you, if it contains chars the shell doesn't like.

Thanks!
Comment 2 Need Real Name 2002-10-28 03:40:17 EST
Created attachment 82344 [details]
Tar of file with "bad unicode" name that crashes nautilus eventually
Comment 3 Alexander Larsson 2002-11-05 04:41:21 EST
Very strange. I can repeat this every time with the RH8 nautilus, but it crashes
in very strange places. It seen to often be in __errno_location in libc (which
reads thread local storage). I also saw it once in __pthread_alt_lock. This
seems to point to a thread issue of some sort.

I also reproduced it by launching gedit on a text file. OOo is not required.

Unfortunately this doesn't happen at all in my gnome cvs build, which means
either it was fixed, or the different build is hiding the issue.
Comment 4 Alexander Larsson 2002-11-05 05:02:17 EST
Tried to valgrind it, but ran out of memory :/
Comment 5 Alexander Larsson 2003-01-16 09:35:46 EST
I can't seem to reproduce it on phoebe. Maybe it's fixed.
Comment 6 Alexander Larsson 2003-08-12 09:05:01 EDT
Marking this fixed, since we haven't seen any dups since then.

Note You need to log in before you can comment on or make changes to this bug.