[From nobody Tue Sep 15 14:47:06 2026
Received: (at submit) by bugs.debian.org; 13 Sep 2026 23:46:49 +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=-16.0 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FOURLA,
 FREEMAIL_FROM,GMAIL,HAS_PACKAGE,NML_ADSP_CUSTOM_MED,NO_RELAYS,
 XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 150; neutral, 128; spammy,
 0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*Ad:N*Bug, 0.000-+--HTo:N*Debian,
 0.000-+--forky
Return-path: <dankamongmen@gmail.com>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <dankamongmen@gmail.com>) id 1x5tuK-00H3xv-3C
 for submit@bugs.debian.org; Sun, 13 Sep 2026 23:46:49 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Nick Black (Public gmail account)" <dankamongmen@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libgdk-pixbuf-2.0-0: glycin decodes fail without CONFIG_SECCOMP in
 kernel
Message-ID: <178934320611.2192258.12580935579555317887.reportbug@schwarzgerat.orthanc>
X-Mailer: reportbug 13.2.0+nmu1
Date: Sun, 13 Sep 2026 19:46:46 -0400
Delivered-To: submit@bugs.debian.org

Package: libgdk-pixbuf-2.0-0
Version: 2.44.7+dfsg-1
Severity: normal
X-Debbugs-Cc: dankamongmen@gmail.com

This is probably something to submit upstream, but I'm unsure.

Following a recent reboot, my Wayfire compositor was unable to load the
panel or set a background. I couldn't coax much debugging from them, but
traced it down to a "bwrap" subprocess. I then noticed various apps were
failing, including reportbug. I was finally able (using strace) to find
a failed seccomp call in libglycin's decoders. I rebuilt my kernel with
CONFIG_SECCOMP enabled, and everything worked.

CONFIG_SECCOMP is enabled in the default Debian kernel, but I don't
think building without it is that rare.

In my ideal world, gdk would fall back on some other decoding mechanism
in the absence of kernel seccomp support. I anticipate that this might
be a non-starter either for security or implementation cost reasons. In
that case, it would at least be nice to get obvious and clear failure
diagnostics. This latter choice is most likely done in libglycin itself.

Feel free to reassign this as you see fit.


-- System Information:
Debian Release: forky/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.2.5nlb2 (SMP w/64 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgdk-pixbuf-2.0-0 depends on:
ii  glycin-thumbnailers      2.1.5+ds-2
ii  libc6                    2.43-5
ii  libgdk-pixbuf2.0-common  2.44.7+dfsg-1
ii  libglib2.0-0t64          2.90.0-1
ii  libglycin-2-0            2.1.5+ds-2
ii  shared-mime-info         2.4-5+b3

libgdk-pixbuf-2.0-0 recommends no packages.

libgdk-pixbuf-2.0-0 suggests no packages.

-- no debconf information
]