Hi I've had all 3 of the chrome/chromium variants go shaky then lockup 100% cpu all 4 @eek only option to close via task manager. It's been same for last 2 rapid releases I assumed the 2md would fix it wrong. I have removed all of the pkg's cleared out deleted .config's .cache's for clean slate, then disabled the refresh as per forum posts. Still the same most triggered by adding bookmark and choose locatoin. disabled bookmark refresh ala forum still broken.

Then got 20 mins with chromium-ungoogled working tried to go to site I had open on firefox and it came up with dns/internet/your connection's broken page. Hmm odd as identical url works fine in firefox. Over course of couple hours I got chromium and google-chrome to work long enough to get the identical error in all 3. Site being blocked internally by dev's.

Goodbye chromium/chromium-ungoogled/google-chrome been fun/anoying/hardwork/frustraighting. But trying to control were I legally visit on web aint happening.

and firefox has magic button in about:config to swap to alsa or jack output, and it works like a charm.

And firefox has the easiest

This could still be a problem on your local end instead of in Chrome/Chromium. What is this URL which according to you is being blocked by Google's developers? I'd like to try that URL in my own browser to compare results.

Also I got curious about your remark about that ALSA/JACK switch in Firefox. I have Jack Audio Connection Kit installed here and simply pipe all ALSA audio into a JACK sink which works transparently for all applications. But I opened "about:config" in Firefox out of curiosity. I do not find any switch in there that lets me toggle its output between ALSA and JACK. Did you install a Firefox extension perhaps?

Hi if you type about:config and drop that line in search bar then add string type in alsa or jack. I've not tested jack yet. close about:config restart and firefox will use your default alsa pcm. in /etc/asound.conf or .asoundrc for user only. I am pulseaudio/pipewire/wireplumber free.
so if all you have is pulse devices listed it will use them I suspect you've not.

https://bflix.gg is the url works on chrome in phone but not on linux googly browser or ungoogly. or on chrom on a windows laptop but is loading on firefox.


media.cubeb.backend

No issues at all with https://bflix.gg on AlienBob's latest chromium-ungoogled (121.0.6167.139). Watched a few seconds of a tv series episode. CPU load 15-20 percent.

Hmm how very odd I wonder if I'd not turned off the https dns, so it was using one of the services as cloudflare/opendns can treat it as an insecure site. The biggest problem was the shacking then lock-up's I know there has been issues with nouveau driver in 6,7dev and is a lot better in 6.8-rc1-rt1 kernel. I was on nvidia driver but gave up as I got it building on the full rt kernel but then it kept crashing with stack-traces scheduling while atomic. Ill reinstall chromium-ungoogled and run it from console.
I've watched 3 films using the alsa switch and sound was good running apulse chromium-ungoogled, but sound quality is even better on firefox. Sadly the video playback using 1080p with nvidia driver with 37" 1080p hd tv was astounding. Nouveau is a good 60% behind in clarity and detail playing the same file with just driver swap. It's not nouveau team has done amazing stuff I've got my fingers crossed that the gtx660 ti gets the gsp firmware blob then nouveau would be on pare with nvidia for video. Nouveau driver beats nvidia on clocking I use pstate switch via boot option and get 300mhz higher gpu clock without overclocking as nvidia wont give full performance even withcoolbits and settings it sticks at 980mhz even though in windows same card runs at 1300.

From these facts I conclude that using your cellular connection, Chrome on your phone) works just fine. But all your other connections use your home LAN and its connection to your ISP. And there it does not work: not Chrome on Windows (which is always the latest version), not Chrome, Chromium or Ungoogled-chromium on Slackware.
As I said earlier: the problem seems to be on your local end, more specifically in the way your home is connected to the Internet. Are you using the wrong DNS IP addresses? Are you hiding behind a VPN? Do you apply some kind of content filtering on your gateway (spam/virus removal, blocking of certain sites)? All kinds of things which you unconsciously control can break your Internet.

It's an issue with mesa/dri I use current mesa-24.0.0, I tried Portable Linux 64-bit 120.0.6099.129-1 and that runs fine as long as I use this startup option to cure an unrealated issue. so it's the 121.0.6167.139 version with the problem. i'll tst previous mesa release as it changed only a few days ago. my url worked on portable line version. I know it's not home network issue as it loads in firefox/konqourer and opera. And I run unbound dns server on this box querying to the internet root server's.

Been enjoying firefox after not useing it for 5 or 6 years. I've never had issues with home internet in the 22 years :-). I've been using Slackware even on 56k dialup modems unlike it MS counterpart and is 100% reliable and 1/3 faster.

Hi it's a mesa-24.0.0 issue not a chromium-ungoogled/chromium/google-chrome all version-121.0.6167.139-x96_64 as this.
As removing mesa-24.0.0 that version and using mesa-23.3.4.
When I searched using error "ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2)" I found the same error msg on a non webbrowser application as a github issue for Electron Forge https://github.com/electron/electron/issues/41082.
From what I've read mesa is not exporting to the correct graphics driver built into it.
media-driver GPU VAAPI. $ DRI_PRIME=1 LIBVA_DRIBER_NAME= should export to the right driver for the system ie intel/amd/nouveau. No doubt a commit to mesa that broke it not the first mesa has caused this kind of problem and wont be the last.

I've just emailed Pat the info and my fix of rolling back to mesa-23.3.4.

I have the same glitching problem with google-chrome and would like to try the mesa rollback solution but where can I obtain the previous version package?

EDIT: I built & installed my own mesa-23.3.4 using the existing SlackBuild but it didn't help.

chris

https://slackware.uk/cumulative/

1 members found this post helpful.

Thanks for that.

I tried the previous mesa-23.3.4 found there but, just like the version I built myself, it provided no better result for running google-chrome here.

chris

I had gliches issues too but not the CPU problems, I fixed it by disabling the hardware acceleration in the Settings > System. I also experimented these glitches in Thorium and Discord, (SBo versions). I'm pretty sure it comes from my old hardware.

Chromium ungoogled Version 121.0.6167.139 Works fine on https://bflix.gg
I have all Intel with Intel TigerLake-LP GT2 [Iris Xe Graphics] and mesa 24.0.0
after 45 min cpu is at 22.6%