So, this month is "März" in German, and trying to start LibreOffice segfaults on the following error: $ libreoffice ls: error initializing month strings /usr/bin/libreoffice: line 58: cd: lrwxrwxrwx 1 root root 38 10. Mä/usr/lib64/libreoffice/program: No such file or directory /usr/bin/libreoffice: line 180: /usr/bin/oosplash: No such file or directory According to another help forum, the problem lies in this code from /usr/lib/libreoffice/program/soffice: # resolve installation directory sd_cwd="`pwd`" if [ -h "$0" ] ; then sd_basename=`basename "$0"` sd_script=`ls -l "$0" | sed "s/.*${sd_basename} -> //g"` cd "`dirname "$0"`" cd "`dirname "$sd_script"`" else cd "`dirname "$0"`" fi sd_prog=`pwd` cd "$sd_cwd" I suppose this goes along with "internationalization" as I am running on a German-enabled OS. Locale is de_DE.utf8. Thanks for the help!
Is this still a problem with latest stable release? I usually don't ask this but I haven't seen any other complaints so I wonder if it was a short lived bug. If not can you backup your user config folder, delete the user config file (after backup), and then try starting from a fresh setup with LibO. Marking as NEEDINFO. Try these things out, if still a problem please reopen this as UNCONFIRMED and put your current version of LibO (should be 3.5.7 or 3.6.1.2+)
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
I'm now using version 4.0.3.3, and yes, this problem recurred again this year (but only in March), using a fresh install. I apparently resubmitted this as Bug #62192 (PS, please mark that as a dupe of this bug), in which another user made a suggestion for how to fix it (ie, there's a coreutil called "realpath" that can resolve paths correctly, and won't puke on month strings using UTF-8 characters). The user there marked it as an "easy hack," but it's something that would have to go into the LO launch script, which I myself am, of course, not empowered to do. Hope this helps! Cheers, EE
Clone of Bug 62192.