Description of problem: KDE doesn't always save the screen's resolution of an user account. Version-Release number of selected component (if applicable): plasma-desktop-5.6.2-2.fc24.x86_64 plasma-workspace-5.6.2-1.fc24.x86_64 sddm-0.13.0-7.fc24.x86_64 How reproducible: Not always, but I'd say that 90% of the times is fairly reproducible. Steps to Reproduce: 1. Install Fedora from the "Fedora-KDE-Live-x86_64-24-20160424.n.0.iso" ISO 2. Boot the installed system; create two user accounts. 3. Set a custom screen resolution on the first user account, using the appropriate graphical KDE tool. In my case, I set it to 1920x1080. 4. Poweroff. Then, perform a clean boot. 5. Log in with the second user account (the one where we didn't change the screen's resolution). Confirm that the resolution is the standard one (1024x768 in my case). 6. Logout. 7. Log in with the first user account, the one with the custom resolution. Actual results: 1. The resolution is not the custom one chosen by the user, but the standard one, which apparently overrides the saved one. Expected results: 1. The resolution should be automatically set; the saved preference should be retrieved and not overridden. Additional info: I'm testing with qemu-kvm.
This might potentially be a blocker, but I'm proposing this as a freeze exception for 24-final, since I don't think it is severe enough. One of KDE's graphical tools, the one which should be responsible for setting and storing the screen's resolution, doesn't always work as expected. This might be a conditional violation of the "2.4.6 Default application functionality" F24 Final Criterion. "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." References: https://fedoraproject.org/wiki/Fedora_24_Final_Release_Criteria#Default_application_functionality
Hi, I'm not sure, but I've the feeling that not saving custom settings not only effects the screen resolution. I see the same symptoms with my two screens. 90% of the times (or so) they are cloned (saved are side by side) after login. Btw. when I look in the file ~/.local/share/kscreen/<6414fe8cde5073ea6e0b588b2c2e6d41> the settings seems correct. So this issue might be better charaterized as a failed restore? HTH Martin Kho
Hi, Upstream report: #kde356884 [1] In comment #20 is a workaround given. Setting up my monitors in xorg.conf wasn't necessary because X default setup is correct for me. Disabling kscreen2 was enough. HTH Martin Kho [1] https://bugs.kde.org/show_bug.cgi?id=356884
Hi, Well, actually there are many more reports indicating issues with kscreens configuration saving/retrieving. Martin Kho
Discussed during the 2016-05-30 blocker review meeting: [1] Decision was made to classify this as a RejectedFreezeException as, while this bug is an annoyance, it can be fixed with an update post-release. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-05-30/f24-blocker-review.2016-05-30-16.01.txt
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.