IRC channel logs
2025-02-08.log
back to list of logs
<erik``>nckx: Re: libfontconfig.so issues, I will check if it is garbled or simply empty when I get back to work on Monday. With time machine, it behaves as expected, and build --check did not complain either. <coyotes4ys>thanks for the tips. i am very close to getting guix the way i want it for the moment. it's a very...different distro <Deltafire>(you can install one using an extension if you wish) <coyotes4ys>well i have openbox without a DE and it's 90% the way i want it <apteryx>anyone using our xvnc-service-type to remotely access their GNOME desktop? <apteryx>the problem seems to be with Wayland, it almost works but the applications launched don't display correctly (I see just the menu bar and a wireframe around their windows) <eikcaz>oh hey, I found a bug in the guix documentation <eikcaz>the home field of the syncthing-configuration does not do what the docs say it does <jakef>the cling package has (force gcc-toolchain*) in its inputs. what does this do? <mirai>I've got it with (wayland #f) but also see wireframes when accessing with XVNC <mirai>non gnome apps work though, e.g. Konsole and emacs <mirai>and if I plug a physical monitor and launch gnome apps they display correctly, seems to occur only with VNC <mirai>afaik, with guix:93ac4c20bf4b46b2bb9d0d2b9bec0b728b34de87 everything was still good (late 2023) but its broken with guix:29d133063010cc4f7c40aadb3124364eaf276797 (recent) <mirai>2024 was a quiet year for me where I didn't boot or update the system so the late 2023 commit is the closest working point I have <nckx>sneek: later tell erik Perhaps ‘guix gc --verify={contents,repair}’ will be able to repair it, although that will of course destroy any evidence of the problem. <apteryx>why is there no sound widget in our xfce environment by default? <apteryx>it seems there's no easy way to adjust sound volume <apteryx>seems there should be xfce4-pulseaudio-plugin present <apteryx>(which show show a volume widget in the panel) <wakyct> weird, I think I"ve always had an xfce volume widget <apteryx>wakyct: ah, I have to add it to the panel, but it's available <apteryx>I was surprised it's not on the panel out of the box <apteryx>just found out that virt-viewer doesn't seem to trigger udev events when resizing the screen <apteryx>gnome-boxes does; not sure what it uses under the hood <apteryx>this is used by our x-resize home grown solution to help desktop lacking native spice support such as Xfce to resize <hapst3r>efraim: hej. I talked to you at Guix Days regarding the release. If you have time and feel like it, we could chat about it for a moment. In particular, I am interested to get to know where it's at currently and what open tasks are. <cbaines>apteryx, do you know anything about IDRAC access to MDC machines that are not berlin or hydra-guix-129? <cbaines>hydra-guix-128 isn't working and it would be good to try rebooting it <apteryx>should be the IP address of idrac of 129 - 1 <apteryx>cbaines: according to old info from rekado ^ <cbaines>apteryx, I get a password prompt, but the password I'm trying doesn't work <hapst3r>is use of Gnus mandatory when attempting to set up Debbugs for Emacs? <nico_>I'm thinking of jumping in to Guix from Debian. I currently manage my config with Ansible and have used Nix as a package manager years ago. Anything I should prepare for or consider before installing as my main OS? <Rutherther>nico_: it's important to consider that by switching to guix system, you're committing to the guix ecosystem. You won't be able to easily run binaries downloaded from the internet, may not be able to easily configure system sw that doesn't have a service made... of course there are workarounds for everything, but they might fail and it might be time consuming to get sw running, when it's not already packaged by someone <nico_>That is insightful. I heard Flatpak is still an option? And appimage hopefully? So would I be able to run Syncthing for example? <nico_>I saw most software I use is already packaged. But my favorite photo editor Ansel (fork of Darktable) not yet, so that would need work. <nico_>Same question for Pipx (python packages/applications) <arjan>syncthing is also packaged and there are even service definitions available for it <Rutherther>nico_: flatpak is an option. AppImages can be harder, they usually need fhs and are difficult to get running in a container. You can for sure run syncthing as that's already packaged in guix and has a service <Rutherther>other than flatpak, you can also use other package managers that run without fhs and are self contained, like nix <Rutherther>as for pipx, I have no idea how it works to say if it will or not. But note that generally, as long as it doesn't provide completely self contained libraries for the packages to use (ie. from top of my head numpy needs libz), it will not work out of the box and you might have to enter a guix shell with LD_LIBRARY_PATH variable set <nico_>Ok, sounds like I should keep it as a side-project for now. I'm still interested, but might not be the best idea to install it on my main system just yet. <yarl>I followed the manual "Base Services" greetd-wlgreet-sway-session, I have a warning: XDG_RUNTIME_DIR does not exists etc. <yarl>Does someone knows the status/fix for this? <yarl>There is a /run/user/982, which is greeter <yarl>But there is no /run/user/1000, for my user. <yarl>In the manual under greetd-service-type, it is mentionned that it provides "Special variation of ‘pam-mount’ to mount ‘XDG_RUNTIME_DIR’" <yarl>Still, seems at least there's missing documentation. <ebrasca>I have (excluded '(".*~" ".*\\.swp" "\\.git" "\\.gitignore")) in my home-dotfiles-configuration and it still links the .git folder. How to fix it? <Rutherther>yarl: if you're using greetd, it should be set and created. So there is either a bug or misconfiguration <apteryx>nico_: people sometimes workaround missing packages via flatpaks or the likes on Guix System <apteryx>but attempting to package it properly for Guix could be a rewarding dive <apteryx>cbaines: sorry, I'd have expect the password to be the same as for 229 and 225 <apteryx>sad, it seems x-resize stopped working even when inside gnome boxes for our vm-image.tmpl <Rutherther>although now that I am looking through the code, I don't see where greetd creates the directory, I see it only setting the env var, hmm <hanker>i think shepherd's supposed to make the directory <ebrasca>How does excluded work in home-dotfiles-configuration? <Rutherther>the system one? it doesn't have anything like that. The user one? it can't, there aren't permissions for user creating /run/user/$USER <Rutherther>okay, I found the rules for creating the directory. Not sure why it isn't being hit for you then <apteryx>shouldn't the binary of a package listed in the `packages' field of my operating-system record be found in /run/current-system/profile/bin ? <yarl>Rutherther: That's related to 'greetd-pam-mount-rules', right? <Rutherther>yarl: yes, greetd pam mount pam service should use those rules to mount the directory <Rutherther>yarl: pam should log to /var/log/secure, so you can check there if you see any errors / anything related to 'greetd' <yarl>Rutherther: Ok. I was not awake. The problem is completely unrelated to greetd. I am connecting through ssh. <yarl>If I login 'locally', through greetd, /run/user/982 is gone and /run/user/1000 is created. <yarl>And I have no problem remotely either. <yarl>Now If I am not logged in locally, I got the missing XDG_RUNTIME_DIR, remotely. <yarl>So, is it ssh configuration? bash configuration? something else? <yarl>Rutherther: Sorry about that. <Rutherther>yarl: no, then it's completely expected. greetd pam rule is for greetd <ebrasca>How to exclude .git directory in home-dotfiles ? <yarl>But, what can I do then so XDG_RUNTIME_DIR created when I only login remotely? <luca>yarl: If you don't mind, could you share how you're using seatd in guix? I remember I tried forever ago but couldn't get it <Rutherther>yarl: if you want it to be created through ssh you will have to decide on how to make it. One way is what luca suggested, in profile file. Another is by switching to elogind and using its pam rule. Other than that you can make your own way, ie. make a shepherd service that will just mkdir it and change permissions to your user <yarl>Rutherther: Ok, thank you a lot, I'll take a look. <yarl>luca: Well, nothing fancy I'm afraid : "(service seatd-service-type)" <yarl>Still, I added "seat" to greeter-supplementary-groups <yarl>and to my user supplementary-groups for a reason I can't remember <apteryx>hm, I get: guix system: error: could not authenticate commit 3afa3aa73a35364f8c429334ac68f50f719f5b22: key 01FD 85F4 1A7B 7F82 0583 06A5 935E BE07 36DC 857E is missing; anyone else? <Rutherther>seatd allows access to the socket via seat group, you add your user to that group so that your user can communicated with seatd. That's how most sw allowing users to do something only root can, works <apteryx>only from my ./pre-inst-env guix system image ... hm. <Rutherther>apteryx: you need to update your local keyring branch <apteryx>yeah, I remembered that, and I did, but it doesn't seem to help. it's on commit 21173006e4 <ebrasca>My home-dotfiles is linking .git, how to prevent it? <apteryx>Rutherther: hm, it now works, perhaps user error... I did do a regular 'guix pull' in between <apteryx>I seem to recall we changed something to only trust the previously pulled guix for authorization for security reasons <apteryx>we used to trust the pre-inst-env one from the checkout <apteryx>but in the event the repository would have been tempered with, it would have been possible for the attacker to authorize themselves, tricking Guix developpers <ebrasca>How to exclude .git directory from being link in home using home-dotfiles? <apteryx>nevermind, x-resize still works at least via gnome-boxes <apteryx>but xfce has a weird gui redrawing issue <apteryx>if I disable the compositor it goes away <ebrasca>I am using home-dotfiles in GuixSD system but it is linking .git directory, how to fix it? <apteryx>if someone has a bit of time, I'd like to sollicit other view points on bug#68453 <ebrasca>I am using home-dotfiles in GuixSD system but it is linking .git directory, how to fix it? <ebrasca>apteryx: I like how it is now more in my opinion. Your sugestion is harder to understand in my opinion. <apteryx>ebrasca: thanks for sharing it; could you share it also on the guix-devel post? <ebrasca>apteryx: I have not jet learn how to respond to them. I am still making my GuixSD first version settup that I will push to my dotfiles git. <apteryx>OK! Welcome home :-). It's been renamed Guix System some years ago (from GuixSD), for your info. <ebrasca>apteryx: I sended a email, I hope I did not do some mistake sendint it. <ebrasca>I did not expect that just clicking on the link will just open my gnus in emacs and fill the data. <nico_>Still unsure if Guix will work for me in practice, but downloading the ISO now :D ... <luca>Remember the ethernet port :P <jas>hi! i did a fresh install and using gnome with nextcloud. the nextcloud app syncs fine, but i can't find any way to pop up the configure window. the app just hides in the background. is anyone using it? <jas>pretty much graphical installation with gnome from guix 1.4.0 and then upgrading. uses x11 <nico_>(I have a Corebooted T530 with ath9k card, so I assume wifi works fine in in the installer? Or is that not an option in the GUI? Of course Ethernet will speed things up. I'll get my cable out. <luca>If wifi works in the installer I'm pretty sure it will work in the actual install as well <luca>But in my experience guix's downloads are kinda slow compared to other distros. Mostly git being fat :P <luca>though to be fair, all fresh linux distros take forever to download and update from the internet <mra>nico_: I've gotten Guix working on my t430, but I needed proprietary drivers for the installer to work. sounds like yours is fine though! <nico_>I can recommend to coreboot it and install an Atheros wifi card in it. <sleepydog>yarl: make sure greetd is in the "users" group <nico_>Hmm, why can't I select Netherlands with English language? <ebrasca>I am using home-dotfiles in GuixSD system but it is linking .git directory, how to fix it? <graywolf>Maybe a stupid question, but how do I install guix from a script? When I am trying to use guix-install.sh, all I am getting is very useful "Can't read standard input. Hint: don't pipe scripts into a shell." error. <graywolf>Is there a non-interactive version of the script? <hapst3r>when packaging a new package, I always relied on `guix build` to tell me that my hash value is wrong when I copy-pasta'ed from other packages. Apparently, this is no longer the case. <hapst3r>Also, ./pre-inst-env guix download $PACKAGE complains about an invalid URI, even though before it downloaded just fine <hapst3r>is there another way to get the hash value while packaging? <nico_>I'm in the installer. I'd like to use Wayland, but it is not immediately clear to me how to change it. Also lack of experience with Guix syntax and conventions. Any recommendations? Or something to change in the future? <hapst3r>graywolf: when you are packaging and before it has been downloaded, build, or committed to the codebase? <graywolf>hapst3r: Yeah, for example `guix hash ~/Downloads/crun-1.20.tar.gz', after I verify the gpg signature. It is well possible there is more efficient way. :) <mra>every once in a while i feel like learning about writing Wayland compositors and it remains hilarious to me that the documentation is still just drew devault's blog and the source code of sway <Rutherther>nico_: there isn't much to do, just make sure to use login manager that supports wayland if you're using login manager, and add the wayland compositor(s) you want <hapst3r>graywolf: thanks for the input, I think I figured it out in the meantime. I actually find it easier to use `guix download --commit=$COMMIT_OR_TAG https://$URL_GIT_REPO`, I just had an initial misunderstanding which value I should use (I used `--format=base32` and <hapst3r>I used `--format=base32` and ran into weird errors, instead I should just have omitted the `--format` argument altogether because by default it uses the `sha256` algorithm, whose value is expected in the package declaration `(sha256 (base32 "$SHA_256_VALUE"))` <nico_>Ok, got a basic install now. Will look into configurating it from here. First installing necessary package.s <nico_>Thanks for the replies so far <theruran>mra: really? there's no proper documentation of the Wayland protocol? <mra>the Wayland protocol is perfectly well-documented. it's wlroots that has somewhat... lacking documentations <mra>at least in my opinion <theruran>ah but the compositor architecture(s) are not well documented <hanker>should /run be mounted as a tmpfs? <craigbro>just update a guix vm from like 6 months ago, and had to explicitely add elogind service to it for home-configuretion to work <craigbro>wondering if there is something other than guix pull I should have done <hanker>fyi, if you're taken by the same inspiration as me to make /run tmpfs <hanker>don't forget to use `(needed-for-boot? #t)` <hanker>and don't use the `no-suid` flag <nico_>Coming live from new Guix SD install <nico_>Thanks. Also found the first daily-use app not available: Fractal Matrix client. But there are workarounds. Do you normally install packages on a user level or system-wide? <nckx>sneek: later ask graywolf There's something you're not saying, that error shouldn't happen if you just invoke ./guix-install.sh. As for ‘non-interactive’: see the code block just under that error, i.e. yes | ./guix-install.sh. That will always select the default. <nckx>nico__: I install most things as my regular user. Saves time when reconfiguring and allows partial (single-package or all-but-one-package) upgrades. <nckx>I'm curious: whence 'Guix SD'? <nckx>That name has been unused for *years* so it's always interesting when new(?) users show up using it. <nico_>I've been following Guix since the beginning, as I already had Nix experience and am pro free software. I never found the moment to take the leap. Is there a way to distinguish OS level from package manager in naming? <craigbro>I installed "emacs-vterm" but emacs still wants to try and build (wants cmake etc..) is that expected? <nckx>nico__: I'm not sure what you mean. But 'guix package' (and shorthands 'guix install/remove/upgrade') operate on your user profile and hence won't show your 'system packages' if that's what you mean. A system with (packages (list emacs …)) won't show 'emacs' in any CLI. <nckx>dstolfa: True. I just marvel at the immortality of GuixSD. <yelninei>nico_ : Packaging fractal will be complicated because all the rust/cargo stuff does not play nicely with guix and youd have to package all of the crates seperately <nico_>In my case I've been following this project for very long, but indeed it is hard to get rid of a name. <nico_>I noticed just that reading the packaging thread on issues.guix.gnu.org <nico_>There is always the webbrowers, iamb TUI and maybe others <nico_>yeah, makes most sense I think <nico_>Already ran it as Flatpak to stay on top of latest developments in Debian. Even the nightly. About a year ago the difference between nightly and stable was very large <luca>For what is worth guix has some automation when it comes to crates.io, and it can write most of the packages for you <luca>but the bigger the program is the more manual work you have to do <luca>edge cases and everything <yelninei>luca: Problem is that fractal is not a pure crate but rather built with meson which complicates things <nckx>Wild to hear people casually mentioning Flatpaks on Guix System as the low-effort solution when it used to be guaranteed pain. <3 <nckx>Not a Flatpak fan myself but it used to be that even after working out the 'obvious' FHS assumptions (which was still tedious) you'd still get weird errors. I think due to their attempt at sandboxing. And we had fewer working portals with more bugs. Sorry to be vague, I'm clearly good at repressing traumatic memories. <nckx>The slow steady march towards ‘I'll just™ run the Flatpak until I have time to package this’ is impressive though. <nico_>I see. Must say I even had weird behavior of Flatpak on Debian with scaling, wrong folders/themes. <nico_>I'd like to use more packages and contribute them. Packaging for Guix seems more duoable than packaging for Debian. <duncan>flatpak and scaling is just a flatpak thing. mostly with QT apps <luca>Debian also has a good amount of automation for packages. Such as cargo <aure84>Hello. Anyone with experience on VM builds with `guix system vm`? <hanker>`corepack pnpm` doesn't work anymore it seems <hanker>getting something about keys not existing <hanker>maybe node is due for an upgrade <meaty>What could cause CMake "find_package" to fail to find a library, even if it's in the inputs? Does the library package really have to have a ...config.cmake file in it? what if it doesn't? <Rutherther>meaty: it doesn't have to have config.cmake specifically, but needs to have something to say information about the package, ie. also pkg-config conf file and to use that you would have to add pkg config to inputs <civodul>meaty: i would check CMakeErrors.out (i think that’s what it’s called), which contains info about what it tried and failed <meaty>civodul: CMakeError.log only has a report 'Determining if the __aarch64__ exist failed', which makes sense cos im that's not the host or target arch <meaty>Rutherther: I put pkg-config in both inputs and native-inputs and it doesn't help; the lib is zstd <meaty>let me put the def im working on in a pastebin if that's ok <lfam>aure84: Did you have a question about `guix system vm` <meaty>the odd thing is that the CMakeLists file finds zlib just fine right using the same methods, which is strange <Rutherther>meaty: yeah, this cmakelists is written in an unfortunate way that doesn't try anything else than the cmake config file for zstd, so you will probably have to patch it. the reason ZSTD is fine is that there is FindZSTD.cmake file as part of cmake <podiki>i'm trying to mirror a channel, but it is failing to push --mirror as a commit is not authenticating...this was a commit that indeed wasn't authenticated so the repo was force reset <podiki>but i guess it remains in the local history; what can one do (without just using a new clone, which doesn't have this commit) <podiki>hmm or actually the reported key is indeed an authorized one. weird <podiki>maybe something about how keyring branch is handled? <lfam>podiki: You mean that `guix git authenticate` is failing, and that's expected? <podiki>no that passes, but i guess how the pre-push hook calls it <lfam>Is it enough to just not use the hook? <podiki>so when doing a mirror it is trying to do the pre-push hook but only with the initial keyring branch? order of how branches are pushed? <podiki>yeah i can just no-verify it, was wondering <podiki>(at first thought it was a bad commit from history, but no) <podiki>confusing since it is a commit on a deleted branch, and i don't see it in a fresh clone <podiki>oh maybe should try a clone with --mirror to compare <podiki>nope. commit shows up locally but not in a fresh clone. i plead git ignorance <meaty>What's the canonical way to define a package that differs from another only by a single config flag? <meaty>as in, this one flag results in a completely different binary and peripheral files <podiki>inherit that package and adjust the inherited configure-flags <lfam>podiki: If the problematic branch in question has been deleted, try garbage collecting the repo with `git gc` <lfam>Then it's still reachable somehow <lfam>Could still be in a Git packfile. I'm not sure of the details but you could try a more aggressive `git gc <podiki>i guess i still have the branch locally despite pruning? i never looked into prune deeply <lfam>Git packs objects into larger files for efficiency. The basic GC may not repack, leaving stale objects in the repo <lfam>You can do a more aggressive `git gc` to repack <podiki>i think i just didn't understand git prune either <lfam>Prune is called by `git gc` <lfam>But, it's hard to say what's going on without more details <podiki>well i deleted the local branches. i guess part of the reason too is that they were not merged some of them (well not directly) <podiki>back to the more guix question then: how pre-push hook works when creating a mirror <podiki>now it complains on the commit which added someones key, that it isn't a descendant of the introductory commit <podiki>i can just use --no-verify, but i'm curious. likely we can make this better <lfam>The pre-push hook is merely designed to help committers avoid mistakes. It's not something that applies in all circumstances. <lfam>There's lot of unusual operations in Git that won't satisfy this tooling. <lfam>Remember, `guix git authenticate` works client-side, when pulling. That's where the security boundary is. <lfam>There's nothing in our security model that requires it to work on every kind of `git push` <podiki>sure, but we might want to help out channel maintainers when they want to mirror/move/etc. so could provide some info <lfam>Sure. My point is that you probably aren't missing anything. I doubt anyone ever tested this or intended it to work <podiki>or where it is expected to give a failure and to know what you are doing <podiki>yeah, i hit this for something else too that i don't remember now (maybe setting a new remote too) <podiki>so i did a "git push --mirror --no-verify" then i did a clone, had to switch to keyring branch and fetch (i'm sure there's a better way), then back on master branch did guix git authenticate <commit> <key> and all looks good <podiki>i guess because keyring is a detached branch it needs to be handled separately <noe>Why does the package-file procedure need to download all of the dependencies of a package? It says it shouldn’t build the package in the manual <noe>For me it downloads up to the ungrafted version...