bug#39341: Installer using 100% of a CPU core

[Maxim Cournoyer]

While using the Guix 1.0.1 installer, I noticed that it was constantly
maxing one of the cores on the machine.

The guilty process is:

--8<---cut here---start->8---
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root   377 99.8  0.3  37268 10328 ?Rs   08:20 377:09 
/gnu/store/8asv37pjsq3n4b4hgz9ys840f9j531hk-kmscon-0.0.0-1.01dd0a2/libexec/kmscon/kmscon
 --login --vt tty1 --no-switchvt --login -- 
/gnu/store/cb92798ps1xpla3ai14ik81vkl7jbw97-installer -p
--8<---cut here---end--->8---

bug#39335: GNOME Help: Getting Started: Videos don't start

[sirgazil via Bug reports for GNU Guix]

None of the three videos of the Getting started section of GNOME Help play. It 
seems as if there is no videos at all.


## Steps to reproduce

1. Start GNOME Help (yelp)
2. Go to Getting Started
3. Click any of the three video thumbnails
4. Click the play button


## Expected result

The video should start.


## Unexpected result

The video does not start.


---
https://sirgazil.bitbucket.io/

bug#39281: gdm doesn't start

[Danny Milosavljevic]

Hi,

thanks for the investigation and patch.

Pushed to guix master as commit 9111f9750084cbc214d36e2ee16308f8edabf11d.

Re-added gnome-initial-setup to gnome with
commit 24882d3d9a0529f34217aac2da2c8d6e2a076a63.

Closing bug report.


pgpKnLzzyRQay.pgp
Description: OpenPGP digital signature

bug#39281: gdm doesn't start

[sirgazil via Bug reports for GNU Guix]

  On Tue, 28 Jan 2020 13:21:40 -0500 Jack Hill  wrote 

 > On Tue, 28 Jan 2020, sirgazil wrote:
 > 
 > > The initial setup window did not appear in my case, but I assume it is 
 > > because somewhere in my system something says I already went through the 
 > > setup (I did see the window in a previous boot).
 > 
 > I beilieve this it tell if it has already run by looking for by 
 > ~/.config/gnome-initial-setup-done

Yep, that file is present.

I also tried with a new user, and the initial setup window was shown as 
expected.

Thanks,

bug#39209: Guix-commits digest settings

[Christopher Howard]

Hi,  yes, this looks like it had immediate benificial effect. It looks
like it is packing about five times as many commit messages into each
email, which has dramatically reduced the inbox clutter. Thank you!


-Original Message-
From: Ludovic Courtès 
To: Christopher Howard 
Cc: 39...@debbugs.gnu.org
Subject: Re: bug#39209: Guix-commits digest settings
Date: Mon, 27 Jan 2020 22:49:17 +0100

Hi Christopher,
Christopher Howard  skribis:
Hello, would it be possible for the Guix-commits list administrator
totune the Digest settings, so as to reduce the numbers of Digest
emailssent each day? I'm using Digest mode, but still receive about 8-
15emails per day. One thing that might help is to increase the number
ofmessages that can be lumped into one digest: I frequently receive
twoor three emails within 30 seconds of each other, than have
ninemessages in each. I think you can adjust also how long the system
waitsbefore creating a new digest.
I’ve changed ‘digest_size_threshold’ from 30 to 300 KB.  This option
isdocumented like this:
  digest_size_threshhold (digest): How big in Kb should a digest
be  before it gets sent out? 0 implies no maximum size.
So I think it should be better now.  Let me know!
Ludo’.

-- 
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com

bug#39281: gdm doesn't start

[sirgazil via Bug reports for GNU Guix]

  On Tue, 28 Jan 2020 13:03:08 -0500 Jack Hill  wrote 

 > On Tue, 28 Jan 2020, Leo Prikler wrote:
 > 
 > > I've attached a patch, that should take care of this bug.  So far, I've
 > > only tested it in a VM (with the package added back into gnome), so it
 > > would be nice if one of you could test this with a real reboot before
 > > commiting.

I uncommented gnome-initial-setup, applied Leo's patch, and GDM works as 
expected.

 > I'm happy to report that after applying this patch on top of 
 > 94600c3960d7e2f12a3a9b6d2ed0d98ddacdd055 (i.e. with gnome-initial-setup 
 > still part of the gnome meta-package), reconfiguring, and rebooting, 
 > everything works as expected. GDM starts up, and after I log it, I'm 
 > presented with the initial setup wizard.
 > 

The initial setup window did not appear in my case, but I assume it is because 
somewhere in my system something says I already went through the setup (I did 
see the window in a previous boot).

bug#39281: gdm doesn't start

[Jack Hill]

On Tue, 28 Jan 2020, sirgazil wrote:

The initial setup window did not appear in my case, but I assume it is 
because somewhere in my system something says I already went through the 
setup (I did see the window in a previous boot).


I beilieve this it tell if it has already run by looking for by 
~/.config/gnome-initial-setup-done


Best,
Jack

bug#39281: gdm doesn't start

[Jack Hill]

On Tue, 28 Jan 2020, Leo Prikler wrote:


I've attached a patch, that should take care of this bug.  So far, I've
only tested it in a VM (with the package added back into gnome), so it
would be nice if one of you could test this with a real reboot before
commiting.


I'm happy to report that after applying this patch on top of 
94600c3960d7e2f12a3a9b6d2ed0d98ddacdd055 (i.e. with gnome-initial-setup 
still part of the gnome meta-package), reconfiguring, and rebooting, 
everything works as expected. GDM starts up, and after I log it, I'm 
presented with the initial setup wizard.


Thanks everyone,
Jack

bug#39172: SElinux guix-daemon.cil file

[Matt Wette]

On 1/27/20 1:50 PM, Ludovic Courtès wrote:

Hello,

Ricardo Wurmus  skribis:


Could we also do this in one expression?

 (typeattributeset file_type (or guix_profiles_t
 guix_daemon_conf_t
 guix_daemon_exec_t
 guix_daemon_socket_t
 guix_store_content_t))

I also think we need to declare our use of “file_type” first:

 (typeattribute file_type)

What do you think?

Matt, does what Ricardo proposes work for you?



I can add that and see if it helps.  I am just coming up to speed on this.

There are other changes I may be proposing.
Note that use of

    (block guix_daemon
        ... guix_daemon_conf_t
    )

results in the type guix_daemon.guix_daemon_conf_t.   According to

    https://github.com/SELinuxProject/cil/wiki

the convention is something like the following, with added typealias

 (block guix
   ... daemon_conf
     )

    (typealias guix.daemon_conf guix_daemon_conf_t)

bug#39294: Can't run ./configure

[Julien Lepiller]

Le 28 janvier 2020 03:31:39 GMT-05:00, Efraim Flashner  
a écrit :
>On Tue, Jan 28, 2020 at 09:17:44AM +0100, Damien Cassou wrote:
>> Julien Lepiller  writes:
>> > $ guix environment guix --pure
>> > ^C if your terminal asks you to install whatever
>> > [env]$ ./bootstrap
>> > [env]$ ./configure --localstatedir=/var # this should now work
>> > [env]$ exit # to exit the pure environment
>> > $ guix environment guix # no need for pure anymore, so now we can
>use things outside of the environment too
>> > [env]$ make
>> 
>> This did the trick, thank you. I got a lot of error messages though:
>> 
>> $ guix environment guix
>> guile: warning: failed to install locale
>> substitute:
>/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash:
>warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
>> 
>> 
>> perl: warning: Please check that your locale settings:
>>  LANGUAGE = (unset),
>>  LC_ALL = (unset),
>>  LANG = "en_US.UTF-8"
>> are supported and installed on your system.
>> 

Also try guix install glibc-utf8-locales (and maybe the same for root, I'm not 
sure).

>
>In the daemon service file you can change the Environment field to
>change LC_ALL=en_US.utf8 to en_US.UTF-8.
>
>> 
>> bash: gpg-connect-agent: command not found...
>> Similar command is: 'gpg-connect-agent'
>> bash: gpgconf: command not found...
>> Install package 'gnupg2' to provide command 'gpgconf'? [N/y] y
>> 
>> Failed to install packages: gnupg2-2.2.18-2.fc31.x86_64 is already
>installed

This message is from fedora, not guix. Apparently it tries to run gpg-agent, 
but it can't because you're in a pure environment (the $PATH does not contain 
/usr/bin or /bin). However, the package is already installed, so dnf can't do 
anything :)

At this question, just kill it with a ^C, because if you say no, it will ask 
the same for other packages.

>
>gpg-connect-agent and gpg-connect-agent look similar to me too ...
>
>not sure about gpgconf. Could it have something to do with SElinux?

bug#39294: Can't run ./configure

[zimoun]

Hi Damien,

On Tue, 28 Jan 2020 at 09:38, Damien Cassou  wrote:
> zimoun  writes:

> > Which Guix version do you use (command "guix describe")?
>
> $ guix describe
> guile: warning: failed to install locale
> Generation 1Jan 27 2020 21:46:02(current)
>   guix 4fc4e5f
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e
>
> >  Against which Git commit?
>
> $ git log | head -n 1
> commit 195e1c1b080e41f5405d820a4f02fc7b20194ace

I think it works with these versions.
And the issue you have reported should come from your env variables,
which are turned off when using '--pure' (or '--container').


> I didn't miss it when I tried. I just missed it while writing the
> email. Adding the option didn't change a thing. Also, I followed the
> easy installation method with guix-install.sh to I expect I'm using
> defaults.

Ok, nice! :-)


All the best,
simon

bug#39294: Can't run ./configure

[zimoun]

Hi Damien,

On Tue, 28 Jan 2020 at 09:18, Damien Cassou  wrote:
> Julien Lepiller  writes:

> > $ guix environment guix --pure

[...]

> This did the trick, thank you. I got a lot of error messages though:

You mean using the option '--pure', right?

Which shell do you use ? Bash or a more exotic one?


> $ guix environment guix
> guile: warning: failed to install locale
> substitute: 
> /gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
> warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)

I think Ludo answered you in another bug report [1]. :-)

Well, you need to install 'glibc-locales' both in your user profile
and in the root profile (do not forget to restart the Guix daemon
service).
Note that the subset 'glibc-utf8-locale's provides ("de_DE" "el_GR"
"en_US" "fr_FR" "tr_TR"), lighter than the fill 'glibc-locales' if it
fits your locale.

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39325#8



All the best,
simon

bug#39325: Problem with locales

[Ludovic Courtès]

Hi,

Damien Cassou  skribis:

> I installed Guix using guix-install.sh on Fedora. Whatever I try, I
> always get warnings about locales:
>
> $ guix package --install glibc-locales
> The following package will be upgraded:
>glibc-locales  2.29 → 2.29 
> /gnu/store/03nvilh2x4z07dxv7h13gh986vvgpnsf-glibc-locales-2.29
>
> substitute: 
> /gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
> warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
> substitute: 
> /gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
> warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
> nothing to be done

The warning comes from ‘guix substitute’, which is started by the
daemon.

Could you (1) make sure your /etc/systemd/system/guix-daemon.service
sets the right locale as done in
,
and (2) run “guix pull && guix install glibc-locales@2.29” as root and
restart the service?

Thanks,
Ludo’.

bug#32845: guix.info: Missing manual

[Ludovic Courtès]

Hi,

sirgazil via Bug reports for GNU Guix  skribis:

> The "https://guix.info/manual/; currently redirects to 
> "https://guix.gnu.org/manual/;, which links to the manual in different 
> languages.
>
> Problem solved?

I think so, thanks!

Ludo’.

bug#39281: gdm doesn't start

[Leo Prikler]

Am Montag, den 27.01.2020, 06:24 +0100 schrieb Leo Prikler:
> Perhaps some GNOME people know how to disable this in other ways, but
> it's the first time I've even seen the dialog, so there's not much
> else I can say.
Welp, I found the culprit.  It appears to be a bug in gdm-service-type
rather than the gnome meta-package.  Specifically, the default GDM
setting appears to be to launch the initial-setup inside GDM "on first
boot", whatever GDM interprets that to be.  This can be disabled by
setting "daemon/InitialSetupEnable=false".
Adding this setting to GDM does not affect the initial user setup,
which is probably what raghavgururajan wanted to achieve with the
inclusion of this package into gnome.  It only skips the initial system
setup -- a step that Guix should already take care of on its own.

I've attached a patch, that should take care of this bug.  So far, I've
only tested it in a VM (with the package added back into gnome), so it
would be nice if one of you could test this with a real reboot before
commiting.

Regards,
Leo
From 9c467dfeb2ab942cf70c0f7f75886e052c864907 Mon Sep 17 00:00:00 2001
From: Leo Prikler 
Date: Mon, 27 Jan 2020 23:56:57 +0100
Subject: [PATCH] services: Disable initial setup in GDM.

* gnu/services/xorg.scm (gdm-configuration-file):
Disable gnome-initial-setup.  Starting it from GDM is probably not the right
idea, given that a configuration record for gdm already exists, and it also
causes bugs like #39281.
---
 gnu/services/xorg.scm | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gnu/services/xorg.scm b/gnu/services/xorg.scm
index 9c84f7413f..2b2fd7539d 100644
--- a/gnu/services/xorg.scm
+++ b/gnu/services/xorg.scm
@@ -862,7 +862,10 @@ the GNOME desktop environment.")
"#TimedLoginEnable=false\n"
"#TimedLogin=\n"
"#TimedLoginDelay=0\n"
-   "#InitialSetupEnable=true\n"
+   ;; Disable initial system setup inside GDM.
+   ;; Whatever settings are set there should already be
+   ;; taken care of through `guix system'.
+   "InitialSetupEnable=false\n"
;; Enable me once X is working.
"WaylandEnable=false\n"
"\n"
-- 
2.25.0

bug#39313: Acknowledgement (artanis's guile-json in conflict with guix)

[David Dashyan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Ohh Ricardo & Julien, thaks for clarifying that! I dont'remember typing "guix 
install
guix" :)
- -- 
David aka zzappie
-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEERmd3RaRNN7cv7WgKXWGXeP1hGZIFAl4v738OHG1haWxAZGF2
aWUubGkACgkQXWGXeP1hGZK3GQ/9GodjiI0kF/XgPIe3+i4UDMlLyAn/9opoaPAW
BjceSnmHM55SfVehNRfyeO/ksv49yJ+3yyPUB0VIQOsTN+Lxc3bwWpSHkNJOZWMP
I41I6D3kLcZI8sukdypVRnTfBDQ8rR/5unko5KCQ6OP+PumGN2gS0zRfZbKAaYCf
9E44J5Wle9E0M5eftyWYwHyVFFpCfnp4Rhs/4UQ8XPfOWF5KL12LPCZnQCO8t56q
depfOzciVpkmhOJhlG9nCbheYWyHkctTX32NVvpOk/9H1Aj3fMDfbuXNRY+GZNkA
XEKYIN9RzKmzFiudJ0IjtApFOjO2RFKnE+iwchMTcr1tmmx2rRKxll4kiuz3Gvbi
n5xKw/n6bGiGX5+3e/LzVw5tCvQ566KjKu80FILrbogyz+/9jQyQ7YqSuaAssxIz
4xr43JgYL7/as0BbR0ywDCa4tp0zI9XSa2xGwUoKQqdf2tVj2yhLU3iU6oNMKoFq
EF1yEphNH/S1CpHPd8UiZpPPJ70cjP4EPLeU2pqN0Gr/TDHM/pm1stpbAVkEo80S
OgaqzJtFpHD+BHL+yzm1dkjy45NanKczf13SvBYRa7UEHAf+PbqTFVU1NZ5RjgCY
apvjiaBKbDm6EeVSnMwkzIrHc/13pr7VBxfT6+jr0QOW8eJtpK9dCW8kTb1XL+6a
/LuQKZc=
=YkpR
-END PGP SIGNATURE-

bug#39325: Problem with locales

[Damien Cassou]

Hi,

I installed Guix using guix-install.sh on Fedora. Whatever I try, I
always get warnings about locales:

$ guix package --install glibc-locales
The following package will be upgraded:
   glibc-locales2.29 → 2.29 
/gnu/store/03nvilh2x4z07dxv7h13gh986vvgpnsf-glibc-locales-2.29

substitute: 
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
substitute: 
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
nothing to be done

$ guix describe
Generation 1Jan 27 2020 21:46:02(current)
  guix 4fc4e5f
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e

Best,

-- 
Damien Cassou

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

bug#39294: Can't run ./configure

[Damien Cassou]

zimoun  writes:
> Which Guix version do you use (command "guix describe")?

$ guix describe
guile: warning: failed to install locale
Generation 1Jan 27 2020 21:46:02(current)
  guix 4fc4e5f
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e

>  Against which Git commit?

$ git log | head -n 1
commit 195e1c1b080e41f5405d820a4f02fc7b20194ace

> I do not know if it is related to the option '--localstatedir=/var'.
> But except if you have changed the default when installing Guix, it is
> required at ./configure time. Well, it is documented for example here
> [1] or there [2] or overthere [3]. I know... :-) My question is:
> because you missed it (as I also did),


I didn't miss it when I tried. I just missed it while writing the
email. Adding the option didn't change a thing. Also, I followed the
easy installation method with guix-install.sh to I expect I'm using
defaults.


Best,

-- 
Damien Cassou

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

bug#39294: Can't run ./configure

[Efraim Flashner]

On Tue, Jan 28, 2020 at 09:17:44AM +0100, Damien Cassou wrote:
> Julien Lepiller  writes:
> > $ guix environment guix --pure
> > ^C if your terminal asks you to install whatever
> > [env]$ ./bootstrap
> > [env]$ ./configure --localstatedir=/var # this should now work
> > [env]$ exit # to exit the pure environment
> > $ guix environment guix # no need for pure anymore, so now we can use 
> > things outside of the environment too
> > [env]$ make
> 
> This did the trick, thank you. I got a lot of error messages though:
> 
> $ guix environment guix
> guile: warning: failed to install locale
> substitute: 
> /gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
> warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
> 
> 
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "en_US.UTF-8"
> are supported and installed on your system.
> 

In the daemon service file you can change the Environment field to
change LC_ALL=en_US.utf8 to en_US.UTF-8.

> 
> bash: gpg-connect-agent: command not found...
> Similar command is: 'gpg-connect-agent'
> bash: gpgconf: command not found...
> Install package 'gnupg2' to provide command 'gpgconf'? [N/y] y
> 
> Failed to install packages: gnupg2-2.2.18-2.fc31.x86_64 is already installed

gpg-connect-agent and gpg-connect-agent look similar to me too ...

not sure about gpgconf. Could it have something to do with SElinux?

-- 
Efraim Flashner  אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

bug#39294: Can't run ./configure

[Damien Cassou]

Julien Lepiller  writes:
> $ guix environment guix --pure
> ^C if your terminal asks you to install whatever
> [env]$ ./bootstrap
> [env]$ ./configure --localstatedir=/var # this should now work
> [env]$ exit # to exit the pure environment
> $ guix environment guix # no need for pure anymore, so now we can use things 
> outside of the environment too
> [env]$ make

This did the trick, thank you. I got a lot of error messages though:

$ guix environment guix
guile: warning: failed to install locale
substitute: 
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: 
warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)


perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.


bash: gpg-connect-agent: command not found...
Similar command is: 'gpg-connect-agent'
bash: gpgconf: command not found...
Install package 'gnupg2' to provide command 'gpgconf'? [N/y] y

Failed to install packages: gnupg2-2.2.18-2.fc31.x86_64 is already installed

-- 
Damien Cassou

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

bug#39294: Can't run ./configure

[Damien Cassou]

Gábor Boskovits  writes:
> The issue seems here, is that the current guix is too old.
> guix environment guix should be enough if the current guix and the
> checked out one shares the dependencies.
>
> Could you try this again after 'guix pull'?


this doesn't help. Maybe the installed guix should point to the master
branch? I don't know how to do that though.

-- 
Damien Cassou

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill