Bug 28303 - Failed to start Setup Virtual Console, & Show Plymouth Boot Screen, on boot, 'start-limit-hit'
Summary: Failed to start Setup Virtual Console, & Show Plymouth Boot Screen, on boot, ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2021-02-06 13:55 CET by andre salaun
Modified: 2021-05-08 13:57 CEST (History)
3 users (show)

See Also:
Source RPM: systemd-241-8.5.mga7.src.rpm
CVE:
Status comment:

Attachments
rpm -qa --last (400.94 KB, text/plain)
2021-02-07 00:16 CET, andre salaun 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description andre salaun 2021-02-06 13:55:05 CET 
A few days ago (around February 1st) this failure appeared at the system startup:

FAILED] Failed to start Setup Virtual Console.
and 
FAILED] Failed to start Show Plymouth Boot Screen

# systemctl status systemd-vconsole-setup
● systemd-vconsole-setup.service - Setup Virtual Console
   Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since Sat 2021-02-06 11:51:07 CET; 1h 58min ago
     Docs: man:systemd-vconsole-setup.service(8)
           man:vconsole.conf(5)
  Process: 801 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS)
 Main PID: 801 (code=exited, status=0/SUCCESS)

févr. 06 11:51:08 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 06 11:51:08 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 06 11:51:08 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.

#  systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since Sat 2021-02-06 11:51:07 CET; 1h 55min ago
  Process: 838 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCES>
  Process: 840 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS)

févr. 06 11:51:08 gaia systemd[1]: Failed to start Show Plymouth Boot Screen.
févr. 06 11:51:08 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 06 11:51:08 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
Comment 1 Aurelien Oudelet 2021-02-06 14:57:16 CET 
Hi, thanks reporting this.

I can't reproduce this on a M7 Plasma x86_64 system.
Meanwhile, can you provide in a text file the output of the following command:

$ rpm -qa --last >> ~/rpm-list_by_date.txt

and please attach here.
We want to look of packages installed/updated through at least 25th January 2021.

Also, have you ever changed a important piece of hardware in your computer?

CC: (none) => ouaurelien

Comment 2 andre salaun 2021-02-07 00:16:39 CET 
Created attachment 12314 [details]
rpm -qa --last
Comment 3 Lewis Smith 2021-02-07 21:24:50 CET 
Thanks for that information. This looks significant :
---
virtualbox-kernel-desktop-latest-6.1.18-4.mga7.x86_64 lun. 01 févr. 2021 01:08:42 CET
virtualbox-kernel-5.10.12-desktop-1.mga7-6.1.18-4.mga7.x86_64 lun. 01 févr. 2021 01:08:42 CET
php-pear-1.10.9-1.2.mga7.noarch               lun. 01 févr. 2021 01:08:42 CET
kernel-userspace-headers-5.10.12-1.mga7.x86_64 lun. 01 févr. 2021 01:08:42 CET
kernel-desktop-latest-5.10.12-1.mga7.x86_64   lun. 01 févr. 2021 01:08:42 CET
kernel-desktop-5.10.12-1.mga7-1-1.mga7.x86_64 lun. 01 févr. 2021 01:08:42 CET
kernel-desktop-devel-5.10.12-1.mga7-1-1.mga7.x86_64 lun. 01 févr. 2021 01:08:39 CET
---
Are you running on real hardware, or in VB ?
From the Grub boot menu, Advanced, are you able to select the previous kernel (which normally gets left) ? If so, please try that instead.

In the excellently presented systemctl and journal output you provided, both failures show timing issues:

● systemd-vconsole-setup.service - Setup Virtual Console
Active: failed (Result: start-limit-hit)
févr. 06 11:51:08 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 06 11:51:08 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.

● plymouth-start.service - Show Plymouth Boot Screen
Active: failed (Result: start-limit-hit)
févr. 06 11:51:08 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 06 11:51:08 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.

CC'ing Dave Hodgins who might

Summary: Failed to start Setup Virtual Console on boot => Failed to start Setup Virtual Console, & Show Plymouth Boot Screen, on boot, 'start-limit-hit'
CC: (none) => davidwhodgins, lewyssmith

Comment 4 Dave Hodgins 2021-02-07 23:29:48 CET 
On my personal use install which is highly customized, ...
[root@x3 ~]# systemctl status systemd-vconsole-setup
● systemd-vconsole-setup.service
   Loaded: masked (Reason: Unit systemd-vconsole-setup.service is masked.)
   Active: inactive (dead)
[root@x3 ~]# systemctl status plymouth-start.service
● plymouth-start.service
   Loaded: masked (Reason: Unit plymouth-start.service is masked.)
   Active: inactive (dead)

On this install I'm using run level 3, so neither of those services will
start. Masking is the only way to stop a static service from trying to start.
That's done with ...
# systemctl mask systemd-vconsole-setup
# systemctl mask plymouth-start.service
On this install, I use "startx startkde" to start plasma.

On one of my testing installs, with minimal customizations ...
[root@hodgins ~]# systemctl status systemd-vconsole-setup
● systemd-vconsole-setup.service - Setup Virtual Console
   Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
   Active: inactive (dead) since Tue 2021-02-02 22:08:54 EST; 4 days ago
     Docs: man:systemd-vconsole-setup.service(8)
           man:vconsole.conf(5)
 Main PID: 694 (code=exited, status=0/SUCCESS)

Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Starting Setup Virtual Console...
Feb 02 22:08:54 hodgins.homeip.net systemd[1]: systemd-vconsole-setup.service: Succeeded.
Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Started Setup Virtual Console.
[root@hodgins ~]# systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
   Active: inactive (dead) since Tue 2021-02-02 22:08:54 EST; 4 days ago

Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Starting Show Plymouth Boot Screen...
Feb 02 22:08:54 hodgins.homeip.net systemd[1]: plymouth-start.service: Succeeded.
Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Started Show Plymouth Boot Screen.

On this install, I'm using lxdm to login and start plasma.

How are you logging in?
Comment 5 Lewis Smith 2021-02-08 09:31:39 CET 
To finish my last sentence (sent truncated by accident):
"CC'ing Dave Hodgins who might ... have an idea"!
In your reply above, I do not think display manager etc are relevant. Have you any idea why these reported errors might arise, for both failed services ?
- Start request repeated too quickly
- Failed with result 'start-limit-hit'

On this Mageia 7 system, for comparison, these are all the journal messages relating to virtual console & plymouth services.
Chw 08 08:52:25 systemd[1]: systemd-vconsole-setup.service: Succeeded.
Chw 08 08:52:25 systemd[1]: Started Setup Virtual Console
Chw 08 08:52:29 systemd[1]: Starting Setup Virtual Console...
Chw 08 08:52:29 systemd[1]: systemd-vconsole-setup.service: Succeeded.
Chw 08 08:52:29 systemd[1]: Started Setup Virtual Console.
...
Chw 08 08:52:24 dracut: Starting plymouth daemon
Chw 08 08:52:27 systemd[1]: Starting Show Plymouth Boot Screen...
Chw 08 08:52:27 systemd[1]: plymouth-start.service: Succeeded.
Chw 08 08:52:27 systemd[1]: Started Show Plymouth Boot Screen.
Chw 08 08:52:29 systemd[1]: plymouth-start.service: Succeeded.
Chw 08 08:52:29 systemd[1]: Started Show Plymouth Boot Screen.
Chw 08 08:52:49 systemd[1]: Starting Terminate Plymouth Boot Screen...
Chw 08 08:52:49 systemd[1]: Starting Hold until boot process finishes up...
Chw 08 08:52:49 systemd[1]: plymouth-quit.service: Succeeded.
Chw 08 08:52:49 systemd[1]: Started Terminate Plymouth Boot Screen.
Chw 08 08:52:49 systemd[1]: plymouth-quit-wait.service: Succeeded
Comment 6 andre salaun 2021-02-08 13:34:10 CET 
(In reply to Dave Hodgins from comment #4)
> On my personal use install which is highly customized, ...
> [root@x3 ~]# systemctl status systemd-vconsole-setup
> ● systemd-vconsole-setup.service
>    Loaded: masked (Reason: Unit systemd-vconsole-setup.service is masked.)
>    Active: inactive (dead)
> [root@x3 ~]# systemctl status plymouth-start.service
> ● plymouth-start.service
>    Loaded: masked (Reason: Unit plymouth-start.service is masked.)
>    Active: inactive (dead)
> 
> On this install I'm using run level 3, so neither of those services will
> start. Masking is the only way to stop a static service from trying to start.
> That's done with ...
> # systemctl mask systemd-vconsole-setup
> # systemctl mask plymouth-start.service
> On this install, I use "startx startkde" to start plasma.
> 
> On one of my testing installs, with minimal customizations ...
> [root@hodgins ~]# systemctl status systemd-vconsole-setup
> ● systemd-vconsole-setup.service - Setup Virtual Console
>    Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service;
> static; vendor preset: disabled)
>    Active: inactive (dead) since Tue 2021-02-02 22:08:54 EST; 4 days ago
>      Docs: man:systemd-vconsole-setup.service(8)
>            man:vconsole.conf(5)
>  Main PID: 694 (code=exited, status=0/SUCCESS)
> 
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Starting Setup Virtual
> Console...
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]:
> systemd-vconsole-setup.service: Succeeded.
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Started Setup Virtual Console.
> [root@hodgins ~]# systemctl status plymouth-start.service
> ● plymouth-start.service - Show Plymouth Boot Screen
>    Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static;
> vendor preset: disabled)
>    Active: inactive (dead) since Tue 2021-02-02 22:08:54 EST; 4 days ago
> 
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Starting Show Plymouth Boot
> Screen...
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]: plymouth-start.service:
> Succeeded.
> Feb 02 22:08:54 hodgins.homeip.net systemd[1]: Started Show Plymouth Boot
> Screen.
> 
> On this install, I'm using lxdm to login and start plasma.
> 
> How are you logging in?

I am using sddm
Comment 7 Dave Hodgins 2021-02-08 19:56:39 CET 
Apologies for jumping to early conclusions about the cause, that were wrong.

Comparing things from Mageia 7 where systemd-vconsole-setup.service fails to
Mageia 8 where it works, the fix is to comment out or remove the line
FONT_UNIMAP=ISO-8859-15
from the file /etc/vconsole.conf

systemd-vconsole-setup.service calls setfont which only accepts file names
present in /usr/lib/kbd/consolefonts/

ISO-8859-15.uni is not present in that directory, but apparently ISO-8859-15
is built in elsewhere, so is already used as the default.

plymouth-start.service is working on my system even after switching from lxdm
back to sddm. As I remove splash quiet from the kernel boot options so I can
see the startup messages, I temporarily put them back to ensure that wasn't
a factor.

As plymouth runs early during the startup, try running "dracut -f" as root.
Shouldn't make any difference, but you never know. :-)

I'll look into plymouth-start.service more to see if I can come up with any
other debug options, but please open a new bug report about it, and let's
keep this one about systemd for the /etc/vconsole.conf change.
Comment 8 andre salaun 2021-02-09 11:47:37 CET 
My vconsole.conf is :
FONT=lat0-16
KEYMAP=fr-latin1

I removed splash quiet from /etc/default/grub and then ran dracut -f.

cat /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="nokmsboot resume=UUID=ebeaa0d7-06b7-4c13-80f5-c1a15b39f1d3 audit=0 vga=794"
GRUB_DEFAULT=saved
GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_RECOVERY=false
GRUB_DISABLE_SUBMENU=n
GRUB_DISTRIBUTOR=Mageia
GRUB_ENABLE_CRYPTODISK=y
GRUB_GFXMODE=1280x1024x32
GRUB_GFXPAYLOAD_LINUX=auto
GRUB_SAVEDEFAULT=true
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_TIMEOUT=10

Curiously this the résult for last boot :

# journalctl -b | grep -iE "vconsole|plymouth|virtual console"

févr. 09 11:14:48 gaia dracut: Starting plymouth daemon
févr. 09 11:14:48 gaia systemd[1]: Starting Show Plymouth Boot Screen...
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
févr. 09 11:14:48 gaia systemd[1]: Starting Setup Virtual Console...
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: Starting Show Plymouth Boot Screen...
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: Starting Setup Virtual Console...
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: Starting Setup Virtual Console...
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: Starting Show Plymouth Boot Screen...
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: Starting Setup Virtual Console...
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: Starting Show Plymouth Boot Screen...
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:48 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: Starting Show Plymouth Boot Screen...
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 09 11:14:48 gaia systemd[1]: Started Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:48 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:48 gaia systemd[1]: Failed to start Show Plymouth Boot Screen.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 09 11:14:48 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:48 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 09 11:14:48 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:48 gaia systemd[1]: Failed to start Show Plymouth Boot Screen.
févr. 09 11:14:49 gaia systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
févr. 09 11:14:49 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 09 11:14:49 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:49 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 09 11:14:49 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 09 11:14:49 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:49 gaia systemd[1]: Failed to start Show Plymouth Boot Screen.
févr. 09 11:14:49 gaia systemd[1]: plymouth-read-write.service: Succeeded.
févr. 09 11:14:49 gaia systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
févr. 09 11:14:49 gaia systemd[1]: Received SIGRTMIN+20 from PID 337 (plymouthd).
févr. 09 11:14:49 gaia systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
févr. 09 11:14:49 gaia systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly.
févr. 09 11:14:49 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:49 gaia systemd[1]: Failed to start Setup Virtual Console.
févr. 09 11:14:49 gaia systemd[1]: plymouth-start.service: Start request repeated too quickly.
févr. 09 11:14:49 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 09 11:14:49 gaia systemd[1]: Failed to start Show Plymouth Boot Screen.
févr. 09 11:14:49 gaia systemd[1]: Received SIGRTMIN+20 from PID 337 (plymouthd).
févr. 09 11:14:49 gaia systemd[1]: plymouth-read-write.service: Succeeded.
févr. 09 11:14:49 gaia systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
févr. 09 11:14:59 gaia systemd[1]: Starting Terminate Plymouth Boot Screen...
févr. 09 11:14:59 gaia systemd[1]: Received SIGRTMIN+21 from PID 337 (plymouthd).
févr. 09 11:14:59 gaia systemd[1]: plymouth-quit-wait.service: Succeeded.
févr. 09 11:14:59 gaia systemd[1]: plymouth-quit.service: Succeeded.
févr. 09 11:14:59 gaia systemd[1]: Started Terminate Plymouth Boot Screen.
Comment 9 Lewis Smith 2021-02-10 21:19:33 CET 
André, thank you for these extra tests; but have you tried (if you still have it) the kernel previous to 5.10.12 from 1 Feb as asked in comment 3.
Is this happening as a VBox client, or on real hardware.

If despite the errors the system boots OK, do the virtual consoles Ctl/Alt/F2-6 work?
Comment 10 andre salaun 2021-02-10 21:54:53 CET 
No it's on real hardware.The system boots correctly otherwise.All tty work.
Sorry about the kernel (I thought I said it but no): I tried several previous kernels and the error is the same.
Comment 11 Dave Hodgins 2021-02-11 03:02:56 CET 
As per comment 4, plymouth can not start if "splash quiet" are removed from the
boot parameters.
Comment 12 andre salaun 2021-02-11 10:31:52 CET 
Of course.
Comment 13 Lewis Smith 2021-02-11 19:41:30 CET 
But why the change?
Dave, can you have a quick look at the updates 30 Jan - 2 Feb, most of which can be ignored en mass. The possible kernel update on 1st Feb is discounted by comment 10. The only thing that looks vaguely relevant is:
 systemd-devel-241-8.5.mga7.x86_64 on 31 jan
which I do not have; systemd itself & relatives have not been updated for a year.
Comment 14 Dave Hodgins 2021-02-12 22:50:42 CET 
I don't know what changed on that installation. I doubt it was caused by an
update.
Comment 15 andre salaun 2021-02-13 01:05:56 CET 
I think you are right.It's probably much older but I hadn't noticed it.

For example :
https://www.mageialinux-online.org/forum/topic.php?id=27902#m273877
or
https://bugzilla.redhat.com/show_bug.cgi?id=1801272

Perhaps the cause is systemd version ? An Mga8 in a Vbox doesn't have these failures.
Comment 16 andre salaun 2021-02-15 22:24:52 CET 
Today night after the last updates no more failures with kernel 5.10.14-desktop-1.mga7 :

journalctl -b | egrep "vconsole|plymouth"
févr. 15 22:05:21 gaia dracut: Starting plymouth daemon
févr. 15 22:05:21 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 15 22:05:21 gaia systemd[1]: systemd-vconsole-setup.service: Succeeded.
févr. 15 22:05:21 gaia systemd[1]: plymouth-read-write.service: Succeeded.
févr. 15 22:05:21 gaia systemd[1]: plymouth-start.service: Succeeded.
févr. 15 22:05:21 gaia systemd[1]: Received SIGRTMIN+20 from PID 339 (plymouthd).
févr. 15 22:05:32 gaia systemd[1]: plymouth-quit.service: Succeeded.
févr. 15 22:05:32 gaia systemd[1]: plymouth-quit-wait.service: Succeeded.
Comment 17 andre salaun 2021-02-16 00:05:47 CET 
Sorry this is not the truth. Plymouth and vconsole does not fail since 2021-02-12
 but I don't know why.

journalctl --list-boots
-12 dad6134e9f0c4deb8d85930ed8165825 Wed 2021-02-10 13:08:47 CET—Thu 2021-02-11 00:16:45 CET
-11 2694f9e0cada45e98e70d32a5e030a11 Thu 2021-02-11 09:58:04 CET—Thu 2021-02-11 10:14:56 CET
-10 0933188fed484c01ada40b0ffd0d6e2e Thu 2021-02-11 10:15:16 CET—Thu 2021-02-11 10:20:14 CET
 -9 b88c243652e3401f82a83c085afcbaba Thu 2021-02-11 10:20:32 CET—Thu 2021-02-11 10:47:32 CET
 -8 ede7d32f205d49938630b6adae909275 Thu 2021-02-11 10:47:51 CET—Thu 2021-02-11 11:16:26 CET
 -7 d8707e6b0dd44ec5b9cf41d45ab9be93 Thu 2021-02-11 11:16:45 CET—Fri 2021-02-12 01:15:31 CET
 -6 fc5620bb71124b12b2d2cc12f297b45f Fri 2021-02-12 09:32:59 CET—Fri 2021-02-12 19:20:07 CET
 -5 ef36de4d340a4cd993d8ee839a90dcc9 Fri 2021-02-12 19:20:31 CET—Sat 2021-02-13 02:15:39 CET
 -4 dd458b2c5c9b47659b44aabff82467d4 Sat 2021-02-13 10:50:52 CET—Sun 2021-02-14 01:15:35 CET
 -3 7e47ccb7d26047b299cef02ab0013b9f Sun 2021-02-14 11:32:34 CET—Mon 2021-02-15 00:39:33 CET
 -2 d0edabe19aa24ffc82e7db6775de4de0 Mon 2021-02-15 12:58:25 CET—Mon 2021-02-15 21:51:21 CET
 -1 da8c9ecf7d6044bb9b2aa20c92e67bd9 Mon 2021-02-15 21:51:48 CET—Mon 2021-02-15 22:05:02 CET
  0 ab1c6f1222524c4097d495cd5d0de293 Mon 2021-02-15 22:05:21 CET—Mon 2021-02-15 23:45:25 CET

journalctl | grep -i "limit-hit"
févr. 11 09:58:05 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 09:58:05 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 09:58:05 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 09:58:05 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:16 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:16 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:16 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:16 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:16 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:15:17 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:32 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:32 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:32 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:32 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:32 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:33 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:33 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:33 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:20:33 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:51 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:51 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 10:47:52 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:45 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:45 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:45 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:45 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'.
févr. 11 11:16:46 gaia systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'.


rpm -qa --last | grep -i "11 févr."
tlp-1.2.2-1.mga7.noarch                       jeu. 11 févr. 2021 22:54:32 CET
gssproxy-0.8.2-2.1.mga7.x86_64                jeu. 11 févr. 2021 21:54:08 CET
light-locker-1.9.0-1.mga7.x86_64              jeu. 11 févr. 2021 10:19:31 CET
lightdm-gtk3-greeter-2.0.6-2.mga7.x86_64      jeu. 11 févr. 2021 10:19:31 CET
lightdm-1.26.0-9.mga7.x86_64                  jeu. 11 févr. 2021 10:19:31 CET
lightdm-gtk-greeter-common-2.0.6-2.mga7.noarch jeu. 11 févr. 2021 10:19:30 CET
lib64lightdm-gobject1_0-1.26.0-9.mga7.x86_64  jeu. 11 févr. 2021 10:19:30 CET

So the 2 changes after Févr. 11 11:16:46 in rpms are tlp and gssproxy.
Comment 18 Aurelien Oudelet 2021-03-05 18:33:41 CET 
Does this still occur?

Status: NEW => NEEDINFO

Comment 19 Aurelien Oudelet 2021-04-06 20:39:01 CEST 
Reasons to systemd-vconsole-setup.service to fail are limited:
- wrong configuration
- missing dependencies like keymap under /usr/share/keymap

/etc/vconsole.conf on Mageia 8 French / France:
FONT=lat0-16
KEYMAP=fr-latin1

/etc/default/console-setup
# CONFIGURATION FILE FOR SETUPCON

# Consult the console-setup(5) manual page.

ACTIVE_CONSOLES=guess

CHARMAP=guess

CODESET=guess
FONTFACE=TerminusBold
FONTSIZE=16

VIDEOMODE=

# The following is an example how to use a braille font
# FONT='lat9w-08.psf.gz brl-8x8.psf'

/etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL=pc105
XKBLAYOUT=fr
XKBVARIANT=
XKBOPTIONS=

BACKSPACE=guess

So, as long as you don't hjave modified these files by hand, there nothing that should prevent systemd-vconsole-setup.service to run.

Also, for plymouth:
two reasons:
- wrong configuration
- it can't set the framebuffer to display something.

/etc/plymouthd.conf
# Administrator customizations go in this file
#[Daemon]
#Theme=fade-in
[Daemon]
Theme=Mageia-Default

By default, /etc/default/grub should have "nokmsboot" option to tell kernel to not load "nouveau" kernel modesettiing driver to display Console (tty) because system will use later nvidia nonfree drivers.

But, if your nvidia card is recent (it uses version 460 an later series), you can switch to nvidia KMS by replacing nokmsboot by nouveau.modeset=0 in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub file.
Also, if your system uses UEFI, you can set there the native screen resolution of your monitor to GRUB:
Line GRUB_GFXMODE=1920x1080x32 for a 1080i (Full HD) HDMI monitor for example.
Also, set
GRUB_GFXPAYLOAD_LINUX=keep
or GRUB_GFXPAYLOAD_LINUX=auto
to prevent Kernel to switch the screen resolution while booting.

Keywords: (none) => NEEDINFO

Comment 20 Aurelien Oudelet 2021-04-20 09:56:00 CEST 
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Comment 21 Aurelien Oudelet 2021-05-08 13:57:17 CEST 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEEDINFO => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.