Bug 96298

Summary: Certain parts of the interface are corrupt (Fedora)
Product: LibreOffice Reporter: Omar <omar.ahafez87>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: harveymodlin, raspberrypi123456789, vsfoote
Priority: medium    
Version: 5.0.0.5 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
See Also: https://bugzilla.redhat.com/show_bug.cgi?id=1283420
https://bugs.documentfoundation.org/show_bug.cgi?id=99446
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: This is how the page settings window looks like. Notice the corrupt "Next Style" item.

Description Omar 2015-12-06 22:28:10 UTC
Created attachment 121089 [details]
This is how the page settings window looks like. Notice the corrupt "Next Style" item.

I installed Fedora linux earlier today, and as I started to use Libreoffice, I found some parts of the interface not rendering correctly. You can see the picture attached for an example of what I'm talking about.
Comment 1 V Stuart Foote 2015-12-07 02:45:37 UTC
We'll need details about your Desktop environment(s) in use. And, does it improve when you switch to one of the other DEs?
Comment 2 Maxim Monastirsky 2015-12-20 19:39:42 UTC
*** Bug 96628 has been marked as a duplicate of this bug. ***
Comment 3 Maxim Monastirsky 2015-12-20 19:41:59 UTC
We have an exact duplicate in Bug 96628. Both apparently are under Fedora + GNOME Shell.
Comment 4 Maxim Monastirsky 2015-12-20 19:57:06 UTC
Added downstream report to 'See Also'.
Comment 5 harv 2015-12-20 20:26:51 UTC
I just noticed something that may be helpful. In Fedora 23, if I login using Gnome Wayland, I observe the corrupted dialog box text labels reported by me and others. However, if I login using just plain old Gnome 3 without Wayland or with Gnome Classic, the dialog box text labels are all perfectly legible and appear to not be corrupted. Thus, the issue we are experiencing may be related specifically to LibreOffice 5 on Gnome with Wayland. Hope this helps with debugging.
Comment 6 Caolán McNamara 2016-06-02 15:41:18 UTC
I fixed this downstream at the end of 2015 and merged that patch into master as well, so this should be fixed now
Comment 7 V Stuart Foote 2016-06-02 16:50:29 UTC
*** Bug 100192 has been marked as a duplicate of this bug. ***