Before participating in this test event, please first read the F45 Anaconda Installer new features instructions (opens in a new tab) .
Atomic desktops (Silverblue, Kinoite, Cosmic/Sway/Budgie Atomic)
| Username | Profile | Default install | Guided partitioning | Custom partitioning | Comments |
|---|---|---|---|---|---|
| Atomic desktop name, and other useful details (hw specs) | |||||
|
Alan B Saichek
|
Kinoite raw-xz aarch64 Fedora-45-20260930.n.0 Rpi 400 (Portuguese), 4 GB RAM, 32 GB Samsung EVO plus SD card |
[1]
[2] [3] [4] |
[1]
sudo arm-image-installer --image=Fedora-Kinoite-Disk-45-20260930.n.0.aarch64.raw.xz --target=rpi4 --media=/dev/sdc --resizefs = Raspberry Pi 4 Uboot is already in place, no changes needed. = Installation Complete! Insert into the rpi4 and boot. Progress: Trying boot mode USB-MSD ..., SPACE key, "1" for boot mode "SD" Firmware not found
[2] sudo arm-image-installer --image=Fedora-Kinoite-Disk-45-20260930.n.0.aarch64.raw.xz --target=rpi4 --media=/dev/sdc --resizefs, = Raspberry Pi 4 Uboot is already in place, no changes needed. = Installation Complete! Insert into the rpi4 and boot. Progress: Trying boot mode USB-MSD ..., SPACE key, "1" for boot mode, "SD", ... Firmware not found." A prior installation of Fedora 44 LXQt on a different 32GB SD booted okay on the same Rpi400 afterward. [3] sudo arm-image-installer --image=Fedora-Kinoite-Disk-45-20260930.n.0.aarch64.raw.xz --target=rpi4 --media=/dev/sdc --resizefs [4] sudo arm-image-installer --image=Fedora-Kinoite-Disk-45-20260930.n.0.aarch64.raw.xz --target=rpi4 --media=/dev/sdc --resizefs |
||
|
Alan B Saichek
|
Kinoite raw-xz aarch64 Fedora-45-20260930.n.0 Rpi 400 (Portuguese), 4 GB RAM, 64 GB USB-MSD | [1] | [1] board: rev c03131 000, boot: mode USB-MSD 4 order f41 retry, part: 1 mbr, bw: start.elf fixup.dat Trying partition 0, 1, Firmware not found | ||
|
Francis Teruel
|
Fedora-COSMIC-Live-45-20261001.n.0.x86_64 | Bare metal: AMD Ryzen 5 7600X, AMD Radeon RX 6500 XT (4GB), 32GB RAM, 1TB SSD | [1] | [1] Correction: I realized after submitting that I tested the traditional COSMIC Live ISO, not the Atomic variant. The default installation via the WebUI completed successfully, and the kmscon workaround was required. | ||
|
Francis Teruel
|
Fedora-CosmicAtomic-Installer-45-20261001.n.0.x86_64 | Bare metal: AMD Ryzen 5 7600X, AMD Radeon RX 6500 XT (4GB), 32GB RAM, 1TB SSD | [1] | [2] | [3] |
[1]
Installation completed successfully using the automatic "use entire disk" partitioning. The system rebooted and booted into the COSMIC desktop without any issues. Stratis storage was not tested.
[2] Installation completed successfully using the guided partitioning and choosing partitions to be removed. The system rebooted and booted into the COSMIC desktop without any issues. Stratis storage was not tested. [3] Installation completed successfully using the custom partitioning with the storage editor, manually creating these partitions: /boot (ext4), /boot/efi, (efi) and / (btrfs). The system rebooted and booted into the COSMIC desktop without any issues. Stratis storage was not tested. |
|
lruzicka
|
Libvirt KVM based VM (Kinoite DVD ostree 20260927) | ||||
|
Rowan Lang
|
Fedora-BudgieAtomic-Installer-45-20260928.n.0.x86_64; Libvirt KVM based VM; 8 Host CPU Cores / 8GiB RAM / 120GiB Storage | [1] | [1] For custom partitioning: GPT partition table; 1 MB BIOS partition; 2 GB ext4 /boot partition; 8 GB Swap partition; 119GB btrfs root / partition. KDE Partition Manager shows all partitions as expected after boot. Checked creating and deleting using a few different partition options before figuring out the standard way to set this up and no issues. | ||
|
WQYeo
|
Kinoite dvd-ostree x86_64 Fedora-45-20260929.n.0; Libvirt KVM based VM | [1] | [1] Libvirt/KVM VM: 4 vCPUs, 6 GiB RAM, UEFI. Selected English (Singapore) language; data encryption disabled. Installation, reboot, and initial setup completed successfully. | ||
|
Éliette Priaulx
|
Fedora-Silverblue-Installer-45-20260928.n.0.x86_64; MSI X299 SLI Plus, Intel i7-7800X, 64GB RAM, AMD RX 9060 XT; Network, UEFI. | [1] |
[1]
USB Boot; Select Install Fedora 45; English (Australia) raises 'No valid VConsole...', Select English (United States) ; Select Use Entire Disk; Skip 'Encrypt my Data', Acknowledge + Erase data and install; Reboot; Accept English United States; Accept English (US) Keyboard; Accept Location Services Enabled; Accept Auto-Melbourne Map Selection; Set Username; Set Password; Start using Fedora.
Bugs: #1, #2 |
Atomic desktops - Remote WebUI feature
| Username | Profile | Remote WebUI | Remote WebUI - reconnect | Remote WebUI - resizing | Remote WebUI - different browsers | Remote WebUI - mobile | Comments |
|---|---|---|---|---|---|---|---|
| Atomic desktop name, and other useful details (hw specs) | |||||||
|
lruzicka
|
Libvirt KVM based VM (Kinoite DVD ostree 20260927) | [1] | [2] | [3] | [4] |
[1]
I did not experience the gray screen with no instructions. I experienced Anaconda screen very similar to what a text installation would have and the instructions were clearly written there.
[2] Reconnect works when I am trying to reconnect from the same browser I started the installation (Firefox) [3] Resizing works, especially when the window is made narrower. If it is made lower (when you move the bottom part up), at a certain point is stops showing the entire content and one needs to start scrolling to get to the content. It is however still accessible and responsive. [4] I can log with Firefox and start the installation. Then I close Firefox and want to reconnect via Chromium. That is not possible and Chromium keeps giving me ERR_CONNECTION_REFUSED. The same happens when I start the installation from anew and want to connect via Chromium. |
|
|
Rowan Lang
|
Fedora-BudgieAtomic-Installer-45-20260930.n.0.x86_64; Libvirt KVM based VM; 8 Host CPU Cores / 8GiB RAM / 120GiB Storage | [1] |
[1]
Test fail only confirmed with browser refresh at the summary screen of the installer. Have not confirmed the issue with any other types of resumptions.
Bugs: #1 |
||||
|
Éliette Priaulx
|
Fedora-Silverblue-Installer-45-20260930.n.0.x86_64; MSI X299 SLI Plus, Intel i7-7800X, 64GB RAM, AMD RX 9060 XT; Network, UEFI. | [1] | [2] | [3] | [4] | [5] |
[1]
Local UI not shown; IP address displayed; firefox desktop connects with pin; installed and booted successfully; confirming this build fixes 'Initializing...' spinner issue present in 20260929 .
[2] Repeated, as in [1]. Able to close window, reopen and continue. If closed prior to installation, progress is lost but settings seem to be retained; if reconecting after installation begins, progress is displayed. [3] As per [1]; resizing browser narrow results in responsive UI menu movement - menu has a transparnt background and interactions pass through it. Bugs: #1 [4] As per [2]; Clients evaluated: Fedora 44 client + FireFox, Windows Server 2025 + Edge, Windows Server 2025 + FireFox (Failure on disconnect/reconnect with this browser) Bugs: #1 [5] As per [2]; Pixel 10 Pro XL + FireFox & Chrome; iPhone 15, Current iOS + FireFox. Failure during reboot tiggered from FireFox iOS with null message. Chrome in Android attached to same session displayed message. Reboot succeeded and OOBE continued. Bugs: #1 |
Stratis support for Anaconda WebUI (Atomic or traditional Live images)
| Username | Profile | Stratis - basic version | Stratis - encrypted pool | Stratis - multiple filesystems | Stratis - multiple devices | Stratis - whole disk | Stratis - multiple pools | Comments |
|---|---|---|---|---|---|---|---|---|
| Optional details about your system (hardware specs, software configuration, etc) relevant for the current test day | ||||||||
|
Leandro Abdallah
|
Fedora-Workstation-Live-45-20260928.n.0.x86_64, KVM/QEMU VM, 4 vCPU, 8 GB RAM, 42.9 GB + 21.5 GB disks | [1] | [1] Completed the Stratis multiple devices test successfully. Created a Stratis pool using two separate disks (vda remaining space 38.6 GiB + vdb whole disk 20 GiB). Installation completed and system booted normally. Verified with stratis pool list, stratis blockdev list, and lsblk -f — the pool spans both devices (vda4 and vdb1 listed as DATA tier) and / and /home are mounted correctly. No unexpected behavior observed. | |||||
|
Leandro Abdallah
|
Fedora-Workstation-Live-45-20260928.n.0.x86_64, KVM/QEMU VM, 4 vCPU, 8 GB RAM, 64 GB disk | [1] |
[2]
[3] |
[4] | [5] | [6] |
[1]
Completed the Stratis basic version test successfully using Anaconda WebUI custom partitioning. Created biosboot, /boot/efi, /boot, and a Stratis pool with root (/) and home (/home) filesystems. Installation completed and system booted normally. Verified with findmnt, stratis pool list, stratis filesystem list, and lsblk -f — all filesystems mounted correctly from the Stratis pool. No unexpected behavior observed.
[2] FAIL — Stratis encrypted pool. Installation completed and Plymouth correctly prompts for the pool password. However, after entering the password, the system enters emergency mode with "Warning: /dev/stratis/fedorapool/root does not exist". The pool unlocks but dracut cannot find the root filesystem, preventing boot. Bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2543511 [3] RETEST — Stratis encrypted pool. Recreated the scenario from scratch with the same image and installation steps. This time the installation completed and the system booted normally — no emergency mode occurred. The bug did not reproduce on this second attempt. Original failure is tracked at https://bugzilla.redhat.com/show_bug.cgi?id=2543511 (see comment for details). [4] Completed the Stratis multiple filesystems test successfully. Created a Stratis pool with three filesystems: root (/), home (/home), and var (/var). Installation completed and system booted normally. Verified with findmnt, stratis pool list, and stratis filesystem list — all three filesystems are mounted correctly from the Stratis pool. No unexpected behavior observed. [5] Completed the Stratis whole disk test successfully. Used almost the entire disk for the Stratis pool, with only /boot/efi (VFAT) and /boot (ext4) outside the pool, plus a biosboot partition. Created root (/) and home (/home) filesystems inside the pool. Installation completed and system booted normally. Verified with findmnt, stratis pool list, stratis filesystem list, and lsblk -f. No unexpected behavior observed. [6] Completed the Stratis multiple pools test successfully. Created two separate Stratis pools on the same disk: pool_root (vda4, 32 GB) with root (/), and pool_home (vda5, 31 GB) with home (/home). Installation completed and system booted normally. Verified with findmnt, stratis pool list, stratis filesystem list, and lsblk -f — both pools are active and their filesystems are mounted correctly from their respective pools. No unexpected behavior observed. |
|
|
lruzicka
|
Libvirt KVM based VM (Kinoite DVD ostree 20260927) | [1] |
[1]
Trying to configure stratis on Kinoite, Anaconda said my layout was valid.
Bugs: #1 |
|||||
|
lruzicka
|
Libvirt KVM based VM (Workstation Live 20260927) | [1] | [1] When following the test case step by step, Stratis works just fine |
Stratis support for Anaconda GTK (DVD/Netinst images)
| Username | Profile | Stratis through Kickstart | Comments |
|---|---|---|---|
| Optional details about your system (hardware specs, software configuration, etc) relevant for the current test day |
Miscellaneous
| Username | Profile | Exploratory testing | Comments |
|---|---|---|---|
| Optional details about your system (hardware specs, software configuration, etc) relevant for the current test day |