Hide Forgot
Description of problem: Autologin with gdm to start Plasma session does not work anymore (yes, i know, there are security concerns, however, it is documented and should work). Version-Release number of selected component (if applicable): unclear. gdm is active, but has not changed. Lots of KDE stuff has been updated by dnf update today. How reproducible: Install Latest patches on Fedora 23, activate gdm (if not already), configure in /etc/gdm/custom.conf: [daemon] AutomaticLoginEnable=true AutomaticLogin=whoever Steps to Reproduce: 1. Install latest Patches on Fedora 23 (no testing repo, just updates) 2. Edit /etc/gdm/custom.conf like shown above, if not already done 3. Reboot Actual results: Session (plasma was the latest) does not start Expected results: User is automatically logged in to the stored session Additional info: With the updates from 1 week ago it was working
By chance i found, that if there is any application left open when shutting down or logging out, autologin works. Currently i use xclock, which i then can find mentioned in ./.config/ksmserverrc and ./.config/session/kwin_10e1d2e5d6000145790359200000023510000_1466860777_736553 So it seems to have to do with, whether any program is started automatically with the session or not, whether autologin works. Seems, someone has added a very genious check somewhere. Very agile, isn't it.
This phenomenon seems fixed with current F24 and updates. Autologin works as expected without the necessity to start additional dummy programs.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.