<raingloom>heyy, so, i'm refactoring my machine configs to use declarative modules, and for some reason this doesn't work: guix system vm --load-path="/whatever" --expression="(use-modules (raingloom machines some-hostname)) some-hostname"
<raingloom>some-hostname **is** defined as a public symbol and i can see it in a REPL and it **is** an operating-system object
<raingloom>(also it kinda sucks that (use-modules) doesn't work now. i had some conditionally loaded modules. but eh, i won't miss it too much.)
<raingloom>well, the module file also returns some-hostname at the end, so i guess i can just use it like that, but it sucks big time that now i can't parameterize my OS.
<jeko>How did I end up with many nginx processes running ?!
<PotentialUser-44>it just freezes there and nothing happens. I also got same issue when booting GuixSD install from USB but it worked after a few reboots.
<PotentialUser-44>Hardware is AMD Ryzen Pro 1300, RX560 GPU, ASrock A320M HDV R4 and I'm booting through UEFI
<helaoban>ok so I understand that I need to specify the "lib" output of gcc in order to have that link. Why is libstdc++ factored out into a separate output?
<bdju>is anyone else using quaternion on guix system? clicking links doesn't open them in the default browser I have configured for xdg-open. also, I don't know how to set a dark theme.
<mroh>bdju: I thought, I have fixed this xdg-open issue maybe a week ago or so. Is this on a recent system?
<bdju>mroh: (fyi, I'm the one from the matrix channel) I don't think xdg-utils missing as a dependency was the problem since that was already on my system. it seems more like the normal xdg config isn't being applied.
<bdju>btw, which browser do you use? I wonder if what you use is in the list of default browsers to try, whereas I'm using qutebrowser which definitely isn't (but it *is* configured as my default and working with other programs)
<bdju>oh, and as for the recency of my system, I maybe haven't updated in a few days
<PotentialUser-35>Hello, I just installed the 32bit version and instead of a login screen I get. "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator."
<PotentialUser-35>When I looked at the logs /var/log/gdm/greeter.log There's this error that spawns others. (.gnome-shell-real:338): Clutter-Critical **: Unable to initialize Clutter: Unable to initialize the clutter backend: no available drivers found
<mange>If you want to use %desktop-services (which includes gdm) you can use something like the example in "(guix) Using the Configuration System" in the manual, at the end of the "System Services" section.
<mange>You can remove the gdm-service-type from your system, so then you can add sddm without any potential for conflict.
<bdju>do any other qutebrowser users here have issues with sites using those cloudflare checks? they seem to loopp forever instead of completing after "5 seconds", so a bunch of sites are inaccessible
<vagrantc>it should only say that if the file is present
<zimoun>what is the best? Add a Debian-like patch to linux-libre allowing the thing or only fix the Guix error message?
<vagrantc>guix has the feature enabled out-of-the-box ... in Debian the file is always present, disabled by default (the patches are to make it enableable at run-time rather than kernel build time) ... not sure about CentOS
<vagrantc>but i would only have guix mention that file if it is present and set to 0
<vagrantc>feel free to quote me on any bug report; i'm not following them directly
<vagrantc>if the file is not present, it is either running a kernel that supports it out of the box, or a kernel that has it disabled and there's no reason to enable it ... or CentOS's patches are different from Debian/Ubuntu and need to detect some other way
<vagrantc>s,no reason,no way short of recompiling,
<zimoun>vagrantc, thanks. I am not sure to come with something but now the issue appears clear. :-)
<civodul>lfam: i'm pretty sure /proc/sys/kernel/unprivileged_userns_clone used to exist
<civodul>but i doesn't exist in the 5.9.10-gnu kernel i'm running
<lfam>Could be, civodul. That would explain why people are having new problems
<vagrantc>nckx: so you have some random patchset on your Guix System build that doesn't behave like the Debian/Ubuntu patch?
<zimoun`>it seems you are interested, I will do an effort to do it asap. :-)
<vagrantc>nckx: it seems like trying to create a file that isn't actually used by the kernel just to make guix container work seems ... not quite right? :)
*jonsger wants to discuss about wayland packages...
<zimoun`>I have a machine with 64 cores and “guix build -m bioconductor.scm” with 300+ packages… but only 1 core is really working. Do I have misconfigured something or the guix-daemon is as lazy as I am ?
<lfam>You could make more build users too, of course. 10 is probably not enough for 64 cores
<nckx>vagrantc: It seems like container support was added using trial & error. ‘Oh, I had to do X to get it to work, let's throw an error if X can't be done.’
<davexunit>nckx: my proposal is to try calling clone with just the user ns flag
<davexunit>if you can fork that way and exit 0, return #t
<vagrantc>that seems better; test for the feature ...
<davexunit>when I originally wrote that procedure I thought this file was present everywhere and thus was a canonical way to test for the feature
<nckx>I'm rebuilding my kernel with NS support to do some trial & error (& hopefully get a patch out of it beyond ‘why don't we just’) but I'm on iteration 3 and losing patience. Now I had to enable CONFIG_POSIX_MQUEUE or ‘guix environment -C’ throws a fit... why?
<vagrantc>davexunit: i think it was more of a Canonical, Ltd. way ... heh. :)
<nckx>I'm sure it doesn't use POSIX message queues. Who does.
<jeko>Day 3… I still can't figure out why guix deploy can't connect to the target. 😭️
<nckx>jeko: I've only used guix offload, not guix deploy, but my first step is always checking whether ‘sudo -i ssh <remote user>@host’ works. If it prompts you interactively for anything, that was the/a problem.