* [ISSUE] Compiz broken with libxml2-2.12
@ 2024-03-09 15:51 furryfixer
2024-03-09 19:40 ` oreo639
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: furryfixer @ 2024-03-09 15:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
New 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compiz broken with libxml2-2.12
2024-03-09 15:51 [ISSUE] Compiz broken with libxml2-2.12 furryfixer
@ 2024-03-09 19:40 ` oreo639
2024-03-09 21:58 ` furryfixer
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: oreo639 @ 2024-03-09 19:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49203#issuecomment-1986959110
Comment:
Can you verify https://github.com/void-linux/void-packages/pull/49205 works for you?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compiz broken with libxml2-2.12
2024-03-09 15:51 [ISSUE] Compiz broken with libxml2-2.12 furryfixer
2024-03-09 19:40 ` oreo639
@ 2024-03-09 21:58 ` furryfixer
2024-03-09 21:59 ` furryfixer
2024-03-09 22:23 ` [ISSUE] [CLOSED] " oreo639
3 siblings, 0 replies; 5+ messages in thread
From: furryfixer @ 2024-03-09 21:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/49203#issuecomment-1986991130
Comment:
I confirm the latest patches resolve the issue for updated x86_64 system, and presumably elsewhere. Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compiz broken with libxml2-2.12
2024-03-09 15:51 [ISSUE] Compiz broken with libxml2-2.12 furryfixer
2024-03-09 19:40 ` oreo639
2024-03-09 21:58 ` furryfixer
@ 2024-03-09 21:59 ` furryfixer
2024-03-09 22:23 ` [ISSUE] [CLOSED] " oreo639
3 siblings, 0 replies; 5+ messages in thread
From: furryfixer @ 2024-03-09 21:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/49203#issuecomment-1986991130
Comment:
I confirm the latest patches (#49205) resolve the issue for updated x86_64 system, and presumably elsewhere. Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ISSUE] [CLOSED] Compiz broken with libxml2-2.12
2024-03-09 15:51 [ISSUE] Compiz broken with libxml2-2.12 furryfixer
` (2 preceding siblings ...)
2024-03-09 21:59 ` furryfixer
@ 2024-03-09 22:23 ` oreo639
3 siblings, 0 replies; 5+ messages in thread
From: oreo639 @ 2024-03-09 22:23 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-03-09 22:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-09 15:51 [ISSUE] Compiz broken with libxml2-2.12 furryfixer
2024-03-09 19:40 ` oreo639
2024-03-09 21:58 ` furryfixer
2024-03-09 21:59 ` furryfixer
2024-03-09 22:23 ` [ISSUE] [CLOSED] " oreo639
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).