Hide Forgot
Description of problem: cold boot is required to add 2nd DE to gdm wheel drop-down list Version-Release number of selected component (if applicable): How reproducible: dnf groupinstall kde-desktop-environment in f25 workstation log out/login or reboot does not add plasma to gdm wheel cold boot is required to have plasma appear on gdm wheel Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This seems to be common on other 2nd DE installs also
This seems *extremely* unlikely to be true. I can't see how a shutdown vs. a reboot could possibly make any difference. Has anyone besides you confirmed that aspect of this? Log out vs. reboot could certainly make a difference, because GDM keeps running after log in, so just logging out doesn't give you a new GDM instance, hence it makes sense that a newly installed desktop won't suddenly show up in GDM. But I can't think of any plausible reason why it wouldn't show up on a reboot but would show up on a shutdown.
Yeah, I couldn't reproduce this. My test: 1. Install F25 Workstation (no user creation during install) 2. Boot, run through g-i-s creating a user 'test' 3. From test's desktop session, run 'dnf groupinstall lxde-desktop' 4. Log out to GDM 5. Select 'test', verify there's no 'LXDE' option in the menu (as expected) 6. Log back in to GNOME as 'test', then reboot (don't shut down) 7. Select 'test' at GDM again, see that there is an 'LXDE' option in the menu now If you really can reproduce this, please provide precise reproduction steps.
I documented this as I understand and tested it at https://fedoraproject.org/wiki/Common_F25_bugs#gdm-session-add .
I would like to add that I could not see the secondary DE in the list. Steps: 1. Install F25 workstation. 2. Reboot, login with user created from step 1 3. Install dnf groupinstall mate-desktop 4. Log out of GDM 5. No Mate option in GDM dropdown list 6. Reboot and still no Mate in dropdown list 7. Shutdown and boot up 8. Mate still doesnt appear in the list.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.