<janas>I have guixSD installed on a x200T and I'm running into an issue where the system freezes after waking up from suspend to RAM. The screen shows my desktop but no input devices work, and the SysReq key has no effect.
<janas>I'm not super knowledgable about this so any ideas would be appreciated. I'm using XFCE
<pkill9>janas: possibly a conflict between xfce trying to handle suspending and elogind handling suspending
<pkill9>you can disable xfce from handling suspending, can't remember how
<pkill9>might not be the same issue though, the issue im thinking of is specifically handling suspendin via closing the lid
<janas>pkill9: Thanks for the tip, I'll look into it. I just realized that my installation was a few weeks out of date so I'm going to try updating it first
<reepca>anyone have any tips on why luatex would be silently exiting with status 127 in the build environment? tried looking it up and it seems to indicate that a command wasn't found or something, but you'd think it would print some sort of message at least, right?
<sneek>civodul, apteryx says: with my patch, I can see that the dbus-configuration used by my system generation contains a system-local.conf file which has a new entry: <includedir>/gnu/store/gw3ckmw2pihc44d23lc8pipfw7wr16g7-network-manager-openvpn-1.8.0/etc/dbus-1/system.d</includedir>
<g_bor>:) yes, but these are handled currently in one pass, packing without compression.
<g_bor>Do you think it would worth to separate these?
<g_bor>like: 'reset-zip-timestamps, then 'disable-jar-compression ?
<rekado>ci.guix.info does have a substitute for /gnu/store/blmkj5wxnw19zqjc17jrfh8l2ap8xigq-python-minimal-3.7.0.drv | /gnu/store/qws8zsa0mm1d7jwlcrg4rr9rmhip30av-python-minimal-3.7.0, but chooses not to deliver it.
<rekado>sound-libraries.scm could provide portmidi and solve this totally made-up problem.
<g_bor>rekado: before I came around guix I was planning to create my own package manager. I came up with a structure where the packages had their individual modules. It meant more files, but having a mode simple module structure, as the module graph became a DAG, getting rid of the circular dependencies.
<g_bor>It also commes with it's own problems, but somehow the benefits were appealing...
<rekado>having one module per package is probably better in the long run, but what I don’t like about this is the boilerplate.
<rekado>it just seems like a lot more effort to write packages with a big module header and all the duplication of modules and package inputs.
<rekado>this could be avoided with a few extra features, so that these files would not be plain Guile modules
<g_bor>rekado: we could discuss this at the Guix days. Also it would be interesting to find out how to transition there without too much pain...
<civodul>too many files is not good for i/o, see Nixpkgs...
<rekado>with future Guile versions one could compile all these tiny modules into a bigger file.
<rekado>I’ll leave the audio question alone for now and work on something easier like removing game-development from the coreutils module closure.
<rekado>what do you think about separating emacs from emacs packages?
<rekado>I wanted to add (gnu package emacs-packages) first
<rekado>because the dependencies of emacs are probably fewer than those of all possible emacs packages that end up in the same module.
<jonsger>what is the exact purpose of separating those modules?
<rekado>reducing dependencies between modules, thereby reducing the number of modules that need to be compiled / interpreted for “guix pull”
<jas4711>civodul: yes, probably, but i have the nss-certs package installed so something else is missing. i'll try to strace it to see what's happening
<g_bor>rekado: I have seen three or more layers of packages, which usually goes like this, in a per language categorization context: bootstrap: a complier, a standard library, a build tool; development tools: most usually commonly used modules of the build tool, test frameworks, linters and the like; and finally the packages as the top layer.
<civodul>jas4711: it's installed globally? i.e., can you see it in /etc/ssl/certs?
<rekado>g_bor: yes. I’d like to separate these layers.
<rekado>g_bor: wanted to do this for java already.
<rekado>(but got stuck distracted with rewriting the bootstrap)
<Swedneck>rn it's just in the system profile, or whatever it's called. /gnu/store
<pkill9>i wouldn't add my package to your profile cos i have wrapped it such that it finds the assets folder, but if you wanted to install it then you would run `guix package -f <module file>` or add my repository as a channel and run `guix package -i marblemarcher`
<Swedneck>thank christ i've used ipfs so i have some slight reference for how gc works
<Swedneck>but if i just wanted to remove the symlinks, what command would i use?
<pkill9>if you want to uninstall a package from a profile, you run `guix package -r <package>`, or if you just installed it you can run `guix package --roll-back` to switch to the previous 'generation' of the profile
<davidl>I was able to download and run guile-bash successfully on my GuixSD install, but when run on PureOS with Guix installed only as a package manager it fails. When I make sure the GUILE_LOAD_PATH is correct, I get this error: bash: symbol lookup error: /gnu/store/pc00g13djrdi5gdp4nbcgmd6qbbn2k5j-guile-bash-0.1.6-0.1eabc56/lib/bash/libguile-bash.so: undefined symbol: sh_xfree
<davidl>I think it's related to linked libraries and perhaps the LD_LIBRARY_PATH, but don't know for sure or what to try do about it.
<bgardner>Hello guix, getting this on a fresh EFI install: /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install: error: /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
<bgardner>guix system: error: failed to install bootloader /gnu/store/ggiq6y4wniqgpc8yn7s0c9hf94xm597v-bootloader-installer
<bgardner>This was right at the end of the copy to /mnt step
<bgardner>Ah, rats. /boot/efi isn't mounted. I bet that's why, my bad. Let me fix that and retry.
<THFKA4>make sure you're booted in EFI mode, my BIOS did not default to it for removable media
<bgardner>THFKA4: Interesting notion. It's about the same spot, so if it dies again I'll check that next, thank you.
<bgardner>Soo, dumb question: During a standard EFI install, should I create /mnt/boot/efi for the empty mountpoint or will that be handled by the guix system init call?
<pkill9>you have to create the directory and mount it yourself yeah
<bgardner>I did at /boot/efi (since the config file refers to it by that name and not by device), my question is do I also need to create the empty folder under /mnt/boot/efi so on reboot it exists to be mounted? The instructions seem a bit unclear.
<pkill9>yeah, but it doesn't need to be mounted to boot
<pkill9>but you'd get an error if you tried to mount to nonexistent directoyr anyways