EXT: [PATCH weston 0/1] Allow forcing outputs on

[Tomasz Olszak]

I probably mislead you, I probably haven't noticed difference between
starting weston without screens and weston state after disconnecting
all screens.
Still great that is was possible to fix so fast.

2018-06-21 15:01 GMT+02:00 Pekka Paalanen <ppaalanen at gmail.com>:
> On Thu, 21 Jun 2018 11:03:36 +0200
> Tomasz Olszak <olszak.tomasz at gmail.com> wrote:
>
>> To reproduce the issue:
>>
>> weston.ini:
>> [output]
>> name=HDMI-A-2
>> mode=74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync
>> force-on=true
>>
>> Connect screen to HDMI-A-1 and start weston. You get weston info:
>> interface: 'wl_output', version: 3, name: 13
>>        x: 0, y: 0, scale: 1,
>>        physical_width: 410 mm, physical_height: 230 mm,
>>        make: 'PHL', model: 'Philips 196V',
>>        subpixel_orientation: unknown, output_transform: normal,
>>        mode:
>> ...
>> interface: 'wl_output', version: 3, name: 14
>>        x: 1366, y: 0, scale: 1,
>>        physical_width: 0 mm, physical_height: 0 mm,
>>        make: 'unknown', model: 'unknown',
>>        subpixel_orientation: unknown, output_transform: normal,
>>        mode:
>>                width: 1280 px, height: 720 px, refresh: 59.855 Hz,
>>                flags: current
>>
>
> The above is all ok. I thought you didn't have any real monitor
> connected and then the x coordinate became odd from the start.
>
>>
>> Now disconnect HDMI-A-1:
>> interface: 'wl_output', version: 3, name: 14
>>        x: 2732, y: 0, scale: 1,
>>        physical_width: 0 mm, physical_height: 0 mm,
>>        make: 'unknown', model: 'unknown',
>>        subpixel_orientation: unknown, output_transform: normal,
>>        mode:
>>                width: 1280 px, height: 720 px, refresh: 59.855 Hz,
>>                flags: current
>>
>> That seems like a bug.
>
> Right, it's a bug, but not the kind of bug I expected. When the Philips
> gets disconnected, the remaining output should at most move to 0,0, not
> move further away.
>
> I've just sent patches to fix this:
> https://patchwork.freedesktop.org/series/45166/
>
>
> Thanks,
> pq