Back to bug 7007

Who When What Removed Added
ossman 2017-08-14 14:08:45 CEST Target Milestone --- LowPrio
astrand 2018-04-20 08:45:17 CEST CC astrand
ossman 2018-04-24 13:06:27 CEST Depends on 7160
huglu 2021-06-18 15:08:17 CEST CC huglu
ossman 2021-11-04 14:44:52 CET Depends on 7785
wilsj 2022-01-04 08:59:30 CET CC wilsj
Target Milestone LowPrio 4.14.0
wilsj 2022-01-04 12:27:56 CET Acceptance Criteria • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
wilsj 2022-01-04 13:50:28 CET Acceptance Criteria • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
• [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor, when disconnecting said
monitor the ThinLinc client should still be usable

• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
wilsj 2022-01-04 13:50:46 CET Acceptance Criteria , when disconnecting said
monitor the ThinLinc client should still be usable

• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor
, when disconnecting said
monitor the ThinLinc client should still be usable
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/8] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor
wilsj 2022-01-04 13:51:18 CET Acceptance Criteria • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/8] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor, when disconnecting said
monitor the ThinLinc client should still be usable
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
• [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/7] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor, when disconnecting said
monitor the ThinLinc client should still be usable
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
wilsj 2022-01-05 09:16:10 CET Acceptance Criteria • [0/4] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/7] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should keep full screen enabled on the
selected monitors
• ☐ Disconnecting a selected monitor should keep full screen enabled
on the remaning monitors
• ☐ Disconnecting a non-selected monitor should keep full screen
enabled on all monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in fullscreen over the remaining
connected monitors
• ☐ Given full screen over one selected monitor, when disconnecting said
monitor the ThinLinc client should still be usable
• [0/1] Full screen over current monitor
• ☐ When disconnecting the monitor which houses the ThinLinc client,
the ThinLinc client should still be usable
• [0/3] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/8] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should not change the number of monitors with
full screen enabled
• ☐ Disconnecting a monitor (selected or non-selected) should keep
full screen enabled on at least one of the remaining monitors
• ☐ Mirroring/of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in full screen over the same
number of monitors (if possible)
• ☐ Given full screen over one selected monitor, when disconnecting
said monitor the ThinLinc client should still be usable
• ☐ Given a previous session with full screen over selected monitors,
disconnecting said monitors and then starting the client should
result in full screen still being enabled on one of the monitors
• [0/2] Full screen over current monitor
• ☐ Connecting a new monitor should result in full screen still being
enabled on one monitor
• ☐ When disconnecting a monitor (including that which houses the
ThinLinc client), the ThinLinc client should still be in full
screen on one monitor
samuel 2022-01-11 10:15:45 CET Resolution --- FIXED
Status NEW RESOLVED
samuel 2022-01-11 10:21:52 CET Keywords relnotes
Assignee ossman samuel
wilsj 2022-01-14 10:11:22 CET Acceptance Criteria • [0/3] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/8] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should not change the number of monitors with
full screen enabled
• ☐ Disconnecting a monitor (selected or non-selected) should keep
full screen enabled on at least one of the remaining monitors
• ☐ Mirroring/of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting with two or more monitors selected, then exiting the
client, then reconnecting with one of the previously connected
monitors disconnected should result in full screen over the same
number of monitors (if possible)
• ☐ Given full screen over one selected monitor, when disconnecting
said monitor the ThinLinc client should still be usable
• ☐ Given a previous session with full screen over selected monitors,
disconnecting said monitors and then starting the client should
result in full screen still being enabled on one of the monitors
• [0/2] Full screen over current monitor
• ☐ Connecting a new monitor should result in full screen still being
enabled on one monitor
• ☐ When disconnecting a monitor (including that which houses the
ThinLinc client), the ThinLinc client should still be in full
screen on one monitor
• [0/3] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should not change the number of monitors with
full screen enabled
• ☐ Disconnecting a monitor (selected or non-selected) should keep
full screen enabled on at least one of the remaining monitors
• ☐ Mirroring/of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting monitor(s) when the client is not running (but was
configured to use full screen on a selected set of monitors with the
previous monitor setup) should result in the same number of monitors
being used as before when starting a session without modifying any
client options
• ☐ Disconnecting monitor(s) when the client is not running (but was
configured to use full screen on a selected set of monitors with the
previous monitor setup) should result in at least full screen over
one of the monitors when starting a session without modifying any
client options
• [0/2] Full screen over current monitor
• ☐ Connecting a new monitor should result in full screen still being
enabled on one monitor
• ☐ When disconnecting a monitor (including that which houses the
ThinLinc client), the ThinLinc client should still be in full
screen on one monitor
wilsj 2022-01-14 14:01:03 CET Acceptance Criteria • [0/3] Full screen over all monitors
• ☐ Connecting a monitor should extend the full screen to cover that
screen as well
• ☐ Disconnecting a monitor should keep full screen enabled on the
remaining monitors
• ☐ Mirroring/joining of displays should behave the same way as when
disconnecting/connecting monitors
• [0/6] Full screen over selected monitors
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the current monitor configuration after each change of the
physical configuration
• ☐ Connecting a monitor should not change the number of monitors with
full screen enabled
• ☐ Disconnecting a monitor (selected or non-selected) should keep
full screen enabled on at least one of the remaining monitors
• ☐ Mirroring/of displays should behave the same way as when
disconnecting/connecting monitors
• ☐ Connecting monitor(s) when the client is not running (but was
configured to use full screen on a selected set of monitors with the
previous monitor setup) should result in the same number of monitors
being used as before when starting a session without modifying any
client options
• ☐ Disconnecting monitor(s) when the client is not running (but was
configured to use full screen on a selected set of monitors with the
previous monitor setup) should result in at least full screen over
one of the monitors when starting a session without modifying any
client options
• [0/2] Full screen over current monitor
• ☐ Connecting a new monitor should result in full screen still being
enabled on one monitor
• ☐ When disconnecting a monitor (including that which houses the
ThinLinc client), the ThinLinc client should still be in full
screen on one monitor
• ☐ Changing the system's monitor configuration [1] with a ThinLinc
client running in full-screen mode should not result in any
significant changes to how the ThinLinc client is displayed
• ☐ The ThinLinc client should closely respect the stored full-screen
mode configuration even if the system's monitor configuration has
changed since the full-screen mode configuration was made
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the system's monitor configuration even if this is changed


[1] This can include (but may not limited to): connecting a display,
disconnecting a display, mirroring two displays, joining two displays
wilsj 2022-01-17 11:26:43 CET Acceptance Criteria configuration even if this is changed


[1] This can include (but may not limited to): connecting a display,
disconnecting a display, mirroring two displays, joining two displays • ☐ Changing the system's monitor configuration [1] with a ThinLinc
client running in full-screen mode should not result in any
significant changes to how the ThinLinc client is displayed
• ☐ The ThinLinc client should closely respect the stored full-screen
mode configuration even if the system's monitor configuration has
changed since the full-screen mode configuration was made
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the system's monitor
system's monitor configuration has
changed since the full-screen mode configuration was made.
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the system's monitor configuration even if this is changed
[3].


[1] This can include (but may not limited to): connecting a display,
disconnecting a display, mirroring two displays, joining two displays.

[2] For the "Full screen on selected monitors" case, some complexity
trade-offs were made in bug 7006. With "Full screen on selected
monitors", changing the system's monitor configuration with ThinLinc
running is expected to behave in the same manner as when starting the
ThinLinc client after the system's monitor configuration has changed, as
specified by bug 7006.

[3] Unsaved changes made to the screen selection (if running with "Full
screen on selected monitors") are expected to be discarded if the
system's monitor configuration changes. • ☐ When changing the system's monitor configuration [1] with a ThinLinc
client running, the ThinLinc display configuration should still be
honoured [2].
• ☐ If the system's screen configuration is temporarily changed, the
ThinLinc display configuration should remain stable between before
the temporary change and after that the change has been restored.
• ☐ The ThinLinc client should closely respect the stored full-screen
mode configuration even if the
wilsj 2022-01-17 12:40:26 CET Acceptance Criteria • ☐ When changing the system's monitor configuration [1] with a ThinLinc
client running, the ThinLinc display configuration should still be
honoured [2].
• ☐ If the system's screen configuration is temporarily changed, the
ThinLinc display configuration should remain stable between before
the temporary change and after that the change has been restored.
• ☐ The ThinLinc client should closely respect the stored full-screen
mode configuration even if the system's monitor configuration has
changed since the full-screen mode configuration was made.
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the system's monitor configuration even if this is changed
[3].


[1] This can include (but may not limited to): connecting a display,
disconnecting a display, mirroring two displays, joining two displays.

[2] For the "Full screen on selected monitors" case, some complexity
trade-offs were made in bug 7006. With "Full screen on selected
monitors", changing the system's monitor configuration with ThinLinc
running is expected to behave in the same manner as when starting the
ThinLinc client after the system's monitor configuration has changed, as
specified by bug 7006.

[3] Unsaved changes made to the screen selection (if running with "Full
screen on selected monitors") are expected to be discarded if the
system's monitor configuration changes.
• ☐ When changing the system's monitor configuration [1] with a ThinLinc
client running, the ThinLinc display configuration should still be
honored.
• ☐ Changing the system's monitor configuration should not affect
ThinLinc's saved display configuration.
• ☐ If the saved display configuration cannot be fully realized on the
current system monitor configuration, an approximate display
configuration that closely resembles that of the saved configuration
should be used [2].
• ☐ The screen configuration UI in both tlclient and vncviewer should
reflect the system's monitor configuration [3].


[1] This can include (but may not limited to): connecting a display,
disconnecting a display, mirroring two displays, joining two displays.

[2] For the "Full screen on selected monitors" case, some complexity
trade-offs were made in bug 7006. With "Full screen on selected
monitors", changing the system's monitor configuration with ThinLinc
running is expected to behave in the same manner as when starting the
ThinLinc client after the system's monitor configuration has changed, as
specified by bug 7006.

[3] Unsaved changes made to the screen selection (if running with "Full
screen on selected monitors") are expected to be discarded if the
system's monitor configuration changes.
wilsj 2022-01-17 13:45:51 CET Status RESOLVED REOPENED
Resolution FIXED ---
wilsj 2022-01-17 15:33:42 CET Resolution --- FIXED
Status REOPENED RESOLVED
frifl 2022-01-20 12:19:17 CET Keywords frifl_tester
CC frifl
ossman 2022-01-24 17:08:37 CET Status RESOLVED REOPENED
Resolution FIXED ---
ossman 2022-01-25 10:16:48 CET Status REOPENED RESOLVED
Resolution --- FIXED
wilsj 2022-01-25 10:17:13 CET Keywords wilsj_tester
wilsj 2022-01-25 13:17:03 CET Status RESOLVED CLOSED

Back to bug 7007