| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
This wasn't done in 97570d30c7f to allow reusing chromiumBeta builds
(without having to perform any changes) in the meantime.
|
|
|
|
|
| |
This reverts commit af9ea49430fe014708fa68b1ffe8513e4ecc9a00.
Reason: Not required anymore.
|
|
|
|
|
|
|
|
|
|
|
| |
If our Chrome derivation is Vulkan enabled, the Chrome GPU process
reliably crashes for me under M92 using the proprietary Nvidia drivers.
This is because the PCI-based GPU detection path fails, and we attempt
to use the Vulkan fallback instead, which then crashes(!!)
Including libpci allows us to use Angle's
src/gpu_info_util/SystemInfo_libpci.cpp path instead, which doesn't
crash, unlike src/gpu_info_util/SystemInfo_vulkan.cpp.
|
|\
| |
| | |
firefox, firefox-bin: 90.0.1 -> 90.0.2
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Their last Chromium commit is a52d7674cc7 from 2019.
Thank you for maintaining Chromium in the past.
|
|/
|
|
|
|
|
|
| |
The recent glibc update (acdcb85) broke the text rendering, see #131074.
This will hopefully work for ungoogled-chromium as well (at least the
patch applies).
Thanks: Lily Foster <lily@lily.flowers>
|
| |
|
|\
| |
| | |
brave: 1.26.74 -> 1.26.77
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The stable channel update to M92 (97570d30c7f) broke the Wayland support:
$ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[31712:31712:0721/114725.940557:ERROR:wayland_connection.cc(137)] Failed to load wayland client libraries.
[31712:31712:0721/114725.940641:FATAL:ozone_platform_wayland.cc(177)] Failed to initialize Wayland platform
[0721/114725.947566:ERROR:process_memory_range.cc(75)] read out of range
Trace/breakpoint trap (core dumped)
|
|\ \
| | |
| | | |
chromium: 91.0.4472.164 -> 92.0.4515.107
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop_20.html
This update includes 35 security fixes.
CVEs:
CVE-2021-30565 CVE-2021-30566 CVE-2021-30567 CVE-2021-30568
CVE-2021-30569 CVE-2021-30571 CVE-2021-30572 CVE-2021-30573
CVE-2021-30574 CVE-2021-30575 CVE-2021-30576 CVE-2021-30577
CVE-2021-30578 CVE-2021-30579 CVE-2021-30580 CVE-2021-30581
CVE-2021-30582 CVE-2021-30583 CVE-2021-30584 CVE-2021-30585
CVE-2021-30586 CVE-2021-30587 CVE-2021-30588 CVE-2021-30589
Note: This won't be the smoothest update. Chromium seems to be fine but
requires gtk3 in $LD_LIBRARY_PATH to find libgtk-3.so.0 (otherwise it
crashes during startup) but Google Chrome fails to initialize
("GPU process exited unexpectedly: exit_code=132") and requires
"--use-gl=angle --use-angle=swiftshader" for hardware(?) acceleration
(which seems to work work fine and performant but SwiftShader should
actually use the CPU instead of the GPU).
|
|/ /
| |
| |
| |
| |
| |
| | |
The stable channel update in #130877 is currently blocked due to
regressions but a cached build on Hydra might be useful for the meantime
(and that build would even be reusable if the PR is merged without any
changes).
|
|\ \ |
|
| | | |
|
|\ \ \
| | | |
| | | | |
tor-browser-bundle-bin: 10.0.18 -> 10.5.2
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
firefox, firefox-bin: 90.0 -> 90.0.1
|
| | | | |
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
palemoon: 29.2.1 -> 29.3.0
|
| |/ / |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The current stable release announcement [0] uses more HTML tags which
broke the detection of "fixes" and "zero_days". Proper HTML parsing
could be done using html.parser [1] but for our purposes the naive regex
trick works well enough.
[0]: https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop.html
[1]: https://docs.python.org/3/library/html.parser.html
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop.html
This update includes 8 security fixes. Google is aware of reports that
an exploit for CVE-2021-30563 exists in the wild.
CVEs:
CVE-2021-30559 CVE-2021-30541 CVE-2021-30560 CVE-2021-30561
CVE-2021-30562 CVE-2021-30563 CVE-2021-30564
|
|\ \
| |/
|/|
| | |
firefox-esr: 78.11.0esr -> 78.12.0esr
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Move makeWrapper to nativeBuildInputs for some packages
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
this is needed after c6e51d03695efa90a8d09b41fe6441953e21d52a
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
make gtk3Support non-optional, because it hasn't been for a long time
also make gtk2 conditional on firefox older than 90, because we can get
rid of it with firefox 90, but it's still needed by the current ESR
release
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This most notably fixes cross _evaluation_ of chromium which previously
would fail because makeWrapper relies on runtimeShell which is not
available in the HostTarget package set.
I tested that the native chromium build still works, but haven't tried
cross compiling it yet. There very well may be additional errors, but at
least they will be build errors, not hard to understand evaluation
errors.
|
|\ \
| | |
| | | |
vieb: 5.2.0 -> 5.3.0
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes: #129115
|
|\ \ \
| | | |
| | | | |
brave: 1.26.67 -> 1.26.74
|