bug#40682: frozen installer in WiFi section -guix 1.1.0

Hi, SergioBG BG skribis: > Here the screenshot of Frozen. Thanks. Looking at the screenshot, it would seem that the installer is stuck somewhere in ‘connman-connect-with-auth’, but it’s hard to tell why/where. I was able to reproduce it in ‘guix system vm’ with the patch below. Cc: Mathieu

bug#40534: Installer: List of languages should be focused on translated ones

On Fri, 10 Apr 2020 15:46:44 +0200 "pelzflorian (Florian Pelz)" wrote: > On Fri, Apr 10, 2020 at 01:34:40PM +0200, Björn Höfling wrote: > > When starting the Guix installer, the first question is to choose a > > language. > > > > You are confronted with a very long list of all sorts of

bug#40650: ‘scandir*’ test failure

On 2020-04-18, Ludovic Courtès wrote: > Vagrant Cascadian skribis: > >> test-name: scandir*, properties >> location: /build/guix-YPdZIs/guix-1.1.0/tests/syscalls.scm:257 >> source: ... > Looking at this test, the only way ‘every’ could return #f is (1) if > ‘lstat’ returns a different inode

bug#40650: guix test suite failures building Debian package

Vagrant Cascadian skribis: > test-name: store-profile > location: /build/guix-YPdZIs/guix-1.1.0/tests/size.scm:36 > source: [...] > + (bash (interned-file > + (search-bootstrap-binary > + "bash" > +

bug#40650: guix test suite failures building Debian package

Vagrant Cascadian skribis: > test-name: gexp->derivation #:references-graphs > location: /build/guix-YPdZIs/guix-1.1.0/tests/gexp.scm:944 [...] > actual-value: #f > result: FAIL This failure is because of this assumption in the test: ;; Note: %BOOTSTRAP-GUILE depends on the

bug#40650: ‘scandir*’ test failure

Hey, Vagrant Cascadian skribis: > test-name: scandir*, properties > location: /build/guix-YPdZIs/guix-1.1.0/tests/syscalls.scm:257 > source: > + (test-assert > + "scandir*, properties" > + (let ((directory > + (dirname > + (search-path %load-path "guix/base32.scm"

bug#40700: herd restart guix-publish crashes system

I saw that the guix-publish service on my Guix System desktop wasn't running correctly so I went to restart it. I ran 'herd restart guix-publish' and my machine instantly started to shut down. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351

bug#39843: Can't open files through file managers in other DEs and WMs

After removing the workaround from my system configuration file and reconfiguring the system with a recent Guix (see below), things work find in MATE, Xfce and sway. I can't reproduce the problems anymore. $ guix describe Generation 72 Apr 17 2020 08:12:14(current) sirgazil-x 66d4b67

bug#40590:

On Sat, Apr 18, 2020 at 01:47:11PM -0400, Keyhenge wrote: > The amd option didn't work, but nomodeset allowed me to get to a shell, > at which point I could start experimenting with various settings to see > if I could get a graphical environment. I finally did by switching over > to the

bug#40590:

Sorry for the late reply on this. Could you try adding the following kernel parameters (via Grub by pressing 'e', then appending the option at the end of the cmdline): * nomodeset and if it doesn't work: * amd_iommu=pt ivrs_ioapic[32]=00:14.0 iommu=soft The amd option didn't work, but

bug#40525: inferior process on core-updates crashes: mmap(PROT_NONE) failed

Christopher Baines writes: > Ludovic Courtès writes: > >> Glad you manage to get more info. >> >> Christopher Baines skribis: >> >>> Following up on this, I've built Guile on core-updates with libgc@7 >>> rather than libgc@8 (which is what's used above), and I can't reproduce >>> the issue.

bug#40612: guix build system --dry-run is broken

Hi Mark, Mark H Weaver skribis: > Yes, of course, I agree that it's not possible to present a build plan > ahead of time when grafts are enabled. That was the case before these > changes, and it's the case today. > > The only part I don't understand is why you decided that "--dry-run" > should

bug#40652: #36924 way solves the problem for me

Hi, Guillaume Le Vaillant skribis: > Ludovic Courtès skribis: > >> ‘%gdm-activation’ would throw an exception if the “gdm” user didn’t >> exist, so apparently it’s run before the activation snippet of >> ‘account-service-type’ (the ordering guarantee is not explicit.) >> >> Hmm I wonder what

bug#40672: shepherd fails to terminate processes after PID file timeout expiration

Ludovic Courtès skribis: > As discussed during , in > Shepherd 0.7.0, if a process created with ‘fork+exec-command’ & co. with > #:pid-file fails to start before #:pid-file-timeout has expired, > shepherd marks it as failed but the process potentially

bug#36862: Root-owned /var/cache/fontconfig sometimes exists, shouldn't.

Hi! Tobias Geerinckx-Rice skribis: > Sometimes fonts break, and after a few frustrating, impotent runs of > ‘fc-cache -rv’ you notice: > > /var/cache/fontconfig: not cleaning unwritable cache directory > > Deleting this stale (root-owned) directory makes fonts fun > again. Happens about once