From: Quiliro Ordonez Baca <quiliro@riseup.net>
To: 29662@debbugs.gnu.org
Subject: bug#29662: 'guix gc' as user makes system unbootable
Date: Mon, 11 Dec 2017 12:21:26 -0500 [thread overview]
Message-ID: <874lox89g5.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me> (raw)
'guix gc' as user makes system unbootable.-
I had executed 'guix gc' and then 'guix package -i blender' and then
'guix package -u', all as user without running 'guix pull' recently
(did it last week). When rebooting, current GrUB boot menu entry did
not work. But previous versions (#1,#2,#3) worked at different
levels. Below each menu entry I post my experience upon boting with
it:
menuentry "GNU with Linux-Libre 4.12.9 (beta)"
Kernel panic
menuentry "GNU with Linux-Libre 4.11.6 (beta) (#1, 2017-06-21 18:01)"
No GUI. Lost keyboad configuration on tty's. Logged in as user. The
output of 'sudo herd status' was 'error: connect:
/var/run/shepherd/socket: No existe el fichero o el directorio'.
menuentry "GNU with Linux-Libre 4.11.6 (beta) (#2, 2017-06-22 15:49)"
Working GUI (no local keyboard as usual) and working Herd. Lost keyboad configuration on tty's.
menuentry "GNU with Linux-Libre 4.11.6 (beta) (#3, 2017-06-30 13:36)"
Working GUI (no local keyboard as usual) and working Herd. Lost keyboad configuration on tty's.
menuentry "GNU with Linux-Libre 4.11.6 (beta) (#4, 2017-06-30 14:57)"
Kernel panic
menuentry "GNU with Linux-Libre 4.11.8 (beta) (#5, 2017-07-02 19:30)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.2 (beta) (#6, 2017-07-16 09:38)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.9 (beta) (#7, 2017-08-31 00:10)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.9 (beta) (#8, 2017-08-31 00:19)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.9 (beta) (#9, 2017-08-31 00:46)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.9 (beta) (#10, 2017-08-31 06:15)"
Kernel panic
menuentry "GNU with Linux-Libre 4.12.9 (beta) (#11, 2017-09-02 15:48)"
Kernel panic
This situation has happened before and has, as in this time, made my
installation unbootable. But I did not notice that it was because of
'guix gc', until now. Is it normal that a user can affect the boot
process for the whole operating system?
next reply other threads:[~2017-12-11 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 17:21 Quiliro Ordonez Baca [this message]
2017-12-11 21:14 ` bug#29662: 'guix gc' as user makes system unbootable Ricardo Wurmus
2017-12-11 21:26 ` Quiliro Ordonez Baca
2017-12-11 21:40 ` Ricardo Wurmus
2017-12-11 22:03 ` Quiliro Ordonez Baca
2017-12-20 14:49 ` Ricardo Wurmus
2017-12-21 21:06 ` Quiliro Ordonez Baca
2017-12-17 22:23 ` Martin Castillo
2017-12-18 9:54 ` Ludovic Courtès
2017-12-18 14:18 ` Martin Castillo
2017-12-18 14:31 ` Ludovic Courtès
2017-12-18 14:46 ` Martin Castillo
2018-01-08 14:34 ` Ludovic Courtès
2018-01-08 18:37 ` Martin Castillo
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=874lox89g5.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me \
--to=quiliro@riseup.net \
--cc=29662@debbugs.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).