ungoogled-software/ungoogled-chromium

Chromium 141 probably won't work with libxml2 < 2.13

Open

#3493 opened on Sep 30, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (18,674 stars) (771 forks)batch import
enhancementhelp wanted

Description

Description

There's a recent Chromium commit that removes compatibility code for libxml2

Who's implementing?

  • I'm willing to implement this feature myself

The problem

This Chromium commit removes some code needed for libxml2 versions < 2.13 which are still widely used.

Possible solutions

You might want to revert this commit. (The first hunk contains the breaking change, the second one can be ignored.)

Alternatives

No response

Additional context

No response

Contributor guide

Tech stack
ccpppython
Domain
build systeminfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with Chromium buildbasic git skillsunderstanding of libxml2
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the referenced Chromium commit (7a9c043) to understand the removal of libxml2 < 2.13 compatibility. Consider reverting the first hunk as suggested. Test that ungoogled chromium builds and functions correctly with libxml2 older versions after the revert. Also check for any potential side effects on other parts of the build.