Comment 6 for bug 1574777

Here are the relevant parts of the log:

[2016-04-28 23:02:17.359724] mirserver: New display configuration:
[2016-04-28 23:02:17.370686] mirserver: 0.1: LVDS 10,0" 135x216mm
[2016-04-28 23:02:17.370872] mirserver: Current mode 1200x1920 57,07Hz
[2016-04-28 23:02:17.370953] mirserver: Preferred mode 1200x1920 57,07Hz
[2016-04-28 23:02:17.371005] mirserver: Logical position +0+0
[2016-04-28 23:02:17.381173] mirserver: 0.2: DisplayPort 9,2" 203x114mm
[2016-04-28 23:02:17.381298] mirserver: Current mode 1920x1080 0,60Hz
[2016-04-28 23:02:17.381354] mirserver: Preferred mode 1920x1080 0,60Hz
[2016-04-28 23:02:17.381406] mirserver: Logical position +1200+0
[2016-04-28 23:02:17.381464] mirserver: 0.3: unused LVDS

qtmir.screens: Screen(0x800400) - id: 1 geometry: QRect(0,0 1200x1920) window: 0x14e6e90 type 7
qtmir.screens: Screen(0x12a4760) - id: 2 geometry: QRect(1200,0 1920x1080) window: 0x11ac1a0 type 10

[2016-04-28 23:02:43.188113] mirserver: New display configuration:
[2016-04-28 23:02:43.198915] mirserver: 0.1: LVDS 10,0" 135x216mm
[2016-04-28 23:02:43.199087] mirserver: Current mode 1200x1920 57,07Hz
[2016-04-28 23:02:43.199148] mirserver: Preferred mode 1200x1920 57,07Hz
[2016-04-28 23:02:43.199199] mirserver: Logical position +0+0
[2016-04-28 23:02:43.199257] mirserver: 0.2: unused DisplayPort
[2016-04-28 23:02:43.199310] mirserver: 0.3: unused LVDS

qtmir.screens: Screen(0x800400) - id: 1 geometry: QRect(0,0 1200x1920) window: 0x11ac1a0 type 7

I'm afraid the "Current mode 1920x1080 0,60Hz" part is the culprit. It seems the monitor tricks Mir into thinking it wants a refresh rate of... 0,6 times per second...

Looking at the EDID data from Xorg.log no such mode is advertised - there is a lot of "The EDID for Idek Iiyama PL2409HD (DFP-1) contradicts itself" messages. Mir's likely less able to work around such quirks still.