Description of problem: I installed the env group "KDE Plasma Workspaces" and expected that after logout KDE is offered as additional desktop env, but I don't see this if pressing the gear-wheel on the gdm login greeter. Why not? Only "yum install @kde-desktop was" helpful: after this, I coukd login into the kde desktop. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.install the group "KDE Plasma Workspaces" 2.logout 3. Actual results: try to login into kde desktop in the GDM greeter, but it's not offered Expected results: kde is offered. Additional info: "yum install @kde-desktop" solves my problem.
This is either a yum or comps problem. Comps defines 2 things: <group> <id>kde-desktop</id> <_name>KDE</_name> ... </group> Which is the core/base classic group (which works), and a newer "Environment" <environment> <id>kde-desktop-environment</id> <_name>KDE Plasma Workspaces</_name> <display_order>10</display_order> <grouplist> ... <groupid>kde-desktop</groupid> </grouplist> <optionlist> <groupid>kde-apps</groupid> <groupid>kde-education</groupid> <groupid>kde-media</groupid> <groupid>kde-office</groupid> <groupid>kde-telepathy</groupid> <groupid>3d-printing</groupid> </optionlist> </environment> Now *I* would expect installing the environment ought to pull in all the stuff listed in <grouplist>, one of which is kde-desktop. That is apparently not the case, as evidenced by this bug. Can anyone clarify how these <environment> items are expected to work?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
No such bug in F22!