Hi, I confirm that this bug can occur on latest Intrepid. I resized my swap, and obviously it changed its UUID. I didn't think I had to update anything more than fstab… But I came across the same problem as in this bug : usplash quits just before “reading files needed to boot” message appears on text console. Using the suggested workaround/fix (blkid → fstab/resume files → rebuild initramfs → reboot) works great and totally solves my problem. USPLASH IS BACK ! YAY !!
But it seems usplash is not hardened on latest intrepid than on hardy, regarding to this swap UUID problem. I think that /etc/…/resume should be kept empty (or non-existent) if there is only one swap device referenced in fstab, and the one from fstab should be taken if “resume” file is empty or non-existent. … when redondant/duplicate configuration data leads to problems… regards, -- [hardy] splash screen disappears after a few seconds https://bugs.launchpad.net/bugs/205990 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
