You are not logged in.
As per the title, I have a problem with stumpwm version 23.11-4 and later, where they simply crash when started. 23.11-3 works fine.
I'm running Arch on three different machines: an AMD/nvidia desktop, an Intel-based desktop, and an Intel-based laptop. All three have the same problem.
Some configuration files are shared between the machines, but I have at least tried to remove my custom stumpwmrc, to no effect.
Anyone else have this problem? I appreciate any help!
Last edited by nbqr (2025-04-01 20:12:05)
Offline
What errors do you get when you run the application through terminal.
Offline
Also https://wiki.archlinux.org/title/Core_d … _core_dump
https://wiki.archlinux.org/title/Debuginfod will be additionally helpful.
Online
Thanks for the help. This is the output I get when I run startx (some unrelated stuff removed):
X.Org X Server 1.21.1.16
X Protocol Version 11, Revision 0
Current Operating System: Linux arch 6.13.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 17:17:30 +0000 x86_64
Current version of pixman: 0.44.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/nbqr/.local/share/xorg/Xorg.1.log", Time: Tue Apr 1 17:05:34 2025
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86RefreshRateToggle
> Warning: Could not resolve keysym XF86Accessibility
> Warning: Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86RefreshRateToggle
> Warning: Could not resolve keysym XF86Accessibility
> Warning: Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
Agent pid 3308
Unhandled XLIB::UNIMPLEMENTED-EVENT in thread #<SB-THREAD:THREAD tid=3301 "main thread" RUNNING
{1001320003}>:
Event code 0 not implemented for display #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)>
Backtrace for: #<SB-THREAD:THREAD tid=3301 "main thread" RUNNING {1001320003}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<XLIB::UNIMPLEMENTED-EVENT {1001820F13}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<XLIB::UNIMPLEMENTED-EVENT {1001820F13}>)
2: (INVOKE-DEBUGGER #<XLIB::UNIMPLEMENTED-EVENT {1001820F13}>)
3: (CERROR "Ignore the event" XLIB::UNIMPLEMENTED-EVENT :EVENT-CODE 0 :DISPLAY #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)>)
4: (XLIB::GET-INTERNAL-EVENT-CODE #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> 50)
5: (XLIB::READ-EVENT-INPUT #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> 50 #S(XLIB::REPLY-BUFFER :SIZE 32 :IBUF8 #(50 62 0 0 66 0 0 0 37 105 0 0 ...) :NEXT NIL :DATA-SIZE 32))
6: (XLIB::READ-INPUT #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> NIL NIL #<FUNCTION (LAMBDA (XLIB::PENDING-COMMAND) :IN XLIB::READ-REPLY) {B80014701B}> #S(XLIB::PENDING-COMMAND :SEQUENCE 17 :REPLY-BUFFER NIL :PROCESS #<SB-THREAD:
THREAD tid=3301 "main thread" RUNNING {1001320003}> :NEXT NIL))
7: (XLIB::READ-REPLY #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> #S(XLIB::PENDING-COMMAND :SEQUENCE 17 :REPLY-BUFFER NIL :PROCESS #<SB-THREAD:THREAD tid=3301 "main thread" RUNNING {1001320003}> :NEXT NIL))
8: (XLIB:KEYBOARD-MAPPING #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> :FIRST-KEYCODE NIL :START NIL :END NIL :DATA NIL)
9: (XLIB::DISPLAY-KEYBOARD-MAPPING #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)>)
10: (XLIB:KEYSYM->KEYCODES #<XLIB:DISPLAY :1 (The X.Org Foundation R12101016)> 65511)
11: ((LABELS STUMPWM::FIND-MOD :IN STUMPWM::GET-MODIFIER-MAP) "Meta_L" NIL)
12: (STUMPWM::GET-MODIFIER-MAP)
13: (STUMPWM::UPDATE-MODIFIER-MAP)
14: (STUMPWM::STUMPWM-INTERNAL ":1")
15: (STUMPWM:STUMPWM ":1")
16: ((LAMBDA NIL :IN "/build/stumpwm/src/stumpwm/make-image.lisp"))
17: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP))
18: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::START-LISP))
19: (SB-IMPL::%START-LISP)
unhandled condition in --disable-debugger mode, quitting
xinit: connection to X server lost
^M
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.I believe this is a problem upstream, there is an issue on the stumpwm Github page that seems to be the exact same problem. Indeed, the last version of stumpwm that works for me is built with SBCL version 2.4.6, as mentioned in the thread; the newer (broken) versions are built with later versions of SBCL.
Should I report this to the maintainer of the Arch package of stumpwm?
Offline
If I understand the upstream bug correctly, you need an update for https://archlinux.org/packages/extra/any/cl-clx/
The current version seems to be the slightly dated https://github.com/sharplispers/clx/com … abe31c8724
Online
Thanks for your help, seth. I think I will wait for an update of the cl-clx package in extra, I'm not in any hurry to get the latest version of the WM. Marking as solved for now.
Offline
Given the pace of the updates (the current clx commit in the repos is from 2022) I'd probably flag it out of date and point at the stumpwm (its only consumer) bug.
Online
I will do that!
Offline