I'm getting this after upgrading packages this morning:
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: unzGetCurrentFileZStreamPos64
Update: this was because I had minizip-ng-compat
and minizip-ng
installed. I didn't have the minizip
package. The latest update of the minizip
package, 1:1.3.1-2
, conflicts with minizip-ng-compat
apparently. I'm not sure, but when I installed the regular minizip
package, ungoogled-chromium
started working again.
I suspect (I can't remember precisely) that minizip-ng-compat
"provides" minizip
but not a compatible one anymore? Strangeness.
Pinned Comments
networkException commented on 2022-09-20 17:36 (UTC)
Please note that normally it's not required to flag this package as out of date. I usually tag releases in the main ungoogled-chromium repository and update the arch packaging right afterwards.
If the package hasn't updated after an ungoogled-chromium release GitHub Actions might still be building or the ungoogled-chromium patchset got updated for non Linux platforms only to match their upstream release cycle