Guix system entirely broken by updating second runc or by accidental hard reset

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Steven Roose
Owner
unassigned
Submitted by
Steven Roose
Severity
normal
S
S
Steven Roose wrote on 13 Jun 2023 04:25
Guix system entirely broken by updating second runc or by accidental hard reset
(address . bug-guix@gnu.org)
FA78DB4C-DF5A-4134-8CEE-D71867760C62@roose.io
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.
Attachment: file
S
S
Steven Roose wrote on 13 Jun 2023 19:02
Re: bug#64031: Acknowledgement (Guix system entirely broken by updating second runc or by accidental hard reset)
(address . 64031@debbugs.gnu.org)
b1bbf3a2-5682-57eb-ffee-88a37d4d032f@roose.io
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:
Toggle quote (17 lines)
> 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@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 64031@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
S
S
Steven Roose wrote on 13 Jun 2023 19:24
(address . 64031@debbugs.gnu.org)
536795e0-d29a-04e5-2437-713bc0a1b055@roose.io
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:
Toggle quote (65 lines)
> 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@gnu.org
>>
>> If you wish to submit further information on this problem, please
>> send it to 64031@debbugs.gnu.org.
>>
>> Please do not send mail to help-debbugs@gnu.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
L
L
Ludovic Courtès wrote on 15 Jun 2023 17:55
Re: bug#64031: Guix system entirely broken by updating second runc or by accidental hard reset
(name . Steven Roose)(address . steven@roose.io)(address . 64031-done@debbugs.gnu.org)
87sfasvhxt.fsf_-_@gnu.org
Steven Roose <steven@roose.io> skribis:

Toggle quote (8 lines)
> 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’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 64031@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64031
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch