Those logs appear to be incomplete and also not relevant to this bug. Next time it happens please run:
journalctl -b0 > journal.txt
or if you had to reboot then run:
journalctl -b-1 > prevjournal.txt
and attach the resulting text file here.
Those logs appear to be incomplete and also not relevant to this bug. Next time it happens please run:
journalctl -b0 > journal.txt
or if you had to reboot then run:
journalctl -b-1 > prevjournal.txt
and attach the resulting text file here.