Bug 123672 - System font size in LO 6.2
Summary: System font size in LO 6.2
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-23 21:15 UTC by Michal Janoušek
Modified: 2019-03-28 19:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Janoušek 2019-02-23 21:15:36 UTC 
Description:
System font size change only menu font but is smaller in 4K monitor.

LO 6.2 https://app.box.com/s/b6brnsy5ca3sgbgr72dpf3nrk9guucy3
LO 6.1.5 https://app.box.com/s/kav58q4xram17ig2wguiwkseawfomwh4

I using LinuxMint 19.1 64 bit with Plasma 5.12 and change size and DPI font to 144.

Actual Results:
Small size font in right panel and bottom panel.

Expected Results:
Same font size across the LO app.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 Xisco Faulí 2019-03-28 17:18:21 UTC 
Thanks for reporting this issue.
We migrated from KDE4 to KDE5 in LibreOffice 6.2
Are the other app's menus shown the same way LibreOffice 6.2 does ?
OTOH, many KDE issues has been fixed in since 6.2.0.3 was released.

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.
Comment 2 Michal Janoušek 2019-03-28 18:59:51 UTC 
Hello, thnaks very much. In Version 6.2 works well :-)
Comment 3 Xisco Faulí 2019-03-28 19:02:05 UTC 
(In reply to Michal Janoušek from comment #2)
> Hello, thnaks very much. In Version 6.2 works well :-)

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.