fix(bluefin, devmode): correctly rebase people to (image)-dx-nvidia-open

[tulilirockz]

This also adds a lil notice for using dx-group after reboot

Should fix: ublue-os/bluefin#4001

[dosubot]

Related Documentation

Checked 8 published document(s) in 0 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[gemini-code-assist]

Code Review

This pull request fixes an issue with rebasing to developer-mode images for variants like nvidia, by correctly constructing the target image name. It also improves the user experience by clarifying instructions and ensuring developer flatpaks are installed correctly when switching. The changes are logical and address the problem described. However, I've identified a related high-severity issue where detecting an existing developer image will fail for these new image name variants, preventing users from switching back. This should be addressed to make the feature fully functional.

[gemini-code-assist]

This change correctly determines the base image name, which is necessary for handling image variants like bluefin-nvidia.

However, this change reveals a significant issue in the logic for detecting if the system is already in developer mode. The check on line 26 (if grep -q -E -e "dx$" <<< "${IMAGE_NAME}") only looks for dx at the very end of the image name.

With this PR, it's now possible to rebase to an image named something like bluefin-dx-nvidia. For such an image, the check on line 26 will fail. This means a user on a ...-dx-nvidia image will be unable to switch back to a non-developer image using this script, as it will incorrectly offer to enable developer mode again.

To ensure the toggle works both ways, the check should be updated to find the -dx infix. For example:

if grep -q -- "-dx" <<< "${IMAGE_NAME}"; then

While this line is outside the diff, this is a critical bug that this PR's changes will expose to users. It should be addressed for the devmode toggle to be reliable.

[fernandomff123]

Hello,

I have reviewed the changes in #157 which were intended to address the OpenImage -> Requesting bearer token -> 403 Forbidden issue.

However, based on my testing:

1. The PR has already been merged and deployed in a recent Bluefin build
2. The error still occurs when running:
   • ujust devmode
   • sudo bootc switch ghcr.io/<user>/<repo>:stable
3. The system reports:

failed to invoke method OpenImage
Requesting bearer token: received unexpected HTTP status: 403 Forbidden

4. bootc status shows an up-to-date Bluefin image (stable-daily)

This indicates that the change in PR 157 does not fully resolve the issue in at least the following scenarios:

• when pulling images from GHCR with a digest SHA (e.g., @sha256:…)
• or when fetching multi-tag manifests
• or when using bearer token scopes that differ between GHCR tags and manifest endpoints

Thus, although PR 157 is present in the codebase, the underlying GHCR authentication problem still blocks bootc switch and ujust devmode, and a follow-up fix is still needed.

Please let me know if you would like additional logs or tests of specific commands.

Thanks!