Bug 142131 - The menus are empty when the window is too large
Summary: The menus are empty when the window is too large
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Skia
  Show dependency treegraph
Reported: 2021-05-06 15:19 UTC by Olivier DENIZOT
Modified: 2021-12-12 04:21 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Good and bad display (120.61 KB, image/png)
2021-05-06 15:19 UTC, Olivier DENIZOT
~3100px Writer w nVidia K2000 GPU (145.37 KB, image/png)
2021-05-14 23:53 UTC, V Stuart Foote

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier DENIZOT 2021-05-06 15:19:52 UTC
Created attachment 171705 [details]
Good and bad display

Hello everybody.

I noticed that since version 7.1, I have problems displaying empty menus (the About window is also empty). If I reduce the width of the window, the display becomes correct again. A window of 1472 pixels works whereas for 1535 pixels, there are refresh defects and no display of menus.

I am using a PC running Windows 10 Pro version 20H2, Intel Q9650 processor, 8GB of RAM, Nvidia K620 card, 2560x1440 screen.


Comment 1 m_a_riosv 2021-05-09 15:42:53 UTC
Please don't set up your own reports as 'new' some else must reproduce the issue.

Try modifying the options in Menu/Tools/Options/LibreOffice/View - Output graphics.

If it doesn't work Please test with a clean profile, Menu/Help/Restart in Safe Mode
Comment 2 Olivier DENIZOT 2021-05-09 22:02:49 UTC
Hello Miguel-Angel.

Thanks for your reply and your help.

I went to the menu you quoted to me. By disabling Skia and using hardware acceleration and smoothing, the display works correctly. The version of the nVidia driver for my Quadro K620 was 461.09 (

I made an update to 462.31 ( By reactivating Skia, the display still does not work.

By restarting in safe mode, Skia is deactivated and the display works correctly.

Comment 3 m_a_riosv 2021-05-10 08:27:36 UTC
Looks something similar to https://bugs.documentfoundation.org/show_bug.cgi?id=135370#c21

Let's see if @Luboš has something about this.
Comment 4 V Stuart Foote 2021-05-14 23:43:52 UTC
For any Skia deny list handling we would need to know the driver details for your Vulkan driver details, not the packaging details.

A utility program like GLview [1] will have the Skia Vulkan API & Driver details.

If Vulkan does not abort out, the skia.log in the user profile will include the device and driver details.

For example my daily driver has a nVidia Quadro K2000 (slightly older than your K620) with the nVidia 461.92 GeForce Drivers ( DCH pkg)--but its Vulkan API compliance is 1.2.155, and its nVidia Vulkan driver version is 461.368.0

The deny list has to work with these internal values.

[1] http://www.realtech-vr.com/home/glview
Comment 5 V Stuart Foote 2021-05-14 23:53:10 UTC
Created attachment 172011 [details]
~3100px Writer w nVidia K2000 GPU

no issue with menus ~3100px width Writer session on K2000 with recent Vulkan drivers

Version: (x64) / LibreOffice Community
Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 6 QA Administrators 2021-11-11 04:15:14 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2021-12-12 04:21:21 UTC
Dear Olivier DENIZOT,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team