Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


https://bugs.freedesktop.org/show_bug.cgi?id=56284

Stephan Bergmann <sbergman@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sbergman@redhat.com

--- Comment #11 from Stephan Bergmann <sbergman@redhat.com> ---
FYI, at least current master towards LO 4.2 on Linux:

* If there is no ~/.config, LO silently creates ~/libreoffice/4 instead of
~/.config/libreoffice/4 and uses that.  This is probably a bug.

* If ~/.config is a directory that is not accessible (no rwx flags) LO refuses
to start with a "The application cannot be started. An internal error
occurred." error box and does not create anything.

* If ~/.config is a directory that is not writeable (just r-x flags) LO refuses
to start with a "The application cannot be started. User installation could not
be completed." error box and does not create anything.

* If ~/.config is a file instead of a directory LO refuses to start with a "The
application cannot be started. The configuration file
'/.../program/bootstraprc' is corrupt." error box (whose wording does make
sense, given that bootstraprc's UserIntsallation=$SYSUSERCONFIG/libreoffice/4
points at a "broken" path) and does not create anything.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.