Your message dated Tue, 12 Nov 2024 14:44:50 +0000
with message-id <e1tas8q-006hik...@fasolo.debian.org>
and subject line Bug#1084230: fixed in xorg-server 2:21.1.14-2
has caused the Debian Bug report #1084230,
regarding xvfb: please consider disabling libunwind, at least on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1084230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xvfb
Version: 2:21.1.13-2
Severity: important
In current unstable, when xvfb-run runs Xvfb, it repeatably crashes in
libunwind on some armhf machines and with some command-line options:
see #1082659. This appears to be a regression with the recent libunwind
1.7.x upload, and is reproducible in an armhf sid chroot on the porterbox
amdahl.
For whatever reason, it seems that `xvfb-run -a -s "-noreset" true`
crashes, but `xvfb-run -a -s "-screen 0 1280x1024x24 -noreset" true`
does not.
As far as I can tell from the source code, the use of libunwind is
optional and not necessary for normal X server functionality: its only
purpose seems to be to print better backtraces if the X server crashes,
and it isn't enabled on every architecture (for example s390x and riscv64
don't build-depend on it). This makes it somewhat ironic that initializing
libunwind is, itself, causing a crash. I think crash dump analysis
frameworks like systemd-coredump, corekeeper and apport are likely to be
a better way to get information out of X server crashes.
Until libunwind can be investigated and fixed (presumably by a porter?),
I think it would be better to disable this optional feature on armhf,
so that X11-related packages can rely on being able to use Xvfb to run
their test suites on buildds.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:21.1.14-2
Done: Timo Aaltonen <tjaal...@debian.org>
We believe that the bug you reported is fixed in the latest version of
xorg-server, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1084...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Timo Aaltonen <tjaal...@debian.org> (supplier of updated xorg-server package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 12 Nov 2024 15:56:38 +0200
Source: xorg-server
Built-For-Profiles: noudeb
Architecture: source
Version: 2:21.1.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaal...@debian.org>
Closes: 1084230 1085704
Changes:
xorg-server (2:21.1.14-2) unstable; urgency=medium
.
[ Simon McVittie ]
* Disable libunwind on armhf (closes: #1084230, #1085704)
* Check basic functionality of xvfb-run at build-time
* Add an autopkgtest to verify basic functionality of xvfb-run
Checksums-Sha1:
af00688d1cd4ab13265bb0890fb5c2ee3f9f9d32 4318 xorg-server_21.1.14-2.dsc
01bcf7a6fbb7a10ee548f1bd1e3f374e8ff94552 177747 xorg-server_21.1.14-2.diff.gz
3037a8a0cf0bb2489f1594a535694d150f8918ad 11032
xorg-server_21.1.14-2_source.buildinfo
Checksums-Sha256:
e78d7b8b4da0c614e5a143a29a30e9267a3adacd8aff89a4ab249fa867bffb49 4318
xorg-server_21.1.14-2.dsc
f59623f2521762fa21a3947bd47b0fc2fec7749b3514877e4f683d71dcbdc8d2 177747
xorg-server_21.1.14-2.diff.gz
91d14d16dd2622e9a24a64bb5fa69e2afafc069aa667d7075e748ed070becf0a 11032
xorg-server_21.1.14-2_source.buildinfo
Files:
6dde07326d664fbd5025636444a320bc 4318 x11 optional xorg-server_21.1.14-2.dsc
0269520b2494ee8a1c0d76ec00fdeddf 177747 x11 optional
xorg-server_21.1.14-2.diff.gz
4e23ba3bfeb1e8fcf711d14623580b7b 11032 x11 optional
xorg-server_21.1.14-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmczXrQACgkQy3AxZaiJ
hNzQDRAAhlBCY9hKtzpLRmh1XNgw2H8IqVZlejHRUTqYvmIMOoZaY7VUsQw6G/Bf
1wvgpBXfuhCWHpnY8m/mkP3DrkabwLnKCdJEvFH1rb6vRxC8FMhs2+l9u8sr7BUt
j3f9EPkTzLYmDn9nYn6bfaVAk3ORGGpkOcMwS+sjwBiGYs+q1rXw2gwiMnYO2wq6
oVYaqrXHq4+xuiJBz1aWNFfPDGqOzTJNG6iOWuDQ8vSDM73/wrUg2zknjmMJrtOv
9jm/qCUrZEO1mbz+CvyvhNkICb1rHRCtKfDFHnJxcDXGDjJ2Hozurajub6csA1Wi
XRNnqakNWKRRYdNbqylKQ7JVgUADfW35On5fJokOG80acUIb5/UvOCYQDH9mKzTO
9FrtaSjhpk+DGV3v/xGQBBuMpyTVfB6xXlk9kTmNjv4yZ409fKBYq1JCg8xoPje0
TXhKOwonFEkIDOJBA0IfKDxWc4D/XtuyZw7cQbwFgXY1iquV1i9R162qkUMESUPS
tpk/EaoBzXwb3ojjkKE1X60t4ug81/gKAlBQ6D+/rj1W1+ueNTw8dbh13xI0IJ4H
CJ7QI00JkWbz9+IYZa4WYZg8rVtdduYQjYlm5B6RRee2MnpGYEtnt+SSycxnK/tL
GVDpj5svfvJNevNkAEFLv32DFJ4va9IEnYiwsvhoEDecH3nzMyE=
=JqyP
-----END PGP SIGNATURE-----
pgpk75SoLtaPL.pgp
Description: PGP signature
--- End Message ---
