| Summary: | plymouth-kcm uses presence of update-alternatives to detect Ubuntu | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Fabian Vogt <fabian> |
| Component: | kcm_plymouth | Assignee: | Marco Martin <notmart> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | leszek.lesner, nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Fabian Vogt
2017-05-01 11:25:16 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 That patch landed years ago; marking as fixed. |