It’s hard to say without knowing more details, could have been fault in the package recipe of your linux distrobution, or with StumpWM. I did have something similar happen, but it was fault with the specific package recipe in Guix, which has since been fixed. I got it to work, by frantically looking through guix issues and luckily someone had posted a workaround/hack.
I’m back to Guix/Guile after getting lost in the woods with Common Lisp - it’s all a very fun learning journey, but the beauty of Guile is unsurpassed in my mind.
Came back to my Guix config deploying StumpWM - looking for a Guile-based WM for Wayland that can take StumpWM’s place, but in the time being I’ve updated my StumpWM config to be the best it’s been, ever!
Hosted on my Codeberg account to be in the same ecosystem as Guile and Guix now.
This Guix/StumpWM configuration is installed on my Framework Laptop 13 AMD Ryzen AI 300 Series (for the curious).
1 Like
May it is because we still miss a Common Lisp system like Guix. If Guile works, Common Lisp should also work.
Much envy here - I’m just to poor and have to be content with second hand ThinkPads 
I’m back to Guix/Guile after getting lost in the woods with Common Lisp - it’s all a very fun learning journey, but the beauty of Guile is unsurpassed in my mind.
Can you elaborate?
I get it, I was there as well - though my second hand ThinkPad was on it’s last legs. I saved up for a year to get this - perhaps I could have spent my money more wisely…
I was just focusing more on Common Lisp and not using Guix or any Guile for a while. I just find Guile Scheme syntax to be more aesthetically pleasing and I couldn’t live without Guix. I have since switched from StumpWM to EXWM.
1 Like