Thanks. The downloader gives me an option to rebase, which I find easier to use. It shows me an option to download from ostree-unverified-registry, but I chose to do it from ostree-image-signed:docker instead. Don’t know why the signed image is not shown on the downloader by default. That said, after switching to nvidia from nvidia-open, the driver version still remains the same. Let’s see if I get freezes again in the upcoming days.

Also, there are two applications that I use outside of flatpak - a firewall(Safing Portmaster) and another password manager, for which I have to install using the rpm installer. The password manager has no problem installing using the rpm-ostree install <name.rpm> command. However, Portmaster installs, but won’t work because of the following error which I found from journalctl.

Jul 05 16:28:23 bazzite systemd[1]: Started portmaster.service - Portmaster by Safing.
Jul 05 16:28:29 bazzite portmaster-start[5786]: Error: failed to exec lock: open /opt/safing/portmaster/core-lock.pid: read-only file system
Jul 05 16:28:29 bazzite systemd[1]: portmaster.service: Main process exited, code=exited, status=1/FAILURE
Jul 05 16:28:29 bazzite portmaster-start[5860]: Error: please set the data directory using --data=/path/to/data/dir
Jul 05 16:28:29 bazzite systemd[1]: portmaster.service: Failed with result 'exit-code'.

Someone has supposedly a work in-progress script to make this work, but I don’t think I’m qualified to scrutinize if doing this brings down the security of the system in any way.

And I don’t know if many other rpm installers have the same trouble installing in atomic distros because it’s a read-only file system. For now, I’ll have to live without my favorite firewall.