SElinux alert and crash on Fedora
-
According to Hector Martín, the lead Asahi programmer, it's an
Upstream Chromium issue. It's already fixed upstream, Vivaldi just needs to update or backport the patch. This affects all Chromium-based browsers which update to the broken version. https://issues.chromium.org/issues/378017037 Possible workaround if you can pass arguments to Chromium: --js-flags="--nodecommit_pooled_pages"Is it still worth filing a bug? Happy to do so, but if it's a known thing then I don't want to create spam.
-
@PertinentAvocado
Hi, in the Chromium report the developer write at Dec 23, 2024:
is this feasible to merge back to M131? or at least M132?
Vivaldi 7.1 is already Chromium 132 so I am not sure if the fix is in Chromium already.
I don't think the Vivaldi developer know this but it doesn't matter, if the fix is in Chromium upstream Vivaldi will get it.Cheers, mib
-
I’m running the latest Vivaldi version on Fedora with no issues. I have disabled SELinux though as it does cause a number of issues across a number of software.
-
@PertinentAvocado Since it is an upstream issue, there is little we can do about a bug, except resolve it as "Upstream".
The patch (or patches) for this issue are in the V8 Javascript engine, which is definitely one component of Chromium we do not dare touch. It is far to easy to trigger bugs (or worse), and this bug has 9 patches, some for specific branches (probably Chromium 133).
If the Chromium team has decided not to backport that indicates a couple of possible things: 1) they do not consider the bug serious, or 2) while (possibly) serious, they are not sure backporting the patch(es) is safe.
I am definitely not going to backport these patches. Sorry.
-
Thanks @yngve — completely understand, backporting was Marcan's suggestion, not mine. Hopefully a fix filters through soon.
-
inconsequential update, after some time away...
vivaldi 7.0.3495.29(chromium130) works
chromium 132.0.6834.110 works
-
Hooray - just downloaded the latest snapshot from https://vivaldi.com/blog/desktop/address-bar-work-vivaldi-browser-snapshot-3597-3/ and it doesn't crash! The stable build still does.
-
@PertinentAvocado
Hi, do you installed the snapshot over the stable or as Standalone?
One can do this but never go back to stable, except the stable is never at some point.
The release of Vivaldi 7.2 for example. -
I had nuked the stable version (and reinstalled and nuked again), so this was a totally clean install.
I have sync set up, so I didn't lose anything.
When stable catches up I guess I'll nuke it again and reinstall stable and re-sync.
I installed from the rpm (on Fedora).
-
@PertinentAvocado
I am sorry but this happen only for Windows users, on Linux stable and snapshot are independent.
So I have 3 different installs and folders in .config and running all for testing.
-
openSUSE has announced that with new installations of their Tumbleweed distribution, the default mandatory access control (MAC) system selected by the installer, will be switched from AppArmor to SELinux in enforcing mode, beginning with the 11 February 2025 snapshot. In the installer, the user can manually change the selection to AppArmor, if they so choose.
