| Summary: | File registrymodifications.xcu is resetted after closing LibreOffice | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | j.t.d.jager |
| Component: | Installation | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | CC: | drechsel |
| Version: | 3.3.1 release | ||
| Hardware: | PowerPC | ||
| OS: | Mac OS X (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 41560 | ||
|
Description
j.t.d.jager
2011-02-04 10:20:46 UTC
me too! (In reply to comment #0) > After closing LibreOffice, the file registrymodifications.xcu will be resetted. > (It happened right after closing. Not at the moment of restarting.) > So the next time LibreOffice starts, it starts with default options (e.g.: > default general options, default autocorrection-options, default toolbars). The > file is situated in ~/.libreoffice/3/user/. > > Note: Not always when closing LO, the file will be resetted. Up to this moment > I can't figure out what is making the reset happens. > > Note: when using quickstart: after a reset of the file the icon of the > quickstart changes from LibreOffice-icon tot OpenOffice-icon It seems to be this will NOT happens, if NOT saving changes to your document when closing LO. That will say: to the last document you close. Ex.: You are working at 6 files. You can close 5 of them without any problems. When you close the last one, you have to close it without saving changes. I cannot confirm commen #2: This workaround does not work on my Macs (Mac OS X 10.5.8 Leopard, PPC ). This one might be related to "Bug 40578 - CONFIGURATION: Tools-Customize-Keyboard changes should be persistent". [This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.