This is a result of recent changes in the nvidia-graphics-drivers package; I see from your bug report that you have the binary driver enabled.
When cryptsetup is installed, /usr/share/initramfs-tools/conf-hooks.d/cryptsetup sets the 'FRAMEBUFFER' option to 'y'. This causes the plymouth, framebuffer, and brltty hooks to be run, and causes /usr/share/initramfs-tools/scripts/init-top/console_setup to be run in the initramfs... where it would *not* be by default except when the initramfs is interrupted.
The oneiric nvidia packages now install an override hook that unconditionally sets FRAMEBUFFER=n in the initramfs. This fixes a legitimate bug, because letting the framebuffer module be loaded in the initramfs garbles the display (in my experience). However, it does so in a way that prevents *any* access to plymouth from within the initramfs, which is a serious regression for those using luks root partitions.
We should try to find a better way to enable the FRAMEBUFFER option to enable the *correct* modules being loaded from within the initramfs, instead of disabling the FRAMEBUFFER option.
This is a result of recent changes in the nvidia- graphics- drivers package; I see from your bug report that you have the binary driver enabled.
When cryptsetup is installed, /usr/share/ initramfs- tools/conf- hooks.d/ cryptsetup sets the 'FRAMEBUFFER' option to 'y'. This causes the plymouth, framebuffer, and brltty hooks to be run, and causes /usr/share/ initramfs- tools/scripts/ init-top/ console_ setup to be run in the initramfs... where it would *not* be by default except when the initramfs is interrupted.
The oneiric nvidia packages now install an override hook that unconditionally sets FRAMEBUFFER=n in the initramfs. This fixes a legitimate bug, because letting the framebuffer module be loaded in the initramfs garbles the display (in my experience). However, it does so in a way that prevents *any* access to plymouth from within the initramfs, which is a serious regression for those using luks root partitions.
We should try to find a better way to enable the FRAMEBUFFER option to enable the *correct* modules being loaded from within the initramfs, instead of disabling the FRAMEBUFFER option.