Bug 304226 - Unable to open files with 2-byte unicode whitespace from within kde
Summary: Unable to open files with 2-byte unicode whitespace from within kde
Status: RESOLVED DUPLICATE of bug 268771
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.8
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-29 07:55 UTC by karl.r.ernst
Modified: 2012-07-29 08:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description karl.r.ernst 2012-07-29 07:55:51 UTC
If a filename has a 2-byte whitespace in it, I am unable to open it from within KDE. Filetype seem to not matter, tested with .jpg imags and plain text files.
Also tested to click on the file from within dolphin, and on the folder view on the desktop, both don't open.
Happens also withnon-kde apps, "open with -> gimp" also fails.

Another weirdness is that KDE seems to think this are 2 seperate files.
a file "test .jpg" -> open with -> gimp shows the gimp error message:
"/home/karl/test could not be openend: file not found
/home/karl/Dokumente/.jpg could not be openend: file not found"

Any other unicode 2-byte character seem to work fine though. Also "file -> open" from within the applications itself (like gwenview, kate) still work fine for the files

Reproducible: Always

Steps to Reproduce:
1. create a textfile "test"
2. open it and write something in it
3. rename the file to e.g. "te st"
4. try to open it
Actual Results:  
kate shows 2 empty files

Expected Results:  
the file with the string should be opened
Comment 1 Jekyll Wu 2012-07-29 08:00:04 UTC
Thanks for reporting.

*** This bug has been marked as a duplicate of bug 268771 ***