I have 3 old machines, 2 from 2008 and one (Lenovo ThinkPad X131e) from 2013. When I installed F43 on them using the Live image shortly after it went Gold, I had trouble with the installer hanging on each, in the last step (forget what it's called). On the newest one, it would hang on roughly 50% of attempts, and on the slower ones on every attempt. When I installed Fedora-Workstation-Live-44-20260206.n.2.x86_64.iso in a KVM guest with one of the older machines as host, the hang happened again. I left it running for hours so it definitely wasn't going to finish. I was able to trigger an error "Cannot parse given Error object" only by opening the menu in the upper right attempting to bring up the storage editor, again the same behavior as with F43. I wasn't able to report the error automatically since it hung after I entered my Bugzilla API key.
AFAIK this problem hasn't been recognized, I'm guessing because it only happens on very slow machines and doesn't even trigger an error report unless one attempts to bring up the storage editor menu, and even then may not be automatically reportable. Also, after rebooting, the install seems to work normally. All of these things discourage reporting. Could people with old, slow machines lying around and nothing essential on them attempt to reproduce this? Thanks. P.S. I haven't yet attempted to use the GTK installer by deleting the anaconda-webui package before invoking the installer, it's possible that the GTK installer doesn't have the same issue. -- _______________________________________________ test mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
