<leoprikler>but it shouldn't: gdk-pixbuf+svg is propagated by gtk
<iskarian>I don't recall if it was posted yet, but if not, evince generates this message when started from command line: Gtk-WARNING **: 15:51:10.567: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg.
<iskarian>This may indicate that pixbuf loaders or the mime database could not be found.
<iskarian>of course, it also has a broken icon (a pencil icon) and that's not generating any error messages, so... *shrug*
<leoprikler>for the record, both icons work fine for me outside a pure environment
<leoprikler>so something within the gnome package makes things work
<apteryx>what is the (gnu packages xdisorg) module meant to contain? What does 'xdisorg' mean?
<apteryx>Seems like a distribution of non-core x11 packages
<apteryx>perhaps it would be better named as xorg-xyz.scm for consistency
<apteryx>although if it stands for a 'disorganized collection of x11 related packages' I like the pun.
<apteryx>leoprikler: beware that if both gdk-pixbuf+svg and gdk-pixbuf (sans svg) are propagated, you can't really be sure which one will be picked. Better check with ldd what is being used.
<apteryx>(I see gdk-pixbuf propagation as a bug, if there are instances of it remaining)
<raghavgururajan>I now get "Exception in thread "main" java.lang.RuntimeException: Could not create parent directory for lock file /.gradle/wrapper/dists/gradle-5.5-all/66q2j3qadt42ygj9lkubqor18/gradle-5.5-all.zip.lck"
<g_bor[m]>Hmm... does it really try to create /.gradle ?
***iskarian_ is now known as iskarian
<raingloom>okay, i can't figure this out. how do you run an executable inside a service with all the environment variables that would be set if you used it inside guix environment?
<ss2>hi! So I've got a package decleration, that inherits from another package decleration. How can I put it into the system profile to be widely available -- without needing to push into a local channel repository?
<raingloom>ss2: you can use the --load-path option or the GUILE_LOAD_PATH environment variable to use a local channel, or just whatever guile module tree you need
<abcdw>describe-package and list-packages for some reason doesn't show packages installed by guix. package-directory-list value equal to "/home/bob/.guix-home-environment/profile/share/emacs/site-lisp/elpa", which seems correct (the directory contains all symlinks to necessary packages).
<raghavgururajan>Exception in thread "main" java.lang.RuntimeException: Could not create parent directory for lock file /.gradle/wrapper/dists/gradle-5.5-all/66q2j3qadt42ygj9lkubqor18/gradle-5.5-all.zip.lck
<mdevos>raghavgururajan: is that /.gradle/wrapper/..., or /some/directory/.gradle/wrapper?
<mdevos>I don't think the java program has write access to /.gradle
<vagrantc>fwiw, i did test building 1.3.0rc2 on debian, but nothing really new so will wait till release to do another upload to debian experimental
<vagrantc>what's the syntax for referencing a specific part of info pages? e.g. if i want to reference info:guix ... on guix-daemon ?
<lfam>I've been building the arm64 linux-libre generic source tarballs "by hand" on the build farm central node. That way they offload to a real aarch64 machine instead of randomly selected an emulated builder which can't complete the task quickly enough
<lfam>I guess it makes sense based on the package description: "It optimizes resource utilization by not depending on any external libraries and instead utilizing features provided by the Linux kernel to the maximum extent possible."
<leoprikler>I have a swap partition setup, but it's not found on boot
<lfam>jbv1[m]: If you aren't comfortable with Git, just send whatever files you made as an email attachment to <email@example.com> and mention that you don't know how to use Git yet. The reviewer will clean it up for you
<leoprikler>manually resuming worked out somehow, but UX=1/10
<nckx>leoprikler: I think the basic steps to go from zero to hibernation hero are (1) add your swap device as ‘resume=/dev/swap0’ to your kernel-arguments (2) reboot. You could add that to the manual somewhere. I'm a bit nervous about it: the possibility for data loss is real.
<nckx>Adding resume=<first swap device> by default is... risky. I don't remember off-hand which heuristic the kernel uses (I use my own fork), and it could easily suspend to a different partition instead.