Summary: | Locale settings not recognized by krusader | ||
---|---|---|---|
Product: | [Applications] krusader | Reporter: | slartibart70 |
Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | albertczyk, bhush94, krusader-bugs-null, plasma-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
slartibart70
2016-05-24 21:17:37 UTC
I also have a very similar issue (probably the same root cause) since I upgraded to Fedora 22 w/ KDE 4.14.17. I have my locale set to es_ES.UTF-8, and krusader (2.4.0-beta3) displays properly the filenames with international characters (like Música, Imágenes), but if I try to display or move any file within a path containing UTF-8 encoded chars, I get a 'file or directory doesn't exist' error. Now, the interesting part is that if I start krusader from a konsole session with $ LANG=C krusader then filenames appear garbled (like Im~A¡genes), but I can move/open them freely. But if I start krusader with $LANG=es_ES.UTF-8 krusader I get the previous behaviour: file names are displayed OK, but it's not possible to move/open. Sorry, didn't read properly that this was related to timestamps, probably I should open a new bug. I found the fix for it: kcmshell4 language (krusader is still controlled by kde4 settings) |