Bug 126985 - right and bottom page margins in settings dialog reset to 0cm.
Summary: right and bottom page margins in settings dialog reset to 0cm.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.5.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-17 10:15 UTC by Holger Jakobs
Modified: 2020-05-20 07:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of error (77.50 KB, image/png)
2019-10-21 05:16 UTC, Heydrun Areyla Colmenares Roa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Jakobs 2019-08-17 10:15:36 UTC
Description:
When a page is in landscape mode and margins are entered in the settings dialog, they are effective. But on opening the settings dialog again, right and bottom margins are reset to 0cm.

Steps to Reproduce:
1. Create new Writer document.
2. Open page settings dialog.
3. Enter all margins > 0cm and press OK.
4. Open page settings dialog.


Actual Results:
Right and bottom margins show 0cm.

Expected Results:
Right and bottom margins should show the values previously entered.


Reproducible: Always


User Profile Reset: No



Additional Info:
Show the current values, but not 0cm.

Version: 6.2.5.2
Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
Comment 1 Dieter 2019-08-20 16:17:44 UTC
I can't confirm that with

Version: 6.2.5.2 (x64)
Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded

To be certain the reported issue is not related to corruption in the user profile, please try it with safe mode (Help => Restart in Safe Mode)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Comment 2 Heydrun Areyla Colmenares Roa 2019-10-21 05:16:33 UTC
Created attachment 155175 [details]
Screenshot of error
Comment 3 Heydrun Areyla Colmenares Roa 2019-10-21 05:26:51 UTC
Comment on attachment 155175 [details]
Screenshot of error

Description:
In Writer, Calc, Inpress or Draw when margins are entered in the settings dialog they are effective, but on opening the settings dialog again two margins are reset to 0cm.

Steps to Reproduce:
1. Create new document.
2. Open page settings dialog.
3. Enter all margins > 0cm and press OK.
4. Open page settings dialog.

Actual Results:
Two margins show 0cm.

Expected Results:
Margins should show the values previously entered.

Reproducible: Always

User Profile Reset: Yes

Additional Info:
I uninstalled LibreOffice 6.2.6.2, after I delete the folder /home/drumy/.config/libreoffice after and /opt/libreoffice6.2, then I install Libreoffice 6.2.7.1. The error persist from version 6.0 to 6.2.7.1 in Debian 9

Version: 6.2.5.2
Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
Comment 4 Dieter 2019-10-21 05:37:28 UTC
Holger, could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 5 QA Administrators 2020-04-19 03:37:13 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2020-05-20 03:41:53 UTC Comment hidden (obsolete)
Comment 7 Holger Jakobs 2020-05-20 06:57:45 UTC
My system is Linux (Ubuntu Mate 18.04)

LibreOffice version 6.3.5.2 still shows has the bug.

The error is no longer present in version 6.4.3.2

All necessary steps to reproduce have already been described. Don't ask for repetition!

Test case including screen shot has already been provided. Don't ask for the same again!
Comment 8 Dieter 2020-05-20 07:00:15 UTC
(In reply to Holger Jakobs from comment #7)
> The error is no longer present in version 6.4.3.2

=> RESOLVED WORKSFORME