Description of problem: updating to systemd-37-11.fc16.x86_64 breaks plymouth on bootup. plymouth appears on boot but shrinks to the size of the logo, the plymouth resolution is set by /etc/default/grub as I'm using the nvidia driver (no kms). GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=0 GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 quiet SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=uk rd.luks=0 LANG=en_US.UTF-8" GRUB_DISABLE_RECOVERY=true GRUB_GFXMODE="1280x800x32" GRUB_GFXPAYLOAD_LINUX="1280x800x32" On shutdown plymouth is unaffected Version-Release number of selected component (if applicable): systemd-37-11.fc16.x86_64 How reproducible: broken on every boot up, downgrading systemd corrects the issue. Additional info: I haven't found anything in the logs, perhaps you could suggest how to debug this issue.
Created attachment 558167 [details] boot.log
Created attachment 558168 [details] messages.log I found this in messages Jan 29 13:45:04 main_pc kernel: [ 1.525811] vesafb: mode is 1280x800x32, linelength=5120, pages=0 Jan 29 13:45:04 main_pc kernel: [ 1.525825] vesafb: scrolling: redraw Jan 29 13:45:04 main_pc kernel: [ 1.525827] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0 Jan 29 13:45:04 main_pc kernel: [ 1.526116] vesafb: framebuffer at 0xdd000000, mapped to 0xffffc90011800000, using 4032k, total 4032k Jan 29 13:45:04 main_pc kernel: [ 1.526204] Console: switching to colour frame buffer device 160x50 Jan 29 13:45:04 main_pc kernel: [ 1.539184] fb0: VESA VGA frame buffer device Jan 29 13:45:04 main_pc kernel: [ 1.539244] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0 Jan 29 13:45:04 main_pc kernel: [ 1.539248] ACPI: Power Button [PWRB]
It seems the bug affects plymouth only on vesafb (not the usual configuration, because non-KMS systems get the blue-white bar in text mode by default). It's just a graphical glitch. It does not prevent booting. I'm not going to block the systemd update on it. I can reproduce it in a VM. The change in systemd that causes it is: http://cgit.freedesktop.org/systemd/systemd/commit/?id=5c0100a53772eb7f4b11db7b071fc63e82e5a1a7 As a fix I'll just make it skip setting the text mode when resetting the terminal from console_setup().
(In reply to comment #3) > It seems the bug affects plymouth only on vesafb (not the usual configuration, > because non-KMS systems get the blue-white bar in text mode by default). It may not be default but it will affect a significant amount of users. It's > just a graphical glitch. It does not prevent booting. I'm not going to block > the systemd update on it. > Agreed it's just cosmetic and shouldn't prevent the push. > As a fix I'll just make it skip setting the text mode when resetting the > terminal from console_setup(). Thanks, I'm looking forward to the next push that includes the fix.
Fixed upstream in: http://cgit.freedesktop.org/systemd/systemd/commit/?id=512947d46f9fd7daf74c059ac8548cc98b294807 Applied in systemd-37-12.fc16: http://koji.fedoraproject.org/koji/taskinfo?taskID=3745447 You will find that the issue is still reproducible with 37-12.fc16, unless you have masked fedora-readonly.service. That's bug 785662.
Thank you for the prompt fix, indeed the issue is still reproducible. Commenting out the line in /lib/systemd/system/fedora-readonly.service resolves the plymouth issue.
systemd-37-13.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-37-13.fc16
Package systemd-37-13.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-13.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1528/systemd-37-13.fc16 then log in and leave karma (feedback).
systemd-37-13.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.