Bug 93473 - Invisible text after setting a style with Radeon on Linux
Summary: Invisible text after setting a style with Radeon on Linux
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-16 21:40 UTC by Aaron Paden
Modified: 2016-03-21 20:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
a document with some text. (9.00 KB, application/vnd.oasis.opendocument.text)
2015-08-16 22:25 UTC, Aaron Paden
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Paden 2015-08-16 21:40:12 UTC
Reproducible demonstration: https://www.youtube.com/watch?v=JawUilA9J0g

Basically, setting a style seems to break writer. New text is invisible, menu elements are no longer highlighted on mouseover.

This is using a radeon r7 with mesa drivers, if that matters.
Comment 1 Joel Madero 2015-08-16 22:02:26 UTC
Please attach a document to demonstrate the issue. Setting to NEEDINFO - once you attach set to UNCONFIRMED.

In the future when reporting bugs pleas always remember the following guidelines:
1) Reproducible enumerated steps (do x, then do y, then z, observed, expected);
2) Attach a simple test case whenever possible

A Youtube video does not replace the above two guidelines. Thanks!
Comment 2 Joel Madero 2015-08-16 22:04:07 UTC
FWIW - I'm running Ubuntu 15.04 with Intel drivers, LibreOffice 5.0 and have zero problems with styles which I use extensively in my work.
Comment 3 Aaron Paden 2015-08-16 22:10:41 UTC
This is not something that is preserved by loading a document, so I don't think it's relevant. This must have something to do with the state of the application itself.

> FWIW - I'm running Ubuntu 15.04 with Intel drivers, LibreOffice 5.0 and have zero problems with styles which I use extensively in my work.

Possibly driver related, though I have no idea how I'd confirm that.
Comment 4 Joel Madero 2015-08-16 22:13:07 UTC
Attaching a document would let us see if it's actually invisible or not so it actually would help. If it shows up as regular text than it's more likely that it's a driver issue, if it shows up invisible on our machines also than it's likely something else.

Also - if you save the document, close it, then open it back up - is the text invisible still or does it show up black as expected? Instead of fighting over good bug reporting it would be nice if you just attached the simple document - worst case it's not relevant, best case it helps us triage the bug....
Comment 5 Joel Madero 2015-08-16 22:14:11 UTC
As you didn't do the simple request (which literally would take 5 seconds) I put this back in NEEDINFO and removing myself from CC as I don't have the time to fight over good bug reporting.
Comment 6 Aaron Paden 2015-08-16 22:25:26 UTC
Created attachment 117953 [details]
a document with some text.

> As you didn't do the simple request (which literally would take 5 seconds) I
put this back in NEEDINFO and removing myself from CC as I don't have the time
to fight over good bug reporting.

My intention was simply to answer your request for information.

> Also - if you save the document, close it, then open it back up - is the text
invisible still or does it show up black as expected? Instead of fighting over
good bug reporting it would be nice if you just attached the simple document -
worst case it's not relevant, best case it helps us triage the bug....

As I've already said, this isn't preserved by saving–so probably not relevant. However, I can certainly upload a document if you insist.
Comment 7 V Stuart Foote 2015-08-17 03:29:33 UTC
@Aaron,

Agree it does not appear to be simply a wayward style applying white text to white background.  The non-highlighted menu items shown in the youtube clip are telling.

Please go to Tools -> Options -> View and uncheck the "Use OpenGL for all rendering", that will get the video driver out of the way.

If that doesn't improve the graphics issue, clear your user profile.

https://wiki.documentfoundation.org/UserProfile
https://wiki.documentfoundation.org/Documentation/UserProfile#Resetting_the_User-Profile
Comment 8 Aaron Paden 2015-08-17 04:36:08 UTC
Hm. So by default, "Use OpenGL for all rendering" is unchecked. Actually, if I click on it, then ok, then go back to the options, the option shows as unchecked again, so I'm not sure if it's actually ever being turned on or off. This is on a fresh profile, and it's true also if I click "Force OpenGL even if blacklisted". So if "Use OpenGL for all rendering" is supposed to be enabled by default, I'm not sure if it is or not because I'm not sure if I can trust the checkbox.

Note that I'm using my distros package, so I'm not sure it isn't an issue with one of their config flags or something.

https://projects.archlinux.org/svntogit/packages.git/tree/trun/PKGBUILD?h=packages/libreoffice-fresh

I'm in the process of building 5.0.1.1 so I can see if this issue exists there.
Comment 9 Aaron Paden 2015-08-28 01:14:51 UTC
I can confirm that this is still an issue in the 5.0.1 release. Package still provided by Arch. I wasn't able to build Libreoffice without flags because of unused variables, and I haven't had time to figure that one out.

I can also confirm that this does not happen on the same machine on Windows.
Comment 10 Keith Curtis 2016-03-05 20:57:18 UTC
I can't repro this on Arch with Intel hardware. Presumably it's a Radeon and Linux specific issue.
Comment 11 Buovjaga 2016-03-21 20:30:45 UTC
Mesa 11.2 will be out soon. Aaron: can you test LibreOffice 5.1.1 with Mesa 11.2 after it hits?
Comment 12 Aaron Paden 2016-03-21 20:39:30 UTC
Oh, sorry, I meant to close this a few weeks ago. I can confirm that this is no longer an issue on my hardware as of at least LibreOffice 5.1.1 and Mesa 11.1.2.
Comment 13 V Stuart Foote 2016-03-21 20:41:31 UTC
we'll give it the correct WFM closure then...