Default Flatpaks on a silverblue base

[EvanDurfee]

I've been working on making my own silverblue-based image using the blue-build template, and the dnf package setup is working great. However, I'm having trouble figuring out how to get the default-flatpaks section to work automatically (perhaps due to the rebase process, or starting from a non-ublue image).
Currently, I've been testing by installing silverblue 42 in gnome boxes, then rebasing to my custom image.

Any notion what requirement I might be missing, or where to find more logs?

I see this output after rebasing into the new image:

evan@fedora:~$ systemctl status system-flatpak-setup.timer 
● system-flatpak-setup.timer - Timer for system-flatpak-setup
     Loaded: loaded (/usr/lib/systemd/system/system-flatpak-setup.timer; enabled; preset: disabled)
     Active: active (elapsed) since Sat 2025-10-11 21:08:52 CEST; 1h 56min left
 Invocation: 82ab2e6a9dce4d62b8ab7ceebf69f19a
    Trigger: n/a
   Triggers: ● system-flatpak-setup.service

Oct 11 21:08:52 fedora systemd[1]: Started system-flatpak-setup.timer - Timer for system-flatpak-setup.


evan@fedora:~$ journalctl -u system-flatpak-setup.service 
Oct 11 19:09:16 fedora systemd[1]: Starting system-flatpak-setup.service - Manage system flatpaks...
Oct 11 19:09:16 fedora gnome-software[3234]: Failed to open display
Oct 11 19:09:16 fedora systemd[1]: system-flatpak-setup.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 19:09:16 fedora systemd[1]: system-flatpak-setup.service: Failed with result 'exit-code'.
Oct 11 19:09:16 fedora systemd[1]: Failed to start system-flatpak-setup.service - Manage system flatpaks.

[xynydev]

This seems like a bug. If you're still facing it, make a report in the modules repo with the output of bluebuild-flatpak-manager apply all