Description of problem: The default directory "Téléchargements" (Download) in a user home directory is not correctly handled by Dolphin. Each time that Dolphin is opened, another directory is created "T?l?chargements". The same occurs after having installed the graphical applet "Vue de dossier" by Fredrik Höglund when it shows the user home directory: double click on one of the directory icons, this launches Dolphin and adds "T?l?chargement" to the Dolphin's window and to the applet window. If this new directory is not erased, nothing more occurs on the next launching. Note that other accentuated directory names such as "Modèles" or a user-created "Elèves" or "Eléves" are not affected. Version-Release number of selected component (if applicable): KDE 4.10.5 + Dolphin 2.2 How reproducible: Always Steps to Reproduce: 1. Install Mageia3 64 bits in French 2. Log in as a user in KDE 3. Launch Dolphin and enter the user directory [or] Install a KDE applet that shows this user directory and double click on one of the icons to launch Dolphin. Reproducible: Steps to Reproduce:
Possible cause has been identified: 1°) During install, the system language (locale) had been set to be compatible with non UTF-8 (checked box in the MCC System Localization section). Unchecking this box was not enough probably because the user profiles did already exist, and things got worst: now each accentuated file or directory name was filled with escaped characters "<?>" (Mod<?>les, Vid<?>os, T<?>l<?>chargements). The solution to erase them did not work because Dolphin read the files generated by the xdg application which are not updated by the system setting (only the config files for the application are), and re-created them each time. Unchecking the MCC box only change the locales (~/locale) from fr_FR to fr_FR.UTF-8 as per /usr/share/locale/ . Solution: - if you let xdg with its default configuration in /etc/xdg/user-dirs.conf: enabled=True filename_encoding=locale - for each user, you have to manually correct the existing user config files in: ~/.config/user-dirs.locale fr_FR -> fr_FR.UTF-8 ~/.config/user-dirs.dirs (just check that the default directories that are always created are okay) (if an entry is absent or equal to "$HOME, the directory won't be re-created) - disconnect/reconnect once and launch Dolphin, erasing older mispelled directories, or hiding, then de-hiding and erasing them. Close/launch Dolphin until it works. 2)° As for the fact only "Téléchargement" caused a problem on these accounts when under (LANG=fr_FR), the apparent answer is that for some reason, the XDG_DOWNLOAD_DIR entry was absent in the ~/.config/user-dirs.dirs (whereas it was present in the /etc/xdg/user-dirs.defaults) I din't try and recreate the starting (install) situation, but it may be the reason with Dolphin "failed" with the fr_FR setting. That's why I'm correcting the title to [WORKAROUND] instead of [SOLVED]. I don't know why xdg didn't updated the files on the existing accounts when I switched to fr_FR.UTF-8 in the system, maybe for the same reason that changing a skeleton directory doesn't change the existing user profiles, but it could be the same reason why it hadn't recreate the XDG_DOWNLOAD_DIR entry before the switch. Also, I wonder whether all local applications read the xdg user files each time they launch, as Dolphin seems to do, or only the first time in a given session, because the LFS manual explains that you have to unlog/relog in order that any change to those files is acknowledged by the local applications.
Summary: KDE + Dolphin and french localization : T?l?chargements => [WORKAROUND] KDE + Dolphin and fr_FR localization : T?l?chargements
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD