Thank you for your bug report, could you add the journalctl log from the
faulty start?
The issue doesn't seem to be a plymouth one though, it sounds like the
system frozen/hit and issue and maybe something got corrupted or in a
buggy state
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875686
Title:
Plymouth fails to appear after troubled reboot in which the system
nearly locked prior to the reboot due to high memory pressure and
Gnome had to reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1875686/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
