New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Chromium 102.0.5005.61 #1964
Conversation
It seems that they are deprecating 32-bit support or what?
Very funny:
|
I hadn't seen any announcements on this yet. According to (1305287) it seems there was an issue with some wayland change causing 32bit builds using libfuzzer to fail which explains why it's checked for explicitly in [3583780]. It seems like a pretty janky way of dealing with that though. Hopefully they can implement a proper fix before Tuesday. |
They've rolled ffmpeg, so expect issues if building against ffmpeg-4. PF4Public/gentoo-overlay/issues/153 Apart from that, builds and runs fine on 64-bit. 👍🏻 Minimal referrer is still functioning ;) PS: W.r.t. 32 bit it could very well be that 32 bit on linux is unsupported for a long time already:
|
@PF4Public @Ahrotahn and could it work with CHROME ffmpe with arch ffmpeg it fails too edit... im building it with its native ffmpeg |
Stop constantly mentioning the maintainers |
Arch seems to be merely rolling ffmpeg back: https://github.com/archlinux/svntogit-packages/blob/140fa66be0604daaf16be4246053c1a359d4e3bb/trunk/PKGBUILD#L109-L111 I'll try the same :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds and runs fine
@teeminus Have you had a chance to test this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds and runs. Not sure if we are clear to merge yet. Maybe waiting a little bit more?
I waited for this PR to be merged. I started working on updating the windows build a few hours ago. Unfortunatelly, the chromium 102 update is not as straight forward as the updates before. Currently compiling failes with the following error:
And I have no idea how to fix that... |
So… maybe ship it while teeminus is "fighting" Windows? |
Sure 👍 |
@teeminus No idea why that error popped up...it compiles and runs fine on my end. |
Yeah, my bad... I had to add a new patch to remove a clang-15 parameter (windows only has clang-14) and that patch was incomplete. Currently it's compiling and if that succeeds I will update the windows PR. |
I wonder, why Nifury didn't get this error? Do you use different building scripts? |
Compiling and linking finished over night. I need to update the patches before pushing my changes and updating the PR. |
Fun fact: Fingerprinting deception is a double-edged sword. Whatsapp web recently started checking browser fingerprint and nullifying the session if browser fingerprint changed. This results in session breaking upon browser restart :) |
>using whatsapp |
Just for that? Nah, too much trouble. |
This PR updates to chromium 102.0.5005.61.
Notes:
The removal in
download_bubble_prefs.cc
in the safebrowsing patch is no longer needed [3579726]There were changes needed to the safebrowsing patch in
safe_browsing_private_event_router.cc
. Instead of updating that I've removed the previous changes and added changes that removes the file from being built along with the few places that call into it. This should also resolve fix-building-without-safebrowsing.patch incomplete? #1935ENABLE_PRINT_CONTENT_ANALYSIS
was added in [3337977] which hooks into safebrowsing in other areas. I've added changes to disable that in the safebrowsing patch.There was a lot of activity in
configuration_policy_handler_list_factory.cc
in remove-unused-preferences-fields.patch, mostly due to the reorganization in [3573473] and [3576875]. The same keys are being removed as before.primary_account_policy_manager.cc
has been moved from components in [3563021] which has changes in remove-unused-preferences-fields.patch and makes 0017-disable-new-avatar-menu.patch no longer neededAppsShortcutDefaultOff
has been removed from 0006-modify-default-prefs.patch due to [3569271]Some removals and an addition to the trk patch: [3572211], [3537450]
SwiftShader has been removed: (1060139)
If you aren't yet using clang 15 you'll need to remove
-no-opaque-pointers
inbuild/config/compiler/BUILD.gn
. This is already removed in stha09's compiler patch.The feature flag to hide the sidepanel button has been removed. I'll submit a PR later on to add flags to hide the sidepanel and the share hub buttons.
Change log
Blog post