#After today's update that replaced omarchy-chromium with mainline, chrome fails to start

10 messages · Page 1 of 1 (latest)

mental shore
#

[0213/201523.028517:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trap (core dumped) chromium

#

After today's update that replaced omarchy-chromium with mainline, chrome fails to start

fierce galleon
lament reef
#

Same problem, need to reboot to snapshot before today update.

#

Yesterday I solved the problem of previous update with

sudo sed -i \
  -e 's/@@MENUNAME/Chromium/g' \
  -e 's/@@usr_bin_symlink_name/chromium/g' \
  -e 's/@@PACKAGE/chromium/g' \
  -e 's/@@uri_scheme//g' \
  -e '/^@@extra_desktop_entries/d' \
  /usr/share/applications/chromium.desktop

that I got from

#

Agreed.
I was slow to type, don´t saw someone referred to same post.

#

We need "stable" updates that don´t render web browser (and all web apps together, like Discord) non functional.

timid schooner
#

I had the same issue.
In my case, I tried to see if it was related to my user profile. I did this:

chromium --user-data-dir=/tmp/chromium-test
and saw chromium was launching just fine.

So I did a backup of my profile:
mv ~/.config/chromium ~/.config/chromium.bak

and started over again with a brand new profile.
I will try to migrate the content of my profile folder until I find the culprit files

upper nacelle
#

FWIW I also had backup and nuke my profiles.