( Yes, I’m on Leap 15.6 / KDE, waiting for Leap 16.1 GA. )
.
So Chrome ran fine this morning … then later i ran “zypper up” and a new Chrome version showed up, so updated it (no updates for any Leap software).
google-chrome-stable 151.0.7922.137-1 ==> 151.0.7922.173-1
So, when I launch Chrome at a CLI, I see this:
myswtest@machine :~> google-chrome-stable
[0821/143237.805723:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[... repeats about 6 times]
[0821/143237.811525:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trap (core dumped)
myswtest@machine :~>
.
Troubleshooting?
- Internet search - nothing conclusive.
- I deleted the sub-directory:
“/home/myswtest/.cache/google-chrome-stable”
- then deleted the “GPUCache” sub-directiory under “/home/myswtest/.config/google-chrome-stable”
- Then I installed Chrome Beta (shows same error)
- Then I installed Chrome Unstable (shows same error)
The fact that I installed the other releases of Chrome tells me that there is something this new Chrome is expecting (low-level library version?), but EOL Leap 15.6 does not provide anymore.
.
.
Then I thought, “I have a Leap 15.6 install in a VBox” to test upgrading from 15.6 to Leap 16.1.
So, I installed the latest Chrome on that 15.6 VBox …
Guess what - it runs with zero problem.
.
Any thoughts on further troubleshooting on the real-metal 15.6 on this laptop? Should I run “strace …” ? (a pain to). Some other troubleshooting tool?
Okay, one thing I forgot to do (which I tell other folks) is to test with a different user account.
So, I logged out of my regular account, logged into my “test” account, and fired up Chrome Stable … no issues starting up.
Then tried Beta and Unstable … no issues.
But I’m confused because when I installed Beta and Unstable, there were NO profiles (.cache and .config) sub-dirs for my regular user account.
Perplexed at this point.
Running some chrome plugins?
Google the error… “third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found”
No plugins …
And yea, as I mentioned above … a 'Net search:
Internet search - nothing conclusive.
So as the test user is hardware acceleration enabled? chrome://settings/system
Yep … it is enabled for the test user.
That was one thing I tried earlier with my regular user account … you can start Chrome from CLI to disable it.
google-chrome-stable --disable-gpu
.
This is so odd. One minute it’s working.
After update, it won’t launch.
And newly installed Beta / Dev same error. All three versions have their own “.config” and “.cache” sub-directories for the user account, so it’s not like they affect each other.
Not really sure, I run google chrome everywhere here and no issues, Intel/Nvidia.
Thanks for the assistance, Malcolm!
I guess I’ll have to run “strace” and dig through a few thousand lines of output … and it might not show anything obvious 
Well, @malcolmlewis will like what I write below.
I decided to log out … I then chose XFCE and logged in. Chrome started no problem. But XFCE didn’t offer me to connect via Wifi.
…
So, I logged out. This time I selected “Plasma / Wayland”.
Chrome popped up on the screen, as usual, with a Gmail tab, a Voice tab, a Messsages tab, and Gov’t tab.
( I tried again using Plasma / X11 - same error ).
.
.
Here’s the biggest issue I have with Wayland. I use this Dell laptop (90% business usage) that has a Trackpad and two (physical) mouse buttons. (see photo)
The left mouse button is not very responsive anymore. Using X11, I can "tap"on the Trackpad with my finger and X11 thinks I am tapping the left-mouse button. (double-tap for right button)
Wayland DOES NOT interpret that tap. I have to lightly tap the left mouse button to select something (menu, icon, etc). I know the left mouse button will go kaput eventually / soon.
.
( Have to figure out issue using X11 )
.
Dell Laptop:
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.4.0-150600.23.103-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 5500
That sounds more like a desktop issue, I use Tumbleweed/Hyprland on a MacBook Pro and the touchpad works fine, I have Leap 16.0/Gnome on an AMD powered laptop that seems to work fine as well. An update may improve that…
Yea, I found the issue with “can’t use the Trackpad in Wayland, like I can with X11”.
It’s because Wayland does not inherit (or import) the settings I had set a long time ago, for the Trackpad settings in Plasma X11 … so I had to enable those settings, once again, while in Wayland (why?).
.
Well … I had a bad feeling this would happen.
Today, I ran a “zypper up” and it showed that an update for the Brave browser (Stable release), so I answered “yes”, but I suspected what the result would be. (I’m currently typing this using the Brave Beta version, not updated yet).
.
After the update, I clicked the Brave Stable icon (in KDE menu) - nothing.
So, I executed it from the command line … slightly different wording, but it’s really the same issue as with Chrome:
myswtest@machine :~> brave-browser-stable
[0822/165245.628203:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0822/165245.629234:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0822/165245.630245:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0822/165245.633547:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0822/165245.633622:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0822/165245.634733:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
/usr/bin/brave-browser-stable: line 30: 14494 Trace/breakpoint trap (core dumped) "$HERE/brave" "$@"
myswtest@machine :~>
.
I’m pretty confident when the update for Brave Beta shows up, it will result in the same problem.
Brave is based on the Chrome architecture, which is why I suspected I’d see the same error.
1 Like
@myswtest you might need to dig more into other desktop environment settings that may be cached since it worked with a test user?
Yea, but the confusing part is
- I have not been in (KDE) System Settings for a long time. (weeks, if not months).
- Because I’m on Leap 15.6, it’s rare there are any low-level system updates (“zypper up”) - mostly I see 3rd party updates. I do see updates with Discover (because of Flatpak updates).
Quite literally, Chrome was working fine … then its update was installed (zypper up). Then, the error at startup. Five minutes before the update, Chrome ran fine.
The same issue after I updated Brave (stable). I’m using Brave Beta right now (as I type), but I’m confident when Brave Beta gets its update, it’ll show the same error.
And yes, I just now finished logging into two different user accounts on this machine, and for each user, they can run Chrome and Brave with no issue (KDE /X11).
Admittedly, if I log in (my user acct) with “Plasma / Wayland”, both Chrome and Brave start up fine.
Of course, both those test users’ KDE settings are not exactly the same as my KDE settings.
So, my challenge is, "what changed in Chrome/Brave that is in conflict with “setting xxx” using X11 ? I guess an “strace …” is in order.
I’ve experienced similar behavior for quite a few months. For a long while - chrome wouldn’t even open. I nuked configs and reset as much as I could to no avail. Then one day it would open - but internet wouldn’t work - meaning chrome would open to the default local page - but could not browse the internet with ERR_CONNECTION_TIMED_OUT.
Inspired by this discourse I took up the mantle again and loaded into icewm and loaded chrome - when magically it began to work. I logged out and logged back into Gnome and chrome works again. I have no idea what that would indicate - but definitely feels like something local user/config - but also something post-transaction missed in the rpm?
Hope this helps someone - but at current it seems a workaround of logging into a different desktop/window manager may provide a correction.
Welcome to the forum … and thanks for stopping in.
Yep. What’s odd is the crash/error began immediately after updating to the newer Chrome. Same with Brave (based on Chrome). When I get the Brave Beta update, I’m positive it will happen to it.
I use KDE / Plasma. I normally log in using KDE / X11. That’s where the issue happens.
If I login using “KDE /Wayland”, Chrome and Brave work fine. If I login using the two other user accounts I created, and login with “KDE / X11”, Chrome and Brave work.
So yea, folks will say, "there is something odd about your “KDE / X11” environment … but keep in mind, this issue only showed up after the update to Chrome and Brave, so the issue is a combination of my X11 config and whatever the (low-level) change that was made in Chrome and Brave.
So, as my workaround, I now login using KDE/Wayland … unfortunately, Wayland on Leap 15.6 is buggy, so that’s just as annoying.
Thought I would provide a follow-up, related to “try this” … unfortunately, none solved the issue.
One interesting side-note: during my 'Net searches, I found a thread out in Google forums , reporting the same problem. And they have referenced this (openSUSE) thread [1] 
Okay, I tried these runs with the arguments:
myswtest@machine :~> google-chrome-stable --no-sandbox
[ ...same error... ]
myswtest@machine :~> google-chrome-stable --no-crashpad --disable-crash-reporter
[ ...same error... ]
There is a suggestion to delete these files:
myswtest@machine :~> cd ./.config/google-chrome
myswtest@machine :~/.config/google-chrome> ll Singlet*
lrwxrwxrwx Aug 28 21:24 SingletonCookie -> 143444
lrwxrwxrwx Aug 28 21:24 SingletonLock -> machine-20444
lrwxrwxrwx Aug 28 21:24 SingletonSocket -> /tmp/com.google.Chrome.ccxxxxx/SingletonSocket
myswtest@machine :~/.config/google-chrome> rm ./Singlet*
myswtest@machine :~/.config/google-chrome> ll Singlet*
ls: cannot access 'Singlet*': No such file or directory
myswtest@machine :~/.config/google-chrome> cd
myswtest@machine :~> google-chrome-stable
[ ...same error... ]
.
[1] The similar thread out in Google-land forum:
https://support.google.com/chrome/thread/462198462/google-chrome-crashes-with-elf-dynamic-array-reader-h-tag-not-found?hl=en
