Google Chrome 79.0.3945.16 beta Fedora 5.2.18-200.fc30.x86_64
% google-chrome [2301:2301:1104/131821.292582:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. [2301:2301:1104/131821.982525:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked. [2301:2301:1104/131821.982735:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected. ....
Installed 11/01
Any thoughts?
On 11/5/19 5:30 AM, Geoffrey Leach wrote:
Google Chrome 79.0.3945.16 beta Fedora 5.2.18-200.fc30.x86_64
% google-chrome [2301:2301:1104/131821.292582:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. [2301:2301:1104/131821.982525:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked. [2301:2301:1104/131821.982735:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected. ....
Installed 11/01
Any thoughts?
Works fine here in a VM running KDE.
[egreshko@f31bk ~]$ rpm -q google-chrome-beta google-chrome-beta-79.0.3945.16-1.x86_64 [egreshko@f31bk ~]$ uname -r 5.3.6-300.fc31.x86_64
You need to provide a bit more about your environment.
Running Gome/Wayland? You video HW and driver?
On Tue, 5 Nov 2019 09:55:09 +0800 Ed Greshko ed.greshko@greshko.com wrote:
On 11/5/19 5:30 AM, Geoffrey Leach wrote:
Google Chrome 79.0.3945.16 beta Fedora 5.2.18-200.fc30.x86_64
% google-chrome [2301:2301:1104/131821.292582:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. [2301:2301:1104/131821.982525:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked. [2301:2301:1104/131821.982735:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected. ....
Installed 11/01
Any thoughts?
Works fine here in a VM running KDE.
[egreshko@f31bk ~]$ rpm -q google-chrome-beta google-chrome-beta-79.0.3945.16-1.x86_64 [egreshko@f31bk ~]$ uname -r 5.3.6-300.fc31.x86_64
You need to provide a bit more about your environment.
Running Gome/Wayland? You video HW and driver?
No Gome/Wayland
Video is pretty vanilla. Here's what lshw has to say: *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f6400000-f67fffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
The driver is whatever Fedora 30 is providing these days.
On 11/5/19 11:21 AM, Geoffrey Leach wrote:
On Tue, 5 Nov 2019 09:55:09 +0800 Ed Greshko ed.greshko@greshko.com wrote:
On 11/5/19 5:30 AM, Geoffrey Leach wrote:
Google Chrome 79.0.3945.16 beta Fedora 5.2.18-200.fc30.x86_64
% google-chrome [2301:2301:1104/131821.292582:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. [2301:2301:1104/131821.982525:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked. [2301:2301:1104/131821.982735:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected. ....
Installed 11/01
Any thoughts?
Works fine here in a VM running KDE.
[egreshko@f31bk ~]$ rpm -q google-chrome-beta google-chrome-beta-79.0.3945.16-1.x86_64 [egreshko@f31bk ~]$ uname -r 5.3.6-300.fc31.x86_64
You need to provide a bit more about your environment.
Running Gome/Wayland? You video HW and driver?
No Gome/Wayland
Video is pretty vanilla. Here's what lshw has to say: *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f6400000-f67fffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
The driver is whatever Fedora 30 is providing these days.
Could you supply the output of
inxi -Gxx
On Tue, 5 Nov 2019 16:40:31 +0800 Ed Greshko ed.greshko@greshko.com wrote:
On 11/5/19 11:21 AM, Geoffrey Leach wrote:
On Tue, 5 Nov 2019 09:55:09 +0800 Ed Greshko ed.greshko@greshko.com wrote:
On 11/5/19 5:30 AM, Geoffrey Leach wrote:
Google Chrome 79.0.3945.16 beta Fedora 5.2.18-200.fc30.x86_64
% google-chrome [2301:2301:1104/131821.292582:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. [2301:2301:1104/131821.982525:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked. [2301:2301:1104/131821.982735:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected. ....
Installed 11/01
Any thoughts?
Works fine here in a VM running KDE.
[egreshko@f31bk ~]$ rpm -q google-chrome-beta google-chrome-beta-79.0.3945.16-1.x86_64 [egreshko@f31bk ~]$ uname -r 5.3.6-300.fc31.x86_64
You need to provide a bit more about your environment.
Running Gome/Wayland? You video HW and driver?
No Gome/Wayland
Video is pretty vanilla. Here's what lshw has to say: *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f6400000-f67fffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
The driver is whatever Fedora 30 is providing these days.
Could you supply the output of
inxi -Gxx
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 Device-2: NVIDIA GF106M [GeForce GT 555M] vendor: CLEVO/KAPOK driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0dce Display: x11 server: Fedora Project X.org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.1.8
On 11/5/19 10:00 PM, Geoffrey Leach wrote:
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 Device-2: NVIDIA GF106M [GeForce GT 555M] vendor: CLEVO/KAPOK driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0dce Display: x11 server: Fedora Project X.org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.1.8
Your graphics controller has both Intel and nVidia integrated.
A guess on my part, but there could be some issue with that. Could you try disabling each in turn in the BIOS so your system only has access to one? See if that makes a difference.
I'd try disabling the Intel first.
On Wed, 6 Nov 2019 05:01:35 +0800 Ed Greshko ed.greshko@greshko.com wrote:
On 11/5/19 10:00 PM, Geoffrey Leach wrote:
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 Device-2: NVIDIA GF106M [GeForce GT 555M] vendor: CLEVO/KAPOK driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0dce Display: x11 server: Fedora Project X.org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.1.8
Your graphics controller has both Intel and nVidia integrated.
A guess on my part, but there could be some issue with that. Could you try disabling each in turn in the BIOS so your system only has access to one? See if that makes a difference.
I'd try disabling the Intel first.
Tinkering with my driver is (alas) beyond my skill level.
However, I do have a couple of interesting items, FWIW.
The chrome website main page is only partially rendered by Firefox. It is, however, correctly rendered by Brave. From that page I was able to obtain the rpm for the stable version, which works fine.
On 11/7/19 1:06 PM, Geoffrey Leach wrote:
Tinkering with my driver is (alas) beyond my skill level.
I'm not suggesting you tinker with your driver.
When you boot your system there normally is the option to use ESC or some key combination to get to a screen where you can do things such as set the Motherboard Time, set boot device order, and other features.
One option, normally, on systems with integrated Intel and nVidia graphics is to disable one or the other.
However, I do have a couple of interesting items, FWIW.
The chrome website main page is only partially rendered by Firefox. It is, however, correctly rendered by Brave. From that page I was able to obtain the rpm for the stable version, which works fine.
OK. I thought your interest was with the Beta.
FWIW, I have no trouble using FF to display the Google Chrome website.