Actually this bug seems to be part of the basic XMir startup. Even if I run a bare XMir server:
sudo X -mir foo -mirSocket /tmp/mir_socket :2
with no X clients at all, XMir still decides to change the monitor resolution. It was right before XMir started...
Actually this bug seems to be part of the basic XMir startup. Even if I run a bare XMir server:
sudo X -mir foo -mirSocket /tmp/mir_socket :2
with no X clients at all, XMir still decides to change the monitor resolution. It was right before XMir started...