Chromium and Ungoogled Chromium DNF Repository

Started by vddvss, December 14, 2019, 02:13:48 PM

Previous topic - Next topic

MauryG5

#120
I've just submitted the report to the Debian bug section; unfortunately, I don't have Tim's email address, so I can't CC him, but I imagine he'll see the report right away. In any case, the Raptor moderators are here, and I assume they've already read it and passed the information along.

Fortunately, Tim saw my message in the Debian bug report anyway and promptly replied, asking for specific details about the bug, which I sent him right away. Now we are waiting for him to fix the issue; he has everything he needs.

tle

#121
I think I might have found a bug with Chromium

Hitting https://browserbench.org/JetStream3.0/index.html?test=mandreel would yield checksum mismatched error. Reported https://issues.chromium.org/issues/577322145

Can anyone who runs Debian version of Chromium help me confirm?
Faithful Linux enthusiast

My Raptor Blackbird

MauryG5

Tim sent me a link to a patch he released for testing; I'm posting the link here. I can't try it out myself right now, so please see if any of you can—thanks.

https://salsa.debian.org/chromium-team/chromium/-/commit/bac3c99cfd739269f7b6c73002e04461abdb4638

tle

That is great! I have also updated my Bugzilla on the Fedora side
Faithful Linux enthusiast

My Raptor Blackbird

MauryG5

So, can you confirm that the patch has fixed the issue?

tle

#125
Yes it does fix the issue but then I ran into yet another issue. "first syscall argument being clobbered with -ENOSYS in the signal context—something our current Trap.cc workaround doesn't cover since it only handles a negated AT_FDCWD". In theory this issue should impact Debian too though I have not verified MR submitted at https://salsa.debian.org/chromium-team/chromium/-/merge_requests/51/diffs

I am waiting for Thân Ngô of Red Hat to investigate the issue.
Faithful Linux enthusiast

My Raptor Blackbird

MauryG5

The problem persists on Debian; on Fedora, the team managed to work around it—even though logs from Chromium's startup still show Zygote-related failures. While the browser functions properly on Fedora, it remains non-functional on Debian. I've sent everything to Tim, providing both the Debian and Fedora logs and pointing out that, on Fedora, they've managed to get it working despite the Zygote issues. Version 156, which I just installed on Fedora, is currently working.