From: "Seswu M. Fafnan" <hadaqada@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#37739: System install issue: 'You have a memory leak'
Date: Mon, 14 Oct 2019 09:43:32 +0200 [thread overview]
Message-ID: <20191014094332.2a801c90db91a84c4ab03047@gmail.com> (raw)
In-Reply-To: <87imos8j9i.fsf@gnu.org>
Hello Ludovic :)
Thank you for responding.
Late in the evening, with help from leoprikler at irc #guix, a workaround was found; going manual, which had until then been too overwhelming for me to face.
I just wrote a bit on that as extra information to the bug report, but will quote it below also.
Reproduction is to use the graphical installer; from the beginning:
English, Denmark, Graphical installer;
Europe, Copenhagen, Danish, Danish (no dead keys)
Guided - entire disk with encryption
ATA scsi (choosing my harddisk)
Everything is one partition
Resulting partitioning scheme looked like:
/dev/sda
/boot/efi
576MB fat32
boot,esp
/
1000GB ext4
cryptroot
I did not encounter the same problem doing the population manually.
The output from the manual command and from the graphical install is not the same, so I can't really compare what happened blow-by-blow.
I tried the graphical approach thrice, getting the issue, then following advice did the manual command - actually in an attempt to secure the screen output - and it worked the first time I did it.
I hope that this helped in determining the source of the problem :]
Kind regards,
Uffe
---------------------------------------
With the help of #guix, a workaround was found;
A manual continuation of the install succeeded where the graphical install did not.
'guix system init /mnt/etc/config.scm /mnt' resulted in successful population of /mnt, and in what seems to me to be a functioning system.
---------------------------------------
On Sun, 13 Oct 2019 22:47:53 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> Hi Seswu,
>
> "Seswu M. Fafnan" <hadaqada@gmail.com> skribis:
>
> > I'm trying to install the full guix system on a pc but there's a problem.
> >
> > When "populating '/mnt'", it bails with an error and claims:
> > 'You have a memory leak (not released memory pool)'
>
> I’ve never seen this message before, but looking at the intertubes, it
> may be a bug in GRUB related to encryption:
>
> https://github.com/NixOS/nixpkgs/issues/21830
>
> Could you explain how to reproduce the issue? In particular, what
> partitioning scheme and encryption setup did you choose?
>
> Thanks in advance,
> Ludo’.
--
Seswu M. Fafnan <hadaqada@gmail.com>
next prev parent reply other threads:[~2019-10-14 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 17:48 bug#37739: System install issue: 'You have a memory leak' Seswu M. Fafnan
2019-10-13 20:47 ` Ludovic Courtès
2019-10-14 7:43 ` Seswu M. Fafnan [this message]
2019-10-16 20:30 ` Ludovic Courtès
2019-10-17 6:22 ` Seswu M. Fafnan
[not found] ` <handler.37739.B.15709935495305.ack@debbugs.gnu.org>
2019-10-14 7:17 ` bug#37739: Acknowledgement (System install issue: 'You have a memory leak') Seswu M. Fafnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191014094332.2a801c90db91a84c4ab03047@gmail.com \
--to=hadaqada@gmail.com \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.