Google messages on web fails in linux

[Prexy]

this has occurred in the last few days. I use Google Messages. I keep a tab open to receive messages but the page crashes as soon as it loads. There is an “Aw, Snap!” message and a help page to resolve the issue but none of it works. I have the same issue on all browsers: Chrome, Firefox, Brave; in normal and incognito mode. None work.

I dual boot with Windows. When I am in Windows, the crashes do not occur. This behavior is the same on two PCs and a laptop. So, hardware is not the answer. I searched this site for alternative software but found nothing. My preference would be to be able to read my messages in the browser, but a desktop app that can read Google Messages is acceptable.

[hendersj]

What do you use for Google Messages, and what DE are you running? (I’m guessing GNOME from the error message, but want to confirm - that message is typically extension-related, IME).

I noticed with the update I did a couple of days ago, I couldn’t get GNOME to log into Google at all, and someone in the openSUSE FB group said they were having issues with their KDE Plasma desktop.

I use Google Chat, Voice, Mail, and Calendar regularly in Chrome, and it has worked fine there.

[myswtest]

@Prexy

this has occurred in the last few days. I use Google Messages. .

There are already 2-3 posts about this in the last week or so

Install the Flatpak version of Chrome using Discover

This seems to be a problem if using Tumbleweed… those of us using Leap 15.6 don’t have the problem.

Read thru these threads

Chrome support, How stupid it is

Today i sent a question to Chrome support. I begin my question with this two sentences : OpenSUSE Tumbleweed Chrome 135 stable I made an error i typed “Tumble weed” instead of “Tumbleweed” after a while i received a message saying : Please be advised that a post you recently published on our “Google Chrome Community” has been removed based on one or more notices from internal content reviewers, as it did not comply with our “Irrelevant Content” policy. We detected this problem automatica…

.

I can't sign in to a specific site with Chromium

Operating System: openSUSE Tumbleweed 20250313 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: MINIPC PN52 type or paste code here I have tested the following browsers Vivaldi (works), Chrome (works), Firefox (works) but Chromium does n…

.
EDIT: I also see this new post:

[HOWTO] G messages web fails to connect to android G Messages, workaround

Google Messages Web fails to connect to Android Google Messages. you get “error code 149 or 159” Uninstall the Chrome RPM. Install with Discover the flapack Chome. Perhaps you need to activate the flatpack backend. To run Chrome in a script execute : /usr/bin/flatpak run com.google.Chrome To run a Chrome Web app execute : /usr/bin/flatpak run com.google.Chrome --profile-directory=Default --app-id=<app-id> to discuss this problem go to enjoy

[Prexy]

I have the latest updates of Tumbleweed and Chrome. I am using the KDE desktop. Like you, I am running other Google tabs (Gmail, Calendar, Drive) with no issues.

[Prexy]

I followed the advice to uninstall Chrome and install the Flatpak version. It was very fast and solved the problem! I didn’t check the decimals, but both versions were 134, which I believe is the latest. What was different between them is way beyond my understanding.
Thanks to all who helped me.

[myswtest]

@Prexy

I followed the advice to uninstall Chrome and install the Flatpak version. It was very fast and solved the problem! I didn’t check the decimals, but both versions were 134, which I believe is the latest.

Good to read you’re back working!

As a rule, the Flatpak option of Chrome (the Chrome version number) will be newer than the “openSUSE customized version” in the default repos.

That’s because the openSUSE devs have to “customize” it to openSUSE standards. That doesn’t happen with the Flatpak option.

[hui]

@myswtest

As a rule, the Flatpak option of Chrome (the Chrome version number) will be newer than the “openSUSE customized version” in the default repos.

That’s because the openSUSE devs have to “customize” it to openSUSE standards. That doesn’t happen with the Flatpak option.

openSUSE does not distribute Google Chrome. Google Chrome is proprietary and cannot be shipped by any linux distribution. Chromium is NOT Google Chrome!

[myswtest]

@hui
openSUSE does not distribute Google Chrome. Google Chrome is proprietary and cannot be shipped by any linux distribution. Chromium is NOT Chrome!

Oh geez … I can’t believe I posted that - you’re correct. My mind was on Firefox app

[paulcee]

Not much to add here, but wanted to confirm the issue for anyone else looking (like I was). Version 135.0.7049.84 (Official Build) (64-bit) here, from the Google repository, on the latest Tumbleweed. Can easily get to that page on Firefox, just not Chrome. Haven’t tried the Flatpak version, but everything I’ve read here seems to confirm it’s Chrome, not Linux or anything else.

I can see verson 136 (beta) and 137 (canary) waiting in the wings when searching for Chrome in the software manager. Hopefully that’ll fix the issue.

[farcusnz]

Chrome 135.0.7049.95 in the repos now but still showing same problem