Bug 104525 - Menu labels turn blank upon hovering (Win10)
Summary: Menu labels turn blank upon hovering (Win10)
Status: RESOLVED DUPLICATE of bug 104139
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.3.0.0.beta1
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-09 11:16 UTC by Pr410
Modified: 2017-01-09 10:51 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Showing the actual fault (52.65 KB, image/jpeg)
2016-12-09 11:19 UTC, Pr410
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pr410 2016-12-09 11:16:07 UTC
Description:
Field texts turn blank (black box shape), and the user can not see the main title. This happens upon moving the cursor between the main title at the top of the window (UI)

Steps to Reproduce:
1.Open writer in LibreOffice.
2.Save file.
3.Move cursor at the top of the window eg from File--edit--view--insert in back and forth motion.


Actual Results:  
1. text fields will turn into small black boxes.

Expected Results:
text fields should remain same and must be visible to the user at all time.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
Comment 1 Pr410 2016-12-09 11:19:37 UTC
Created attachment 129423 [details]
Showing the actual fault
Comment 2 Buovjaga 2016-12-11 18:17:40 UTC
Is this enabled Tools - Options - LibreOffice - View - Use OpenGL for all rendering
If yes, please copy & paste to a comment the contents of your C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 3 Pr410 2016-12-12 05:57:57 UTC
Hi Buovjaga,

Your condition doesn't apply to my case.
Comment 4 tommy27 2016-12-12 06:28:22 UTC
I don't reproduce it under Win8.1 x64 using LibO 5.4.0.0.alpha0+
Build ID: 33f5bc54aaa7fe7aa9335726e30f9c349155e04d
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-01_23:21:05
Locale: it-IT (it_IT); Calc: group

do you have the same issue with latest regular release like 5.2.3.3?
Comment 5 Pr410 2016-12-12 06:54:33 UTC
I am testing the beta1 version that has been listed at the top.
Comment 6 Pr410 2016-12-12 06:55:25 UTC
(In reply to Pr410 from comment #5)
> I am testing the beta1 version that has been listed at the top.

Using Windows 10 pro.
Comment 7 tommy27 2016-12-14 19:30:52 UTC
*** Bug 104682 has been marked as a duplicate of this bug. ***
Comment 8 tommy27 2016-12-14 19:32:56 UTC
just found a dupe, hence this is confirmed.
status -> NEW

maybe Win10 specific?
Comment 9 tommy27 2016-12-15 06:27:30 UTC
the reporter from bug 104682 said he's using Yes, Windows 10 64bit v.1607 current build 14393.576 4k display.

looks probably Win10 specific.
Comment 10 Pr410 2016-12-16 08:07:41 UTC Comment hidden (no-value)
Comment 11 tommy27 2016-12-17 06:56:28 UTC
let's raise priority.
Comment 12 Pr410 2016-12-18 11:50:28 UTC
(In reply to tommy27 from comment #11)
> let's raise priority.

Hi Tommy27
If you know how to prioritise the task, please go ahead and let me know the procedure as well.

Many thanks
Rana
Comment 13 tommy27 2016-12-18 12:09:26 UTC
I've already changed the priority.
It's the Importance field, now to "highest major".

I think it's a very important UI glitch that may affect LibO reputation among Windows 10 users... It would be important to fix it before 5.3.0 final release.
Comment 14 V Stuart Foote 2016-12-22 15:56:34 UTC
for OP, please retest with 5.3.0beta2
http://downloadarchive.documentfoundation.org/libreoffice/old/5.3.0.0.beta2/win/

or beta2+
http://dev-builds.libreoffice.org/daily/libreoffice-5-3/Win-x86_64@62-TDF/

or current master.
http://dev-builds.libreoffice.org/daily/master/

*** This bug has been marked as a duplicate of bug 104139 ***
Comment 15 rdwjdh 2016-12-22 16:33:26 UTC
Fixed
Comment 16 Pr410 2017-01-09 10:51:01 UTC
Hi guys,
I was away, I hope you all had a great break too. 
Glad to know that our issue has been fixed. If anyone working on anything new let know.