Question

0

Chrome not working after upgrading to Ubuntu 22.04

rated 0 times [ 0] [ 0] / answers: 1 / hits: 5320 / 3 Years ago, sat, october 23, 2021, 10:34:00

I upgraded to the new LTS Ubuntu 22.04. Since then Google Chrome, when opened, doesn't load any pages and eventually gives the warning about the page becoming unresponsive (even when loading the blank tab!).

I have tried deleting my profile directory, as well as launching in incognito to see if it was a plugin, but both cases resulted in the same behaviour.

I have removed and reinstalled Chrome, as well as restarting my machine a number of times.

I have the following enabled in my ppa list:

http://dl.google.com/linux/chrome/deb/

Running sudo apt update && sudo apt upgrade tells me everything is up to date.

When launching from the command line I get the following error

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

Interestingly, Chromium seems to work fine.

I have read the following similar questions, but none of them have provided me with a way forward:

Google chrome not opening in Ubuntu 22.04 LTS

va_getDriverName() failed with unknown (though my vainfo returns normal results AFAICT)

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

antoccasiona

Add To Favorites

Follow

Total Points: 430

Total Questions: 127

Total Answers: 131

Location: Netherlands

Member since Sat, Jun 26, 2021

3 Years ago

antoccasiona questions

1 org.bluez.Error.AuthenticationTimeout; org.bluez.Error.Failed br-connection-unknown

Tue, Mar 8, 22, 09:39, 2 Years ago

1 NTFS hard drive is read only

Sat, Sep 24, 22, 09:39, 2 Years ago

1 dbus calls to gnome shell don't work under Ubuntu 22.04

Sun, Jan 15, 23, 11:08, 1 Year ago

1 HP laptop: Ubuntu install and live disk failed: pcie trouble: fixed

Sat, Aug 27, 22, 18:13, 2 Years ago

1 How to batch rename sequentially prefixed numbers to new sequential prefixes via terminal?

Sat, Feb 25, 23, 11:04, 1 Year ago

View All

answered 3 Years ago housecoarmer · Accepted Answer

Are you on Wayland or X11? I've seen this error message occur when libva fails to connect to wayland.

You could try switching to x11, if you are on wayland: On your log in screen, start typing your password, and a settings icon shows in bottom right. There you can select an x11 session.

To further debug, you can also try:

$ sudo apt install vainfo

$ vainfo --display wayland

$ vainfo --display x11