Bug 2406260 - WebUI: org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path'
Summary: WebUI: org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute '...
Keywords:
Status: CLOSED DUPLICATE of bug 2394554
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 43
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-24 21:14 UTC by Andre Robatino
Modified: 2025-11-21 08:54 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-21 08:54:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
/tmp/journal.log (3.02 MB, text/plain)
2025-10-24 21:14 UTC, Andre Robatino 		no flags Details
View All

Description Andre Robatino 2025-10-24 21:14:44 UTC 
Created attachment 2110736 [details]
/tmp/journal.log

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 (Workstation Edition)
Anaconda version: 43.44
Anaconda UI version: 53.14.g7ea927aa
Comment 1 Andre Robatino 2025-10-25 00:36:59 UTC 
Very old legacy BIOS machine with dual boot Windows 11/Fedora 42 (so MBR partitioning) and a 1 GiB /boot. Used Mount Point Assignment since "Reinstall Fedora" doesn't actually work. Despite the error, the machine seems functional after rebooting. Looks like a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2406198 .
Comment 2 Andre Robatino 2025-10-25 00:38:08 UTC 
To be clear, it WAS Fedora 42, is now 43 and seems to work.
Comment 3 Andreas M. Kirchwitz 2025-10-29 05:01:03 UTC 
Very similar here, same problem, and although after a reboot Fedora 43 seems to work, such a system should not be used. How do I get a clean installation?

Bug #2406198 talks about subvolumes. I have no such thing.
Comment 4 Andre Robatino 2025-10-29 05:10:36 UTC 
I have 3 machines that have experienced the same issue. The one thing they have in common is that they're old. The newest is a Lenovo X131e UEFI machine from 2013, the other two are legacy BIOS. I've attempted F43 clean installs many times on all 3 and the only two that fully completed were on the X131e, and even on that several other attempts failed. Is your machine old as well?

Regarding root/var/lib/machines, I tried deleting that using Storage Editor before install and it didn't help, so something else is going on. I currently know of no reliable way to get a clean install. My last install on the X131e was clean so I got lucky on that one.
Comment 5 Katerina Koukiou 2025-11-21 08:54:52 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.