Bug 2458429

Summary: WebUI: org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path'
Product: [Fedora] Fedora Reporter: nitscheelia
Component: anacondaAssignee: Martin Kolman <mkolman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: alpha, anaconda-maint, kkoukiou, mkolman, w
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-04-20 06:23:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journal.log of the crash none

Description nitscheelia 2026-04-14 19:14:20 UTC 
Installer WebUI Critical Error:
org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path'

Please attach the log file /tmp/journal.log to the issue.

---[ System & Environment Information ]---
OS: Fedora Linux 43 (KDE Plasma Desktop Edition)
Anaconda version: 43.44
Anaconda UI version: 53.14.g7ea927aa

Reproducible: I could reproduce it in the same session (without restart)

Steps to Reproduce:
1. Use the installer to try to install fedora kde
2. setting custom mounts: / (btrfs), /boot (ext4), with a shared /boot/efi (shared with arch linux)
3. 
Actual Results:
installer crashes on the last step

Expected Results:
it installs fedora

EDIT (not sure how relevant):
I seems to have installed fedora, kinda...I could boot into it (from my arch grub, after updating that)
But after rebooting fedora with updating, it gets stuck somewhere between kernel and userland. (eg. init=/bin/bash boots, but everything else does not)
Comment 1 nitscheelia 2026-04-14 19:16:37 UTC 
Created attachment 2137126 [details]
journal.log of the crash
Comment 2 Katerina Koukiou 2026-04-20 06:23:06 UTC 

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