[DEV] An attempt to package chromium for ppc64le in the official Fedora DNF repo

[MauryG5]

Unfortunately it still doesn't work for me either. After 5 minutes of use it locks and then after a few minutes it closes on its own...

[Hasturtium]

It was working but a little dodgy at v123, but an upgrade to v127 was pushed out, and now it bombs out at startup complaining about some kind of org.freedesktop.ScreenSaver.GetActive error. I'm still using Firefox ESR with the baseline JIT enabled, and holding out for longer.

[ClassicHasClass]

My next immediate step is to pull the JIT up to Fx128, since I'm also needing it for Github in particular (grr).

[tle]

Unfortunately it still doesn't work for me either. After 5 minutes of use it locks and then after a few minutes it closes on its own...

Thanks for the feedback. I am working with Than Ngo of Red Hat on verifying the expected behaviour of the patchset.

[MauryG5]

Perfect thanks TLE friend, I also reported to the Fedora team but no one has responded yet, there is a report open for some time now and you can read it by going to the site dedicated to Fedora problems on ppc64 that you may have already read.

[ClassicHasClass]

In the meantime, the patch sets for Baseline Interpreter/Compiler in Firefox 128ESR are now available. I'm typing this in it myself and the test suites all pass, so I'm pretty confident it will work well.

https://www.talospace.com/2024/08/baseline-jit-patches-available-for.html

[tle]

In the meantime, the patch sets for Baseline Interpreter/Compiler in Firefox 128ESR are now available. I'm typing this in it myself and the test suites all pass, so I'm pretty confident it will work well.

https://www.talospace.com/2024/08/baseline-jit-patches-available-for.html

Great work. Looks pretty solid, it has not crashed for me yet. I reckon when we get WASM working perfectly, we could try to get your patchset merged downstream with Fedora or Debian

[MauryG5]

TLE I saw your post on the Fedora bug report on Chromium which I opened and I also saw a post by another user who says to try the version that ends in 88-2. I have just installed the latest version which should be after 88-2 or 99 and as I also reported on Fedora Bug, it still doesn't work and always makes the same error and freeze...

[tle]

TLE I saw your post on the Fedora bug report on Chromium which I opened and I also saw a post by another user who says to try the version that ends in 88-2. I have just installed the latest version which should be after 88-2 or 99 and as I also reported on Fedora Bug, it still doesn't work and always makes the same error and freeze...

Please contribute to this ticket https://bugzilla.redhat.com/show_bug.cgi?id=2308642 instead

[tle]

Good news. The version 133.0.6943.98 no longer leak or crash on me. Kudos to Than Ngo of Red Hat.

It's still a bit sluggish but I am quite happy that now I actually use it

[MauryG5]

guys there is a problem after the last Chromium update, after it opens the main window, it crashes, exits and closes everything. I use it on Debian 12 so the problem is precisely the last update. I think the same will happen if you update to the latest version of Fedora. So be careful and I hope that Raptor is already aware of the problem to fix the bug.

[tle]

guys there is a problem after the last Chromium update, after it opens the main window, it crashes, exits and closes everything. I use it on Debian 12 so the problem is precisely the last update. I think the same will happen if you update to the latest version of Fedora. So be careful and I hope that Raptor is already aware of the problem to fix the bug.

What version do you have issue with?

[MauryG5]

I had the problem with the last update, but even after the update, it still didn't work. I tried uninstalling and reinstalling Chromium, but the bug still persisted. I then decided to delete all the Chromium files, then uninstall and reinstall again, and this time it worked. So perhaps the problem was with some additional file that Chromium uses to work.

[tle]

I had the problem with the last update, but even after the update, it still didn't work. I tried uninstalling and reinstalling Chromium, but the bug still persisted. I then decided to delete all the Chromium files, then uninstall and reinstall again, and this time it worked. So perhaps the problem was with some additional file that Chromium uses to work.

I am running v138.0.7204.157-1.fc43 on Fedora 43 and it works fine