Problem with Chromium after latest update on unstable branch

ARM Technical Assistance
1

Just carried out latest update on unstable branch, running KDE on a RPI-5.
Chromium is now Version 131.0.6778.85.

Chromium appears at first to work, but any page is replaced after 20 -30 seconds with:

Aw, Snap!
Error code: SIGTRAP

This behaviour is consistent, even for non-web pages, such as “settings”.
I’ve tried removing chromium, deleting chromium folders in .config and .cache, rebooting and reinstalling. Same problem. Same with both X11 and Wayland.

I checked the journal. It gives:

systemd-coredump[6142]: Process 5482 (chromium) of user 1000 terminated abnormally with signal 5/TRAP, processing…

and then proceeds to give the coredump.

(I remember when a coredump actually came from core memory, not semiconductor memory :smiley:)

So working with firefox, for the moment.

2

I concur. Chromium is unusable after the update. Perks of a rolling distro ha :slight_smile:

3

I cannot reproduce using

 $ chromium --version
Chromium 131.0.6778.85 Arch Linux

I suggest - if applicable - to disable/ remove any extension you may have added.

Then verify if the issue persist.

Try re-enabling/ re-add your extensions one by one until you make the browser fail.

4

I’ve installed a completely clean chromium, after I’ve deleted

.config/chromium,

.cache/chromium

and renamed

.config/chromium-flags.conf

There are no extensions. Maybe it’s a KDE-specific issue.

5

Well, i just switched to “testing” branch which still has version 130. I could have tried to start afresh like you said without any addons but as jong just confirmed, i guess addons are not the problem here. I opened a new thread suggesting that fresh installations should not come with the unstable branch enforced. Just an idea.

6

I am not an expert on the ARM architecture - so is xorg vs. wayland an issue?

7

Would it help if i shared the coredump?

8

so is xorg vs. wayland an issue?

Wayland doesn’t work for me. See:

9

I am seeing this issue also with my xfce. I downgraded chromium and seems to go away.

10

I have tried to downgrade just the chromium package but could not do it. Searched online but “downgrade” package wasn’t available in the package repository. In the end i downgraded the whole system to “testing” branch. Was it really possible to downgrade just Chromium?

11

Should be in /var/cache/pacman/pkg/ if you have not deleted your cache.

12

Yeah it wasn’t there, i think i cleaned the cache at some point. But i also tried to download the older chromium package from a testing or stable repository of Manjaro. The links were probably available somewhere online but couldn’t really find any. I could have maybe done a “pacman-mirrors” after editing the conf file and then just update or DOWNdate :slight_smile: chromium. And then lock it and get back to the original branch.

Yeah whatever. I think it is better if i stay on testing. Unstable is a little bit too adventureous.

13

I will stay on unstable and use the older package until a newer version with a fix comes along.

14

Also downgraded and put on hold. Staying on unstable.

15

I have tested chromium on rpi5 manjaro-xfce using unstable branch.

chromium is at 131.smthng and works without hickups.

card created with manjaro-arm-installer.

//note - chromium is at 122 on stable branch - the most activity seems to be in unstable and testing branch.

16

Is anybody else having problems share any of the following entries in their chromium-flags.conf file?

--enable-features=MiddleClickAutoscroll
--ozone-platform-hint=auto
--in-process-gpu
--ignore-gpu-blocklist
--enable-zero-copy
--use-angle=gles
17

I don’t think that’s related in any way to the problem I reported with the latest version. When I reinstalled a ‘clean’ version, I had renamed the file, so chromium could not see it, but the issue was still there.

18

Yeah man i know, i have the same issue with you on version 131, i am just trying to find some commonality so that maybe we can pinpoint what the cause is.

19

Just a FYI. There is an archived repo for arch-arm packages. It has the packages that was current on a given date. For example the previous package version of chromium can be found here that is in our unstable branch:

http://tardis.tiny-vps.com/aarm/repos/2024/11/19/aarch64/extra/

Be aware that arch-arm’s repo (in reality their stable branch) is more aligned with our unstable branch and we run behind them when our mirrors get synced with theirs so you will have to click around on the dates to find the version you are looking for. Even more so if you are on our stable or testing branches.

Also it is not generally recommended not to downgrade packages as a lot of times it can possibly cause issues due to various reasons. Sometimes depending on what the package is and what versions of packages it was built with you can get by with doing it and using it temporary until the issues is fixed with a future package.

Upgrading a package can also cause issues. The problem gets worse the farther down in our branches you go. It very likely that things will break say if you are on the stable branch and try to install a newer package that is in our unstable branch or the latest package that is in tardis.tiny-vps repo.

20

Ok you say “arch-arm packages”. Now i am confused. Aren’t we supposed to look for Manjaro arm packages? I mean i could probably find the arch chromium packages but would it be the same package with what manjaro had? I thought manjaro had its own packages and did not rely on arch packages.