Description of problem: Upon startup, plymouthd keeps running in virtual console 1, not allowing the override autologin, and consuming ~30% of cpu. The keyboard is being unresponsive, but otherwise I can ssh into the machine, sudo and systemctl stop and kill the plymouthd service. I am on mageia v8 x86-64 updates-testing, with : ``` root@telaviv1:~ # cat /etc/systemd/system/getty@tty1.service.d/override.conf [Service] Type=simple ExecStart= ExecStart=-/sbin/agetty --autologin shlomif --noclear %I 38400 linux root@telaviv1:~ # ``` How reproducible: Always Steps to Reproduce: 1. Reboot. 2. 3.
Summary: pon startup, plymouthd keeps running in virtual console 1, not allowing the override autologin, and consuming ~30% of cpu => Upon startup, plymouthd keeps running in virtual console 1, not allowing the override autologin, and consuming ~30% of cpu
Now it seems that doing "systemctl start getty@tty1.service" as root starts this CPU-hogging plymouthd process, and doing "ctrl+alt+f1" and then "Esc" does not dismiss it.
Unsure for assignee, start with base system. CC Thomas for his view.
Assignee: bugsquad => basesystemCC: (none) => tmb
An update: it appears "@sbin/plymouthd" is being started automatically, even after I killed it using htop and did "systemctl stop plymouth-start.service". So it needs to be killed again.
(In reply to Shlomi Fish from comment #3) > An update: it appears "@sbin/plymouthd" is being started automatically, even > after I killed it using htop and did "systemctl stop > plymouth-start.service". So it needs to be killed again. Another update: I believe I was able to fix to fix this particular bad symptom (= where plymouthd keeps getting started after boot and consumes CPU) by creating the file /etc/systemd/system/plymouth-start.service with these contents (without the quotes delimiters): “““ [Unit] Description=Show Plymouth Boot Screen DefaultDependencies=no Wants=systemd-ask-password-plymouth.path systemd-vconsole-setup.service After=systemd-vconsole-setup.service systemd-udev-trigger.service systemd-udevd.service Before=systemd-ask-password-plymouth.service ConditionKernelCommandLine=!plymouth.enable=0 ConditionVirtualization=!container [Service] # ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session # ExecStartPost=-/bin/plymouth show-splash ExecStart=/bin/true Type=forking KillMode=none SendSIGKILL=no ””” And then do "sudo systctl daemon-reload" (see https://serverfault.com/questions/700862/do-systemd-unit-files-have-to-be-reloaded-when-modified ). My mageia v8 x86-64 system came up normally after rebooting due to a new kernel.
CC: (none) => micheelsen