Bug 379403 - plymouth-kcm uses presence of update-alternatives to detect Ubuntu
Summary: plymouth-kcm uses presence of update-alternatives to detect Ubuntu
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_plymouth (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-01 11:25 UTC by Fabian Vogt
Modified: 2019-08-01 15:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Vogt 2017-05-01 11:25:16 UTC
$SUBJ can't possibly work, other distributions (like openSUSE) use it as well.

There should also be a way to override the command for regenerating the initrd using a CMake variable.
Comment 1 Leszek Lesner 2017-05-23 11:39:03 UTC
Yeah that detection is a bit poor. 
I guess OpenSUSE does not use update-alternatives for setting a default.plymouth. 

As I had a nother issue on ubuntu/debian with update-alternatives I added this patch that checks with update-alternatives --list default.plymouth if the plymouth theme is already registered with alternatives system or not. 
I think this could be used (if it fails on opensuse as it should if there is no default.plymouth) to skip the rest of the stuff. 

https://phabricator.kde.org/D5942
Comment 2 Nate Graham 2019-08-01 15:14:36 UTC
That patch landed years ago; marking as fixed.