Bug 26034

Summary:	"Start request repeated too quickly" for systemd-vconsole-setup.service
Product:	Mageia	Reporter:	Mészáros Csaba <csablak>
Component:	RPM Packages	Assignee:	Base system maintainers <basesystem>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	csablak, davidwhodgins, tmb
Version:	7	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	plymouth-0.9.4-1.mga7	CVE:
Status comment:
Attachments:	journal messages

Description Mészáros Csaba 2020-01-08 11:36:14 CET

Description of problem:
Start computer - boot

Error message red: "Start request repeated too quickly" for systemd-vconsole-setup.service

Workaround (temporally) maybe the problem is elsewhere?
In any case, there is no error message.

edit: /usr/lib/systemd/sytem/plymouth-start.service
[service]
...
RemainAfterExit=yes

Mészáros Csaba 2020-01-08 11:36:23 CET

CC: (none) => pingvin

Comment 1 Lewis Smith 2020-01-11 20:21:44 CET

Sorry for the trouble you are having, and thank you for your workaround.

It might help to have all the systemd journal messages. Can you please do:
 # journalctl -b | grep systemd > journal.txt
and attach that file to this bug; it should not be big. [There is surely a neater way of doing this without the grep, but I could not discover it].

Plymouth has no registered maintainer, so assigning this to the base system group. (I have checked for duplicates).
CC'ing Thomas as the main systemd committer.

CC: (none) => tmb
Assignee: bugsquad => basesystem

Comment 2 Mészáros Csaba 2020-01-12 09:02:21 CET

Created attachment 11453 [details]
journal messages

Here is the attachment you requested.

Comment 3 Aurelien Oudelet 2020-09-04 11:17:15 CEST

Sorry for leaving this,

Attached journalctl seems incomplete. Could you provide an other one running this without grep systemd command?

Keywords: (none) => NEEDINFO

Comment 4 Aurelien Oudelet 2021-07-06 13:14:16 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 5 Mészáros Csaba 2021-07-07 06:57:08 CEST

Hi all!
I just looked at Mageia 8 and it already has a workaround solution in it. And I didn't even see an error message about it. If you haven't caused a problem so far, imho can be closed.

Comment 6 Dave Hodgins 2021-07-07 07:56:53 CEST

Thanks for the update. Closing.

Status: NEW => RESOLVED
CC: (none) => davidwhodgins
Resolution: (none) => FIXED