Bug 113109 - GPU acceleration mask Menus like "File-Edit-Display-..."
Summary: GPU acceleration mask Menus like "File-Edit-Display-..."
Status: RESOLVED DUPLICATE of bug 107764
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.4.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-13 22:36 UTC by Personnel
Modified: 2018-05-30 17:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Personnel 2017-10-13 22:36:44 UTC
Description:
Please, DELETE the Hardware Acceleration ENABLE per default.
Leave it DISABLE per default at "normal" installation.

On SAFE MODE option, add a check box to ENABLE or DISABLE the normal start of LibreOffice WITH ou WITHOUT the GPU acceleration (OpenGL acceleration) ... and ADD a question to allow the user to reply of a bug of the Menus of the TOP of the screen or a truncation of the bottom bar (zoom, page, sheets).

I am both problems with brands news towers (Fujitsu & HP) and Win10 Pro 64Bits with :
- Intel GMA integrated chipset solution
- Nvidia add PCI-express card

Windows Update done and Drivers for GPU installed from the builder or from the official main site (Intel or NVidia).

BUG found in 45min with 3 install. of LibreOffice (32bits or 64bits Installer + JAVA in 32bits or 64bits) + rollover to 5.3.6 instead of 5.4.2.

Steps to Reproduce:
Top menus are missing (File, Edit, Display ...).
Bottom of the bar are truncated (pages, zoom, sheets).

Actual Results:  
activate Hardware acceleration (GPU) in LibreOffice setting > Display > 3x Check Box on the right.

Expected Results:
Top Menus are not displayed (but bars menus can be forced by ALT+F and then, left arrow).


Reproducible: Always

User Profile Reset: Yes (delete installation + delete local setting folder of LibreOffice in User Folder)

Additional Info:
Delete LibreOffice Folder (Program File + User Folder/Local Setting) don't solve the issue.


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Comment 1 Personnel 2017-10-13 22:46:31 UTC
i3-6100 integrated Intel GMA GPU acceleration.
Nvidia GTX 770 GPU acceleration.
Comment 2 V Stuart Foote 2017-10-14 03:38:40 UTC
(In reply to Personnel from comment #0)
> Description:
> Please, DELETE the Hardware Acceleration ENABLE per default.
> Leave it DISABLE per default at "normal" installation.
> ...

This looks to be duplicate of bug 107764, but before closing please recheck.

Note, there are 3 possible rendering modes (controlled with check-boxes on Tools -> Options -> View: Graphics Output):

1. CPU only

2. Hardware accelerated (can be either integrated GPU or discrete GPU, just not done by the CPU).

3. OpenGL accelerated (i.e. not done by CPU _and_ uses a different set of graphics libraries/drivers for the GPU)

Anti-aliasing can be enabled or disabled for each of these modes with its check-box.

1 & 2 show as "default" rendering, while 3 shows as "GL" rendering in the Help -> About dialog.

On Windows builds, OpenGL acceleration is enabled by default as is anti-alaising.

OpenGL support will be tested on launch (a blacklist criteria, and simple rendering test) if it fails it will be disabled and "default" hardware acceleration with GPU used. 

If OpenGL passes and is enabled--the Use hardware acceleration checkbox will be grayed out/disabled.

So, please recheck:

Is clipping-- of the menu bar (File, Tools, Help, etc.) at top edge, or the status bar (Page, Style, Language, Zoom, etc.) on the bottom edge--happening when OpenGL rendering is enabled?

Is it correct with CPU only or Hardware accelerated "default" rendering? 

If so--that is the same as bug 107764
Comment 3 QA Administrators 2018-05-02 15:47:01 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-05-30 16:47:48 UTC Comment hidden (obsolete)
Comment 5 V Stuart Foote 2018-05-30 17:07:17 UTC

*** This bug has been marked as a duplicate of bug 107764 ***