https://bugs.kde.org/show_bug.cgi?id=488270
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #15 from Zamundaaa <xaver.h...@gmail.com> ---
(In reply to docw2732 from comment #10)
> Created attachment 171578 [details]
> kwinoutputconfig.json after the issue happened
What I can see in there is
1. your Samsung screens have the same serial number (boo Samsung!)
2. the screens do have different EDID hashes though, so we can identify them
with that
3. despite that, there are two entries in the config that are completely
identical
but I'm still not sure how that happens, this situation is supposed to be
handled already.
Could you attach the EDID of your screens here, so that we can put it into an
autotest, hopefully find the cause and prevent the issue from happening again
in the future? You can get the EDID blobs with
> cat /sys/class/drm/card1-DP-1/edid > edid.bin
> cat /sys/class/drm/card1-DP-2/edid > edid2.bin
(In reply to Elabajaba from comment #14)
> I also have this issue, and I believe it's due to having a display connected
> but disabled in KDE's display settings. On wakeup both the positioning
> between the displays (orientation is fine, it always remembers my vertical
> monitor is set to vertical) and the primary display selection gets scrambled.
>
> I don't think it's an AMD driver bug or hardware issue as it works properly
> on Gnome.
Please attach your kwinoutputconfiguration.json and the EDID data as well
--
You are receiving this mail because:
You are watching all bug changes.
