Just installed version 5.1.2.2(x64). I have a dual monitor system running Win7_64 with a NVidia GeForce GTX560 video card. When I run "writer" ( noticed this in Calc as well but those are the only two I've tried), if I move the writer window from the primary display (the one with windows task bar) to the secondary display and try to access any menu (either menu bar or popup) the text and graphics within the menu disappear/reappear as I move the mouse over the menu items. When it disappears, I still see the grey background of the menu but all decorations (text and separators) disappear and it is very hard to stop on a specific menu item to click on it without the text, but if I release mouse button on a specific X/Y location within the menu the function that would normally be displayed at that location IS executed. So it seems like a painting issue and not a menuitem clicked issue. Also if I hover over an item that would create a submenu, the submenu initially displays but when I start moving towards it the submenu does the same thing. If I move "writer" back to the primary display the problem does not seem to occur. I recently upgraded my machine from Vista 32bit and version libreoffice 4.1.3 which combination worked on the same hardware. When still on Vista 32bit I tried version 5.0.5 but had sever display problems on both monitors so I went back to 4.1.3. I looked around for a 64bit version of Libreoffice 4.1.3 to try on my win7_64 system ( or any 4.x 64bit version) but could not find one to try. For now I'll only use primary display ( or I may try the 32bit version of 4.1.3)... Just thought you'd want to know.
please post a screenshot
What was the status of OpenGL rendering on your system? Tools -> Options -> View: Use OpenGl for all rendering (on restart) Should probably be disabled given your GPU and Widncows 7 and drivers, but if not the issues described can manifest with OpenGL rendering. P.S. 64-bit builds for Windows only arrived with the 5.0.0 release.
Created attachment 124704 [details] Screen shot of menu being displayed incorrectly on secondary monitor
I checked on the state of : Tools -> Options -> View: Use OpenGl for all rendering (on restart) Currently it is "checked/selected", if I "uncheck/disable" that option then the menus seem to display correctly (if somewhat more sluggish). Not sure why this should display fine on the primary monitor and not the secondary since the same GPU would be involved. But for now I'll just run with with OpenGL disabled.
OK then, not unexpected. One last thing before we close this WFM, please post the text from your C:\Users\<yourusername>\AppData\Roaming\LibreOffice 4\cache\opengl_device.log we use this information from troubled systems to blacklist non-functioning OpenGL implementations.
Created attachment 124709 [details] opengl_device.log Requested opengl_device.log file.
Thanks for your assist... Also is there a link to the blacklist so I can check potential cards before I purchase? Tried searching google (libreoffice opengl blacklist) but all I got were links to other bugs or unrelated items.
@Richard, The driver string is passing the balcklist--which is why 5.1.2.2 is opening for you with OpenGL rendering enabled. http://opengrok.libreoffice.org/xref/core/vcl/opengl/opengl_blacklist_windows.xml which cuts off with the nVidia 353.62 driver release. You can see we don't currently track GPU/driver combos for black-listing OpenGL support on Windows (its worse on Linux) and just set the threshold by driver. If you grab the OpenGL Extension Viewer utility from RealTech-VR http://www.realtech-vr.com/glview/ you can test and post up the summary of just what your GPU/driver pairing support, especially if you are getting 100% 4.4 support on your GTX560 based card.
Created attachment 124710 [details] Opengl Viewer report Capture of report information from the OpenGL Extensions viewer. Note that my card is listed as 100% compatible up through 4.4. The only items listed as not fully compatible are 4.5 (90%) and ARB 2015 (30%). If there is anything else I can provide let me know.... As a Firmware Engr. myself I know how helpful any "good" :-) information is.
Given support level for the GPU/driver mix, to me this is a legitimate bug. But testing the mix to confirm could prove a challenge--Windows 7 and a GTX 560 GPU. I've moved my nVidia systems to Windows 8.1 and 10--dual monitor but I don't get the same issue. Adding to the OpenGL meta issue bug 93529 for visibility, one of the devs working on the numerous OpenGL glitches may get back to you with specific questions. Meanwhile if you need to use the second monitor, disable OpenGL or just try to stay on the primary display ;-)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 120075 has been marked as a duplicate of this bug. ***
Dear Richard, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 127929 has been marked as a duplicate of this bug. ***
Richard, aksrmartin, christine Please test with daily master LO that is now 6.4+. YOu can get it from https://dev-builds.libreoffice.org/daily/master/. It will not interfere with you stable working LO.
I tried the libo-master64_2019-09-30_09.18.03_LibreOfficeDev_6.4.0.0.alpha0_Win_x64.msi If OpenGL is selected and the spreadsheet is open in my 2nd monitor, then the Delete dialog box has no display of controls. They still work, however, when I blindly clicked on where the OK button is. When the spreadsheet is open in my 1st monitor, then the Delete dialog displays controls correctly. If OpenGL is not selected, then the Delete dialog shows controls in both monitors. I am running Windows 10 64 bit with AMD Radeon HD 5700 graphics controller. Libre office Calc still has a problem with OpenGL. I don't know what OpenOffice Calc uses, exactly, because in thatTools / Options / View menu it doesn't explicitly say "OpenGL". The menu says "Use Hardware Acceleration". Whether I check this or not makes no difference. Of course, it also doesn't display a Delete dialog, so that's probably no real comparison to Libre Office. Anyway, my test shows a problem with OpenGL and the new Libre Office Calc, same as with older versions of Libre Office. The contents of my C:\Users\<yourusername>\AppData\Roaming\LibreOffice\ 4\cache\opengl_device.log: DriverVersion: 15.200.1062.1004 DriverDate: 8-3-2015 DeviceID: PCI\VEN_1002&DEV_68BE&SUBSYS_22871787&REV_00 AdapterVendorID: 0x1002 AdapterDeviceID: 0x68be AdapterSubsysID: 0x22871787 DeviceKey: System\CurrentControlSet\Control\Video\{FE1EFCE3-D597-4189-9900-A5CE76BF007F}\0000 DeviceString: AMD Radeon HD 5700 Series
(In reply to aksrmartin from comment #16) > I tried the > libo-master64_2019-09-30_09.18.03_LibreOfficeDev_6.4.0.0.alpha0_Win_x64.msi > Thanks for retesting. > If OpenGL is selected and the spreadsheet is open in my 2nd monitor, then > the Delete dialog box has no display of controls. They still work, however, > when I blindly clicked on where the OK button is. When the spreadsheet is > open in my 1st monitor, then the Delete dialog displays controls correctly. > Even on current GPUs with current Windows 10 WMMD GPU drivers we do get occasional OpenGL rendering glitches--lately around the RenderContext() double buffering. > If OpenGL is not selected, then the Delete dialog shows controls in both > monitors. Good, the default GDI Hardware Acceleration for the GPU is functioning--you won't have to fall back to even slower CPU only rendering. > I am running Windows 10 64 bit with AMD Radeon HD 5700 graphics controller. > No current driver support for a Radeon HD 5700, AMD abandoned it as legacy Catalyst device. > Libre office Calc still has a problem with OpenGL. I don't know what > OpenOffice Calc uses, exactly, because in thatTools / Options / View menu it > doesn't explicitly say "OpenGL". The menu says "Use Hardware Acceleration". > Whether I check this or not makes no difference. Of course, it also doesn't > display a Delete dialog, so that's probably no real comparison to Libre > Office. Apache OpenOffice has not implemented any support for OpenGL. > > Anyway, my test shows a problem with OpenGL and the new Libre Office Calc, > same as with older versions of Libre Office. > > The contents of my C:\Users\<yourusername>\AppData\Roaming\LibreOffice\ > 4\cache\opengl_device.log: > > DriverVersion: 15.200.1062.1004 > DriverDate: 8-3-2015 > DeviceID: PCI\VEN_1002&DEV_68BE&SUBSYS_22871787&REV_00 > AdapterVendorID: 0x1002 > AdapterDeviceID: 0x68be > AdapterSubsysID: 0x22871787 > DeviceKey: > System\CurrentControlSet\Control\Video\{FE1EFCE3-D597-4189-9900- > A5CE76BF007F}\0000 > DeviceString: AMD Radeon HD 5700 Series That is old unsupported AMD hardware and their drivers are not going to be the most functional on Windows 10 which with that AMD GPU and driver should probably be black listed. Otherwise if you can't upgrade the Graphics card, might be best to disable OpenGL in your profile.
As Skia with Vulkan will replace OpenGL UI rendering on all platforms, it does not make sense to keep OpenGL UI reports open. Details about Skia: https://www.collaboraoffice.com/success-story/implementing-vulkan-capable-libreoffice-user-interface-using-the-skia-library/