Bug 1218623

Summary:	systemd-vconsole-setup.service fails with "No usable source console found: Device or resource busy"
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Tony Walker <tony.walker.iu>
Component:	Basesystem	Assignee:	E-mail List <screening-team-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	Andreas.Stieger
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Tumbleweed
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Tony Walker 2024-01-08 16:39:59 UTC

On startup, systemd-vconsole-setup emits "No usable source console found: Device or resource busy" and fails to restart as it should. When boot-up is complete, systemd-vconsole-setup is marked as failed and is not running. It can be started manually without error.

This issue seems similar to, but different from, bugs #1215282 and #943312.

The solution for me was to modified /usr/lib/systemd/system/plymouth-start.service as
follows:

1) change "KillMode" from none to "mixed",
2) add "IgnoreOnIsolate=true" to the "[Unit]" section, and
3) run "dracut -f".

I rebooted a few times and the errors were not generated.

There may be other and better solutions, but I verified my proposed solution against the package for Fedora 39 and found my changes were identical.

Comment 1 Andreas Stieger 2024-01-08 17:16:24 UTC

Reported in bug 1218618, thank for the workaround

*** This bug has been marked as a duplicate of bug 1218618 ***