| Summary: | Settings for identical monitors get inappropriately cloned on reboot and end up overlapping | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Marcello Massaro <dev> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | account+kde, nate, nico, shawn.peterson |
| Priority: | NOR | ||
| Version First Reported In: | 5.20.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Output of kscreen-console bug | ||
|
Description
Marcello Massaro
2020-02-03 08:30:48 UTC
After updating to Plasma 5.18, the issue seems to be gone. I'm having the same issue. Having two (and possible will apply to more than two) monitors of the same brand and model causes kscreen to generate the same Id, which causes the settings to not be stored correctly. STEPS TO REPRODUCE 1. Connect to monitors of the same brand and model 2. Configure them with different rotations 3. Reboot and check the generated files inside ~/.local/share/kscreen. OBSERVED RESULT Since both monitors get assigned the same id, the last configuration is applied to both monitors. EXPECTED RESULT Keep different configurations for each monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.10.7-arch1-1/5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The configuration works until I reboot, in which case it resets. I have tried, without success: 1. Delete the ~/.local/share/kscreen folder. 2. Generate a random hex string of 32 characters and created a file inside ~/.local/share/kscreen/outputs and added that configuration to the one generated under ~/.local/share/kscreen/hash. Created attachment 134941 [details]
Output of kscreen-console bug
Included the output of kscreen-console bug
Does this still happen in Plasma 5.25? We did a lot of multimonitor robustness work in that release. Could you test? Thanks! (In reply to Nate Graham from comment #4) > Does this still happen in Plasma 5.25? We did a lot of multimonitor > robustness work in that release. Could you test? Thanks! Hey Nate! Thanks for your work, but I don't have two of the same brand and model monitors, so I can't test. However, I remember fixing it by checking the "Only for this specific display arrangement" option for "Save display's properties", in case it helps someone else. Thanks again! 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! I'm having this issue in KDE 5.26.2(Arch Linux). I've two LG monitors that are also the same model. When monitors truly have the same data, KScreen can only de-duplicate them by looking at their connector names. If you're using an AMD GPU, these unfortunately are volatile and can swap positions on boot. Are you using an AMD GPU? Can you paste the output of `kscreen-doctor -o`? Nicolas, thanks. That worked for me. Nate, I wanted to mention that I did not experience this bug until I switched both of my connection cords to display ports. Prior to that, I had one of them as hdmi and one of them as display. I did not get the bug until then. Cool, if "Only for this specific display arrangement" works for you, then it sounds like things are working. |