Bug 101367

Summary: Bad font rendering in window
Product: LibreOffice Reporter: adpinto95
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: aron.budea
Priority: medium    
Version: 5.1.4.2 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Can't read text in window
Another example

Description adpinto95 2016-08-07 14:45:05 UTC
Created attachment 126645 [details]
Can't read text in window

Hello,

i'm running Xubuntu 16.04 and i'm running LibreOffice calc.

Details of LibreOffice Calc:
- Version: 5.1.4.2
- Build ID: 1:5.1.4-0ubuntu1
- CPU Threads: 4; OS Version: Linux 4.6; UI Render: default; 

There appears to be an issue with the font rendering in some windows (see attachment), where you can't read the description at all. In this case, when i try to delete a sheet from LibreOffice Calc, i can't read the message in the window.

What's the best course of action to solve this issue?

Best regards,

Ad
Comment 1 Thomas Hackert 2016-08-07 14:52:40 UTC
Hello adpinto95, *,
I cannot confirm your bug with
OS: Debian Testing AMD64
LO: Version: 5.1.5.2
Build ID: 1:5.1.5~rc2-1
CPU Threads: 4; OS Version: Linux 4.5; UI Render: GL; 
Locale: de-DE (de_DE.UTF-8); Calc: group
DM/WM: XFCE/XFWM 4.1.2 (default font: Liberation Sans, fixed font: Liberation Mono)

Which DM/WM are you using on XUbunt and which font? Does changing the font in your DM changes the text in the dialog?
HTH
Thomas.
Comment 2 adpinto95 2016-08-07 17:18:59 UTC
Created attachment 126649 [details]
Another example
Comment 3 adpinto95 2016-08-07 17:22:14 UTC
(In reply to thackert from comment #1)

Hello again,
i'm using XFCE (Version 4.12) as DE and xfwm4 as WM. the font i am using is open Sans 8.
Yes, changing the font in my DM changes the font in the dialog.

more details:
OS: linux 
Kernel: x86_64 Linux 4.6.0-040600-generic



Ad.
Comment 4 Aron Budea 2016-08-08 00:11:08 UTC
Please update to LibreOffice 5.1.5 or 5.2.0, the bug is fixed there.

*** This bug has been marked as a duplicate of bug 99446 ***