Bug 1087903 - Google Chrome and Chromium show empty (transparent) window with NVidia drivers
Google Chrome and Chromium show empty (transparent) window with NVidia drivers
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: X11 3rd Party Driver
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
Stefan Dirsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-03 13:54 UTC by Stefan Hundhammer
Modified: 2018-04-03 14:47 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Output of rpm -qa | sort (149.82 KB, text/plain)
2018-04-03 13:54 UTC, Stefan Hundhammer
Details
Output of "xdpyinfo" (44.89 KB, text/plain)
2018-04-03 14:02 UTC, Stefan Hundhammer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hundhammer 2018-04-03 13:54:23 UTC
Created attachment 765784 [details]
Output of    rpm -qa | sort

With the recent TW update, both Google Chrome and Chromium don't render anything on my machine; I only get a transparent window, not even window manager borders.

The window appears to get the keyboard focus, it shows up in the (Xfce) task list, and I can use Alt-Tab to cycle between it and the other windows on my desktop as usual.

In some regions of this transparent window I even can create a rectangular selection with the mouse; I can see the selection rectangle, but nothing else. When I try to make a screenshot, the screenshot also doesn't contain any content (other than the windows below it and the desktop background).

All this worked well all the time for over two years, but something in the recent TW update broke it. I am not sure if it's on the NVidia driver side or on the Chrome/Chromium/WebKit side; I suspect NVidia.

Versions:

Tumbleweed from 2018-04-01

[shundhammer @ morgul] ~ % rpm -qa | grep nvidia

nvidia-glG04-390.42-11.1.x86_64
nvidia-computeG04-390.42-11.1.x86_64
x11-video-nvidiaG04-390.42-11.1.x86_64
nvidia-gfxG04-kmp-default-390.42_k4.15.13_1-11.4.x86_64

[shundhammer @ morgul] ~ % rpm -qa | grep chrom
google-chrome-stable-65.0.3325.181-1.x86_64
chromium-65.0.3325.181-1.2.x86_64
chrome-gnome-shell-10.1-1.1.x86_64

[shundhammer @ morgul] ~ % uname -a

Linux morgul 4.15.13-1-default #1 SMP PREEMPT Sun Mar 25 08:34:58 UTC 2018 (950fc49) x86_64 x86_64 x86_64 GNU/Linux

[shundhammer @ morgul] ~ % cat /etc/os-release

NAME="openSUSE Tumbleweed"
# VERSION="20180401"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="20180401"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20180401"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
Comment 1 Stefan Hundhammer 2018-04-03 13:58:58 UTC
When I start it on the command line, it shows this:

[shundhammer @ morgul] ~ % google-chrome
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[24200:24200:0403/155530.139403:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable.
[24200:24200:0403/155530.139431:ERROR:gpu_info_collector.cc(62)] gl::GLContext::MakeCurrent() failed


When I terminate it via the Xfce task list, I also get this:

[24136:24173:0403/155551.926321:ERROR:browser_gpu_channel_host_factory.cc(120)] Failed to launch GPU process.

Same with chromium.
Comment 2 Stefan Hundhammer 2018-04-03 14:01:35 UTC
Not sure if this is related at all, but "glxgears" just shows this error:

[shundhammer @ morgul] ~ % glxgears
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  35
  Current serial number in output stream:  37
Comment 3 Stefan Hundhammer 2018-04-03 14:02:32 UTC
Created attachment 765786 [details]
Output of "xdpyinfo"
Comment 4 Stefan Hundhammer 2018-04-03 14:02:52 UTC
[shundhammer @ morgul] ~ % glxinfo 
name of display: :0.0
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  50
  Current serial number in output stream:  49
Comment 5 Stefan Dirsch 2018-04-03 14:05:03 UTC
Looks like a broken system. Could I have access to morgul, please?
Comment 6 Stefan Hundhammer 2018-04-03 14:05:53 UTC
I also tried google-chrome-beta (V 66.0.3359.66-1) with the same results.
Comment 8 Stefan Dirsch 2018-04-03 14:47:42 UTC
libGL.so.1 was referring to libGL.so.1.2.0, an ancient Mesa libGL (not being owned by any package any longer) instead of libglvnd's libGL.so.1.0.0 wrapper. Manually fixed on the system. IIRC this was an interim problem for TW users. Last time I stumbled across this was about 1 year ago I believe. CLosing as fixed.