Description of problem: If you cancel the boot process i.e. at the cryptsetup password enter stage for an encrypted home partition and have enabled an persistent overlay every boot after that will get you into an uninitialized live system with no user to log in. Version-Release number of selected component (if applicable): Fedora Image: Fedora-Live-KDE-x86_64-19-1.iso Stick creation script: https://git.fedorahosted.org/cgit/livecd/tree/tools/livecd-iso-to-disk.sh blob(b0b51537fb9b371bc13648b0b20f200f4620f1d9) Steps to Reproduce: 1. Create a live stick with encrypted home and persistent overlay 2. Boot until password entering and stop the boot there (i.e. ctrl + alt + del) 3. Boot the stick again Actual results: You get to the log-in screen and can't log in as no user is defined. Expected results: Auto log-in to the live system. Additional info: I tracked this bug down to the /etc/rc.d/init.d/livesys init script in the squashfs.img of the live iso. There is a line that says: if [ -e /.liveimg-configured ] ; then configdone=1 fi This would be fine if not just 5 lines later where a touch /.liveimg-configured In my opinion this file should only be created AFTER the actual initialization has finished at the end of the script not in the beginning.
triage to livecd-tools
livesys is part of spin-kickstarts
ok. I moved this to the end.
For the record: Move configured set to the end. Fixes bug #991466 https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/fedora-live-base.ks?id=a47186bb673789cb3ba6bae8af26bf0a86b7dcac
See also: Bug 998083 - gnome-initial-setup runs on live image boot in current Rawhide