Dear Adrian, this bug has already been fixed in 0.17.1-2, which is waiting for sponsorship on Debian mentors.
https://mentors.debian.net/package/stimfit/ The failing test tried to run `stimfit --help`, which initializes the wx/GTK application and therefore fails in the headless ci.debian.net environment. In 0.17.1-2 I replaced that test with a headless-safe test. The `python3-stfio` import autopkgtest remains unchanged. Best wishes, Christoph > On 23 Jun 2026, at 10:22, Adrian Bunk <[email protected]> wrote: > > Source: stimfit > Version: 0.17.1-1 > Severity: serious > > https://tracker.debian.org/pkg/stimfit > > Issues preventing migration: > ∙ ∙ Autopkgtest for stimfit/0.17.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: > Failed ♻, loong64: Failed ♻, ppc64el: Failed ♻, s390x: Failed ♻ > > > ... > 166s autopkgtest [05:24:10]: test stimfit-help: [----------------------- > 167s 05:24:11: Error: Unable to initialize GTK+, is DISPLAY set properly? > 167s autopkgtest [05:24:11]: test stimfit-help: -----------------------] > 167s autopkgtest [05:24:11]: test stimfit-help: - - - - - - - - - - results > - - - - - - - - - - > 167s stimfit-help FAIL stderr: 05:24:11: Error: Unable to initialize > GTK+, is DISPLAY set properly? > ... > 167s autopkgtest [05:24:11]: @@@@@@@@@@@@@@@@@@@@ summary > 167s python3-stfio-import PASS (superficial) > 167s stimfit-help FAIL stderr: 05:24:11: Error: Unable to initialize > GTK+, is DISPLAY set properly?
