Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails on amd64 in
qemu since around 2025-04-21. What's worse, it fails because it times
out (and then causes issues with autopkgtest). Can you please
investigate the situation and fix it? I copied some of the output at the
bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.

Because the test times out and tmpfails, I'm going to add it to the
reject_list on amd64 as tmpfails are rescheduled immediately by the
migration software so the test is a bit hard on the infrastructure.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/packages/f/firejail/testing/amd64/70492454/

791s autopkgtest [01:45:13]: test application-tests:
[-----------------------
791s /tmp/autopkgtest.TRfOb0/autopkgtest_tmp/test/apps
/tmp/autopkgtest.TRfOb0/autopkgtest_tmp/test
791s + export MALLOC_CHECK_=3
791s + MALLOC_CHECK_=3
791s + export MALLOC_PERTURB_=115
791s + MALLOC_PERTURB_=115
791s + export LC_ALL=C
791s + LC_ALL=C
791s + sudo ls
791s The XKEYBOARD keymap compiler (xkbcomp) reports:
791s > Warning:          Multiple symbols for level 1/group 1 on key <FK23>
791s >                   Using F23, ignoring XF86TouchpadOff
791s > Warning:          Symbol map for key <FK23> redefined
791s >                   Using last definition for conflicting fields
791s > Warning:          Symbol map for key <FK24> redefined
791s >                   Using last definition for conflicting fields
791s Errors from xkbcomp are not fatal to the X server
10791s autopkgtest [04:31:53]: ERROR: timed out

Ping to the maintainer, since firejail has just been removed from
testing because of this bug.

But also...

Is this really 2025-04-21 (so the issue would have been introduced
by firejail 0.9.74-1, accepted in unstable on 2025-04-20), or is it
a typo (as the mail was written on 2026-04-21)?

Hi,
Easy to verify:
https://ci.debian.net/packages/f/firejail/testing/amd64/
First one seems to be from 2026-04-17 while 2026-04-14 had a passing test.

So, it looks like a typo.

I'll note that at the time of writing my e-mail several runs were still
in the queue (including on unstable) and the issue seems to have
improved somewhat a day later. From 2026-04-22 21:20:20 the tests seem
to respond less flaky and the reported hanging test passed most of the
time, but when it didn't (2026-04-22 22:53:55 and 2026-04-22 23:09:16)
it still hung.

Paul

Hello,

Since this is a transitional issue, should it still be considered serious?

I wanted to note, that firejail will be used by Debian mediawiki
instance and therefore this issue would be good to resolve in a way or
the other.

Regards

We believe that the bug you reported is fixed in the latest version of
firejail, 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 1134557@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann <reiner@reiner-h.de> (supplier of updated firejail 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 25 Oct 2026 13:53:53 +0100
Source: firejail
Architecture: source
Version: 0.9.80-2
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann <reiner@reiner-h.de>
Changed-By: Reiner Herrmann <reiner@reiner-h.de>
Closes: 1134557
Changes:
 firejail (0.9.80-2) unstable; urgency=medium
 .
   * Disable X11 autopkgtests, as they are too unrealiable in debci.
     (Closes: #1134557)
   * Several smaller autopkgtest improvements.
   * Bump Standards-Version to 4.7.4.
   * Bump debhelper compat level to 14.
   * Update watch file to version 5.
Checksums-Sha1:
 c30625065be1ea5181637216de9e2d0b2af23015 2373 firejail_0.9.80-2.dsc
 876c9fb1a107de32f1b53a673d55abcb14f53d39 17304 firejail_0.9.80-2.debian.tar.xz
 bb8a5460eda5749140e2e5ec12322936ca4b1a84 6381 firejail_0.9.80-2_amd64.buildinfo
Checksums-Sha256:
 4489b4275e08b30734b02202eb286215ea0fd1d08565f62c69940975453b23ec 2373 firejail_0.9.80-2.dsc
 6c28bb228525afe2b921c5bb00ca81c5438c19303c61204b0b13aa4ee666ffa4 17304 firejail_0.9.80-2.debian.tar.xz
 7dec1420af7871b3dcc2cb1b6b3eceb64a28858b2afecf1e921ca281b4ff85f6 6381 firejail_0.9.80-2_amd64.buildinfo
Files:
 7d081c5be2d3fac831ec683ad60c9752 2373 utils optional firejail_0.9.80-2.dsc
 077a49fc65303eaa6928697562eaae1d 17304 utils optional firejail_0.9.80-2.debian.tar.xz
 6957ebd2f0e747cbe201575fdf122640 6381 utils optional firejail_0.9.80-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAmrd/VsACgkQzPBJKNsO
6qeLQA//eIhFUfvI5cRWrfa2tOyMNzIHniwmWnkOhqQ5qKigAc8IEgbh3dvvhPzK
2Ww2/SQVYkI58O1JHfXa3U/Xm/k+kRfCpmRgw4VATrCuAHlOcXlgJXFLjW3M+Eni
dvqDL8dQqF3SZc8ZGTFKrSMOl4zakInR9EYbjdczeWH8Mh42HqzXtODVF5KQ2rGp
1h3C7FDQJh4gcB5LytbvFHhHAru3HATcIb40DC4BvarFoFaxpT6ZRNFYaPelP+5b
p6oQZcdGzn7/wPcJzJZ5ZLTaUuk0UJrvnVlnVZstqTqcJ42wVDMWV5NcVoZ1Ndgn
lNvZmsBzN7mCTtlJAXs6xQnW03rV/P52Sz+FPQp3zrPtZU3Ng8DBvDXTyJTy4qIL
XhcVczxJ/mdQkw5sGpPQi7IKEupBMbPQYzxTyhrTfEj/GuZtIr83CJWTH/Te9R6G
cONRA7Rk7JFXhAaTfR/PbRcLAGHdo62R+fbEyub7OXORExy4h4I+TCCnAFFKJnK/
SnbcyIvI183/14jik/QM5b70ANLdjdlbM3iUlo6t6Iy5aS2YzdfKQcZujL16LNGr
XUQTrnMSpcgImKcWpXkZFZ6OtzQyFr0VvIHswH5YTVD0t8vUQbma16V/doBxonhD
gr/cDW5GyokPyWFXqdbByYI8HKYNxPHELYUJ+8C2BAS9NLqsrNM=
=k3Cx
-----END PGP SIGNATURE-----