In Fedora Modular Server installs from current composes, Cockpit does not have Fedora branding, but generic upstream appearance. Proposing as a Beta FE - this doesn't break anything functionally, but we intend for Cockpit to be Fedora branded out of the box.
There are several bugs mixing in here. 1) Cockpit didn't know how to handle `ID=fedora-modular` in /etc/os-release, so it fell back to default branding. This is fixed in Cockpit 155 2) fedora-modular-release has both `NAME="Fedora Modular Server Edition"` and `VARIANT="Server Edition"` set in /etc/os-release, so when 1) is fixed, we end up with "Fedora Modular Server Edition Server Edition" on the login page. We need to drop " Server Edition" from NAME 3) Lastly, we are missing the fedora-logos package from the default install, which upon investigation is usually pulled in implicitly by the Fedora plymouth theme, but we're missing that as well. We need to make sure fedora-logs ends up on the install one way or another.
(In reply to Stephen Gallagher from comment #1) > 2) fedora-modular-release has both `NAME="Fedora Modular Server Edition"` > and `VARIANT="Server Edition"` set in /etc/os-release, so when 1) is fixed, > we end up with "Fedora Modular Server Edition Server Edition" on the login > page. We need to drop " Server Edition" from NAME Pull-request to make this change: https://src.fedoraproject.org/rpms/fedora-modular-release/pull-request/1
This will be fixed once the platform module is rebuilt with the updated fedora-modular-release.
This is now fixed as of compose Fedora-Modular-27-20171120.n.3
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.