<rdrg109>[Q] I have installed guix using the guided graphical installation. Everything worked fine. I got the sucessfull screen with the "Reboot" button on it. However, when I reboot my system, the grub shell is shown and I don't know how to boot into Guix. What could I have done wrong? I'm asking because I'm going to try to install it again.
<rdrg109>Additional information: When I execute "boot" in the grub shell, I get "error: you need to load the kernel first"
<unmatched-paren>Try mashing F12 as your computer boots to enter the boot menu. Exactly this issue happened to me when I installed.
<TheNewGuy>Hello all! (Hopefully) potentially new Guix user here. I'm trying to install Guix from USB on a Librebooted Thinkpad X200 using the graphical installer, but it crashes to a black screen and loops right after selecting a guided partition, with or without encryption. I have tried a few different settings going through the installer and it doesn't
<TheNewGuy>seem to make a difference. I couldn't find anyone having the exact same problem on the issues page either. I'd appreciate any ideas!
<patched[m]>Have you tried the latest image rather than the stable? It solved another bug that made it impossible for me to install
<podiki[m]>apteryx: I think I found the fix for geeqie (at least the not starting clutter error)
<TheNewGuy>I'm back! Unfortunately I had the same problem with the latest .iso, after choosing to "Install everything in one partition," the screen goes black and takes me back tot the start of the installation process without actually doing anything :(
<podiki[m]>TheNewGuy: I also ran into the partitioning part being rather brittle in the summer
<podiki[m]>it was better behaved if i made sure the disk was completely wiped of partitioning information (some left over from previous failed install did not go well), and on a later reinstall I did the installation manually
<apteryx>lilyp: why do you consider that "keeping the old emacs as-is" the correct behavior? I'd have thought discovering the newly installed Emacs packages (in the profile it's working from) could be automatically picked up by running our package loader entry point (guix-emacs-autoload-packages)
<sneek>apteryx, podiki[m] says: I sent a potential source patch (from upstream) for geeqie, hope that fixes the clutter startup error
<podiki[m]>(my laptop and Pi homeserver are still on Arch still)
<KE0VVT>Do I need to put "tor" in "(use-service-modules)"?
<KE0VVT>podiki[m]: Tell me if the Pi goes OK. Maybe I could run a Kodi box with Guix instead of LibreELEC.
<podiki[m]>KE0VVT: I don't plan on trying it anytime soon, mostly because reproducing the set up would take some doing (since it is not a simple guix config.scm); also not sure how well guix runs if at all on a pi?
<podiki[m]>KE0VVT: on use-service-modules I would think so? or networking? (since that is where it is defined)
<KE0VVT>Yeah, I'm leary about putting Guix on a Pi.
<rdrg109>Third attemp to install Guix: Now I'm getting "Operating system not found" even though the installation was successfully completed. This time I did what some other used recommended me: reboot the efi partition. When I didn't format the efi partition, I was brought to the GRUB shell.
<M6piz7wk[m]>rdrg109: FWIW when that happened to me using the forsaken channel i just used the installer to generate the config.scm file and then ran `guix system init -f file /mnt`.. it's probably a good idea to also chroot in and run `guix pull` bcs the installer doesn't do that for some reason
<M6piz7wk[m]>oh `guix pull` prior to `guix system init` should make an updated guix install 🤔
<Karthik[m]>vagrantc: It literally saved many manual installation steps to go through, paving the way for guix adoption. Your work is great!
<rdrg109>M6piz7wk[m]: Are you sure the command is "guix system init -f file /mnt"? I'm asking this because my guix complain that "f" is an unrecognized option.
<vdv>i try to inherit a package and try to overwrite an input via (inputs (alist-delete "wayland" (package-inputs "wayland-new"))) but the compilation complains that a dependency of the inherited package is missing
<rdrg109>I have failed again with the installation. I have mounted the partition where "/" is supposed to be on to "/mnt". I executed "chroot /mnt", then I executed "ls", but I get "bash: ls: command not found". Is this an expected behavior?
<rdrg109>Additional info: I executed "find /mnt -perm /111 -type f -name 'ls'" and I got 2 lines: "/mnt/gnu/store/<<hash1>>-coreutils-8.32/bin/ls" and "/mnt/gnu/store<<hash2>>-coreutils-8.32/bin/ls".
<apteryx>is it me of 'guix build -f package.scm' is broken on core-updates-frozen?
<xelxebar>pingpongdull: login to console? Whatever program the user's shell points to.
<xelxebar>pingpongdull: If you mean after logging in from a login manager, then it typically executes the window manager.
<cjtenny>hmm, emacs from guix is only using 16 terminal colors, even though it detects 256. emacs from debian (my guix host) is using all 256. this happens on the terminal emulator from debian and the same terminal emulator from guix. though the colors are *all* loading slightly different with debian emacs under guix vs debian terminal, probably due to slightly different terminal versions/builds. down the
<raghavgururajan>KE0VVT: Didn't read the full backlog. I think you have to add "tor" to the `supplementary-groups` in your config.scm.
<lilyp>apteryx: all you really need to do is to load the subdirs file, perhaps followed by regenerating the autoloads using already existing guix-emacs procedures
<lilyp>if you want to, you can enhance guix-emacs by a procedure that does that
<apteryx>OK, I'll experiment when I get a chance. Thanks for the pointers.
<cjtenny>there's something funny where programs using readline only work properly if I have ncurses installed in the profile. I figured it was realted to setting search-path TERMINFO_DIRS but that's still not the cause of my emacs terminfo woes...
<slyfox>on llv i usually run lit with -v or -vv. it prints exact command it was running the tests.
<slyfox>i would expect rust to have something similar
<unmatched-paren>i'll 1. disable the problematic test and build/install 1.53.0 without it, then 2. use rustc --emit=llvm-ir on the file _with 1.53.0_, 3. do the same --emit thing with 1.52.0, then 4. run diff on the two
<unmatched-paren>since that's the only thing i can think of with my limited knowledge of the rustc build process
<slyfox>maybe rust's build system has a way of building unoptimized compiler to speed things up slightly?
<unmatched-paren>to be fail it doesn't actually take as long to bootstrap itself as i thought, it's just quite frustrating when i've been waiting an hour for it to bootstrap, and then it's nearly there, and then this tiny little test fails and brings the whole thing down
<raghavgururajan>Yt-dlp project page says "The main focus of this project is adding new features and patches while also keeping up to date with the original project.". So I assume they expect the youtube-dl to continue development. 🤷♂️️
<unmatched-paren>are there any languages that are basically just dialects of C with cleaner, more readable syntax? because if that existed i would 100% use it
<nckx>There are .log files, I forget the exact layout, but it might simply be tests/channels.log.
<nckx>The tests don't run in a sandbox so they are quite susceptible to environmental differences (which is probably a net good thing, if annoying).
<unmatched-paren>should i try some environment options like --container to try to sandbox it more?
<ouestbillie>hey all I just installed from iso, basic graphical install, just partitionned manually with luks and seperate home. It says it installed sucessfully but when I boot I get scrambled characters and some kind of prompt but I can't make sense of anything, looks like a firmware issue but I'm not sure how to investigate, any ideas (running on hp elitebook folio 9480m)
<ouestbillie>unmatched-paren: no cause its really unreadble, not even random glyphs just scrambled... but it would be my first guess
<ouestbillie>i should mention i tried the manual install before graphical (switched as a sanity check) and those same scrambled characters appear before the outputs becomes legible, the first line is something modprobe pcrk, but the googlez said that was a harmless warning...
<unmatched-paren>can you try typing 'boo' and then pressing tab? if it's a grub prompt it should autocomplete to 'boot' i think
<unmatched-paren>if it isn't grub then i can't help you, i just have this one idea for what it might be
<unmatched-paren>i got a grub prompt when i first installed, but it wasn't scrambled...
<ouestbillie>unmatched-paren: no i'll make sure to do that next time, but thats just a minor inconvenience atm, rereading my config.scm when booting from usb in shell mode I see theres not password entry for the user I created, is that normal?
<jgeerds>Hi, I would like to patch a file from an emacs-xyz package. The "emacs-substitute-sexps" function seems not to work in my case because the REPLACEMENT is always considered a string (it uses emacs' "format" function). What I want is a quoted emacs list consisting of a string like '("my string") -- Can someone point me to the right direction?
<ouestbillie>unmatched-paren: can I pastebin my config from the installer, a little noob on rescue mode here?
<apteryx>civodul: at this level of heretic idea, it may be better to bootstrap rust on non-x86_64 the way upstream wants us to do it (with a prebuilt binary bootstrap...), leaving a large FIXME in tho sources.
<apteryx>but your idea to build the first rust with mrustc and gcc -O0 sounds good to try
<sam_>I would really encourage trying with the bundled LLVM copy just for test purposes
<sam_>it's quite common for test failures to occur as a result of using the system copy. they patch LLVM quite heavily at times with various patches not yet landed upstream.
<GNUtoo>apteryx: Thanks it worked, though sometimes some programs (like busybox) are compiled for the host architecture
<GNUtoo>but that's probably not related to the target but rather a bug
<roptat>Noisytoot, gitile assumes the repository name is the first element after the /, so in your case it assumes the user wants the repository named "noisytoot"
<roptat>that's because I use other URLs for the repo, like repo/tree to show files, repo/commits to show the log, etc. So how is gitile supposed to know you if you want a repository named "noisytoot/commits" and not the history of the "noisytoot" repository?
<rekado>pankow and grunewald are both ready now; missing a cable for kreuzberg. But: these machines could already get to work. What can I do to let ci.guix.gnu.org push as many builds as possible to them?
<unmatched-paren>"When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license." said (proprietary) license is here: https://code.visualstudio.com/license
<lilyp>so whenever someone's like "go package vscodium" we have to be like "no, we don't do blobs"
<dstolfa>unmatched-paren: makes sense that MS would do something like that
<dstolfa>but... isn't electron still problematic according to the FSF because nobody's been able to untangle things?
<singpolyma>dstolfa: that sounds kind of like the Debian position that Smalltalk might be nonfree because the source code isn't a text file
<dstolfa>singpolyma: i'm not saying i agree with this position, i've just heard it in the past.
<singpolyma>Well if Mozilla hadn't made xulrunner unviable....
<dstolfa>unmatched-paren: i do understand where this came from though... portability has been a complete nightmare for native apps with phones and different operating systems available, and developers genenrally just wanted 1 source base across many platforms. hence, we have this mess now
<asdf-uiop>Hi! Trying to use a relative path for 'guix package --install-from-file' leads to this: "guix package: error: failed to load '~/local-guix-channel/my-packages/my-tools.scm': No such file or directory". If I replace '~' with '/home/username', it works. Is that to be expected?
<nckx>If Chicken Scheme invokes GCC and doesn't misguidedly mess with environment variables, GCC should see C_INCLUDE_PATH which should point to $HOME/.guix-profile/include which should include the linux/ headers you previously installed.
<nckx>And system reconfigure to update the system & system packages.
<nckx>KE0VVT: A kind of input that emulates traditional/legacy distro ‘dependencies’. I.e. ‘if I install A, also install B’. Fragile, unguixy things but some software all but requires it to run without invasive patching.
<nckx>If package A propagates B and package C propagates B' (a different version or even build of B), there will be conflicts that need to be resolved, often by upgrading both A and C but sometimes not even that helps.
<KE0VVT>nckx: I'm guessing that is Telegram Desktop's fault, considering how hacky the software is to begin with.
<raghavgururajan>I am afraid you have to use time-machine to install gajim and telegram-desktop for now.
<KE0VVT>raghavgururajan: Oh no, will my Gajim not run now?!
<KE0VVT>Too late. I ran "guix upgrade" a minute ago.
***Tirifto_ is now known as Tirifto
<KE0VVT>Where does Guix store Sway's default config?
<nckx>KE0VVT: You can always ‘guix package --roll-back’ to undo upgrades (see ‘guix package --list-generations’ for your profile's history).
<nckx>I have a /gnu/store/csn24vrwmn85p35i6kakn72xzln1gi02-sway-1.5.1/etc/sway/config but no clue if that's the ‘default config’ or an unused example file and the defaults are baked in. Both are plausible.
<nckx>However, Guix does not provide its own defaults anywhere else; whatever decides would be Sway upstream.
<nckx>check-system is broken because the (arbitrarily chosen) ddcci-driver-linux module is incompatible with Linux 5.15.
<KE0VVT>nckx: Why does Guix put the hash first? Makes it hard to "cd" into a dir.
<nckx>Because if it was put last people would ask why it wasn't put first.
<nckx>It's a hand-written (non-autotools) ./configure script that doesn't accept the standard arguments or ignore unknown ones. So you'll have to write a custom configure phase that (apply invoke "./configure" configure-flags) only.
<jgart>nckx, why does the nix package definition patch the configure shebang?
<nckx>Maybe they don't patch shebangs by default like Guix does? Maybe it's obsolete cruft? I can't say.