Aurora-cli and bling and possibly zsh problems

I did a new Aurora install, and IDK what I did or if it was in the wrong order, but enabling aurora-cli failed on a couple of brew packages. I tried to enable bling and that gave back an error.

Changed to zsh and tried to run it again and got errors. Starship wasn’t being sourced and the bling script wasn’t being run.

Has anybody else had any issues on a new install lately?

I ended up just copying my .zshrc from my other Aurora install and that fixed things. I’m willing to chalk this all up to some weird confluence of failed brew install and dependency issues which broke the whole flow of things, but I thought I’d report it anyhow.

Propably related to the refactor of ublue-bling.

It has currently some issues. But what kind of errors did you get? and was this with updated image right after install?

It was after the updated image as you say. I should of saved the errors. I’ll fire up a new image this morning via VM and see if I can’t replicate it. If I recall it was unable to enable bling something around line 37 or 38.’

Also…weirdly when I exit ujust --choose menu I get this:

✗  ujust --choose
error: Chooser `fzf --multi --preview 'just --unstable --color always --justfile "/usr/share/ublue-os/just/00-entry.just" --show {}'` failed: exit status: 1

I can’t see how that would be related but I thought I’d throw it out there.

yeah, its not related and that “error” has always been there. Its just how the chooser menu has been don using fzf etc.

So what happens that if you exit with ESC or CTRL+c the programs quits as it interprets it as “no valua entered”

The exit code 130 in Unix-like systems standardly represents termination by signal SIGINT (Signal Interrupt). The system interprets this not as a “clean exit,” but as the chooser process failing to return a value, hence the “failed” error message.

weird that I didn’t notice that before. I guess I don’t use the --choose option that often. Very interesting. Thanks for the explanation.