"error: make-custom-binary-output-port: unbound variable" after guix home reconfigure

  • Open
  • quality assurance status badge
Details
3 participants
  • Kristofer Hjelmtorp
  • kristofer
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
kristofer
Severity
normal
K
K
kristofer wrote on 5 May 12:08 +0200
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
1003257793.76369.1714903738678@office.mailbox.org
Hello everyone!

I have somehow managed to get my Guix install into an erroneous state.

After running a "guix home reconfigure" I now get this error backtraces error everytime I try to to anything with guix except "guix --help". Which also means I can't do a roll-back (or at least I have not managed to do it).

I'm running Guix on a foreign distro (Debian container on a Chromebook).

dev@penguin:~ $ guix pull
Backtrace:
11 (primitive-load "/home/dev/.config/guix/current/bin/guix")
In guix/ui.scm:
2312:7 10 (run-guix . _)
2275:10 9 (run-guix-command _ . _)
In ice-9/boot-9.scm:
1755:12 8 (with-exception-handler _ _ #:unwind? _ # _)
1749:15 7 (with-exception-handler #<procedure 7f342cb121e0 at ic…> …)
In guix/store.scm:
662:15 6 (call-with-store #<procedure 7f342ebcd1e0 at guix/scrip…>)
575:2 5 (open-connection _ #:port _ #:reserve-space? _ # _)
In ice-9/boot-9.scm:
1755:12 4 (with-exception-handler _ _ #:unwind? _ # _)
In guix/store.scm:
582:19 3 (_)
942:11 2 (buffering-output-port _ _)
In ice-9/boot-9.scm:
1676:22 1 (raise-exception _ #:continuable? _)
1674:22 0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1674:22: In procedure raise-exception:
error: make-custom-binary-output-port: unbound variable

This is the third time I have managed to get into this state.
The first time I had to uninstall and re-install Guix completely, which fixed it. The second time I had Guix installed in to "~/guix-profile/bin" and could use that to roll-back my home environment.

But this time I don't have that. So I would appreciate any guidance on how to diagnose this and if there are way to get my out of this state without having to uninstall and re-install Guix.

Best Regards
Kristofer
K
K
Kristofer Hjelmtorp wrote on 11 May 10:53 +0200
Same situation in GuixSD install
(name . 70781@debbugs.gnu.org)(address . 70781@debbugs.gnu.org)
1431897402.35672.1715417614975@office.mailbox.org
I now managed to get the same state on my GuixSD machine.
I can do a "sudo guix system reconfigure" but I can't handle my users guix command.
Are re-installation the only option?
Attachment: file
P
P
pelzflorian (Florian Pelz) wrote on 14 May 11:15 +0200
(name . Kristofer Hjelmtorp)(address . kristofer.hjelmtorp@mailbox.org)(name . 70781@debbugs.gnu.org)(address . 70781@debbugs.gnu.org)
87h6f0sqim.fsf@pelzflorian.de
Hello Kristofer. Even though I do not understand at all how to get into
such a state, it appears using an older guix has helped you before, so
you could try running
/var/guix/profiles/per-user/dev/current-guix-<SOME-NUMBER>-link/bin/guix
instead of guix.

Regards,
Florian
K
K
Kristofer Hjelmtorp wrote on 28 May 21:57 +0200
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(name . 70781@debbugs.gnu.org)(address . 70781@debbugs.gnu.org)
1831305061.294129.1716926279409@office.mailbox.org
Hi Florian

Thanks for the response.

With your help I managed to fix my GuixSD install at least.
I couldn't use the "/var/guix/profiles/per-user/dev/current-guix-<SOME-NUMBER>-link/bin/guix" they gave me the same error. But I noticed that there where older Guix Home configuration laying around there and after activating one of those I could roll-back.

I think the issue was that I had added "guile-next" to my Guix Home config.

Toggle quote (11 lines)
> On 05/14/2024 11:15 AM CEST pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:
>
>
> Hello Kristofer. Even though I do not understand at all how to get into
> such a state, it appears using an older guix has helped you before, so
> you could try running
> /var/guix/profiles/per-user/dev/current-guix-<SOME-NUMBER>-link/bin/guix
> instead of guix.
>
> Regards,
> Florian
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 70781
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