Bug 416978

Since around the change of kscreen outputs to use hashes (last quarter of last year) at around the solving of: https://phabricator.kde.org/D25021 My tripple screen setup stops working after each restart.


Hardware Setup:
Thinkpad docked into a docking station (open lid, screen 1)
Two identical screens (LG) attached to the docking station, both connected through different display ports (screen 2 & 3)

System Setup:
Arch with xorg, and kscreen version 5.17.5-1

If I startup the system the two LG screens are always cloned (handled as one). I currently can manualy change the layout to a working (next to each other) setup through the display configuration. but after another reboot (I shut it down each evening) everything is back to cloning. 

The config files are looking like this:
$ find .local/share/kscreen/outputs 
.local/share/kscreen/outputs
.local/share/kscreen/outputs/a08b296dca3c3f699c0f4ec6cf0497ee
.local/share/kscreen/outputs/cd131e344da8a46cf0f28edd071ad178
$

I would expect that at least one other file would appear for the third screen, but it seems that the two LG screens produce the same hash and therefore overwrite each other (or better the last overwrites the first):

$ cat .local/share/kscreen/outputs/a08b296dca3c3f699c0f4ec6cf0497ee
{
    "id": "a08b296dca3c3f699c0f4ec6cf0497ee",
    "metadata": {
        "fullname": "xrandr-unknown",
        "name": "eDP-1"
    },
    "mode": {
        "refresh": 59.977149963378906,
        "size": {
            "height": 1080,
            "width": 1920
        }
    },
    "rotation": 1,
    "scale": 1
}
$ cat .local/share/kscreen/outputs/cd131e344da8a46cf0f28edd071ad178
{
    "id": "cd131e344da8a46cf0f28edd071ad178",
    "metadata": {
        "fullname": "xrandr-24BK55-16843009",
        "name": "DP-2-3"
    },
    "mode": {
        "refresh": 59.950172424316406,
        "size": {
            "height": 1200,
            "width": 1920
        }
    },
    "rotation": 1,
    "scale": 1
}
$

Within the `Display Configuration` the second screen is identified as `DP-2-2`, so my guess is that the name is not included within the hashing.