'journalctl -b -1' comes back with: Specifying boot ID has no effect, no persistent journal was found
I'm assuming though you're after the boot log for the previous session (that froze) so I've manually extracted this from /var/log/syslog in the attached archive (prevboot.txt). Unfortunately nothing new was added to /var/crash as a result of the freeze. Something additional to mention which may be related (given it's display related), I had to reboot the machine a couple of times to get this as it seemingly had issues starting the display manager. Visually the display kept flicking between the boot log and another one with some further logging info. The graphical login screen was never displayed. Syslog was showing messages as follows: Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Only fix was to reboot it. I've attached the boot log for this one as 'prevboot1.txt'. This problem happened on two different boots. ** Attachment added: "boot logs" https://bugs.launchpad.net/ubuntu/+bug/1904230/+attachment/5435802/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
