Bug 2461820 - On the very last stage of installation, installer quits with some "path" related error.
Summary: On the very last stage of installation, installer quits with some "path" rela...
Keywords:
Status: CLOSED DUPLICATE of bug 2394554
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-25 15:19 UTC by klugemann
Modified: 2026-05-04 10:53 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-05-04 10:53:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description klugemann 2026-04-25 15:19:06 UTC
this error happens every time, unless another error happens during earlier stage.
My installation process: only assign mount points to pre-existing partitions.
Partitions are : EFI (not formatted), /boot (256000 MiB, ext4, set to format), / (155000 MiB, btrfs, set to format).

Error text:
"Danger alert:
Installation failed
The installer cannot continue due to a critical error: Installation of the system failed: Storing configuration files and kickstarts
Error details
org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path'"

Despite the installation quits with error, to resulting system is bootable, but it's correct functionality is questionable.

Reproducible: Always

Steps to Reproduce:
1. install gparted.
2. create partitions: 2.56 GiB ext4, and 155 GiB btrfs.
3. set installer to only attach mount points to existing partitions: (/boot/efi - existing FAT32 EFI partition, /boot - existing 2.56 GiB EXT4 partition formatted, / - existing BTRFS 155 GiB formatted partition)
4. setting username and password, NOT setting up Administrator account.
5. proceeding to install.
6. error occur only at the very last stage of the installation progress
Actual Results:
installer shows error, prior to finalizing.
System is normally booting, after restart.
But it is unknown if the setup is 100% correct, and safe to use for production.

Expected Results:
finish installation process without errors, and report success.

Additional Information:
I will attach a link to the the "journal.log", from /tmp folder, recommended by the installer.

Link 1 - current error (at the end of installation)
https://mega.nz/folder/gygR2aAD#yFT-hu_SiZISscwYfMooEA

(addon)
Link 2 - another one error (happens independently, during software install phase)
https://mega.nz/folder/5qB0kZCb#LjdUpfdMv2ro4bvKHhKfwA
(no log attached yet)(this bug is not stably reproducible)

Comment 1 Katerina Koukiou 2026-05-04 10:53:11 UTC

*** This bug has been marked as a duplicate of bug 2394554 ***


Note You need to log in before you can comment on or make changes to this bug.