#1120354 stumpwm: Stumpwm does not compile. Event code 0 not implemented for display.

Package:
stumpwm
Source:
stumpwm
Submitter:
Johannes Strelka-Petz
Date:
2026-01-02 01:51:03 UTC
Severity:
normal
Tags:
#1120354#5
Date:
2025-11-07 17:19:03 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
     upgrade from bookworm to trixi
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Resolved by manual upgrade of clx at least version 0.7.6
     Building clx from https://github.com/sharplispers/clx using ASDF
     This issue appears from sbcl-2.4.6-103-g9e354f04e, when SBCL's read-sequence was corrected.
     clx from 0.7.6 handles this and works with SBCL 2.4.6 as well.
     see https://github.com/stumpwm/stumpwm/issues/1201
   * What was the outcome of this action?
     stumpwm compiles and starts
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

#1120354#10
Date:
2025-11-08 12:27:15 UTC
From:
To:
Johannes Strelka-Petz <johannes@oskars.org> writes:

I have (just) rebuilt stumpwm in a trixie environment using

  sbuild --chroot-mode unshare -d trixie stumpwm_22.11-3.dsc

So it doesn't "ftbfs" in the usual Debian definition, since the source
package is able to generate the binary packages in the environment used
by the autobuilders.

If I understand correctly there may is some issue recompiling a
customized/configured stumpwm in your environment. It would be helpful
if you could give a recipe to reproduce the problem starting with a
minimal Debian install.  Some kind of container / chroot may be helpful
for testing that recipe.

All the best,

David

#1120354#19
Date:
2025-11-09 11:44:16 UTC
From:
To:
Ahoj!

Sorry for my inaccurate description of the error.
The error does not arise when compiling the source code but when sbcl is
building stumpwm for the first time after a packet upgrade.
I do not know what this lisp building is realy called or does exactly.
I have no customized/configured stumpwm but
vanilla stumpwm version 2:22.11-3 from trixie.

I think the problem exists not only for me because stumpwm issue 1201
reports that sbcl version =>2.4.6 does not work with
clx version <0.7.6.
https://github.com/stumpwm/stumpwm/issues/1201

Trixie provides stumpwm with sbcl version 2.5.2 and cl-clx-sbcl version
0.7.5 which do not work together.
clx does also not work under trixie which stumpwm depends on.
The depencies are not met for clx and stumpwm.
Is stumpwm or clx running under trixie on your system?

Best regards
Johannes Střelka-Petz

#1120354#26
Date:
2026-01-02 01:48:34 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
cl-clx-sbcl, 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 1120354@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benda Xu <orv@debian.org> (supplier of updated cl-clx-sbcl 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: Fri, 02 Jan 2026 00:30:38 +0900
Source: cl-clx-sbcl
Architecture: source
Version: 0.7.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team <debian-common-lisp@lists.debian.org>
Changed-By: Benda Xu <orv@debian.org>
Closes: 1110774 1120354
Changes:
 cl-clx-sbcl (0.7.7-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1110774, #1120354)
     + Thanks to <prd.stee@gmail.com> for the report.
     + Thanks to Johannes Strelka-Petz <johannes@oskars.org>.
   * Drop {clos,sbcl,8bit,asdf}.patch as they no longer apply.
Checksums-Sha1:
 a12ca8ae2960ae6f11725227aafc14ba2957fc1b 1978 cl-clx-sbcl_0.7.7-1.dsc
 bfbb6b2b1152498da2215657961eea3b653bfb8e 462809 cl-clx-sbcl_0.7.7.orig.tar.gz
 6aeb466fd97c877462c185048e6468c91a672b92 4096 cl-clx-sbcl_0.7.7-1.debian.tar.xz
 7229e7bf02554ede9e44b7e75eac36e75c4bfe56 7168 cl-clx-sbcl_0.7.7-1_source.buildinfo
Checksums-Sha256:
 054157d5ea387c543af20044955bf9c0bad999fa80b3a0256e30401f1ff5079d 1978 cl-clx-sbcl_0.7.7-1.dsc
 51c62d2fdd75c1390b940b0ded16880d378ecf8b5c556917611f4804dcadf981 462809 cl-clx-sbcl_0.7.7.orig.tar.gz
 d6ca7e7819c31d49c6ba68af475c6be49b722340e6d97cd6799430f48f258c2c 4096 cl-clx-sbcl_0.7.7-1.debian.tar.xz
 87abb8eb4ec1bc11e4e8df0bdca86ada2303e89d8d6980a307812a2a8b42372a 7168 cl-clx-sbcl_0.7.7-1_source.buildinfo
Files:
 8144e78aaadbf4ebc0feac316bc8b5e9 1978 lisp optional cl-clx-sbcl_0.7.7-1.dsc
 4f9ec9e92d4fe23375262a56c2fa9809 462809 lisp optional cl-clx-sbcl_0.7.7.orig.tar.gz
 8c785f13e558e5032dfc720f2e8c28ea 4096 lisp optional cl-clx-sbcl_0.7.7-1.debian.tar.xz
 c98b932bc50580cf441a7587206d7175 7168 lisp optional cl-clx-sbcl_0.7.7-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEENTS8ZhMowhj4Iw2H33YQtSHxcSIFAmlXH7MPHG9ydkBkZWJp
YW4ub3JnAAoJEN92ELUh8XEih3kP/iz53Fzc39A0DZBSkIOm0B9JWGg7WvLqSDLW
2UCK5eqWJ1xABIqigvJZxlEu9x8DPwDj8PBR11CzRgPjpNfdKQHn3lIfT6ttyTIF
1iWMdV1NYINniIt74YQFOTQOP9f7Tfwk5MyzOG3U+57d/ONrInB0M3qge7A8opKR
xR3gTdI4qm2pZmM+UrKVtiwM2oPl381RDFjl69RtUSi7vvCP6RNbq6CNIRXRMjPn
KTd+nJQnLrUKPH2PZGdwt//kE/96zf3nCmg2vPiZYDrVvm8OXB6sT9J7jeTwUZO7
1WHvCc50ilguXKTs66lN+ZRsy8uO4uUL0MCC4OBRgo5jhkNwk6luY/DnnhRW6UWl
1qoofW0vt7zPoRyOWFy/sPRBqdzNx+jLfNDqAq88JdrVKwXZu5SC7E96ld0oqm6G
UPsy5yrPmBDa0bUSiwsfI4Ho9iaAJq8kb7ZHs7nLUknWIKLuyigktFHjXo0MZbfF
0630yCwcWIncUJu/wBZaN0EutL94N1126KMxravAkZ9whxnuipeTW0JedI0/SioI
O32sZE91JGQRai8l3f08Jv+cbZsAb2ATidyAqupzJnB9TniFusloSH8qHN6R6V2Z
Xok1WHzxXmeXphkH0qY+mvXH7R6qX5l2DmcQ6I4UhUY+B5DF3Blm/kOCP7TYm8Zz
DImDgHRd
=CSGh
-----END PGP SIGNATURE-----