Took another crack at debugging this and got my package upgraded. I get the same freeze if I set RESUME=None, but if I set `RESUME=UUID=$(blkid -s UUID -o value "/dev/mapper/cryptswap1")` I was able to get the old behaviour back on the newer initramfs-tools
From looking at the newer initramfs-tools diff I don't think but bug is here, but that the change here is further revealing the bug.
And was pointed toward plymouth likely being part of the problem. Sure enough, by removing `quite splash` from the boot options, the problem also goes away.
Took another crack at debugging this and got my package upgraded. I get the same freeze if I set RESUME=None, but if I set `RESUME= UUID=$( blkid -s UUID -o value "/dev/mapper/ cryptswap1" )` I was able to get the old behaviour back on the newer initramfs-tools
From looking at the newer initramfs-tools diff I don't think but bug is here, but that the change here is further revealing the bug.
I posted an issue for some support on the nvidia dev forum here: https:/ /devtalk. nvidia. com/default/ topic/1050238/ linux/freeze- after-login- screen- in-ubuntu- 18-04-with- 1050ti- mobile/
And was pointed toward plymouth likely being part of the problem. Sure enough, by removing `quite splash` from the boot options, the problem also goes away.