IRC channel logs
2024-08-13.log
back to list of logs
<chubbymomo>Hello, everyone. I'm having an issue that is just about bringing me to my knees. I've been trying to install Guix on my UEFI motherboard. It can't seem to detect as UEFI. The guix installation drive detects in UEFI, I use the graphical installation, which installs an efi partition. Nonetheless, it won't detect. At this point, I feel like it's my motherboard but I have two things that kind of pin me as far as that's concerned. Arch Linux installs <chubbymomo>me to take a hike. Any help would be appreciated. <tadhg>have you tried the non graphic install process? <tadhg>at least getting near the last step and exporting the generated config and playing with it manually, 100% should try running the `guix system init` command from terminal and look for console messages about the bootloader that may be relevant and not shown in the graphic tool <chubbymomo>I did the installation using the shell with guix time-machine <tadhg>oh wait what? I thought you said you used the graphic install tool? <tadhg>I believe there is a way to manually invoke grub-install with stuff in the gnu/store to redo the bootloader if everything else is setup, might even be able to just do `guix system reconfigure` if you can `chroot` into the system from the installer but I don't know how to actually accomplish either of those off the top of my head <chubbymomo>Sorry, I used the graphical installer, then at the end I used the shell. Basically, I used it's partitioning and the config.scm it generates. <chubbymomo>Do you have an idea on where I could look for doing the grub-install or system reconfigure? <chubbymomo>I had previous trouble setting up chroot with Guix. <chubbymomo>Horrible part is that I can manually use the efi shell for my motherboard and use the efi file to launch... <jaft_r>So – being aware that, without actually sharing my config, the cause might particular to my Guix setup but – is there any /common/ reason PulseAudio might launch even after both the pulseaudio-service-type and alsa-service-type were removed from the system services? <jaft_r>AwesomeAdam54321: fair; I could see that. <jaft_r>jackhill: setting up the Pipewire home service turned out to be pretty straightforward. I was able to screenshare using Chromium so I think I should be alright. I did want to doublecheck one thing, though; how'd you setup the xdg-desktop-portal config. file, for your setup? <jpoiret>jaft_r, AwesomeAdam54321: pulseaudio doesn't use dbus, the client library tries to connect to a running server and if one isn't present, it simply forks off a new one <jpoiret>yes, you read that right: a client connecting might spawn a server by itself :) <jpoiret>the pulseaudio service in Guix just configures PA but doesn't start it, so you *should* keep it and set autostart=false <jpoiret>that way you're 100% sure that even if pipewire-pulse isn't started yet, pulseaudio won't magically start <jpoiret>(if something tries to connect to PA very early, that can happen) <jaft_r>jpoiret: …huh; welp, good to know. I'll add it back and specify that. Good stuff to know for getting Pipewire setup. <jaft_r>Only tangentially related (DBus) but you might know: I've got the DBus service that comes with %desktop-services but I find I have to manually run "dbus-update-activation-environment --all", on start-up, if things like Gnome's keyring are to work properly. I feel like that should be covered by some service but I haven't tweaked and messed with custom setups /that/ much. <jpoiret>it depends on how you start the dbus user session <jpoiret>for programs started with dbus to inherit the proper env variables, dbus needs to be aware of them, and that command imports the ones it can see from its own environment <jpoiret>some variables like DISPLAY/WAYLAND_DISPLAY are set by your WM and thus only programs forked by your WM will be able to see it <jpoiret>i'd say it's a complex engineering issue, how to manage propagation of env variables by services in general. I wish shepherd had something for that <jaft_r>Gotcha; thanks a ton. I really wasn't certain, at all, so this definitely makes things clearer. <Rutherther>Should I disable the pulseaudio service when I use pipewire? The way I understood from jpoiret messages, pulseaudio shouldnt get started automatically, but only with first client. But since pulseaudio stuff is replaced with pipewire-pulseaudio, should be fine, right? <jpoiret>Rutherther: the problem is, if PW hasn't started yet for some reason, but something else wants to use PA, the PA client library won't find pipewire-pulse (the PA compatibility server for PW), and since it's a strictly PA-aware library, it will start the original PA server and not pipewire-pulse <jpoiret>but if you keep the PA service in your system config and set it to not autostart, then it won't get started even in this case, ensuring you end up using only PW <Rutherther>Oh, so this client fork to make a server can be inhibited by setting this autostart to false? <Rutherther>Ah, great. I was beginning to worry the library is written in such a way to do the fork aby time without possibility to configure <rynn>Anyone run into an issue where Music simple doesn't list all your music in the Music folder? Currently only show 9/14 of the folders there. Not sure if it's a guix-specific issue or not. <gabber>can i retrieve sources of a package from a git server that does not listen to the usual port? do sources have to be public so i can package them with guix? <civodul>gabber: hi! if sources are not public, one trick is to use ‘git-checkout’, which can clone the repo “on the client side” (e.g., connecting to your user’s ssh agent) <sneek>civodul, you have 1 message! <sneek>civodul, RavenJoad says: I figured out the most important problem of Guix in a Xen-hosted VM issue. Turns out I disabled VGA output somehow, which meant the actual output ended up wrong. Now, the initrd is still garbled, until init cleans up the output. That _is_ a Guix issue because it happens in Proxmox too. <gabber>AwesomeAdam54321: i have crafted the repository local guix.scm which uses the local files, now i want to pack the code as .deb for which i need a proper package definition (i think) <gabber>civodul: where can i find more information or an example for git-checkout? <gabber>nvm, i think i found the relevant hints (: <civodul>gabber: ‘git-checkout’ is defined in (guix git) <civodul>you can import that module and then write: (package (source (git-checkout …)) …) <gabber>thanks! can i also make use of "special" ssh host configs this way, e.g. a non-standard port or username? <weary-traveler>civodul: is the idea with git-checkout to use an existing checkout, or to use the user's configuration to create the checkout first before invoking build? <sneek>Welcome back weary-traveler, you have 1 message! <sneek>weary-traveler, abcdw says: There is no "not-yet-implemented" feature list, but arei is highly extensible, so implementing you own features is quite comfortable. We still stabilizing API a bit, but take a look at arei-module.el for inspiration <civodul>weary-traveler: it’s mostly equivalent to running “git clone” by hand and then using ‘--with-source=PKG=/path/to/checkout’ or similar <civodul>that is, the checkout is performed by the user, and then the whole source tree is passed as a source of the derivation <weary-traveler>i see, thanks for the elaboration. i agree this should be documented <civodul>gabber: and yes, it will honor ~/.ssh/config, except for a few “advanced” constructs that libssh doesn’t recognize like ProxyJump IIRC <gabber>it does not seem to honor my host shortname: `failed to resolve address for FOO: Name or service not known' <gabber>i have only a hostname and a port directive configured for that name <civodul>does that host name appear in ~/.ssh/config? <gabber>i use it to checkout git repos all the time <civodul>not sure what’s happening, it should be honored <gabber>hmm... i'll give it some more tries, but it does not seem to honor neither the hostname nor the port directive. <gabber>is there another way how i can convert a package definition into a .deb package? <weary-traveler>gabber: ooc, if you provide the hostname and port directly does it work? <gabber>weary-traveler: what syntax would I use for that? HOSTNAME:PORT:org/repo.git? <tadhg>I think without the second colon, just insert :PORT between the first / and the hostname <tadhg>Like example.com:1234/xyz/repo.git <weary-traveler>gabber: man "git clone" has the syntax. i can never remember myself <gabber>thanks, kind strangers! though i have no dice (connection times out) <weary-traveler>gabber: connection timing out on a connection string that you're able to use on the CLI? <gabber>no. actually, the one that works on the cli (ssh://FQDN:PORT/path/to/repo.git) produces "failed to set hostkey preference: The requested method(s) are not currently supported" <civodul>gabber: re .deb, you can try “guix pack -f deb PKG” <gabber>civodul: yes, but for this i need a package defined in my `guix pull` checkouts, no? this is why i try to add the package to a channel first <chubbymomo>So, considering it's a bit up in the chat, I just wanted to ask if anyone had an idea as to why using UEFI boot, I can't get Guix to show up? More details are further up. <Rutherther>could you provide more details, such as the command that fails with error message and its log? <podiki>hi all, how is core-updates doing? <podiki>been away a bit, but wanted to get on mesa-updates again, but should rebase/wait on core-updates? <dariqq>Hi guix, anyone here familiar with the shepherd codebase? <dariqq>specifically where should i look to make shepherd --silent actually do something <jaft_r>dariqq: are you looking to modify shepherd? <weary-traveler>in a guile script one can use "-e" to specify a function to be applied to the commandline arguments. what's a way to accomplish that with "guix repl"? <dariqq>jaft_r: unfortunately yes. Trying to solve my issue 72277. And the shepherd --silent option , which i think should solve it, does not do anything (though it is advertised via --help) <jaft_r>Huh…; well, I know crap-all about shepherd but, if I've found the right area (just did a rgrep), you certainly aren't imaging things, dariqq. Got the code pulled down? <dariqq>jaft_r: yeah i found that as well. Now i need to dive into the code to see what the option should change <dariqq>great when you find the commit that removed the option and it is from 11 years ago ... <dariqq>i think i might have fiound the solution. Actually easier than i though. Now at least i only have the guile deprecation warning instead of the whole shepehrd messages. (the messages are still in the logfile so that is nice <jaft_r>dariqq: nice. Btw, did the commit mention why it was removed? Feels like a relatively important feature to just silently (funnily) not-available for so long. <rbrins>I was trying to get my guix config into my .dotfiles dir so I could use gnu stow and accidently broke my symlink and can't guix pull now. Is it as simple as removing the current dir in .dotfiles/.config/guix/ and adding the symlink to the .dotfiles, and finally stow . to finish it? <rbrins>nevermind, after removing the hard-copied current dir in the .dotfiles, and running guix pull, it seemed to fix itself. I could NOT create symlink though because it errored with read-only file system.