| Summary: | Unfilled arrow styles are not saved properly | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Alexander Karatarakis <alex.karatarakis> |
| Component: | Draw | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | rb.henschel |
| Priority: | medium | ||
| Version: | 3.5.4 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Alexander Karatarakis
2012-06-21 06:48:30 UTC
The root cause of this problem is described in issue 47406. You can find discussions about that problem in the developer mailing list too. I have adapted the arrow heads to the new, corrected way the z attribute is interpreted. But it is possible, that you still have the old file in your user profile. Please rename your LO user profile folder temporarily and start LO newly and test the behavior in this new environment. If save and reload is okay there, then rename the file 'standard.soe' in your original user folder and copy the corresponding file from the newly created user folder to your original one. On Windows the file is located in \LibreOffice\3\user\config; I guess it is in a similar path in Ubuntu. After that action change back the name of your original LibreOffice user folder. Another way to get the correct file is to download it from the source repository http://opengrok.libreoffice.org/raw/core/extras/source/palettes/standard.soe Notice, that you cannot use documents using this unfilled line ends in old and new versions of LibreOffice, in turns. I tried deleting the entire LibreOffice\3\user\config folder (and it was recreated on next launch) as well as replacing standard.soe with the file you linked but it did not fix the issue. It is still an issue in LibreOffice 3.5.5.2 but I just tried Libreoffice 3.6 Beta 2 and it works as expected. I had to purge 3.5.x to install 3.6 so it may indeed be a problem with old configuration files that were removed. Since the new version (3.6b2) works, I assume this is resolved. Also, thanks for the quick response :). |