Description: I got an Excel-Sheet where the filename had german umlaute ü/ä Filename is displayed as: BBB Iphonezübehör.xls Investigating the filename on the command line (ls -l) showed: 'BBB Iphonez'$'\303\274''beh'$'\303\266''r.xls' Trying to open this file with LO from commandline (soffice <FILENAME>) causes LO to hang :-( hf@b65:~$ ps ax|grep libr 7977 pts/1 S+ 0:00 /usr/lib/libreoffice/program/oosplash BBB Iphonez??beh??r.xls Opening from LO-dialog shows a box with: The operation on /tmp/BBB Iphon..(weird characters)....xls was started with an invalid parameter. Steps to Reproduce: 1.Create/copy a sheet with a filename like the one mentioned above (difficult, unable to use german umlaute for saving on my LINUX-Box, use WINDOWS to create one) 2.try to open the file (soffice <FILENAME>) 3. Actual Results: LO hangs (commandline) or gives an error message (LO-dialog) Expected Results: LO should give an error message but should not hang on commandline Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: The environment: LIBREOFFICE: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3; Locale: de-DE (en_DE.UTF-8); UI-Language: en-US Calc: threaded LINUX: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal
On pc Debian x86-64 with master sources updated today, here's the test I did: - Create a brand new xls file with LO containing just "test" in A1 - Save file with "test.xls" - Close LO - Rename the file with: mv test.xls "BBB Iphonezübehör.xls" - ./soffice /tmp/BBB\ Iphonezübehör.xls (Debian automatically put \ to escape the space) => no pb I also did: - ./soffice "/tmp/BBB Iphonezübehör.xls" => no pb I must recognize, I don't understand BBB Iphonez'$'\303\274''beh'$'\303\266''r.xls what's the encoding?
I did some more investigation and found the problem. It's not related to LibreOffice. My KDE Regional Setting was somehow set to en_DE.UTF-8 which doesn't exist. Strange. It should be de_DE.UTF-8. Setting the correct locale solved the problem. Even more strange. Now I get an error message from LO despite the wrong locale. I think it was just a weird configuration of my box. Everything is fine now.