On Thu, 2026-02-19 at 01:32 +0000, Andre Robatino wrote: > The newest one, the X131e from 2013, has 4 GB of RAM. That machine is UEFI. > The other two are both legacy BIOS desktops from 2008, one is a Lenovo > ThinkCentre M58p with 16 GB of RAM, the other is a Compaq Presario SR5413WM > with 4 GB of RAM. As I said, the only one of the three where it would > complete even part of the time was the one from 2013 with 4 GB, so I'm pretty > sure the issue is speed, not RAM. I realize that almost no one today uses > such old machines and I'm guessing that's even more true of testers, but > given it's happened on all three of my old machines it shouldn't be hard to > reproduce if the machine is slow/old enough, although to actually get it to > stop with an error message it's necessary to try opening the storage editor > menu, and even then the error seems to be somewhat random (I only saw the > latest error once) so I don't think that would be helpful in reporting it.
Hmm, yeah, doesn't sound like RAM, then. When it's in the apparently-stuck state, can you get to a console with ctrl-alt-f2 or ctrl-alt-f3 and see what the journal and /tmp/*.log files show? If not, since you say it seems like the install actually completes, can you boot the installed system and look at the logs in /var/log/anaconda and see what they say? Thanks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ 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
