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