bug#35549: dune failure

2019-05-04 Thread Gabriel Hondet
The error was mine, sorry, ocamlfind was not installed through guix and thus the paths returned were wrong. I'm closing this. Gabriel signature.asc Description: PGP signature

bug#35549: dune failure

2019-05-04 Thread Ricardo Wurmus
> I'm closing this. Closing. -- Ricardo

bug#35395: GUIX website redirections are failing

2019-05-04 Thread Ludovic Courtès
Hello, Most redirects are now gone (that is, the web site itself doesn’t refer to them), so I think we can close this bug. Thanks, Ludo’.

bug#35350: Some compile output still leaks through with --verbosity=1

2019-05-04 Thread Ludovic Courtès
Hi Mark, Mark H Weaver skribis: > Ludovic Courtès writes: [...] >> So there are two things. To fix the issue you reported (build output >> that goes through), I think we must simply turn off UTF-8 decoding from >> ‘process-stderr’ and leave that entirely to ‘build-event-output-port’. > > Can

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread Mathieu Othacehe
Hello, > I believe I read about Guile error messages not doing line wrapping in > terminals on the Guix or Guile mailing lists recently, but I cannot > find it. Proper line wrapping may be the better solution. In fact the textbox where the backtrace is displayed isn't doing any line wrapping. Th

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 11:43:28AM +0200, Mathieu Othacehe wrote: > Hello, > > > I believe I read about Guile error messages not doing line wrapping in > > terminals on the Guix or Guile mailing lists recently, but I cannot > > find it. Proper line wrapping may be the better solution. > > In fac

bug#35541: Installer does not add %base-packages

2019-05-04 Thread Ludovic Courtès
Hello, Ludovic Courtès skribis: > I think we should email info-g...@gnu.org and possibly write a post on > the blog within at most two days with an explanation of the issue, > workarounds, proper fix (which is to edit the config file and > reconfigure), and an ETA for the bug-fix release. Unles

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread Ludovic Courtès
Hi, sirga...@zoho.com skribis: > In my case, "wpa-supplicant" would *always* fail to start (I rebooted and > tried the graphical installer around 4 times). Could you check whether the sequence of events in /var/log/messages always looks like the snippet I showed? Could you also: 1. Let the

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread Danny Milosavljevic
Hi, On Sat, 4 May 2019 14:24:03 +0200 "pelzflorian (Florian Pelz)" wrote: > I now get linewrapping, but provoked errors (these are not new bugs!) > are cut off like > > In ./gnu/installer/keymap.scm > 163:7 8 (_ _) > In unknown file: >7 (scm-error misc-error #f "~A" ("Unable to

bug#35553: getlogin and getlogin_r fail with error ENXIO

2019-05-04 Thread Danny Milosavljevic
http://man7.org/linux/man-pages/man8/pam_loginuid.8.html suggests that we should use that for all "entry point"s for the user. I guess we can add it. Are you logging in using gdm? We don't refer to pam_loginuid.so anywhere, so it's understandable that /proc/self/loginuid is not set either. Appa

bug#35559: armhf-linux flash image: "No space left on device"

2019-05-04 Thread Danny Milosavljevic
http://berlin.guixsd.org/log/64f1pzamnmb0x2bi8krp78nnbywpkqh1-disk-image ERROR: In procedure copy-file: In procedure copy-file: No space left on device copying 410 store items [ ]Backtrace: In ./gnu/build/vm.scm: 337:3 19 (initialize-par

bug#35553: getlogin and getlogin_r fail with error ENXIO

2019-05-04 Thread Bruno Haible
Danny Milosavljevic wrote: > Are you logging in using gdm? I'm using the guix-1.0 installation image (guix-system-vm-image-1.0.0.x86_64-linux). It shows a screen "Logging in..." for less than one second and then starts the user's desktop immediately. Bruno

bug#35541: Installer does not add %base-packages

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 02:40:30PM +0200, Ludovic Courtès wrote: > Please tell me what you think! > It is a good text. However, I find it more tragic that Xfce and MATE do not work than that these commands are missing until installed, but it depends on the audience I guess. Regards, Florian

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 02:49:55PM +0200, Ludovic Courtès wrote: > Hi, > > sirga...@zoho.com skribis: > > > In my case, "wpa-supplicant" would *always* fail to start (I rebooted and > > tried the graphical installer around 4 times). > > Could you check whether the sequence of events in /var/log

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Ludovic Courtès
Hello! GNOME Shell is crashy since the 3.28 upgrade (it’s an install that was made before the 3.28 upgrade; I wonder whether the same happens on a fresh install.) It occasionally crashes (SIGSEGV) and is automatically respawned, which is kinda okay: as a user, you notice that it flickers for a se

bug#35380: disk-image fails to install efi grub

2019-05-04 Thread Marius Bakke
rendaw <7e9wc56emja...@s.rendaw.me> writes: > On 5/4/19 12:10 AM, Marius Bakke wrote: >> rendaw <7e9wc56emja...@s.rendaw.me> writes: >> >>> On 5/3/19 7:17 AM, Marius Bakke wrote: That means you can't just take an operating system hard drive from one EFI system to another. >>> I'm absolut

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Timothy Sample
Hi Ludo, Ludovic Courtès writes: > Hello! > > GNOME Shell is crashy since the 3.28 upgrade (it’s an install that was > made before the 3.28 upgrade; I wonder whether the same happens on a > fresh install.) GNOME Shell has been quite stable for me since Ricardo made sure that it was using GDK-Pi

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 04:13:20PM +0200, Ludovic Courtès wrote: > Hello! > > GNOME Shell is crashy since the 3.28 upgrade (it’s an install that was > made before the 3.28 upgrade; I wonder whether the same happens on a > fresh install.) > On a fresh install I have no such issues, however pressi

bug#35541: Installer does not add %base-packages

2019-05-04 Thread Ludovic Courtès
"pelzflorian (Florian Pelz)" skribis: > On Sat, May 04, 2019 at 02:40:30PM +0200, Ludovic Courtès wrote: >> Please tell me what you think! >> > > It is a good text. However, I find it more tragic that Xfce and MATE > do not work than that these commands are missing until installed, but > it dep

bug#35541: Installer does not add %base-packages

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 04:54:23PM +0200, Ludovic Courtès wrote: > "pelzflorian (Florian Pelz)" skribis: > > On Sat, May 04, 2019 at 02:40:30PM +0200, Ludovic Courtès wrote: > >> Please tell me what you think! > >> > > > > It is a good text. However, I find it more tragic that Xfce and MATE > >

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread Ludovic Courtès
Ludovic Courtès skribis: > You would expect wpa_supplicant to create its PID file atomically: write > it under a different name, then rename(2)… but no: Shepherd commit 72631752149d000c8c98ae0cc66e0b0c2eda94ef changes ‘read-pid-file’ to better deal with this. Ludo’.

bug#35561: Fresh install, guix pull exits with error, hash mismatch

2019-05-04 Thread Calle Kabo
manager@guix ~$ guix pullMigrating profile generations to '/var/guix/profiles/per-user/manager'...substitute: updating substitutes from 'https://ci.guix.gnu.org '... 100.0%substitute: updating substitutes from 'https://ci.guix.gnu.org '... 100.0

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread Ludovic Courtès
Hi Florian, "pelzflorian (Florian Pelz)" skribis: >> Could you also: >> >> 1. Let the installation image boot; >> >> 2. Confirm with ‘herd status wpa-supplicant’ that the ‘wpa-supplicant’ >> service is marked as stopped (failed to start); >> > > $ herd status wpa-supplicant > Status o

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 05:32:23PM +0200, Ludovic Courtès wrote: > At this point, could you also check: > > 3b. The output of “pgrep -fa wpa_supplicant”. > root@gnu ~# pgrep -fa wpa_supplicant 481 /gnu/store/ifqy2dr2hbqplv14k50dzprw3k2bz9m9-wpa-supplicant-2.7/sbin/wpa_supplicant -P/var/run/w

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread Mathieu Othacehe
Hey, > ,use (system repl debug) ; or #:use-module (system repl debug) > (terminal-width 200) > > f.e. at the top of gnu/installer.scm Thanks for testing Florian. Based on Danny suggestion we could set COLUMNS to 200 to have a more verbose backtrace (like guix itself). Using higher values,

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread Mathieu Othacehe
And the patch ... Sorry, Mathieu >From 3348df0c72e9bcdf31b63155d9c6bdbaee515524 Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Sat, 4 May 2019 18:10:40 +0200 Subject: [PATCH] installer: Increase backtrace verbosity. * gnu/installer.scm (installer-program): Set COLUMNS env variable to 20

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Ricardo Wurmus
Timothy Sample writes: >> GNOME Shell is crashy since the 3.28 upgrade (it’s an install that was >> made before the 3.28 upgrade; I wonder whether the same happens on a >> fresh install.) > > GNOME Shell has been quite stable for me since Ricardo made sure that it > was using GDK-PixBuf with SV

bug#35530: NSS-3.43 fails its test suite on armhf-linux

2019-05-04 Thread Ricardo Wurmus
Ricardo Wurmus writes: > Mark H Weaver writes: > >> NSS-3.43 fails its test suite on armhf-linux: >> >> https://hydra.gnu.org/build/3484222 > > I can reproduce this. Looks like all problems are with the tests in > ssl_drop_unittest.cc: > > ssl_drop_unittest.cc:182: Failure > ssl_drop_un

bug#35541: Installer does not add %base-packages

2019-05-04 Thread Ricardo Wurmus
Ludovic Courtès writes: > Ludovic Courtès skribis: > >> I think we should email info-g...@gnu.org and possibly write a post on >> the blog within at most two days with an explanation of the issue, >> workarounds, proper fix (which is to edit the config file and >> reconfigure), and an ETA for

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread Danny Milosavljevic
Hi Mathieu, On Sat, 04 May 2019 18:14:48 +0200 Mathieu Othacehe wrote: > Thanks for testing Florian. Based on Danny suggestion we could set > COLUMNS to 200 to have a more verbose backtrace (like guix itself). Good idea in principle. > Using higher values, the backtrace becomes really long and

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 06:14:48PM +0200, Mathieu Othacehe wrote: > Thanks for testing Florian. Based on Danny suggestion we could set > COLUMNS to 200 to have a more verbose backtrace (like guix itself). > It works (I have applied both patches). This is one of the longer backtrace steps: In ic

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 07:06:17PM +0200, Danny Milosavljevic wrote: > So I'd be for either presenting the entire backtrace or suppressing the > entire backtrace, not having teaser backtraces :) Let’s assume someone is getting an error in the installer for some reason. If they are Guix developers

bug#35542: Installer does not display full backtrace on error

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 07:38:07PM +0200, pelzflorian (Florian Pelz) wrote: > On Sat, May 04, 2019 at 07:06:17PM +0200, Danny Milosavljevic wrote: > > So I'd be for either presenting the entire backtrace or suppressing the > > entire backtrace, not having teaser backtraces :) > > Let’s assume some

bug#35350: Some compile output still leaks through with --verbosity=1

2019-05-04 Thread Mark H Weaver
Hi Ludovic, Ludovic Courtès writes: > Mark H Weaver skribis: > >> Ludovic Courtès writes: > > [...] > >>> So there are two things. To fix the issue you reported (build output >>> that goes through), I think we must simply turn off UTF-8 decoding from >>> ‘process-stderr’ and leave that entire

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Mark H Weaver
Ludovic Courtès writes: > GNOME Shell is crashy since the 3.28 upgrade (it’s an install that was > made before the 3.28 upgrade; I wonder whether the same happens on a > fresh install.) > > It occasionally crashes (SIGSEGV) and is automatically respawned, which > is kinda okay: as a user, you not

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Mark H Weaver
Earlier, I wrote: > FWIW, I've found GNOME Shell to be quite solid on my X200, including > since the 3.28 upgrade. However, I run it under Wayland, by running > "XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session" from a > text console. Perhaps that makes a difference? > >> The thing t

bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media

2019-05-04 Thread Ricardo Wurmus
Mark H Weaver writes: > Earlier, I wrote: > >> FWIW, I've found GNOME Shell to be quite solid on my X200, including >> since the 3.28 upgrade. However, I run it under Wayland, by running >> "XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session" from a >> text console. Perhaps that mak

bug#35566: Dvorak keyboard layout in graphical installl mode

2019-05-04 Thread Daniel Dinnyes
Hi All, I have been trying to install Guix with System Install method, using a ISO image with KVM. I found that in the graphical install mode, while being asked for keyboard layout, there was no option for Dvorak layout. Not sure if this is intentional, or left out by accident, but it is something

bug#35540: Installer displays encrypted partition password entry in cleartext

2019-05-04 Thread pelzflorian (Florian Pelz)
On Fri, May 03, 2019 at 03:50:52PM +0200, Ludovic Courtès wrote: > That’s why I think that seeing what you actually type is useful. > Seeing the password is useful, unless someone is shoulder surfing while you install, which is possible. > Other options include: > > 1. Hiding the passphrase,

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread Ludovic Courtès
Hi, "pelzflorian (Florian Pelz)" skribis: > On Sat, May 04, 2019 at 05:32:23PM +0200, Ludovic Courtès wrote: [...] >> Could you also try running (as root): >> >> while herd restart wpa-supplicant; do : ; done >> >> to see the frequency at which the service fails to start? >> > > It display

bug#35541: Installer does not add %base-packages

2019-05-04 Thread Ludovic Courtès
"pelzflorian (Florian Pelz)" skribis: > On Sat, May 04, 2019 at 04:54:23PM +0200, Ludovic Courtès wrote: >> "pelzflorian (Florian Pelz)" skribis: >> > On Sat, May 04, 2019 at 02:40:30PM +0200, Ludovic Courtès wrote: >> >> Please tell me what you think! >> >> >> > >> > It is a good text. Howeve

bug#35550: Installer: wpa_supplicant fails to start

2019-05-04 Thread pelzflorian (Florian Pelz)
On Sat, May 04, 2019 at 11:14:29PM +0200, Ludovic Courtès wrote: > Hi, > > "pelzflorian (Florian Pelz)" skribis: > > > On Sat, May 04, 2019 at 05:32:23PM +0200, Ludovic Courtès wrote: > > [...] > > >> Could you also try running (as root): > >> > >> while herd restart wpa-supplicant; do : ;

bug#35569: [core-updates] bison is not reproducible

2019-05-04 Thread Maxim Cournoyer
It seems that the static library archive 'liby.a' contains build time timestamps: --8<---cut here---start->8--- diffoscope --exclude-command bin/stat /gnu/store/aqcpvkx93zbf1zr46qi5h1yf6a1cj9i1-bison-3.3.2{,-check} --- /gnu/store/aqcpvkx93zbf1zr46qi5h1yf6a1cj9

bug#35371: [core-updates] python-cffi fails its test suite

2019-05-04 Thread Maxim Cournoyer
Maxim Cournoyer writes: [...] > _ test_dlopen > __ > > def test_dlopen(): > ffi = FFI() > ffi.cdef("double sin(double x);") >> m = ffi.dlopen(lib_m) # unicode literal > > testing/

bug#35573: containerd is not reproducible

2019-05-04 Thread Maxim Cournoyer
On the master branch: --8<---cut here---start->8--- diffoscope --exclude-command=bin/stat /gnu/store/hvjq3730myw4bz1prha0sy1iasjs92zb-containerd-1.2.5{,-check} --- /gnu/store/hvjq3730myw4bz1prha0sy1iasjs92zb-containerd-1.2.5 +++ /gnu/store/hvjq3730myw4bz1prha0s

bug#35529: libdrm fails to build on armhf-linux

2019-05-04 Thread Ricardo Wurmus
Mark H Weaver writes: > Hydra failed two consecutive attempts to build libdrm on armhf-linux: > > https://hydra.gnu.org/build/3481547#tabs-summary > > Both build attempts were made on hydra-slave2, which is a Wandboard Quad > based on the Freescale i.MX6 SOC. This has built fine on berlin.

bug#35574: bcm5974 touchpad is not recognized as touchpad

2019-05-04 Thread pelzflorian (Florian Pelz)
On *some* reboots my Macbook’s touchpad does not work properly; it behaves like mouse wheel, I can only scroll. Only when I press it down, I can move the pointer to the right, but never to the left. This happens both with synaptics and libinput driver. Restarting xorg-server does not help; this