Not sure how to replicate this, but i found this tweet and thought it would be useful to see if it was true. Linux Lessons: #libreoffice exits with no error message if the user running it doesn't have an existing ~/.config/ that they own. https://twitter.com/nwe23/status/565183077681733632
How it is possible to not have a ~/.config with writing permission in his home ? Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #1) > How it is possible to not have a ~/.config with writing permission in his > home ? The tweet said that the ~/.config didnt exist when opening LO, so i'm assuming it meant that the folder wasnt present. So i guess it would be possible to test this by renaming ~/.config to something else and then launching LO to see if it starts.
It would be interesting to know which Linux distribution he uses, because this folder, for example under Ubuntu, is created when you create your session, that is before you launch LibreOffice for the first time. This folder contains many subdirectories with data configuration for other softwares like gtk, totem, evince, unity, etc. Best regards. JBF
(In reply to Jay Philips from comment #2) > So i guess it would be > possible to test this by renaming ~/.config to something else and then > launching LO to see if it starts. No, if I do that I will destroy my Ubuntu session. See my previous comment. best regards. JBF
I've asked the tweet user to add more details to the bug report.
I should point out that this was a problem for a server running libreoffice in --headless mode, to do file conversion. The account which was running libreoffice was a /local/ software user, rather than a normal user account with home directories mounted under NIS, and didn't have a .config in their home directory. There were also some other issues which are probably more important which were mostly down to the initial install being the libre-office-headless package, which didn't actually include the ability to open files, and when --convert-to was done that was causing the silent exit (the exiting without access to ~/.config was a separate yet parallel issue!) After also installing some other libre-office packages (such as calc), it started working. I would suggest adding an error message when a --convert-to is issued with --headless and the desired format packages aren't installed.
Setting back to UNCONFIRMED to get retested.
(In reply to nickengland from comment #6) > ...I would suggest adding an error message when a --convert-to is > issued with --headless and the desired format packages aren't installed. Sound reasonable; packaging questions (if they're not TDF-provided DEBs or RPMs) should be directed to the appropriate distro maintainers. That being said, we should be able to recover from a missing ~/.config/ and at least give some reasonable error message. Status -> NEW
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear Yousuf Philips (jay), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug