GNU bug report logs - #64031
Guix system entirely broken by updating second runc or by accidental hard reset

Previous Next

Package: guix;

Reported by: Steven Roose <steven <at> roose.io>

Date: Tue, 13 Jun 2023 02:26:02 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 64031 in the body.
You can then email your comments to 64031 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#64031; Package guix. (Tue, 13 Jun 2023 02:26:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Steven Roose <steven <at> roose.io>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 13 Jun 2023 02:26:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Steven Roose <steven <at> roose.io>
To: bug-guix <at> gnu.org
Subject: Guix system entirely broken by updating second runc or by accidental hard reset
Date: Tue, 13 Jun 2023 04:25:18 +0200
[Message part 1 (text/plain, inline)]
I'm writing this from my phone after a 3 hour attempt to fix my Guix system without success, it seems totally FUBAR.

So here is what I did:

$ guix package -I runc

Shortly after, my battery ran out and my laptop did a hard reset (yes trying to configure hibernate on low battery has been on my todo list for a while). I think the above command already finished when it reset, but I'm not entirely sure. It's been some hours.

So the current situation is this:

* All GUI apps I tried give "command not found", hence no Firefox or Thunderbird.
* My ~/.guix-profile/manifest is empty. Meaning that all guix package commands done in this profile give "unsupported manifest format".
* Idk if this is normal, but listing profiles as my regular user lists two profiles: ~/.guix-profile and ~/.config/guix/current.

I tried various things:

* editing PATH to remove my user profile (thinking this might use another runc) 
* running guix package -r from a root bash using the --profile= flag for the broken profile: same manifest error. When doing this for the ~/.config/guix/current profile, it says no runc found.
* guix pull, reconfigure and reboot from root
* asking for help on IRC (weechat works yay) 

I'm kinda hopeless. I can't do anything productive.

If I should post this in a forum instead of here, feel free to forward me.
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#64031; Package guix. (Tue, 13 Jun 2023 17:03:01 GMT) Full text and rfc822 format available.

Message #8 received at 64031 <at> debbugs.gnu.org (full text, mbox):

From: Steven Roose <steven <at> roose.io>
To: 64031 <at> debbugs.gnu.org
Subject: Re: bug#64031: Acknowledgement (Guix system entirely broken by
 updating second runc or by accidental hard reset)
Date: Tue, 13 Jun 2023 18:02:10 +0100
I figured if my current profile is broken, somehow I should fix it or 
roll it back. I also figure reinstalling my system won't work if I keep 
my home directory.

I also still don't understand why I have two different profiles and I 
don't know what is the different between profiles and whatever `guix 
home` does.

But I tried some things:


$ guix home roll-back
guix home: error: cannot switch to home environment generation '-1'


$ guix home list-generations
Backtrace:
           7 (primitive-load "/home/steven/.config/guix/current/bin/…")
In guix/ui.scm:
   2300:7  6 (run-guix . _)
  2263:10  5 (run-guix-command _ . _)
In ice-9/boot-9.scm:
  1752:10  4 (with-exception-handler _ _ #:unwind? _ # _)
In guix/status.scm:
    859:3  3 (_)
    839:4  2 (call-with-status-report _ _)
In unknown file:
           1 (raise #<&profile-not-found-error profile: "/var/guix/p…>)
In ice-9/boot-9.scm:
  1685:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Wrong type (expecting exact integer): #<&profile-not-found-error 
profile: "/var/guix/profiles/per-user/steven/guix-home">


$ guix home describe
guix home: error: no home environment generation, nothing to describe


So I guess I'm not using `guix home`.


Just to help me move forward, is there a summary on what profiles 
actually are? Because they are separate from the guix system packages 
that it also seems separate from guix home.

On 6/13/23 03:26, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>   bug-guix <at> gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 64031 <at> debbugs.gnu.org.
>
> Please do not send mail to help-debbugs <at> gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>




Information forwarded to bug-guix <at> gnu.org:
bug#64031; Package guix. (Tue, 13 Jun 2023 17:26:01 GMT) Full text and rfc822 format available.

Message #11 received at 64031 <at> debbugs.gnu.org (full text, mbox):

From: Steven Roose <steven <at> roose.io>
To: 64031 <at> debbugs.gnu.org
Subject: Re: bug#64031: Acknowledgement (Guix system entirely broken by
 updating second runc or by accidental hard reset)
Date: Tue, 13 Jun 2023 18:24:54 +0100
Ok, I don't know how to close this issue, but I managed to fix it with 
guix package --roll-back. I took me so long to find that possibility 
because both `guix system` and `guix home` have a `roll-back` *command* 
while in packages it's a flag. I thought it was for individual packages 
maybe.

I don't know how to close issues here, but someone feel free to close this.

On 6/13/23 18:02, Steven Roose wrote:
> I figured if my current profile is broken, somehow I should fix it or 
> roll it back. I also figure reinstalling my system won't work if I 
> keep my home directory.
>
> I also still don't understand why I have two different profiles and I 
> don't know what is the different between profiles and whatever `guix 
> home` does.
>
> But I tried some things:
>
>
> $ guix home roll-back
> guix home: error: cannot switch to home environment generation '-1'
>
>
> $ guix home list-generations
> Backtrace:
>            7 (primitive-load "/home/steven/.config/guix/current/bin/…")
> In guix/ui.scm:
>    2300:7  6 (run-guix . _)
>   2263:10  5 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
>   1752:10  4 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/status.scm:
>     859:3  3 (_)
>     839:4  2 (call-with-status-report _ _)
> In unknown file:
>            1 (raise #<&profile-not-found-error profile: "/var/guix/p…>)
> In ice-9/boot-9.scm:
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Wrong type (expecting exact integer): #<&profile-not-found-error 
> profile: "/var/guix/profiles/per-user/steven/guix-home">
>
>
> $ guix home describe
> guix home: error: no home environment generation, nothing to describe
>
>
> So I guess I'm not using `guix home`.
>
>
> Just to help me move forward, is there a summary on what profiles 
> actually are? Because they are separate from the guix system packages 
> that it also seems separate from guix home.
>
> On 6/13/23 03:26, GNU bug Tracking System wrote:
>> Thank you for filing a new bug report with debbugs.gnu.org.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>   bug-guix <at> gnu.org
>>
>> If you wish to submit further information on this problem, please
>> send it to 64031 <at> debbugs.gnu.org.
>>
>> Please do not send mail to help-debbugs <at> gnu.org unless you wish
>> to report a problem with the Bug-tracking system.
>>




Reply sent to Ludovic Courtès <ludo <at> gnu.org>:
You have taken responsibility. (Thu, 15 Jun 2023 15:56:02 GMT) Full text and rfc822 format available.

Notification sent to Steven Roose <steven <at> roose.io>:
bug acknowledged by developer. (Thu, 15 Jun 2023 15:56:02 GMT) Full text and rfc822 format available.

Message #16 received at 64031-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Steven Roose <steven <at> roose.io>
Cc: 64031-done <at> debbugs.gnu.org
Subject: Re: bug#64031: Guix system entirely broken by updating second runc
 or by accidental hard reset
Date: Thu, 15 Jun 2023 17:55:26 +0200
Steven Roose <steven <at> roose.io> skribis:

> Ok, I don't know how to close this issue, but I managed to fix it with
> guix package --roll-back. I took me so long to find that possibility
> because both `guix system` and `guix home` have a `roll-back`
> *command* while in packages it's a flag. I thought it was for
> individual packages maybe.
>
> I don't know how to close issues here, but someone feel free to close this.

Hi!  Glad you found the explanation and solution.

I’m closing by emailing to 64031-done.

Thanks,
Ludo’.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 14 Jul 2023 11:24:05 GMT) Full text and rfc822 format available.

This bug report was last modified 1 year and 344 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.