Bug 116485 - With OpenGL the menu, tab and button backgrounds are black
Summary: With OpenGL the menu, tab and button backgrounds are black
Status: RESOLVED DUPLICATE of bug 113630
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-19 09:24 UTC by Mike Sapsard
Modified: 2018-03-21 21:10 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Screenshot of artifacts on Toshiba (29.01 KB, image/jpeg)
2018-03-19 09:26 UTC, Mike Sapsard
Details
png original screenshot of Toshiba (78.24 KB, image/png)
2018-03-19 15:28 UTC, Mike Sapsard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Sapsard 2018-03-19 09:24:00 UTC
Description:
Using the nvidia card on Toshiba laptop with OpenGL the menu, tab and button backgrounds are black. This does not happen with alternative Intel 915 card.

Artifacts also appear on Dell Inspiron 13-5378 laptop with OpenGL.

Steps to Reproduce:
1. Switch to nvidia card
2. Open LO
3. Select Tools|Options|LO|View and set Use OpenGL for all rendering.

Actual Results:  
Artifacts appear on screen

Expected Results:
No artifacts on screen


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Toshiba===========================
System:    Host: mike-SATELLITE-P850 Kernel: 4.15.2-041502-generic x86_64 (64 bit gcc: 7.2.0)
           Desktop: Cinnamon 3.6.7 (Gtk 2.24.30)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: TOSHIBA product: SATELLITE P850 v: PSPKFE-00P007EN
           Mobo: TOSHIBA model: QFKAA v: 1.00
           Bios: TOSHIBA v: 6.70 date: 02/20/2013
CPU:       Quad core Intel Core i7-3630QM (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19156
           clock speeds: max: 3400 MHz 1: 1198 MHz 2: 1231 MHz 3: 1198 MHz
           4: 1254 MHz 5: 1205 MHz 6: 1197 MHz 7: 1238 MHz 8: 1197 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           bus-ID: 00:02.0
           Card-2: NVIDIA GK107M [GeForce GT 640M] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 driver: nvidia
           Resolution: 1366x768@59.99hz
           GLX Renderer: GeForce GT 640M/PCIe/SSE2
           GLX Version: 4.6.0 NVIDIA 390.25 Direct Rendering: Yes
Toshiba===========================

Dell==============================
System:    Host: mike-Inspiron-13-5378 Kernel: 4.15.2-041502-generic x86_64 (64 bit gcc: 7.2.0)
           Desktop: Cinnamon 3.6.7 (Gtk 2.24.30)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: Dell (portable) product: Inspiron 13-5378
           Mobo: Dell model: 0P87CH v: A00
           Bios: Dell v: 1.23.3 date: 01/26/2018
CPU:       Dual core Intel Core i5-7200U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10848
           clock speeds: max: 3100 MHz 1: 716 MHz 2: 715 MHz 3: 716 MHz
           4: 700 MHz
Graphics:  Card: Intel Device 5916 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.05hz
           GLX Renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2)
           GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes
Dell==================================



User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 Mike Sapsard 2018-03-19 09:26:26 UTC
Created attachment 140700 [details]
Screenshot of artifacts on Toshiba
Comment 2 Mike Kaganski 2018-03-19 09:51:16 UTC
Please don't use JPEG for screenshots, when you intend to show UI elements and artifacts. PNG will do much better for that, and often with smaller size.
Comment 3 Mike Sapsard 2018-03-19 15:28:38 UTC
Created attachment 140715 [details]
png original screenshot of Toshiba
Comment 4 Buovjaga 2018-03-21 21:10:43 UTC
I think it's the same as bug 113630

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