Hi,
I upgraded my system today and I've noticed some problems when trying to write
passwords in login pages:
* The text cursor is not shown.
* Writing is horribly slow.
* The input method indicator in the GNOME desktop (top right)
disappears/reappears erratically.
Anyone else experiencing this
Eccomi!
On Sun, 3 Nov 2019 15:23:01 -0500
Leo Famulari wrote:
>
> Hm... I'm not sure but I have a guess.
>
> By default, ntpd will not change your clock if it is very wrong. If it
> is only a couple minutes wrong, then ntpd will slowly adjust the time,
> but if it is wrong by some large thresh
On Mon, Nov 4, 2019 at 9:53 AM Thompson, David wrote:
>
> Sure, I could just grab a bunch of pre-built stuff from Debian's
> repositories and stuff it in a tarball, but I want to use Guix in
> order to have a reproducible toolchain and because this bundle will
> include several Guile libraries tha
Hi,
Thank you for the explanations.
On Sun, 3 Nov 2019 at 18:19, Marius Bakke wrote:
>
> zimoun writes:
> > What should be the correct behaviour of "out" vs "static"?
>
> 'static' outputs typically contain *only* the .a libraries, as you
> found. If you want the headers, you need to add prot
Hello all,
First, context and parameters:
I have a project for which I'd like to release pre-built binaries that
will "just work" on major FHS-based distributions such as Ubuntu and
Fedora. As far as native executables go, this bundle requires Guile
and roughly a dozen C shared libraries. The g
Hello Guix!
Jakob wrote a great tutorial on how to use ‘guix deploy’ to deploy Guix
System to one machine or to several virtual private servers (VPSs):
https://guix.gnu.org/blog/2019/managing-servers-with-gnu-guix-a-tutorial/
Give it a spin, and spread the word!
Ludo’.
Hello,
Jonathan Frederickson skribis:
> On Nov 3, 2019, at 9:24 AM, Ludovic Courtès wrote
>> Now, this would be very much stateful: you can’t tell in advance whether
>> you’re going to build a new profile based on the current Guix, or
>> whether you’re going to reuse a previously cached profile
Ludovic Courtès writes:
> That sounds like a good idea. ‘guix develop’ could keep the profiles it
> manages under ~/.cache/guix.
>
> Now, this would be very much stateful: you can’t tell in advance whether
> you’re going to build a new profile based on the current Guix, or
> whether you’re going
