Not having any joy with F43. Downloaded this morning. Booting on Mac Pro 3,1. I get into Fedora from usb drive. When I go to Install To Drive, I get a pop up window that I can’t read because it’s literally fraction of a second. Looks like some kind of authentication.
Then a few seconds later I get error with Anaconda pid file error /run/user/0/ or something like that. I’ve rebuilt the USB Fedora 43 KDE download 3 times but I never get the process started.
I, too, am having issues with F43 KDE iso. I have downloaded it twice. Both times it has failed to boot. Gives “out of memory” and “kernel panic” errors.
Won’t boot in VM or hardware.
I was looking forward to this release but I guess it’s not to be.
I was starting new empty drive. Ended up finding 42 iso image. Downloaded that and updating that to 43. Try the workstation non KDE or even the MATE Desktop.
the brief authentication popup is normal (yeah, I know it looks weird). the later thing is the real problem, but it would help to know exactly what the error is.
that does still sound like a bad image, though. or possibly you really don’t have enough RAM. how much memory does the system you’re trying to boot it on have?
I have a similar issue. The iso boots fine, but when I click the Install to Disk it opens briefly then closes before it can really load. I also ran it from terminal, this was the output:
liveuser@localhost-live:~$ liveinst
Warning: The unit file, source configuration file or drop-ins of webui-cockpit-ws.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Home directory /home/liveuser already exists.
Starting installer, one moment...
anaconda 43.44-3.fc43 for Fedora 43 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
Default browser set in anaconda.conf: slitherer
Using default browser: slitherer
Using Slitherer browser command with XWayland workaround: QT_QPA_PLATFORM=xcb slitherer
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
qml: The webpage at <strong jscontent="failedUrl"></strong> might be temporarily down or it may have moved permanently to a new web address.
Waiting for all threads to finish...
/usr/libexec/anaconda/webui-desktop: line 202: 4648 Segmentation fault (core dumped) HOME="$BROWSER_HOME" XDG_CURRENT_DESKTOP=GNOME pkexec --user $INSTALLER_USER env DISPLAY=$DISPLAY "${user_environment[@]}" "${BROWSER[@]}" http://"$WEBUI_ADDRESS""$URL_PATH"
/usr/libexec/anaconda/webui-desktop: line 197: kill: (4648) - No such process
liveuser@localhost-live:~$
I have installed Fedora 41 with no problem in this machine, and I have upgraded to Fedora 42 without problem in the past.
I am booting the KDE version of Fedora 43.
Running an older nvidia graphics card (with no drivers installed in the live environment obviously), so this may be related to some 3d acceleration missing problem?
Fedora 43 has a new installer, so new bugs for hardware that isn’t widely used and wasn’t tested in beta. I have 3 Fedora systems, so installed F43 beta on the oldest.
When reporting issues you should a) provide hardware details so others can try to reproduce the issue, and b) ensure vendor firmware is fully updated so you aren’t chasing a solved problem.
Workaround is to install F42 and then upgrade. That “worked for me” on my 2nd oldest system.
the vulkan fallback message is just a warning. The fatal issue is:
/usr/libexec/anaconda/webui-desktop: line 202: 4648 Segmentation fault (core dumped) HOME="$BROWSER_HOME" XDG_CURRENT_DESKTOP=GNOME pkexec --user $INSTALLER_USER env DISPLAY=$DISPLAY "${user_environment[@]}" "${BROWSER[@]}" http://"$WEBUI_ADDRESS""$URL_PATH"
but all we can tell from that is that the installer process crashed for some reason. That doesn’t sound like the same problem as eric’s, so you’re probably seeing two different things.
The system logs - which you can check in a graphical viewer, if KDE has one, or by running journalctl - might show some more information around the time of the crash…
Hi all,
New to Linux, been using it on and off for the past 4-5 years, but never managed to really get into it.
Been running Fedora 42 for the past 4 months without any issues, but having the same issue as others in this thread installing Fedora 43.
System:
MB: ASUS ROG Rampage V Extreme
CPU intel i7 6850
64GB RAM
Nvme samsung evo 970
GPU: ASUS ROG Strix 1080 ti OC 11GB
When i try to run the installer, a authentication popup shows for a micro second, and then a full screen white window open for a second or two and then it closes.
this from journalctl:
Oct 30 04:07:17 localhost-live liveinst[6858]: Starting installer, one moment…
Oct 30 04:07:17 localhost-live liveinst[6858]: terminal size detection failed, using default width
Oct 30 04:07:17 localhost-live liveinst[6858]: anaconda 43.44-3.fc43 for Fedora 43 started.
Oct 30 04:07:17 localhost-live liveinst[6858]: * installation log files are stored in /tmp during the installation
Oct 30 04:07:17 localhost-live liveinst[6858]: * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
Oct 30 04:07:17 localhost-live liveinst[6858]: * when reporting a bug add logs from /tmp as separate text/plain attachments
Oct 30 04:07:17 localhost-live liveinst[6858]: Waiting for all threads to finish…
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: INFO:anaconda.modules.runtime.runtime:Exit called with RebootData(action=-1, eject=False, kexec=False)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Payloads/Task/3.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: INFO:anaconda.core.threads:Running Thread: AnaTaskThread-TearDownSourcesTask-1 (140502473111232)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: INFO:anaconda.modules.common.task.task:Tear down installation sources
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:anaconda.modules.payloads.base.initialization:Tearing down sources…
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:anaconda.modules.payloads.base.initialization:Tearing down a source: Source(type=‘LIVE_OS_IMAGE’, >
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:anaconda.modules.payloads.base.initialization:Running a task: Unmount an installation source
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:anaconda.modules.payloads.source.mount_tasks:Unmounting installation source
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: INFO:program:Running… umount /run/install/sources/mount-0000-live_os_image
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:program:Return code: 0
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: INFO:anaconda.core.threads:Thread Done: AnaTaskThread-TearDownSourcesTask-1 (140502473111232)
Oct 30 04:07:17 localhost-live systemd[1]: run-install-sources-mount\x2d0000\x2dlive_os_image.mount: Deactivated successfully.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: INFO:program:Running… udevadm settle --timeout=300
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: DEBUG:program:Return code: 0
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: DEBUG:testdata:sysfs attr /sys/class/block/nvme0n1/device/model: 53616d73756e6720535344203937302045564f20>
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: DEBUG:testdata:sysfs attr /sys/class/block/sdb/device/model: 4461746154726176656c657220332e300a
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: DEBUG:testdata:sysfs attr /sys/class/block/sda/device/model: 4b494e4753544f4e20534134303053330a
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Storage/Task/2.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Storage/Task/3.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.core.threads:Running Thread: AnaTaskThread-UnmountFilesystemsTask-1 (139706107414208)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.modules.common.task.task:Unmount filesystems
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.core.threads:Thread Done: AnaTaskThread-UnmountFilesystemsTask-1 (139706107414208)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.core.threads:Running Thread: AnaTaskThread-TeardownDiskImagesTask-1 (139706107414208)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.modules.common.task.task:Tear down disk images
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: INFO:anaconda.core.threads:Thread Done: AnaTaskThread-TeardownDiskImagesTask-1 (139706107414208)
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:Stop modules.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Services[6921]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Services has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Security[6920]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Security has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Runtime[6926]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Runtime has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Users[6928]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Users has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Payloads[6930]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Payloads has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Storage[6932]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Storage has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Localization[6950]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Localization has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Timezone[6941]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Timezone has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Modules.Network[6947]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:anaconda.modules.boss.module_manager.module_manager:org.fedoraproject.Anaconda.Modules.Network has quit.
Oct 30 04:07:17 localhost-live org.fedoraproject.Anaconda.Boss[6888]: DEBUG:dasbus.connection:Disconnecting from the bus.
Oct 30 04:07:17 localhost-live audit: MAC_STATUS enforcing=1 old_enforcing=0 auid=1000 ses=2 enabled=1 old-enabled=1 lsm=selinux res=1
Oct 30 04:07:17 localhost-live audit[1428]: AUDIT2313 pid=1428 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: op=setenforce lsm=sel>
Oct 30 04:07:17 localhost-live dbus-broker[2201]: selinux/macstatus: avc: op=setenforce lsm=selinux enforcing=1 res=1
Oct 30 04:07:17 localhost-live systemd-logind[1467]: Session c6 logged out. Waiting for processes to exit.
it’s a bit of a shot in the dark, but can anyone affected by this please try editing /usr/libexec/anaconda/webui-desktop and changing line 172 from:
DEFAULT_BROWSER_CMD=$(get_default_browser)
to:
DEFAULT_BROWSER_CMD=firefox
before launching the installer? Then launch the installer and see if it works. Thanks!
YAY
This did the trick for me. Thank you very much
Great.
I’m curious, BTW - how long did you wait for the installer to run before? And what did you do when you ‘gave up waiting’ - did you reboot the system, or leave it running and poke around?
I’ve seen the installer take a long time to start up on KDE this cycle in some tests, presumably related to 2404262 – slitherer causes very high CPU usage without 3D acceleration support (qemu VM with no 3D passthrough, bare metal with nomodeset) . So that’s why I ask.
No wait time almost, maybe half to one second.
But i’m afraid i celebrated too soon, got a new error in step 3:
Installation failed:Error details
org.fedoraproject.Anaconda.BootloaderInstallationError:
Failed to set new efi boot target. This is most likely a kernel or firmware bug.
I tried to run the installer again, and then it couldn’t delete my existing partitions. I then ran KDE Part Manager - manually deleted all partitions on disk, and run the installer gain. Just to get the same error as above in step 3
that’s definitely a separate issue, but man, you sure are cursed this install 
that error basically means ‘we called the thing to write an EFI boot manager entry and it failed’. There should be a log of the exact call and result in /tmp/program.log, I think (look for efibootmgr). can you find that and paste it? thanks! and sorry for the trouble…
All part of the learning process, right ?
Really appreciate the help. Thank you very much
Couldn’t find any entry regarding efibootmgr, so here is the entire content:
16:27:36,622 INF program: Running… udevadm settle --timeout=300
16:27:36,635 DBG program: Return code: 0
16:27:36,657 INF program: Running [2] mdadm --version …
16:27:36,659 INF program: stdout[2]:
16:27:36,659 INF program: stderr[2]: mdadm - v4.3 - 2024-02-15
16:27:36,659 INF program: …done [2] (exit code: 0)
16:27:36,659 INF program: Running [3] dmsetup --version …
16:27:36,661 INF program: stdout[3]: Library version: 1.02.208 (2025-07-30)
Driver version: 4.50.0
16:27:36,662 INF program: stderr[3]:
16:27:36,662 INF program: …done [3] (exit code: 0)
16:27:36,716 INF program: Running… udevadm settle --timeout=300
16:27:36,723 DBG program: Return code: 0
16:27:36,737 INF program: Running… udevadm settle --timeout=300
16:27:36,744 DBG program: Return code: 0
16:27:36,759 INF program: Running… udevadm settle --timeout=300
16:27:36,765 DBG program: Return code: 0
16:27:36,779 INF program: Running… udevadm settle --timeout=300
16:27:36,785 DBG program: Return code: 0
16:27:36,795 INF program: Running… udevadm settle --timeout=300
16:27:36,803 DBG program: Return code: 0
16:27:36,813 INF program: Running… udevadm settle --timeout=300
16:27:36,821 DBG program: Return code: 0
16:27:36,831 INF program: Running… udevadm settle --timeout=300
16:27:36,838 DBG program: Return code: 0
16:27:36,848 INF program: Running… udevadm settle --timeout=300
16:27:36,855 DBG program: Return code: 0
16:27:36,865 INF program: Running… udevadm settle --timeout=300
16:27:36,874 DBG program: Return code: 0
16:27:36,884 INF program: Running… udevadm settle --timeout=300
16:27:36,891 DBG program: Return code: 0
16:27:36,900 INF program: Running… udevadm settle --timeout=300
16:27:36,907 DBG program: Return code: 0
16:27:36,916 INF program: Running… udevadm settle --timeout=300
16:27:36,924 DBG program: Return code: 0
16:27:36,933 INF program: Running… udevadm settle --timeout=300
16:27:36,939 DBG program: Return code: 0
16:27:36,949 INF program: Running… udevadm settle --timeout=300
16:27:36,955 DBG program: Return code: 0
16:27:36,964 INF program: Running… udevadm settle --timeout=300
16:27:36,971 DBG program: Return code: 0
16:27:36,980 INF program: Running… udevadm settle --timeout=300
16:27:36,986 DBG program: Return code: 0
16:27:36,996 INF program: Running… udevadm settle --timeout=300
16:27:37,003 DBG program: Return code: 0
16:27:37,012 INF program: Running… udevadm settle --timeout=300
16:27:37,018 DBG program: Return code: 0
16:27:37,028 INF program: Running… udevadm settle --timeout=300
16:27:37,035 DBG program: Return code: 0
16:27:37,045 INF program: Running… udevadm settle --timeout=300
16:27:37,051 DBG program: Return code: 0
16:27:37,060 INF program: Running… udevadm settle --timeout=300
16:27:37,067 DBG program: Return code: 0
16:27:37,075 INF program: Running… udevadm settle --timeout=300
16:27:37,082 DBG program: Return code: 0
16:27:37,091 INF program: Running… udevadm settle --timeout=300
16:27:37,097 DBG program: Return code: 0
16:27:37,106 INF program: Running… udevadm settle --timeout=300
16:27:37,113 DBG program: Return code: 0
16:27:37,122 INF program: Running… udevadm settle --timeout=300
16:27:37,128 DBG program: Return code: 0
16:27:37,137 INF program: Running… udevadm settle --timeout=300
16:27:37,147 DBG program: Return code: 0
16:27:37,156 INF program: Running… udevadm settle --timeout=300
16:27:37,163 DBG program: Return code: 0
16:27:37,171 INF program: Running… udevadm settle --timeout=300
16:27:37,178 DBG program: Return code: 0
16:27:37,187 INF program: Running… udevadm settle --timeout=300
16:27:37,193 DBG program: Return code: 0
16:27:37,204 INF program: Running… udevadm settle --timeout=300
16:27:37,211 DBG program: Return code: 0
16:27:37,220 INF program: Running… udevadm settle --timeout=300
16:27:37,226 DBG program: Return code: 0
16:27:37,235 INF program: Running… udevadm settle --timeout=300
16:27:37,242 DBG program: Return code: 0
16:27:37,251 INF program: Running… udevadm settle --timeout=300
16:27:37,258 DBG program: Return code: 0
16:27:37,267 INF program: Running… udevadm settle --timeout=300
16:27:37,273 DBG program: Return code: 0
16:27:37,282 INF program: Running [4] btrfs --version …
16:27:37,284 INF program: stdout[4]: btrfs-progs v6.17
-EXPERIMENTAL -INJECT -STATIC +LZO +ZSTD +UDEV +FSVERITY +ZONED CRYPTO=libgcrypt
16:27:37,285 INF program: stderr[4]:
16:27:37,285 INF program: …done [4] (exit code: 0)
16:27:37,285 INF program: [libmkod] custom logging function 0x7fe1e2dc6680 registered
16:27:37,285 INF program: [libmkod] context 0x56200ac58cd0 released
16:27:37,285 INF program: Running [5] btrfs subvol list -a -p -s /mnt/sysroot …
16:27:37,287 INF program: stdout[5]:
16:27:37,287 INF program: stderr[5]:
16:27:37,287 INF program: …done [5] (exit code: 0)
16:27:37,287 INF program: Running [6] btrfs subvol get-default /mnt/sysroot …
16:27:37,289 INF program: stdout[6]: ID 5 (FS_TREE)
16:27:37,290 INF program: stderr[6]:
16:27:37,290 INF program: …done [6] (exit code: 0)
16:27:37,290 INF program: Running… udevadm settle --timeout=300
16:27:37,298 DBG program: Return code: 0
16:27:37,307 INF program: Running… udevadm settle --timeout=300
16:27:37,314 DBG program: Return code: 0
16:27:37,323 INF program: Running… udevadm settle --timeout=300
16:27:37,331 DBG program: Return code: 0
16:27:37,339 INF program: Running… udevadm settle --timeout=300
16:27:37,346 DBG program: Return code: 0
16:27:37,355 INF program: Running… udevadm settle --timeout=300
16:27:37,361 DBG program: Return code: 0
16:27:37,370 INF program: Running… udevadm settle --timeout=300
16:27:37,376 DBG program: Return code: 0
16:27:37,385 INF program: Running… udevadm settle --timeout=300
16:27:37,397 DBG program: Return code: 0
16:27:37,406 INF program: Running… udevadm settle --timeout=300
16:27:37,412 DBG program: Return code: 0
16:27:37,421 INF program: Running… udevadm settle --timeout=300
16:27:37,428 DBG program: Return code: 0
16:27:37,437 INF program: Running… udevadm settle --timeout=300
16:27:37,443 DBG program: Return code: 0
16:27:37,452 INF program: Running… udevadm settle --timeout=300
16:27:37,462 DBG program: Return code: 0
16:27:37,471 INF program: Running… udevadm settle --timeout=300
16:27:37,478 DBG program: Return code: 0
16:27:37,487 INF program: Running… udevadm settle --timeout=300
16:27:37,499 DBG program: Return code: 0
16:27:37,508 INF program: Running… udevadm settle --timeout=300
16:27:37,514 DBG program: Return code: 0
16:27:37,523 INF program: Running… udevadm settle --timeout=300
16:27:37,533 DBG program: Return code: 0
16:27:37,542 INF program: Running… udevadm settle --timeout=300
16:27:37,548 DBG program: Return code: 0
16:27:37,557 INF program: Running… udevadm settle --timeout=300
16:27:37,567 DBG program: Return code: 0
16:27:37,576 INF program: Running… udevadm settle --timeout=300
16:27:37,582 DBG program: Return code: 0
16:27:37,591 INF program: Running… udevadm settle --timeout=300
16:27:37,602 DBG program: Return code: 0
16:27:37,611 INF program: Running… udevadm settle --timeout=300
16:27:37,617 DBG program: Return code: 0
16:27:37,626 INF program: Running… udevadm settle --timeout=300
16:27:37,634 DBG program: Return code: 0
16:27:37,643 INF program: Running… udevadm settle --timeout=300
16:27:37,650 DBG program: Return code: 0
16:27:37,659 INF program: Running… udevadm settle --timeout=300
16:27:37,665 DBG program: Return code: 0
16:27:37,674 INF program: Running… udevadm settle --timeout=300
16:27:37,681 DBG program: Return code: 0
16:27:37,690 INF program: Running… udevadm settle --timeout=300
16:27:37,697 DBG program: Return code: 0
16:27:37,705 INF program: Running [7] btrfs subvol list -a -p /mnt/sysroot …
16:27:37,708 INF program: stdout[7]: ID 256 gen 18 parent 5 top level 5 path <FS_TREE>/root
ID 257 gen 12 parent 5 top level 5 path <FS_TREE>/home
16:27:37,708 INF program: stderr[7]:
16:27:37,708 INF program: …done [7] (exit code: 0)
16:27:37,708 INF program: Running [8] btrfs subvol get-default /mnt/sysroot …
16:27:37,711 INF program: stdout[8]: ID 5 (FS_TREE)
16:27:37,711 INF program: stderr[8]:
16:27:37,711 INF program: …done [8] (exit code: 0)
16:27:37,721 INF program: Running… udevadm settle --timeout=300
16:27:37,727 DBG program: Return code: 0
16:27:37,739 INF program: Running… udevadm settle --timeout=300
16:27:37,746 DBG program: Return code: 0
16:27:37,827 INF program: Running… udevadm settle --timeout=300
16:27:37,835 DBG program: Return code: 0
16:27:37,858 INF program: Running… udevadm settle --timeout=300
16:27:37,865 DBG program: Return code: 0
16:27:38,851 INF program: Running… losetup --list
16:27:38,864 INF program: Running… dbus-daemon --print-address --syslog --config-file=/usr/share/anaconda/dbus/anaconda-bus.conf
16:27:41,177 INF program: Running… losetup –list
16:27:41,194 INF program: Running… udevadm settle --timeout=300
16:27:41,203 DBG program: Return code: 0
16:27:41,215 INF program: Running… udevadm settle --timeout=300
16:27:41,225 DBG program: Return code: 0
16:27:45,511 INF program: Running… hwclock --hctosys --localtime
16:29:27,001 DBG program: Return code of hwclock: 0
Just tried installing Fedora 42, and it went smoothly. So an OS can definitely be installed.
Mac Pro 3,1 NVidia Quadro K5000 Mac compatible video card, & 64 GB RAM. Don’t think RAM is an issue or shouldn’t be an issue here.
In regards to the authentication message it is literally to quick to capture or even see the text. It just looks like an authentication box hence the verbiage. I could be wrong. Literally talking a micro-second.
I worked around the problem by find Fedora 42 iso and installed that and then migrated immediately to 43.
I really hate to think my Mac Pro days are coming to an end. It’s stuff full of drives like no other system can without having to resort to some god awful ugly disk enclosure sitting on a desk. IT’s also the world’s greatest space heater in winter keeping my room nice and toasty here in the PNW.
I could certainly try. I have an identical machine to set up, but if your starting on a fresh drive what other browser would be in place besides Firefox?
the edit changes from the KDE default browser environment for webui (which is a qtwebkit-based thing called ‘slitherer’ that Neal ginned up back in July and didn’t tell me about) to firefox. It should make the installer run in firefox instead of the slitherer thing. I’m curious to find out whether the problem for at least some of you is to do with slitherer, since it’s a fairly new innovation.
d’oh, the messages must’ve moved, they do that. try something like:
grep -5 efibootmgr /tmp/*log
journalctl | grep -5 efibootmgr
hopefully one of those will find it…