On 1/5/20 1:59 AM, [email protected] wrote:
I'm resurrecting this thread to report that I was affected by this problem. I hope a solution will be implemented soon because it takes me the better part of a day to restore my system, and that's a lot of time to lose to an unpredictable glitch.
What was the original report? Hanging during boot at that message?I also get this every now and then, but usually rebooting helps. It definitely relates to the order in which sys-usb and/or sys-net are started (maybe the hardware init wasn't completely done yet?). There's a racing condition in there somewhere. There were a few github reports in the past and it got better with 4.
Anyway you can choose to not automatically start sys-net & sys-usb at boot, but do it manually and/or script it yourself. That's what I'm doing and why rebooting usually suffices for me.
-- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2121a058-38a2-dae8-1fd3-6b3dfeb47bea%40hackingthe.net.
smime.p7s
Description: S/MIME Cryptographic Signature
