From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Compiz broken with libxml2-2.12
Date: Sat, 09 Mar 2024 23:23:00 +0100 [thread overview]
Message-ID: <20240309222300.EF1D125C06@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49203@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Closed issue by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/49203
Description:
### 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"/></screen></core></compiz>
> ^
> 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.
prev parent reply other threads:[~2024-03-09 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 15:51 [ISSUE] " furryfixer
2024-03-09 19:40 ` oreo639
2024-03-09 21:58 ` furryfixer
2024-03-09 21:59 ` furryfixer
2024-03-09 22:23 ` oreo639 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240309222300.EF1D125C06@inbox.vuxu.org \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).