Bug 1175965 - [Jump] Plymouth textmode splash causes broken colors in terminal
[Jump] Plymouth textmode splash causes broken colors in terminal
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem
Leap 15.3
aarch64 Other
: P5 - None : Major (vote)
: ---
Assigned To: Cliff Zhao
E-mail List
Depends on: 1164073
  Show dependency treegraph
Reported: 2020-08-31 13:29 UTC by Guillaume GARDET
Modified: 2022-10-26 09:46 UTC (History)
8 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume GARDET 2020-08-31 13:29:31 UTC
+++ This bug was initially created as a clone of Bug #1164073 +++

On Jump, Plymouth is broken on aarch64 openQA tests on textmode and GNOME:
* Textmode: https://openqa.opensuse.org/tests/1378236#step/first_boot/3
* GNOME: https://openqa.opensuse.org/tests/1378364#step/first_boot/10

Bug #1164073 was the bug for Leap 15.2 which was fixed before the release.
Comment 1 Guillaume GARDET 2020-08-31 13:46:49 UTC
It seems we are missing the following plymouth update https://build.opensuse.org/request/show/769401
Comment 2 Guillaume GARDET 2020-09-01 07:57:17 UTC
Max committed an update to plymouth:

as a workaround.
Comment 3 Lubos Kocman 2021-04-14 15:45:42 UTC
Is this still actual?
Comment 4 Cliff Zhao 2021-04-14 16:32:32 UTC
(In reply to Lubos Kocman from comment #3)
> Is this still actual?

The terminal color problem is still actual.
But I think it is brought into our system when fix bnc#804158, the customer don't want the TTY to be cleared at that time. You may try to remove the "/usr/lib/systemd/system/getty@tty1.service.d", see this problem disappear. Because of the requirement conflict, this bug only could be hanging here.
Sorry for the delay.

[1], https://bugzilla.suse.com/show_bug.cgi?id=804158
[2], https://build.opensuse.org/request/show/173023
Comment 5 Cliff Zhao 2022-10-26 09:46:49 UTC
As comment4 referred, it could not fix from the Plymouth side. 
and I think it's improper to hold the bug in the current stage for a long time.