Edit: I must have missed something while scanning through the logs. In
dbus.log I get
dbus-daemon: Activated service 'org.fedoraproject.Anaconda.Modules.Network' failed: Process org.fedoraproject.Anaconda.Modules.Network exited with status 1 dbus-daemon: Reloaded configuration
I haven’t found any fixes when researching this yet.
Edit again: There’s no
anaconda-ks.cfg around anywhere, I’m not sure if that’s an issue or not.
I admit I’m new to Silverblue. Anaconda seems to start properly:
Starting installer, one moment... anaconda 29.24.3-1.fc29 for Fedora 29 (pre-release) started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 * when reporting a bug add logs from /tmp as separate text/plain attachments
On the log tab I get lots of these:
INF startup_utils: Waiting 600 sec for modules to be started. INF startup_utils: Waiting 599 sec for modules to be started. INF startup_utils: Waiting 598 sec for modules to be started.
and so on until it times out:
Anaconda DBus modules failed to start on time.
The odd thing is, I don’t time out when using the exact same .iso file in a VM.
Possible relevant links are here because I’m not allowed to put all of them in this post.
I doubt it’s because my PC is too slow because if so, then the VM shouldn’t have even become close to working, and also, I don’t think my PC is that bad. I’ve got a Ryzen 3 1300X, 8 GB of RAM… (full list at https://pcpartpicker.com/list/cCxFHh)