We Finns are persistent, especially women. 
1 Like
We’ve an update that has two recommended fixes.
https://bugzilla.opensuse.org/show_bug.cgi?id=1239780#c20
For me, this issue has been resolved, I no longer have the error 159. I thank the people/mod who tracket it down to the solution.
If I understand, they fix Chromium. Right ?
So, the problem is not solved for Chrome. Right ?
I use Chrome from opi. Google Chrome is based on Chromium, the error was in the first place of Chromium. The issue was common for both browsers at least on openSUSE Tumbleweed that i use and where i found it.
opi is not a source of packages. It points to where packages can be found. And then helps installing them. Thus people now still do not know where your Chrome came from.
Of course it is not the source, but the connection between the source and the end user.
People will know when they’ll use opi chrome
alb@tumbleweed $ opi chrome
Do you want to install Chrome from Google repository? (Y/n) y
Which version do you want to install?
1. google-chrome-stable
2. google-chrome-beta
3. google-chrome-unstable
4. google-chrome-canary
Pick a number (0 to quit): 3
Package signing key gpg-pubkey-7fac5991 ('Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>).
Package signing key gpg-pubkey-d38b4796 ('Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>).
Repository 'Main Update Repository' is up to date.
Repository 'Main Repository (NON-OSS)' is up to date.
Repository 'Main Repository (OSS)' is up to date.
Retrieving repository 'google-chrome' metadata .....................................................................................................................................................................................................................................................................................................................[done]
Building repository 'google-chrome' cache ..........................................................................................................................................................................................................................................................................................................................[done]
Repository 'openSUSE-20250211-0' is up to date.
Repository 'packman-essentials' is up to date.
Repository 'Open H.264 Codec (openSUSE Tumbleweed)' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
google-chrome-unstable liberation-fonts
2 new packages to install.
Package download size: 114.7 MiB
Package install size change:
| 367.7 MiB required by packages that will be installed
367.7 MiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: liberation-fonts-2.1.5-1.10.noarch (Main Repository (OSS)) (1/2), 1.5 MiB
Retrieving: liberation-fonts-2.1.5-1.10.noarch.rpm .....................................................................................................................................................................................................................................................................................................[done (2.4 MiB/s)]
Retrieving: google-chrome-unstable-136.0.7091.2-1.x86_64 (google-chrome) (2/2), 113.2 MiB
Retrieving: google-chrome-unstable-136.0.7091.2-1.x86_64.rpm ..........................................................................................................................................................................................................................................................................................[done (18.4 MiB/s)]
Checking for file conflicts: .......................................................................................................................................................................................................................................................................................................................................[done]
(1/2) Installing: liberation-fonts-2.1.5-1.10.noarch ...............................................................................................................................................................................................................................................................................................................[done]
update-alternatives: using /usr/bin/google-chrome-unstable to provide /usr/bin/google-chrome (google-chrome) in auto mode
(2/2) Installing: google-chrome-unstable-136.0.7091.2-1.x86_64 .....................................................................................................................................................................................................................................................................................................[done]
Running post-transaction scripts ...................................................................................................................................................................................................................................................................................................................................[done]
Do you want to keep the repo 'google-chrome'? (Y/n) y
alb@tumbleweed $
Every time we check for updates zypper ref/dup if there is a new Chrome version available, it is updated/installed like anything else in tumbleweed.
The source is Google for Chrome.
@alb what do you expect as your using unstable?
Just to be more updated. Old habit.
I did the same thing in Firefox with Nightly when used this browser on Debian sid.
I’ve been on Unstable Chrome for about a year, the only major problem for me it was the error 159 where i had to completely remove Chrome for about 2/3 weeks and switch to Firefox full time, Almost everything else has been very stable with my chrome-dev selection.
Chrome Unstable simply has a higher version number and a new feature updates come quickly.
I use Tumbleweed, so i like to have rolling browser like the distro.
It is always surprising that users run developement builds, but don‘t know how to report the bugs properly. Maybe have a read at the Google support sites about the differences of stable, beta, unstable and canary (and how to report bugs in unstable and canary)
That‘s an missunderstanding. Chrome stable is rolling. Chrome unstable is like factory.
Quote from the Chromium support pages:
Remember, Dev channel browsers and Canary builds may still crash frequently.
I know the procedure of bug reporting but i didn’t, i wasn’t sure if it was a bug in browser or something in the distro that’s why i commented here above after seeing someone similar to me. Then if i tell them i use Tumbleweed opi, packman and stuff, i dont think they bother with my report at all.
I read that a user from here reported it, but i can’t find the link now.
This is correct, i am wrong here in the definition of stable/dev.
There is no reason to use developement products, when there are no intentions to report bugs (for whatever reason).
The devs will ask you for informations and often can pinpoint if the issue is with the product or an external factor.
The „noise“ from additional (often problematic) factors like opi can be reduced by installing a product the most basic way.
opi is often recommended by some users without thinking about the implications. opi also points you to untested and incompatible (broken) home and developement repos. You can screw your system easily.
I didn’t report it because i wasn’t sure where the problem was browser or system. In this case, I wanted to collect evidence firstly. I usually report bugs for my installed apps.
I use opi for codecs and browser, the link to install directly from chrome okay, I’m not sure if it automatically proceeds with the next update this way?
With opi the upgrade procedure is automatic and it seems more practical to me.
It seems you don’t understand the commands. With zypper ar- f you add the Chrome repository so that with zypper dup Chrome automatically gets updated.
1 Like
Thanks for the clarification, something similar with opi not much difference just straight from the source. As long as i get codecs from opi, it doesn’t cost me anything to keep the chrome.
However, I kept that procedure in mind in case i’ll use it on other occasions. Thanks!
Again, you do not get codecs “from opi”. You get codecs from Packman. And yes, the Packman repo, when added correctly (by opi), will deliver updates when zypper up, or zypper dup, or YaST equivalents are done.
2 Likes
Issue still exists in TW 20250410 even after updating Chrome to latest version 135.0.7049.114
Crash seems to be caused by libc.so.6 which is part of TW
Stack trace of thread 3:
#0 0x00007f3f57719806 __mmap (libc.so.6 + 0x119806)
#1 0x00007f3f57645a03 getrandom_vdso (libc.so.6 + 0x45a03)
#2 0x000055fb6b5e69a0 n/a (/opt/google/chrome/chrome + 0xeaa89a0)
ELF object binary architecture: AMD x86-64
Seems like that would be useful information to include in a bug on bugzilla.o.o.
It is already in the bug report in comment 14 but the bug report is closed as resolved/fixed but still exists for me in 20250410
No issues here running 135.0.7049.114 (on Leap 15.6)
“what” bug report in Reply #14. I jumped back to #12 thru #16 … no bug link I see
Then it’s probably either worth reopening it or opening a new bug and referencing whatever bug it’s been noted in.