IRC channel logs
2025-07-01.log
back to list of logs
<cancername_>It would be awesome if someone could help me figure out what's going wrong her. <cancername_>I did check the web, but all past issues of the sort seem unrelated. <cancername_>okay, something else is definitely wrong. guix describe shows a guix that is definitely not the one I had prior to rebooting <cancername_>when listing PATH, ~/.guix-home/... is present. shouldn't ~/.guix-profile be as well? <cancername_>after setting my PATH such that guix points to ~/.config/guix/current/bin/guix, I got a "proper" guix instead of /run/current-system/profile/bin/guix. why did I have to do that? isn't guix home supposed to set PATH appropriately? <cancername_>it's worth noting that I use fish, but even running bash -i results in a broken PATH. <cbaines>I'm going to turn off qa.guix.gnu.org for a bit as I still can't work out why data.qa.guix.gnu.org isn't working <cbaines>civodul, I can't figure it out yet, maybe the fibers thread(s) are stuck in some kind of loop, or maybe the GC is just running over and over again <bdju>Is there anything packaged for easily sending a magic packet to wake up a machine on the LAN? I've read about etherwake and wakeonlan but I don't see them packaged. <noe>bdju, try package wol <jakef>lilyp: I'm revisiting that matplotlib issue #70687. do you know if there's bug report upstream? <wingo>guix. i upgraded recently and now my compose key is not working. gnome, wayland. what could that be, i wonder? <wingo>it would seem that pressing the right alt, which is marked as my compose key, seems to toggle the keyboard into some other mode <wingo>i want to compose = e -> euro symbol <wingo>hmm, it seems it was a weird interaction between dead keys and compose <wingo>switching to a layout without dead keys seems to have done the job <vntsuyo>can I make a root service depend/require a home service? <noe>vntsuyo, I don’t think so since they run in two different instances of shepherd <vntsuyo>noe: i see, i'll find a workaround then