Bug 399901

Summary: On Ubuntu-based distros, current boot splash only becomes highlighted after you change it at least once with the KCM
Product: [Applications] systemsettings Reporter: Patrick Silva <bugseforuns>
Component: kcm_plymouthAssignee: Plasma Bugs List <plasma-bugs>
Status: CONFIRMED ---    
Severity: normal CC: kde, nate, oioi555x, postix
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: icons kcm - current icon theme highlighted with a blue border
plymouth kcm - no boot splash is highlighted
kcm after theme changing and reboot

Description Patrick Silva 2018-10-16 21:58:57 UTC
Created attachment 115691 [details]
icons kcm - current icon theme highlighted with a blue border

For example, icons kcm highlights the current theme with a blue border. See the screenshot.
However in plymouth kcm it's impossible to know the current boot splash. As you can see in my screenshot, no boot splash is highlighted.

Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.14.80
Qt Version: 5.11.1
KDE Frameworks Version: 5.52.0
Comment 1 Patrick Silva 2018-10-16 21:59:50 UTC
Created attachment 115692 [details]
plymouth kcm - no boot splash is highlighted
Comment 2 Nate Graham 2018-10-17 14:50:46 UTC
Yeah, this KCM hasn't been ported yet, do it doesn't get the nice blue border.
Comment 3 Patrick Silva 2018-10-20 01:14:33 UTC
Created attachment 115762 [details]
kcm after theme changing and reboot

I configured another theme and rebooted. Now current theme is highlighted.
Comment 4 Nate Graham 2018-10-21 18:37:05 UTC
How strange. Well, these quirks will still all be fixed with the new design, once it's adopted?
Comment 5 Nate Graham 2019-08-01 15:10:37 UTC
Git commit 894f6706afeff7fff73ad0afe4cbf90dfe9b0387 by Björn Feber.
Committed on 01/08/2019 at 14:51.
Pushed by bfeber into branch 'master'.

Improve the look of the Plymouth Boot Splash Screen KCM UI

Summary:
Related: bug 408573

Port the KCM to the new GriedView KCM design.
{F6771665}
Credits go to @broulik, he basically did all the work.

Test Plan: Open the Plymouth Boot Splash Screen KCM.

Reviewers: #plasma, #vdg, ngraham, broulik

Reviewed By: #plasma, #vdg, ngraham, broulik

Subscribers: davidedmundson, abetts, ngraham, broulik, #vdg, plasma-devel, #plasma

Tags: #plasma

Maniphest Tasks: T7270

Differential Revision: https://phabricator.kde.org/D20549

M  +0    -3    src/helper.cpp
M  +99   -53   src/kcm.cpp
M  +19   -4    src/kcm.h
M  +3    -3    src/kcm_plymouth.desktop
M  +63   -150  src/package/contents/ui/main.qml

https://commits.kde.org/plymouth-kcm/894f6706afeff7fff73ad0afe4cbf90dfe9b0387
Comment 6 Kai Uwe Broulik 2019-08-01 15:28:52 UTC
The plymouth not selecting is supposedly a Ubuntu-specific quirk where the /etc/plymouth/plymouth.conf doesn't exist out of the box, so the KCM needs to be adjusted to read the alternatives symlink instead.
Comment 7 Nate Graham 2019-08-01 15:31:49 UTC
Hmm, it just worked when I tried the new KCM on Neon, which is Ubuntu-based.
Comment 8 Kai Uwe Broulik 2019-08-01 16:02:10 UTC
I am on neon as well but never touched the setting, I didn't have the file mentioned until I used the KCM once.
Comment 9 Nate Graham 2019-08-01 16:14:37 UTC
Oh I see.
Comment 10 Patrick Silva 2020-08-12 11:43:24 UTC
This issue persists on neon unstable based on ubuntu 20.04.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.19.80
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Comment 11 oioi555x 2022-06-28 06:22:03 UTC
I opened an MR to fix this issue.
https://invent.kde.org/plasma/plymouth-kcm/-/merge_requests/18