Let’s use this thread for feedback/ideas, and then we can be good OSS citizens by kicking the tyres to get the terminal of our dreams! Here’s our in progress pull request for Bluefin.
If you’ve not used GNOME nightly remotes before, here’s a good article from OMGLinux so that you can move back to the stable release in the future.
My bazzite-deck-gnome:testing image shows a problem when using Prompt, which is installed as a host binary instead of a Flatpak. On a fresh boot, when I start Prompt, it can’t find any containers. I’ve checked that prompt-agent does get correctly started with the correct arguments, but for some reason, it doesn’t correctly see and enumerate my existing distrobox containers. However, if I manually run a podman ps before starting Prompt, then containers are correctly shown and listed.
It doesn’t have to be podman ps – if I just wait for the ublue-update script to run ~20 minutes after boot, then it touches the distrobox containers, which also allows Prompt to see them correctly. Presumably if you run any distrobox services at boot or login, then it should also “fix” the problem.
Can anyone else please verify whether this is true for them as well?
Someone more systemd-savvy than I could try creating a systemd unit that just runs podman ps on boot to list available containers without the overhead of entering one. That might be enough.
I’ve also commented on that issue that you’ve linked on GitLab.
There’s still a larger issue with Prompt just not always working correctly with distrobox containers. Any user-created distrobox containers would be a potential source of headaches when using Prompt, especially if one is picked as the default container in the profile. I feel like there is a bug there in Prompt that still needs to be fixed.
Ok I’ve set up a wiki page with some instructions/tips for using Prompt. Additions/fixes welcome, also if you have your own setup you wanna share we can document whatever we want.
