The bug is still the same. What happened was that the system froze at a different message in that particular try. Journalctl from a successful initialization showing the most common point of failure:
systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight. systemd[1]: Started Uncomplicated firewall. systemd-udevd[400]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. systemd[1]: Starting Load/Save RF Kill Switch Status... The messages after the one of intel backlight are the ones related with /dev/rfkill. This is why it freezes showing: [ OK ]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight. Probably the RF Kill has a serious enough failure when this bug happens that the entire system freezes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
