I'm running LO as a non-root/non-privileged user - as one does on a typical operating system. When I "Manage Templates", choose the Default Template and Edit it - it opens, but a top blue bar tells me the template is open in Read Only mode, suggesting I click a button in order to edit the template - even though that's what I said I want to do. This is already a problem, and doubly so because I'm not told the _reason_ I can't edit the template; nor was I prevented from doing so in the Manage Templates dialog. But the more serious problem is that when I try to save - to overwrite - the template file, I get: "Error saving the document Default: Write Error. The file could not be written." this is again twice a problem: First, the write failing, which I suspect is due to the fact that I'm not root, so I can't overwrite that file, and second, that I'm not told what actually happened, just a vague message about an error. The immediate thing to fix is to clarify to the user why they're experiencing this, i.e. some message saying "The default template can only be edited by a system administrator / root user" or something along those lines. Alternative, Edit must not be available on the context menu of nonroot-user-edit But - this would not be satisfactory, since a user _does_ need to be able to edit their default document template. So one of the following needs to happen: 1. The default template is duplicated into a user's account when LO is first started. 2. The default template is duplicated into a user's account when the user first manages templates. 3. The default template is duplicated into a user's account when the user first opens it for editing 4. The user is prompted to set their default template to a duplicate of the system-wide one, to be able to edit it, and must themselves choose whether to do this. In any of those cases - once the duplication happens, choosing the default template should open the user-home-directory-version, not the system-wide version; and a system-wide default may potentially also start being presented. 5. When trying to save a root-only-editable template, the user will be prompted to either give up or provide the root password.
We just badly need to rename that template from the idiotic "default" name (which lies, because it has nothing to do with what happens by default)
(In reply to Mike Kaganski from comment #1) > We just badly need to rename that template from the idiotic "default" name > (which lies, because it has nothing to do with what happens by default) Well, users coming from MSO assume that this is how you edit the styles you get in a new document. In fact, that's what I usually remember :-P So, changing the name would also need to be accompanied by making it more obvious to the user how to actually edit the defaults.
We install factory settings in the restricted area; same happening for Gallery content see bug 131529. Content that is typically editable needs to be installed in the user space.
(In reply to Heiko Tietze from comment #3) > Content that is typically editable needs to be installed in the user space. So, I'm guessing you would support one of options (1.) - (3.)?
No duplication. We need to check what can be moved from /usr/lib/libreoffice/share/ to ~/.config/libreoffice/4 (in terms of Linux).
Dear Eyal Rozenberg, 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
No change with Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f0868e555a3054487c49690c9e2398bedf9067b7 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US