SUMMARY: Have a strange issue with Plasma not wanting to remember which monitor I set as the main monitor, the built in monitor of the Lenovo T520 or the Auria monitor connected to the T520 via DP. Seems to happen after I sleep the system or do a restart. One morning is set the Auria monitor to 30Hz refresh rate that at first made me think my vision or monitor was on its last leg. Seems to be a very random issue as this morning it came out of sleep just fine with the monitors settings perfectly intact... One time it came out off Sleep in the morning but this time it would only let me choose between 20 or 30 hurts and resolution was maxed at 1920 x 1080 until after I rebooted the system then it would let me select 60Hz and the true max res of the monitor of 2560 x 1440 I really have no idea why one day it sleeps and wakes just fine and other days it just messes up the external monitor? STEPS TO REPRODUCE 1. Connect second monitor to DP output of T520 Laptop 2. Sleep or restart PC 3. Task bar will move back to laptop display and or resolution and refresh will be wrong on second display OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 20.0.1 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Kernel version: 5.6.11-1-Manjaro Lenovo T520 computer 2nd Generation Core Processor Family Integrated Graphics Controller (Intel Corporation) Auria monitor connected via DP cable.
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26? If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!