bug#68243: alacritty segmentation fault
This is what guix system describe shows: > commit: aabfddbe8bc16fa82067e88e7d79c8c1bc802414 So that should be the one that works, I guess. The newer one doesn't. On 1/7/24 09:06, Efraim Flashner wrote: I meant more of what's the guix version from the generation which contains the non-working alacritty. On Fri, Jan 05, 2024 at 02:51:34PM +, ste...@roose.io wrote: How can I check generations for packages? `guix package -l` doesn't seem to show any useful information. I can't seem to find out what the syntax should be for the PATTERN arguments in guix package, like `guix package --list-generations=PATTERN`. I try `guix package -l alacritty`, `guix package --list-generations=alacritty` but always get `invalid syntax: alacritty`.. On 1/5/24 12:52 PM, Efraim Flashner wrote: On Thu, Jan 04, 2024 at 03:32:55PM +0000, Steven Roose wrote: I've been using alacritty as my default terminal for about a year without much issues. I'm currently on v0.12.3 of alacritty and use it with i3 and Xorg. A month or two ago I noticed that upgrading GuixSD broke alacritty. Since it's my main terminal and I didn't have any other terminals installed, I was forced to rollback my system through GRUB because I couldn't literally not even open a terminal to investigate or roll-back by CLI. I was trying another system upgrade now and noticed the issue is still not fixed. When running alacritty from an already-open alacritty only shows me "segmentation fault". The working and broken version is both 0.12.3, so I think it might not be an alacritty issue but more a linking/build issue. I'm basically stuck on a months-old Guix until this is fixed. If there is any way I can be of use by providing debug/log files of some kind, please let me know. Looking at 'alacritty --help' it looks like you can try adding -v (up to 3) to get a more verbose output so hopefully we get more of an error message. Which generation are you on that is working for you? Which one do you know is segfaulting? I'd like to try to narrow it down.
bug#68243: alacritty segmentation fault
I've been using alacritty as my default terminal for about a year without much issues. I'm currently on v0.12.3 of alacritty and use it with i3 and Xorg. A month or two ago I noticed that upgrading GuixSD broke alacritty. Since it's my main terminal and I didn't have any other terminals installed, I was forced to rollback my system through GRUB because I couldn't literally not even open a terminal to investigate or roll-back by CLI. I was trying another system upgrade now and noticed the issue is still not fixed. When running alacritty from an already-open alacritty only shows me "segmentation fault". The working and broken version is both 0.12.3, so I think it might not be an alacritty issue but more a linking/build issue. I'm basically stuck on a months-old Guix until this is fixed. If there is any way I can be of use by providing debug/log files of some kind, please let me know.
bug#64031: Acknowledgement (Guix system entirely broken by updating second runc or by accidental hard reset)
Ok, I don't know how to close this issue, but I managed to fix it with guix package --roll-back. I took me so long to find that possibility because both `guix system` and `guix home` have a `roll-back` *command* while in packages it's a flag. I thought it was for individual packages maybe. I don't know how to close issues here, but someone feel free to close this. On 6/13/23 18:02, Steven Roose wrote: I figured if my current profile is broken, somehow I should fix it or roll it back. I also figure reinstalling my system won't work if I keep my home directory. I also still don't understand why I have two different profiles and I don't know what is the different between profiles and whatever `guix home` does. But I tried some things: $ guix home roll-back guix home: error: cannot switch to home environment generation '-1' $ guix home list-generations Backtrace: 7 (primitive-load "/home/steven/.config/guix/current/bin/…") In guix/ui.scm: 2300:7 6 (run-guix . _) 2263:10 5 (run-guix-command _ . _) In ice-9/boot-9.scm: 1752:10 4 (with-exception-handler _ _ #:unwind? _ # _) In guix/status.scm: 859:3 3 (_) 839:4 2 (call-with-status-report _ _) In unknown file: 1 (raise #< profile: "/var/guix/p…>) In ice-9/boot-9.scm: 1685:16 0 (raise-exception _ #:continuable? _) ice-9/boot-9.scm:1685:16: In procedure raise-exception: Wrong type (expecting exact integer): #< profile: "/var/guix/profiles/per-user/steven/guix-home"> $ guix home describe guix home: error: no home environment generation, nothing to describe So I guess I'm not using `guix home`. Just to help me move forward, is there a summary on what profiles actually are? Because they are separate from the guix system packages that it also seems separate from guix home. On 6/13/23 03:26, GNU bug Tracking System wrote: Thank you for filing a new bug report with debbugs.gnu.org. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): bug-guix@gnu.org If you wish to submit further information on this problem, please send it to 64...@debbugs.gnu.org. Please do not send mail to help-debb...@gnu.org unless you wish to report a problem with the Bug-tracking system.
bug#64031: Acknowledgement (Guix system entirely broken by updating second runc or by accidental hard reset)
I figured if my current profile is broken, somehow I should fix it or roll it back. I also figure reinstalling my system won't work if I keep my home directory. I also still don't understand why I have two different profiles and I don't know what is the different between profiles and whatever `guix home` does. But I tried some things: $ guix home roll-back guix home: error: cannot switch to home environment generation '-1' $ guix home list-generations Backtrace: 7 (primitive-load "/home/steven/.config/guix/current/bin/…") In guix/ui.scm: 2300:7 6 (run-guix . _) 2263:10 5 (run-guix-command _ . _) In ice-9/boot-9.scm: 1752:10 4 (with-exception-handler _ _ #:unwind? _ # _) In guix/status.scm: 859:3 3 (_) 839:4 2 (call-with-status-report _ _) In unknown file: 1 (raise #< profile: "/var/guix/p…>) In ice-9/boot-9.scm: 1685:16 0 (raise-exception _ #:continuable? _) ice-9/boot-9.scm:1685:16: In procedure raise-exception: Wrong type (expecting exact integer): #< profile: "/var/guix/profiles/per-user/steven/guix-home"> $ guix home describe guix home: error: no home environment generation, nothing to describe So I guess I'm not using `guix home`. Just to help me move forward, is there a summary on what profiles actually are? Because they are separate from the guix system packages that it also seems separate from guix home. On 6/13/23 03:26, GNU bug Tracking System wrote: Thank you for filing a new bug report with debbugs.gnu.org. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): bug-guix@gnu.org If you wish to submit further information on this problem, please send it to 64...@debbugs.gnu.org. Please do not send mail to help-debb...@gnu.org unless you wish to report a problem with the Bug-tracking system.
bug#64031: Guix system entirely broken by updating second runc or by accidental hard reset
I'm writing this from my phone after a 3 hour attempt to fix my Guix system without success, it seems totally FUBAR. So here is what I did: $ guix package -I runc Shortly after, my battery ran out and my laptop did a hard reset (yes trying to configure hibernate on low battery has been on my todo list for a while). I think the above command already finished when it reset, but I'm not entirely sure. It's been some hours. So the current situation is this: * All GUI apps I tried give "command not found", hence no Firefox or Thunderbird. * My ~/.guix-profile/manifest is empty. Meaning that all guix package commands done in this profile give "unsupported manifest format". * Idk if this is normal, but listing profiles as my regular user lists two profiles: ~/.guix-profile and ~/.config/guix/current. I tried various things: * editing PATH to remove my user profile (thinking this might use another runc) * running guix package -r from a root bash using the --profile= flag for the broken profile: same manifest error. When doing this for the ~/.config/guix/current profile, it says no runc found. * guix pull, reconfigure and reboot from root * asking for help on IRC (weechat works yay) I'm kinda hopeless. I can't do anything productive. If I should post this in a forum instead of here, feel free to forward me.
bug#63315: rustc broken because of missing glibc library
Since a week or so, I can't build rust crates that depend on (g?)libc (hint: almost all of them). I get errors like this: /var/cargo-target/debug/build/thiserror-0cbbe89a1097b949/build-script-build: /gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libc.so.6: version `GLIBC_2.34' not found (required by /var/cargo-target/debug/build/thiserror-0cbbe89a1097b949/build-script-build) Somehow my cargo and rustc versions are different though: $ cargo version cargo 1.65.0 $ rustc --version rustc 1.60.0 I find the following in my GNU store (excluding some locales and fhs stuff): /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35/lib /gnu/store/bvr8vy58g56amcs81h2qwa003x8yspv3-glibc-2.35/lib /gnu/store/l0yryi5jsa1grnvw01c9nkz9c81cv224-glibc-2.35-static/lib /gnu/store/ip9mj1pwymxi1yq32zbhwp3n3bycy6yi-glibc-2.35/lib /gnu/store/0hr9jpczkcgpgqkhf4q4868xd57h5a62-glibc-2.35/lib /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/lib /gnu/store/j3cypk9c28iyd7s6q829vc94pwi187cn-glibc-2.33/lib /gnu/store/4jdghmc65q7i7ib89zmvq66l0ghf7jc4-glibc-2.33-static/lib /gnu/store/ayc9r7162rphy4zjw8ch01pmyh214h82-glibc-2.33/lib /gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib So it seems I have v2.33 and v2.35 but not v2.34 (that version doesn't exist in the repo anymore). Also this: $ ls -al /run/current-system/profile/lib/libc.so lrwxrwxrwx 1 root root 76 Jan 1 1970 /run/current-system/profile/lib/libc.so -> /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so $ ls -al /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so lrwxrwxrwx 1 root root 66 Jan 1 1970 /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so -> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35/lib/libc.so $ ls -al /run/current-system/profile/lib/libc.so.6 lrwxrwxrwx 1 root root 78 Jan 1 1970 /run/current-system/profile/lib/libc.so.6 -> /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so.6 $ ls -al /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so.6 lrwxrwxrwx 1 root root 68 Jan 1 1970 /gnu/store/ks87cpc36kh8hqwr569pks4yrzfl7mnv-gcc-toolchain-11.3.0/lib/libc.so.6 -> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35/lib/libc.so.6 So it seems the ones in my profile are 2.35. It's very well possible I did something special in my setup to mess this up because I can't imagine rust building to be broken for everyone. But I can't figure out what I might have done.
bug#63255: Firefox crashes when triggering file dialog open
Whenever I right click and "safe image as" or when I try to do a file upload, firefox segfaults. This is an excerpt trying to save google's logo to disk: ** Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /run/current-system/profile/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Bail out! Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /run/current-system/profile/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Redirecting call to abort() to mozalloc_abort
bug#63247: guix weather should report on all substitute servers configured
Currently guix weather only reports on the two default guix substitute servers. When you have configured other servers in your guix-daemon config, I think it would be expected behavior that guix weather also checks these for the given package. Currently using guix weather with an already-configured substitute URL requires manually passing that URL in --substitute-urls=.
bug#63154: Settings schema 'org.gnome.nm-applet.eap' is not installed
Recently did a system upgrade and getting that error now when entering password for a new wifi network. It also kills the networkmanager applet. Full error: (nm-applet:2051): GLib-GIO-ERROR **: 19:06:02.763: Settings schema 'org.gnome.nm-applet.eap' is not installed Seems related to https://issues.guix.gnu.org/41651 from two years ago.
bug#62818: rust-analyzer broken after rustc got bumped
The Guix version of rust-analyzer that is in rust-apps.scm is somehow dependent on rustc 1.60.0 and seems to use it internally to do compilation and checks. Guix recently published rustc v1.65.0 to the repo and after pulling that in, many compilations fail with some very strange error message "this crate is not compiled for the right Rust version, please recompile with version 1.60". One possible workaround would probably be to instruct rust-analyzer to use a different directory to store its artefacts, but that would mean building everything twice and keeping two sets of build artifacts which can become quite sizable. It seems that either rust-analyzer should be make rustc-version-independent, no idea how that would work, or rust-analyzer should be updated alongside rustc whenever possible.
bug#59850: ecryptfs-utils has a dependency on gettext
The ecryptfs-mount-private util from the ecryptfs-utils package requires gettext.
bug#59850: ecryptfs-utils has a dependency on gettext
Additionally it seems to have a dependency on `keyutils`. On 12/6/22 00:56, Steven Roose wrote: The ecryptfs-mount-private util from the ecryptfs-utils package requires gettext.
bug#59926: request: lnav
Package request: lnav (the log navigator) Website: https://lnav.org/
