Description: If trying to open a document that has german umlauts in its file-path LibreOffice will tell me that the respective file does not exist. This applies to opening the file from within the file-exploroer via double-clicking as well as if using the File->Open dialog from within the application. A similar behavior can be observed when trying to save a file into a directory containing umlauts in its name. With version 5 this problem did not exist. I have Steps to Reproduce: 1. Copy an existing spreadsheet into a directory named "testä" 2. Try opening said file 1. Open a new, empty ODT file 2. Try to save it into a folder named "testä" Actual Results: In either case I get the error message claiming the given file wouldn't exist. In case of the saving process it will then tell me there was some problem with the user's permission to save the file (might or might not be correlated with the actual bug) Expected Results: It should be able to handle umlauts in file paths Reproducible: Always User Profile Reset: No Additional Info: Version: 6.0.4.2 Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 4; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: en-US (nds_DE.UTF-8); Calc: group
Could not reproduce on Windows 8.1: in Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 4; OS: Windows 6.3; UI render: GL; Locale: en-US (en_US); Calc: CL and Version: 6.2.0.0.alpha0+ Build ID: b1740fba0d1e6e3d69c3781734509317f42a0e4f CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-15_08:49:04 Locale: en-US (en_US); Calc: CL
Then I guess this is a Linux specific problem. I am running Linux Mint 18.3 (KDE edition) with the 4.12.14 kernel
No problem here with Linux and KDE. Do other programs behave OK? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Arch Linux 64-bit Version: 6.0.4.2 Build ID: 6.0.4-1 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
I used to have a problem with umlauts on my system (for details see https://unix.stackexchange.com/questions/425929/problems-with-umlauts-cant-type-in-terminal-cant-open-files) but that only hindered me from opening files via double-click from within the file explorer. Starting the application and opening the file from in there worked without any problems. I thought the problem to be fixed though as all other applications (including LibreOffice 5.x which I had installed from the Ubuntu-repository) are working just fine. Could it be that LibreOffice 6.x is handling system locales a little different than generation 5? The problem might be that I have set my machine up to using english in the first place. In order to get umlauts working on my machine I had to play with my locale settings. My current setup is therefore a mix of german and english locales. Below is the output of the locale command: LANG=nds_DE.UTF-8 LANGUAGE=en_US LC_CTYPE="nds_DE.UTF-8" LC_NUMERIC="nds_DE.UTF-8" LC_TIME="nds_DE.UTF-8" LC_COLLATE="nds_DE.UTF-8" LC_MONETARY="nds_DE.UTF-8" LC_MESSAGES="nds_DE.UTF-8" LC_PAPER="nds_DE.UTF-8" LC_NAME="nds_DE.UTF-8" LC_ADDRESS="nds_DE.UTF-8" LC_TELEPHONE="nds_DE.UTF-8" LC_MEASUREMENT="nds_DE.UTF-8" LC_IDENTIFICATION="nds_DE.UTF-8" LC_ALL= As you can see everything except the LANGUAGE is set to german. Any chance that LibreOffice 6 is relying on exactly that parameter in order to determine what characters to expect?
Okay I just tried opening a problematic file via the terminal and got this output I18N: X Window System doesn't support locale "nds_DE.UTF-8" As it seems there is something going on in the X Window System... Though it seems strange to me that LibreOffice is the only problem suffering from that problem...
Yep, it sounds like LibreOffice is not the one to blame.
Yes it isn't. I fixed the problem by setting my locale to "de_DE.utf8" for everything except LANG and LANGUAGE. Thanks to anyone involved here and sorry for wasting your time. As said before: LibreOffice 6 appears to be using another mechanism for the whole thing as all other applications installed on my machine as they were working perfectly fine. But if configured properly it works just as well ^^