bluefin: `ujust bluefin-cli` throwing an error

Describe the bug

I just tried disabling bluefin-cli and then re-enabling it to reset it to default. However when I tried rerunning ujust bluefin-cli I get the following error at the end of the printout:

Error: invalid option: --no-lock
Exiting...
Rerun script with ujust bluefin-cli

Rerunning it throws the same error.

What did you expect to happen?

Expected bluefin-cli to install all the shell bling (back to their defaults) I got used to using.

Output of bootc status

No staged image present
Current booted state is native ostree
Current rollback state is native ostree

Output of groups

andyb wheel

Extra information or context

Let me know if you need anymore information from me. Loving using Bluefin so far and this is the first setback I’ve encountered using it so far.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 22 (10 by maintainers)

Most upvoted comments

This is also the first time I’ve really raised an issue on GitHub before. So do I close this now as the author because my issue has been solved or do I leave it to you members in case you need to do some admin things?

Not back to December.

I’m saying. Make sure updates are working manually first before relying on automatic updates. You were able to install the RPM, but updates broke afterwards. With the update you just received you will now see the date the image was built in Grub which should give you a hint if updates broke.

You will also have to rerun rpm-ostree reset when the major version of Fedora Updates.

Can you make sure you’re up to date on the latest image?

Will do later today when I’m back on my personal laptop