"Install to Hard Drive" App crashes immediately on kde spin

Ask Fedora
1

I installed the kde spin on a usb, booted it and everything worked fine but when I try installing to hard drive the app just crashes with this error:

Traceback (most recent call last):
  File "/usr/lib64/python3.11/site-packages/pyanaconda/threading.py", line 275, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.11/threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.11/site-packages/pyanaconda/ui/lib/storage.py", line 97, in reset_storage
    sync_run_task(task_proxy)
  File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task
    task_proxy.Finish()
  File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 450, in _call_method
    return self._get_method_reply(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply
    return self._handle_method_error(error)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error
    raise exception from None
pyanaconda.modules.common.errors.general.AnacondaError: 'NoneType' object has no attribute 'getPartitionByPath'
2

Hello @justlinus, welcome.
Which hardware you have got?
I’m not an expert, but it looks like something related to storage. Just speculating. Could you open a terminal and paste here the result of the command lsblk?
In the BIOS the storage is configured as RAID or AHCI or what?

3

The installer expect that the user either already have empty (unallocated) space on the drive for installation, tell the installer to use the entire drive while removing already defined partitions and data, or designate specific partitions to use for the install.

If you have not done one of those things and the drive is already fully claimed by existing partitions then the install will fail because of no space designated and available for use.

I agree with the above that the messages seems to indicate no space available.

4

How far did the installer get before it crashed? The installer needs to scan your mass storage devices, so it may be having a problem with one of your devices.
Are you using a newly purchased storage device? There have been problems with phony name-brand SSD’s sold on ebay and Amazon.

The installer should warn you if there isn’t enough free space, so You could try booting the Live Desktop from the USB and running the KDE Partition Manager, or command-line tools like fdisk to see if the KDE Spin finds the expected storage layout.