Score:2

Chrome on Ubuntu 22.04.1 LTS takes 30+ seconds to launch and has weird display issues while launching

sk flag

When launching Chrome on Ubuntu 22.04.1 LTS, it takes 30+ seconds to launch properly. It will create a window almost immediately but has weird rendering issues (the window is invisible but if you drag another window across it will create "trails" of the window that was dragged across, like it used to on older versions of windows when something would crash). If I take a screen recording on the laptop it just shows a black screen the whole time until it renders properly. I can still re-size and move the window around while its in this state.

Edit to add: If I open a new window while chrome is still running it opens fine, but if I close Chrome and re-open it, it goes through the whole loading issue.

So far I have tried disabling GPU Rasterization in Chrome settings as well as hardware acceleration. If I turn these off Chrome will never render properly. I have also tried checking for updates, un-installing and re-installing Chrome. From what I have read so far it seems like it might be an issue with the Nvidia card/drivers.

I'm running it on a dual-booted Dell XPS-15 1920, with 32 GB ram, i7-12700H, and an Nvidia 3050 Ti mobile.

Anyone have suggestions before I just try re-installing Ubuntu?

Screen Recording

Video of screen

Score:1
ph flag

I had exactly the same issue! Solved it by downgrading Nvidia drivers to version 510. Hope it helps!

Martin avatar
sk flag
I'll give this a shot and let you know how it goes
Martin avatar
sk flag
This worked thank you! For anyone else checking this out I followed the steps [here](https://www.reddit.com/r/pop_os/comments/r1ofn7/how_do_you_downgrade_nvidia_driver/) 'sudo apt-get purge '*nvidia*'' 'sudo apt install nvidia-driver-510' They also recommended backing up your system for doing this. Edit: the mini-Markdown is messing with the code so make sure to check the link for the proper code
Noky avatar
sa flag
I have the same machine and had the same problem. After several tests, I determined that the "open" version of the Nvidia 525 driver was the underlying issue. Switching to the "proprietary" 525 driver ultimately solved my problem. Versions 510 and 515 (proprietary) worked as well.
Score:0
cm flag

I reread your post - sounds like you already tried this.... It had worked for me previously

Have you checked to see if Chrome is using "Use hardware acceleration when available"? Try disabling that setting the the Chrome settings.

Instructions: Click the stacked 3 dots on the top right Chrome. Select "Settings". Select "System". Change "Use hardware acceleration when available" slider to off. Relaunch Chrome.

Martin avatar
sk flag
Thank you but yeah that was one of the first recommendations I got, it allows me to launch chrome but I still have the issue with Chrome taking 30+ seconds to launch
Score:0
ke flag

I had the same issue after upgrading to Jammy 22.04 from Focal 20.04, on Google Chrome 114.

It looks like turning Off 'Use hardware acceleration when available' in Settings --> System, relaunching Google Chrome, then turning On again 'Use hardware acceleration when available', did the trick.

I was already on the same nVidia driver 535 in Focal 20.04. So, something went badly after the Ubuntu upgrade. I believe I forced it to ditch the settings and renew them with the same driver, albeit for a different Ubuntu system software.

Score:0
bi flag

I had the same exact same symptoms, and this thread made me realize it was a GPU issue. When I ran lspci it showed that my integrated graphics were being used instead of the Nvidia card.

I used the stock Software & Updates application, went to the Additional Drivers tab and installed the NVIDIA driver metapackage from nvidia-driver-530(proprietary,tested).

After I restarted my computer Chrome booted instantly and there have been no further issues.

sceenshot of Software & Updates application

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.