"I am tired of telling each user how to work around a problem."
Frustratingly, you didn't mention the workaround in this bug, and Googling found your G+ post which says "cd /etc/init; for p in plymouth*;do echo "manual" > ${p}.override;done" which doesn't quite work.
For those stuck, the answer is that the override files need to be called, eg. plymouth.override, NOT plymouth.conf.override.
With that correction, X fails to start, but Ctrl+Alt+F1 [Ctrl+Alt+←] at least gets me a terminal with which I can view /var/log/Xorg.0.log and see the problem, which I don't think is related to this bug any more.
"I am tired of telling each user how to work around a problem."
Frustratingly, you didn't mention the workaround in this bug, and Googling found your G+ post which says "cd /etc/init; for p in plymouth*;do echo "manual" > ${p}.override; done" which doesn't quite work.
For those stuck, the answer is that the override files need to be called, eg. plymouth.override, NOT plymouth. conf.override.
With that correction, X fails to start, but Ctrl+Alt+F1 [Ctrl+Alt+←] at least gets me a terminal with which I can view /var/log/Xorg.0.log and see the problem, which I don't think is related to this bug any more.