Asked for feedback on what to bake into Bazzite and Bluefin

Contributing
1

On Mastodon we asked “what’s something you wish was included in Bazzite or Bluefin?” Linking here for people who want to see the notes we were given as something to work on!

Thanks to @j0rge for chiming in!

2 Likes
2

Some of the results from the Bazzite survey that do not depend on anyone upstream outside of the Universal Blue project:

  • Better installer that has the option to install the OS offline (which will eventually happen soon)
  • Developer focused images (coming soon as bazzite-dx images)
    • Development also being gaming focused (including specifics to web games)
  • COSMIC desktop environment image
  • The implementation of unl0kr for easier encryption/decryption of your drive (Keyboard-less encryption support)
  • Even better handheld PC support (ROG Ally & Legion Go, simplify the experience with 1 ujust command instead of multiple for each decky plugin)
    • Also a ujust command for a specific fan curve for a certain handheld
  • Better integration with containers (Distrobox/Toolbx) [This thread shows off what’s to come]
    • Pre-installed default container
    • Keyboard shortcuts to enter the default container
    • Guidance with containers (cheat sheet outside of documentation from webpages)
  • Changelogs visible outside of a ujust command and external resources (Discourse announcements/newsletters, Github, & website)
    • Perhaps an application that shows the output of ujust changelogs command for Game Mode
  • Options for network post-install configurations like a toggle to enable different DNS servers
  • Wake-On-Lan support for network streaming
  • zram-swap size is too small
  • More battery optimizations
  • ARM support (volunteers are welcome!)
  • Squash remaining bugs and stability (some of these issues may fall under upstream or due to hardware quirks and drivers)
  • “Powerwash” feature (revert Bazzite to stock without using flashing the ISO, also in the Universal Blue roadmap)
  • Transparency about the project’s state and more up-to-date disclosure of major existing issues on download page, website, and Github README
  • Easier for new Linux users who are used to Windows/macOS/etc.
  • Auto-mounting drives could be easier (upstream, but I should finish the guide once I figure out the most universal method for this :smile:)
  • Better documentation for forking Bazzite

A few feedback comments are out of our control of the project. (Steam/Gamescope, desktop environments, upstream applications, Fedora, OCI, OSTree, etc.)

2 Likes
3

Feedback wanted here! Prototyping the Bluefin-cli experience

You can use this on any Linux so if you have people who just know how to use distrobox they can help out here. Once we do that we can bust out a cheat sheet since we need time to daily drive it.

We have ARM builders, what we’re missing here is a volunteer to finish off the ARM images.

This one’s surprising to me because we’re public about everything we do, anyone have any ideas? If anything I feel like I’m overtalking on the forums as to the state of things lol. Also I know the effort nick’s putting into the Bazzite Buzz so I feel like we’re doing a decent job considering no one else is showing up to help. :smiley:

1 Like
4

Is the size something you can configure in /etc? I personally would prefer to have no swap at all.

5

I think so, but I think this user wanted a larger default

6

Will think on how to drill into this point of feedback. I wonder of it’s just a matter of how we package the communication that we do have. I think the Bazzite Buzz is good. I have seen announcements get picked up by a media outlet like with the Bazzite support of the Legion Go.

1 Like
7

Team Fin,

I’d like to see the a defined strategy for extensibility. There are some tools I use which won’t have broad appeal, but I’d like to back them into “my bluefin-dx”. Is the strategy that I fork the toolboxes and extend with personal tools (and then rebase from master) or do you have another strategy in mind?

8

hello,

there are multiple strategies to add tools to your system, If it can work within container there is that option but if it needs(or you just want it to be) to be a part of your host image there are 2 strategies you can use first one is fork the repo but i recommend doing standard OCI container thing and just make your own containerfile which uses FROM statement to extend a previously existing image.

so in case of bluefin-dx that would be FROM ghcr.io/ublue-os/bluefin-dx:latest

you can check out my usage here (it is a bit more involved):

and you can check out my youtube video on this subject here:

Containerfile or Dockerfile uses standard Containerfile constructs Like RUN and COPY and FROM

RPM packages from repos are installed using rpm-ostree command and you have just files you can copy them wherever you want except /var /opt and /usr/local.

if you have any questions let me know

1 Like
9

Oh, is it possible to include tools for controlling CPU, GPU, fan use/curves for the desktop images? On my laptop, it’s been rough with how hot and loud it gets, so having some ways to just hard limit some things would be a great help.

10

What tools do people usually use for these?

11

If you happen to use an Asus ROG laptop, then the Asus image should come with a special utility that I think helps manage that.

12

I vote for neovim as a more modern replacement for vim

13

I also toss in a vote for ripgrep (executable: rg) which is very useful for searching for code in directory tries.