Comment 30 for bug 2020782

I've also tested the "vv5" package in a fresh VM and can confirm that zero hz is now supported, and now facing the same scenario where multiple monitors are automatically enabled.

Another issue that still stands is the "config history" issue I've mentioned. If you exclusively change the resolution from gnome display settings, it can apply a new resolution and revert to a previous config (via the timeout prompt) without any issue. But when the resolution is changed via the NICE DCV client's options (or via `xrandr` for that matter), mutter does not register that resolution change in `config_history`, and cannot revert back to the previous config when prompted. This is reproducible with just the default gnome desktop environment and the `xrandr`

The reproducer is as follows:

(assume that the initial resolution is 1920x1080)

- Set a resolution via `xrandr`, e.g. (1366x768)
- Open gnome display settings, and try to set the resolution to 1024x768
- Press "revert back" when prompted
- The resolution will not go back to 1366x768 as it should and will stay at 1024x768

I've debugged this and noticed that gnome display settings use mutter's org.gnome.Mutter.DisplayConfig DBus interface and calls ApplyMonitorsConfig for resolution changes, whereas neither NICE DCV nor xrandr does that, so mutter is not notified about the change.

I guess this will need a separate issue.