<malaclyps>okay so I did guix system build ~/system.scm (which is where my system configuration is held). It gave me a gnu store directory, and I did "find -L . -name "*libwacom*" in that store directory, to no result. Is there another way I should be checking to see whether that system has a non-empty libwacom?
<leoprikler>it appears the system does not reference libwacom directly, but indirectly
<malaclyps>I originally found the problem by diffing the X windows log, where Xwindows errors from "Failed to load /gnu/store/29gkxw93z6nj7ki2yswf8wggzlxvycsg-xf86-input-libinput-0.28.2/lib/xorg/modules/input/libinput_drv.so: /gnu/store/1iy0fwk1hmvangichipg9kh9pwynl40y-libwacom-1.1/lib/li bwacom.so.2: file too short "
<malaclyps>i mean, really what I want/need to do is to rebuild the bad libwacom directory, but guix build --repair doesn't seem to be doing that
<malaclyps>let's see what sudo guix build --repair libwacom --no-substitutes does
<leoprikler>--no-substitutes does not do what you want, probably
<leoprikler>you will have to build everything from scratch, which is overkill
<malaclyps>yes, apparently I am starting with building ghostscript :)
<malaclyps>so, what I think we've established is that this my wacom /gnu/store/1iy.../ does not contain what yours contains, and is corrupt. But guix build --repair does not recreate a new, correct version. This seems like it should not happen under guix.
<leoprikler>tbh I'm not quite sure what repair actually does
<leoprikler>try --repair together with --check -- the latter forces rebuilding afaik
<leoprikler>To clarify what this does: this generates the missing goa-1.0.vapi file. That file appears to not be installed alongside goa-1.0 for some reason (probably because we don't want a vala dep inside there).
<elais[m]>Has anyone had trouble running Wayland? Everytime I select a Wayland session from the sddm menu the cursor turns to an x and can move but the screen doesn't leave the login. I feel like I'm missing something.
<elais[m]>On tty7 I see a blinking cursor. Does sddm start the session on tty 7?
<atw>hmm ok less helpful than I had hoped. My guess is that the cursor with an x is actually an X11 session and that wayland has not launched.
<atw>at one point I was trying to go totally X11-less. I had system config like (packages (list weston wayland ...)) (services (list (sddm-service (sddm-configuration (display-server "wayland")))) ...)
<gnutec>I upgrade Freedoom (guix package -u openttd minetest freedoom) and when I start, the command returns incompatible with "The Ultimate DOOM". Is it the "prboom"? Should I reinstall, or use other alternative?
<oriansj>samplet: actually with stage0; is is straight bootstrap from a 357byte hex0 using unpacked sources until you get to mes-m2 and then one could simply provide an unpacked gzip/tar scheme program(s) to do the rest from there
<roelj>So, when I try to run a Docker image created with "guix system docker-image ..." it fails with "failed to start service 'host-name'", even though I only added one service to the services list (I even excluded %base-services).
<roelj>How is the created image supposed to be run?
<jje>how are we supposed to run opensmtpd as a service? i have it configured as a service but shepherd always says it is stopped. when i run "sudo herd start smtpd" herd says "failed to start smtpd. are the some shepherd logs i should consult? and when i run "sudo smtpd" from the command line it starts right up. what am i doing wrong?