You forgot to answer the question:
doktor5000 wrote:So what actually happens when you boot, and when exactly do you run that command?
From the log, you hit some ordering cycles.
dec 07 18:11:09 killer systemd[1]: Found ordering cycle on preload.service/start
dec 07 18:11:09 killer systemd[1]: Found dependency on prefdm.service/start
dec 07 18:11:09 killer systemd[1]: Found dependency on plymouth-quit.service/stop
dec 07 18:11:09 killer systemd[1]: Found dependency on rc-local.service/start
dec 07 18:11:09 killer systemd[1]: Found dependency on vmware-USBArbitrator.service/start
dec 07 18:11:09 killer systemd[1]: Found dependency on preload.service/start
dec 07 18:11:09 killer systemd[1]: Breaking ordering cycle by deleting job prefdm.service/start
dec 07 18:11:09 killer systemd[1]: Job prefdm.service/start deleted to break ordering cycle starting with preload.service/start
See the related bug reports:
https://bugs.mageia.org/show_bug.cgi?id=16086 and
https://bugs.mageia.org/show_bug.cgi?id=16260You can try to fix it via disabling the preload service as root via
- Code: Select all
systemctl mask preload.service
or by simply uninstalling the preload package via
- Code: Select all
urpme preload