Summary: | KScreen configuration with identical monitors broken | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Niklas Andersson <niklas.andersson> |
Component: | kded | Assignee: | Daniel Vrátil <dvratil> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | clchildress, cwoelkers, dvratil, imntreal, job, kde, leandro.basilio, linux, nasus.maximos, nexces, rafaelalcantaraperez, saintdev, sebas, simgunz, sutasu, trebor_x |
Priority: | HI | Keywords: | multiscreen |
Version: | git | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kscreen/1bd8dc46e4cd0836d69464437dff0ed732f731cf | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | kscreen-console bug report |
Description
Niklas Andersson
2013-09-25 00:30:56 UTC
I have about the same problem with my dual monitor setup. However, my monitors will be in a "cloned" mode after reboot. Please let me know if I can give more information to help debug this issue. Very similar problem with a laptop and external monitor. External monitor, native resolution 1920x1080, will often default to the laptop displays native resolution, 1366x768, if it comes on at all. If the external monitor is allowed to power save, a setting that is internal to the monitor, than the resolution will change as well 2 out of 3 times. Steps to reproduce. 1. Plug in an external monitor via VGA. 2. Start KScreen and change the display resolution for the external monitor to its native resolution. 3. Wait for monitor to power save, log out of KDE, or reboot the system. Computer is running OpenSuSE Tumbleweed with KDE 4.11.2 and Kscreen 1.0.1. Created attachment 83160 [details]
kscreen-console bug report
Bug report for my first comment.
(In reply to comment #2) Additional info. My laptop has an AMD GPU. The problem only occurs when using the proprietary drivers. Using the open source radeon driver does not cause the problem to occur. The problem is that all your monitors have the same EDID, so when we save the configuration we are "technically" saving different configurations for the same monitor. The solution is take into account the "port" when there is more than one monitor with the same EDID, this can open a can of worms.... but we will try :p. I've got the same or a similar problem (not sure which): I am also experiencing this problem. When I log out, my settings are lost and when logging back in my two monitors are mirrored. Usually if I restart the computer my settings will be correctly applied upon login, but usually not without a restart. I have an Intel chipset (core i5), one monitor is hooked up via VGA and the other is DVI (adapted from the displayport port on the PC). (In reply to comment #7) I meant to mention that when I ran "kscreen-console bug", I noticed that my monitors DO have completely different EDID information. I'm running KDE 4.11.3 on OpenSUSE 13.1. I'm very surprised that the level of importance for this bug is set to 'normal' and it's not addressed for so long time. For so many people it's 'show stopper' as in my case when on multiple workstations with more then one monitor it's impossible to use KDE out of the box and people quickly adopts alternative solutions as gnome and unity where it's not an issue. Are you sure your issue is a duplicate of this one (identical EDID data from multiple monitors?) If not, please report a new ticket, and provide the data developers need to reproduce. Expanding on Alex's comment#5 KScreen stores the configuration and identifies individual outputs by a hash of their edid information. When restoring / applying a saved config, it will try to find an output in the config, will match the wrong one (since it just looks at the id, and that's identical for more than one output) and apply that. Applying the config mixed up the config, the screen setup is now borked. A potential fix: https://phabricator.kde.org/D2156 Git commit 1b1c51cddda7c1d2610e52ee72054df634c9f95c by Sebastian Kügler. Committed on 14/07/2016 at 02:47. Pushed by sebas into branch 'sebas/identicalmonitors2'. improve output identification Summary: When identical outputs (i.e. outputs with the same edid) are connected, the serializer can't match the outputs solely by their id, it will most likely return the wrong one and set that up. In this case, we also compare the output's name with the name saved in the config: this one is different for every monitor. This change should allow to configure and restore setups with identical screens connected. Test Plan: Only compile-tested so far. I'm running out of nightly hours. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2156 M +20 -1 kded/serializer.cpp http://commits.kde.org/kscreen/1b1c51cddda7c1d2610e52ee72054df634c9f95c Git commit 1bd8dc46e4cd0836d69464437dff0ed732f731cf by Sebastian Kügler. Committed on 20/07/2016 at 14:14. Pushed by sebas into branch 'master'. improve output identification Summary: When identical outputs (i.e. outputs with the same edid) are connected, the serializer can't match the outputs solely by their id, it will most likely return the wrong one and set that up. In this case, we also compare the output's name with the name saved in the config: this one is different for every monitor. This change should allow to configure and restore setups with identical screens connected. Test Plan: Only compile-tested so far. I'm running out of nightly hours. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2156 M +20 -1 kded/serializer.cpp http://commits.kde.org/kscreen/1bd8dc46e4cd0836d69464437dff0ed732f731cf |