Installer Crashing

i have tried installing bazzite, kinoite, and the original version (with kde), all of them have this issue on my pc, and I’m running the iso’s through ventoy. just before the GUI of the installer loads it throws this error:

hTraceback (most recent call last): File "/sbin/anaconda", line 498, in <module> ignore_oemdrv_disks() File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/lib/storage.py", line 366, in ignore_oemdrv_disks matched device_matches("LABEL=OEMDRU", disks_only=True) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/storage.py", line 179, in device_matches single_spec_matches = udev.resolve_glob(full_spec) File "/usr/lib/python3.12/site-packages/blivet/udev.py", line 192, in resolve_glob for dev in get_devices(): File "/usr/lib/python3.12/site-packages/blivet/udev.py", line 105, in get_devices dev = device_to_dict(device) File "/usr/lib/python3.12/site-packages/blivet/udev.py", line 77, in device_to_dict result = dict(device.properties) File "/usr/lib/python3.12/site-packages/pyudev/device/_device.py", line 1181, in getitem return ensure_unicode_string(value) File "/usr/lib/python3.12/site-packages/pyudev/_util.py", line 56, in ensure_unicode_string value = value.decode(sys.getfilesystemencoding()) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbf in position 8: invalid start byte

i’d give the log file it says it generates but i don’t know how to locate it or get it out of that live boot environment and onto my actual hard drive.

Have you been able to replicate that if you burned the installer directly on to a USB stick (ie not using Ventoy)?

haven’t used Ventoy in a while, so I’m not sure if there could be a bug in the version that’s used or maybe if there is an issue with the USB drive that could be causing some corruption.

with the regular fedora kde iso on a usb using rufus it gets way less far into the installer, the console says

[ OK ] Started plymouth-start.service - Show Plymouth Boot Screen. [ OK ] Started systemd-ask-password-plymouth.path - Forward Password Requests target cryptsetup.target - Local Encrypted Volumes. [ OK ] Reached target paths.target - Path Units. [ OK ] Stopped systemd-vconsole-setup.service - Virtual Console Setup. Starting systemd-uconsole-setup.service - Virtual Console Setup... [ OK ] Finished systemd-uconsole-setup.service - Virtual Console Setup. Mounting sys-kernel-config.mount - Kernel Configuration File System. [ OK ] Mounted sys-kernel-config.mount - Kernel Configuration File System. [ OK ] Reached target sysinit.target - System Initialization. [ OK ] Reached target basic.target - Basic System. [ 9.503108] dracut-initqueue [906]: Unknown device "/dev/disk/by-label/FEDORAx20INST": No such device [ 9.506595] dracut-initqueue[907]: Unknown device "/sys/": No such device 9.5228411 dracut-initqueue [916]: mount: /run/initramfs/live: unknown filesystem type". [ 9.514935] dracut: FATAL: Failed to mount block device of live image [ 9.514942] dracut: Refusing to continue [ 9.522878] dracut-initqueue[916]: dmesg (1) may have more information after failed mount system call. dracut: FATAL: Failed to mount block device of live image dracut: Refusing to continue

i have managed to boot into the live kde environment using basic graphics mode booting from ventoy, but the install to hard drive application wont open, basic graphics mode from the rufus install hangs on the loading screen where it has the fedora logo and a loading throbber over top of your bios’s loading screen

Per Bazzite won’t boot installer from USB, try a different (high quality) USB drive.

If that fails, make sure your vendor firmware is fully updated so you aren’t chasing a solved problem in the firmware.

If that fails, please try the Fedora 40 Live Installer. Don’t skip the checks to ensure the USB image is not corrupted. Use the “live” environmentto provide hardware details (as text), so others with similar hardware will find this topic with web searches. I suggest installing the inxi package, and running inxi -Fzxx. Post the output as pre-formatted text using the </> button from the top line of the text input panel.

the usb i’m using is this samsung one

it’s got a B450 AORUS M motherboard,
an EVGA Nvidia RTX 2060 graphics card
an AMD Ryzen 5 2600X Six-Core CPU
it’s got an ssd and a hard drive, both are formatted as ntfs
it’s currently running the latest windows 11 pro insider preview build

Counterfeit USB drives are all too common, and focus on the high-end models. The Fedora Installer has an option to verify the contents.

The LHDB probes for B450 AORUS M running Fedora 40 suggest your hardware should work with “BIOS F66 03/22/2024”.

bios update fixed not being able to liveboot without basic graphics mode, but install to hard drive still shows the input admin password prompt for like 0.1 seconds before closing and then nothing else happens, what is that verification tool called and where exactly can i find it, if that’s a stupid question then that’s because you didn’t make clear what exactly you mean by “the installer” do you mean something in the live boot environment, do you mean something in thar menu where you select to boot in that environment, do you mean the tool used to write the iso to a usb.

When booting the live image, the GRUB menu should include an option with “Test this media”. This is what pops up when I boot from the KDE spin live image:

yes i have that option and have been using it the entire time, every time i have tried to boot into the live environment (other than when i’ve selected to troubleshooting option for low graphics mode) i have used tested the media

You mentioned a number of Fedora “spins” and also bazzite. Which one are you using?

The F40 Workstation (Gnome) installer runs with username “liveuser” and an empty password, but I don’t recall being asked for the password to do an install, only for things like sudo dnf install inxi.

Please review the LHDB probes for differences between your system and the ones running F40. It is possible those systems were upgraded from a previous Fedora version. Some systems have had problems with the Fedora 40 installer. Workarounds are to use an F39 installer and then upgrade to 40. It would be worth trying the 41 Beta Installer as it may have fixed some of the F40 installer issues.

i am attempting to use kde plasma spin, running liveinst with sudo in konsole yeilds this btw:

`liveuser@localhost-live:~$ sudo liveinst
Traceback (most recent call last):
File “/usr/bin/anaconda-cleanup”, line 82, in
devicetree.populate(cleanup_only=True)
File “/usr/lib/python3.12/site-packages/blivet/threads.py”, line 53, in run_with_lock
return m(*args, **kwargs)
^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/blivet/populator/populator.py”, line 446, in populate
self._populate()
File “/usr/lib/python3.12/site-packages/blivet/threads.py”, line 53, in run_with_lock
return m(*args, **kwargs)
^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/blivet/populator/populator.py”, line 471, in _populate
new_devices = udev.get_devices()
^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/blivet/udev.py”, line 105, in get_devices
dev = device_to_dict(device)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/blivet/udev.py”, line 77, in device_to_dict
result = dict(device.properties)
^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/pyudev/device/_device.py”, line 1101, in getitem
return ensure_unicode_string(value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/site-packages/pyudev/_util.py”, line 56, in ensure_unicode_string
value = value.decode(sys.getfilesystemencoding())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: ‘utf-8’ codec can’t decode byte 0xbf in position 0: invalid start byte
Starting installer, one moment…
anaconda 40.22.3-1.fc40 for Fedora 40 started.

  • installation log files are stored in /tmp during the installation
  • shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
  • when reporting a bug add logs from /tmp as separate text/plain attachments
    Traceback (most recent call last):
    File “/sbin/anaconda”, line 348, in
    startup_utils.live_startup()
    File “/usr/lib64/python3.12/site-packages/pyanaconda/startup_utils.py”, line 360, in live_startup
    inhibit_screensaver()
    File “/usr/lib64/python3.12/site-packages/pyanaconda/screensaver.py”, line 96, in inhibit_screensaver
    inhibit_id = session_proxy.Inhibit(“anaconda”, “Installing”)
    ^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/client/proxy.py”, line 161, in getattr
    member = self._get_member(self._get_interface(name), name)
    ^^^^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/client/proxy.py”, line 211, in _get_interface
    self._handler.specification.members
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/client/handler.py”, line 212, in specification
    self._specification = self._get_specification()
    ^^^^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/client/handler.py”, line 332, in _get_specification
    xml = self._call_method(
    ^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/client/handler.py”, line 435, in _call_method
    self._message_bus.connection,
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/connection.py”, line 169, in connection
    self._connection = self._get_connection()
    ^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/connection.py”, line 336, in _get_connection
    return self._provider.get_session_bus_connection()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File “/usr/lib/python3.12/site-packages/dasbus/connection.py”, line 67, in get_session_bus_connection
    return Gio.bus_get_sync(
    ^^^^^^^^^^^^^^^^^
    gi.repository.GLib.GError: g-io-error-quark: Could not connect: No such file or directory (1)`

i will try the 39 amd 41 installers next

edit: same exact issue and log on the 41 beta and on 39

Do any of the installers boot to graphical mode or are you stuck with a text console? If you are stuck with text, you could try the server installer, then work on getting graphics working. There should be some details of graphics driver issues in dmesg or joutnalctl.

kde boots fine and everything works fine except the install to hard drive application, which i have already described the behaviour of

here is a demonstration of that, it boots into the live kde environment just fine, the only issue is the “install to hard drive” application does nothing

The text in the youtube video is not legible here. Have you looked for added details in the log files? The Fedora Workstation (Gnome) Live Installer boots to a screen with graphic “button” that runs the installer.

Are you using Wayland or Xorg? Which Fedora KDE installer are you using (F40 or F41, …)?

F40, which log files where (could you be more specific, there are alot of things in /tmp/ and most of them say i don’t have permission to access them), and how am i supposed to know whether i’m using wayland or xorg, i haven’t messed with anything i’m using the exact fedora 40 kde iso as is available from the website, and in regards to the install button in gnome are you referring to one equivalent to the one in the kde welcome center, because as far as i’m aware that just opens liveinst same as the desktop shortcut or calling liveinst in a terminal

also here is lsblk (the “ffedoraaaaes” partition is where i plan on installing fedora)

liveuser@localhost-live:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.3G  1 loop 
loop1         7:1    0   8.8G  1 loop 
├─live-rw   253:1    0   8.8G  0 dm   /
└─live-base 253:2    0   8.8G  1 dm   /run/media/liveuser/Anaconda
loop2         7:2    0    32G  0 loop 
└─live-rw   253:1    0   8.8G  0 dm   /
sda           8:0    0   1.8T  0 disk 
├─sda1        8:1    0   128M  0 part 
├─sda2        8:2    0   1.5T  0 part /run/media/liveuser/DATA
└─sda3        8:3    0   293G  0 part /run/media/liveuser/ffedoraaaaes
sdb           8:16   1  59.8G  0 disk 
├─sdb1        8:17   1  59.7G  0 part 
│ └─ventoy  253:0    0   2.5G  0 dm   /run/initramfs/live
└─sdb2        8:18   1    32M  0 part 
sr0          11:0    1  1024M  0 rom  
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part 
├─nvme0n1p2 259:2    0 952.6G  0 part /run/media/liveuser/Acer
├─nvme0n1p3 259:3    0   610M  0 part 
└─nvme0n1p4 259:4    0   300M  0 part

If you paste the text then highlight it before clicking on the </> button it retains formatting as seen on-screen.

I copied your posted text so I could show the difference.

liveuser@localhost-live:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.3G  1 loop 
loop1         7:1    0   8.8G  1 loop 
├─live-rw   253:1    0   8.8G  0 dm   /
└─live-base 253:2    0   8.8G  1 dm   /run/media/liveuser/Anaconda
loop2         7:2    0    32G  0 loop 
└─live-rw   253:1    0   8.8G  0 dm   /
sda           8:0    0   1.8T  0 disk 
├─sda1        8:1    0   128M  0 part 
├─sda2        8:2    0   1.5T  0 part /run/media/liveuser/DATA
└─sda3        8:3    0   293G  0 part /run/media/liveuser/ffedoraaaaes
sdb           8:16   1  59.8G  0 disk 
├─sdb1        8:17   1  59.7G  0 part 
│ └─ventoy  253:0    0   2.5G  0 dm   /run/initramfs/live
└─sdb2        8:18   1    32M  0 part 
sr0          11:0    1  1024M  0 rom  
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part 
├─nvme0n1p2 259:2    0 952.6G  0 part /run/media/liveuser/Acer
├─nvme0n1p3 259:3    0   610M  0 part 
└─nvme0n1p4 259:4    0   300M  0 part

Looking at that output it seems you have already partitioned the nvme drive and fedora cannot install that way unless you are doing a custom install where you define the partitions to use. It presently appears to have no free space in which to install.

You should remove all the partitions on the drive you seem to be installing on so it has no defined partitions, then when you start the installer it will create those partitions for you as needed.

Look in the ~/Desktop/liveinst.desktop you will see there are some environment variables.

I just tried the KDE Fedora 41 Beta installer. It appears to work (I can select language and bring up the disk configuration screen) when started from the KDE Welcome Screen or the Desktop icon. Running liveinst in a terminal it fails as you describe fails. You haven’t explained why you are unable to use the icon – it would seem to be much simpler than posting fuzzy videos.

Log files are usually plain text and have a .log extension. You need to use sudo, e.g. sudo grep liveinst /tmp/*.log.