unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 17 Oct 2019 08:22:04 +0200	[thread overview]
Message-ID: <20191017082204.4f05a8f689ebb4e6f9eeca36@gmail.com> (raw)
In-Reply-To: <87zhi0igam.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2947 bytes --]

Hello Ludovic,

Yes, I did did a similar install - in fact I was simply 'continuing' the install manually from the point where the graphical install failed.

So, I was using the config file that the graphic config had produced.
I still am.
There is some complaints from the package manager about localization, and also something about putting my .guix-profile directory into an environment variable. I've tried to figure out what the latter is about, but I don't know how it is -supposed- to work, so I'm not sure what to do about it. From what I hear on irc, the profile and probably everything in the .guix-profile dir is repeatedly generated, which means it's not -there- I should correct things probably. So I'm a bit confused on that point.
I also have some trouble with the window manager I chose, i3. It seems it didn't fully install. It's called up, and works.. the status bar didn't though, not until I installed it manually, and I still haven't gotten dmenu to work properly.

Regardless.. those three things are probably besides the point/bug. The system got up and started, it works, I can log into it, and if I knew what I was doing I could probably remedy the remaining things in a snap.

I've attached the config file I used. (generated by the graphical installer)

Uffe


 On Wed, 16 Oct 2019 22:30:57 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Seswu,
> 
> "Seswu M. Fafnan" <hadaqada@gmail.com> skribis:
> 
> > 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.
> 
> So doing a similar installation using the “manual” installation process
> worked, right?
> 
> Did you end up with an OS config file different from the one produced by
> the graphical installer?  Could you post that config file that
> eventually worked so we can compare it to what the installer produces?
> 
> Thanks for the update!
> 
> Ludo’.


-- 
Seswu M. Fafnan <hadaqada@gmail.com>

[-- Attachment #2: config.scm --]
[-- Type: application/octet-stream, Size: 1747 bytes --]

;; This is an operating system configuration generated
;; by the graphical installer.

(use-modules (gnu))
(use-service-modules desktop networking ssh xorg)

(operating-system
  (locale "en_DK.utf8")
  (timezone "Europe/Copenhagen")
  (keyboard-layout
    (keyboard-layout "dk" "nodeadkeys"))
  (bootloader
    (bootloader-configuration
      (bootloader grub-efi-bootloader)
      (target "/boot/efi")
      (keyboard-layout keyboard-layout)))
  (mapped-devices
    (list (mapped-device
            (source
              (uuid "d1a5a5b6-7205-4005-9f55-989d33f3264e"))
            (target "cryptroot")
            (type luks-device-mapping))))
  (file-systems
    (cons* (file-system
             (mount-point "/boot/efi")
             (device (uuid "35CD-F935" 'fat32))
             (type "vfat"))
           (file-system
             (mount-point "/")
             (device "/dev/mapper/cryptroot")
             (type "ext4")
             (dependencies mapped-devices))
           %base-file-systems))
  (host-name "tabula-rasa")
  (users (cons* (user-account
                  (name "seswu")
                  (comment "Seswu")
                  (group "users")
                  (home-directory "/home/seswu")
                  (supplementary-groups
                    '("wheel" "netdev" "audio" "video")))
                %base-user-accounts))
  (packages
    (append
      (list (specification->package "i3-wm")
            (specification->package "nss-certs"))
      %base-packages))
  (services
    (append
      (list (service openssh-service-type)
            (service tor-service-type)
            (set-xorg-configuration
              (xorg-configuration
                (keyboard-layout keyboard-layout))))
      %desktop-services)))

  reply	other threads:[~2019-10-17 12:02 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
2019-10-16 20:30     ` Ludovic Courtès
2019-10-17  6:22       ` Seswu M. Fafnan [this message]
     [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191017082204.4f05a8f689ebb4e6f9eeca36@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).