[From nobody Tue Sep 22 12:41:06 2026
Received: (at submit) by bugs.debian.org; 19 Sep 2026 22:17:26 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-14.9 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,FOURLA,HAS_PACKAGE,SPF_HELO_NONE,SPF_PASS
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 47; hammy, 150; neutral, 170; spammy,
 0. spammytokens: hammytokens:0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian, 0.000-+--forky, 0.000-+--HTo:N*System,
 0.000-+--HTo:N*Bug
Return-path: &lt;vincent@vinc17.net&gt;
Received: from joooj.vinc17.net ([155.133.131.76]:49534)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;vincent@vinc17.net&gt;) id 1x83N7-006Zu9-0c
 for submit@bugs.debian.org; Sat, 19 Sep 2026 22:17:26 +0000
Received: from smtp-qaa.vinc17.net (135.197.67.86.rev.sfr.net [86.67.197.135])
 by joooj.vinc17.net (Postfix) with ESMTPSA id 15A7B444;
 Sun, 20 Sep 2026 00:17:22 +0200 (CEST)
Received: by qaa.vinc17.org (Postfix, from userid 1000)
 id 7B1ABCA0158; Sun, 20 Sep 2026 00:17:21 +0200 (CEST)
Date: Sun, 20 Sep 2026 00:17:21 +0200
From: Vincent Lefevre &lt;vincent@vinc17.net&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: glycin-loaders: makes viking hang on startup
Message-ID: &lt;20260919221721.GA147643@qaa.vinc17.org&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Reportbug-Version: 13.2.0+nmu1
X-Mailer-Info: https://www.vinc17.net/mutt/
User-Agent: Mutt/2.4.2+43 (ecf9b675) vl-188789 (2026-09-06)
Delivered-To: submit@bugs.debian.org

Package: glycin-loaders
Version: 2.2.1+ds-1
Severity: grave
Justification: renders package unusable

The upgrade of the glycin packages to 2.2.1+ds-1 always makes
viking hang on startup. This is a major regression.

In a strace output, I can see

151847 00:11:54 (+     0.000287) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80659, tv_nsec=881834125}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:54 (+     0.500649) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80660, tv_nsec=382410768}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:55 (+     0.500440) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80660, tv_nsec=882825665}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:55 (+     0.500688) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80661, tv_nsec=383470261}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:56 (+     0.500539) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80661, tv_nsec=884106115}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:56 (+     0.500612) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80662, tv_nsec=384631909}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:57 (+     0.500495) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80662, tv_nsec=885167417}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:57 (+     0.500620) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80663, tv_nsec=385768879}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:58 (+     0.500363) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80663, tv_nsec=886256775}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
151847 00:11:58 (+     0.500546) futex(0x7fd93969e018, FUTEX_WAIT_BITSET_PRIVATE, 16, {tv_sec=80664, tv_nsec=386709411}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out)
[...]

where the pid 151847 is one of the viking threads. But this issue
was introduced by the upgrade of the glycin packages:

viking depends on these packages via the libgdk-pixbuf-2.0-0
package.

Currently in unstable, libgdk-pixbuf-2.0-0 is at version
2.44.8+dfsg-1, which depends on libglycin-2-0 (&gt;= 2.2~beta.1).

Downgrading libgdk-pixbuf-2.0-0 (and the other packages of the
same source) to 2.44.7+dfsg-1 does not solve the problem. Also
downgrading the packages of glycin source to 2.1.5+ds-2 makes
the problem disappear.

Note that due to the above dependency, I could not downgrade
the packages of glycin source without libgdk-pixbuf-2.0-0.

-- System Information:
Debian Release: forky/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages glycin-loaders depends on:
ii  bubblewrap       0.12.0-1
ii  libc6            2.43-5
ii  libcairo2        1.18.4-3
ii  libgcc-s1        16.2.0-2
ii  libglib2.0-0t64  2.90.0-1
ii  libheif1         1.23.4-1
ii  libjxl0.11       0.11.2-5.1
ii  librsvg2-2       2.62.1+dfsg-1

Versions of packages glycin-loaders recommends:
ii  libheif-plugin-aomenc  1.23.4-1
ii  libheif-plugin-dav1d   1.23.4-1

Versions of packages glycin-loaders suggests:
ii  libheif-plugin-libde265  1.23.4-1
ii  libheif-plugin-x265      1.23.4-1

-- no debconf information

-- 
Vincent Lefèvre &lt;vincent@vinc17.net&gt; - Web: &lt;https://www.vinc17.net/&gt;
100% accessible validated (X)HTML - Blog: &lt;https://www.vinc17.net/blog/&gt;
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
]