Skip to content
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

Compiz broken with libxml2-2.12 #49203

Closed
furryfixer opened this issue Mar 9, 2024 · 2 comments
Closed

Compiz broken with libxml2-2.12 #49203

furryfixer opened this issue Mar 9, 2024 · 2 comments
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed

Comments

@furryfixer
Copy link
Contributor

Is this a new report?

Yes

System Info

Void 6.6.20_1 x86_64 AuthenticAMD uptodate hold rDFFFF

Package(s) Affected

compiz-core-0.8.18_2

Does a report exist for this bug with the project's home (upstream) and/or another distro?

[https://gitlab.com/compiz/compiz-core/-/merge_requests/175/diffs?commit_id=ea7b3731b1a8a0f2fb7aa765a84374658b67b1b7]

Expected behaviour

Compiz starts normally when invoked. (works with libxml2 downgrade to 2.11)

Actual behaviour

Compiz fails to start. When started manually, the following error or similar occurs:

Entity: line 1: parser error : Extra content at the end of the document
name="force_independent_output_painting" type="bool"/>
^
compiz (core) - Warn: Unable to parse XML metadata

Steps to reproduce

I suspect anyone using up-to-date package versions of compiz-core and libxml2 will experience the problem. Upstream has patched this in 8.18 I think, so I suspect Void just needs to rebuild (rev-bump?). Unfortunately, my git skills are limited, so I do not feel comfortable doing a PR myself that likely will need all the packages in compiz-reloaded rebuilt.

@furryfixer furryfixer added bug Something isn't working needs-testing Testing a PR or reproducing an issue needed labels Mar 9, 2024
@oreo639
Copy link
Member

oreo639 commented Mar 9, 2024

Can you verify #49205 works for you?

@furryfixer
Copy link
Contributor Author

furryfixer commented Mar 9, 2024

I confirm the latest patches (#49205) resolve the issue for updated x86_64 system, and presumably elsewhere. Thanks.

@oreo639 oreo639 closed this as completed Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed
Projects
None yet
Development

No branches or pull requests

2 participants