Support for KVM - probably reconnecting issue

[TomaszGawlikPL]

I am using 3 PC's with KVM (monitor, mouse and keyboard are switched between 3 connected PCs). On two of them I use Monitorian. Unfortunately when switched to different PC with Monitorian instance running and back to previous one it does not work. Restarting app does the trick. I did not checked sources yet but it is probably a matter of checking if connection is alive. For example if brightness is changed but "connection" is broken (other instance was initialized later) than changing brightness does not change its value. It is read correctly but changes are not applied - read value is unchanged. This could be used to detect the strange state. There might be easier more direct ways to check this.

[emoacht]

Thank you for reporting.
Could you read Contributing Guidelines and post operation.log? Don't forget to post the exact time when each change happened so that I can find the corresponding event or action in the log. How to produce these logs is explained in Reporting in readme.

[emoacht]

Is it possible to provide operation.log within a few days? If not, this issue will be closed.
I have seen so many people just opened an issue but did not respond to the request for additional information.

[Gawson]

operation.log

This is operation log from one of the PC's. Second does not want to generate log. It claims "wait for more log to be registered".

[Gawson]

Desktop PC is sometimes able to recover (Nvidia graphics P2200). On a Dell Laptop (integrated Intel card) I did not see this behaviour. I need to restart app nearly each time I switch computers with KVM.

p.s. (this is my private Github account)

[Gawson]

Ok. Got log from Dell laptop.
operation.log
probe.log

[emoacht]

Thank you for the logs.
The first operation.log shows that the control over the monitor was restored.
The second operation.log shows that this app was restarted and after that the monitor is regarded as not compatible with DDC/CI completely untill the app was restarted again.
It is hard to distinguish between a monitor that can be compatible but not accessible at that time and a monitor that is not compatible completely.

[emoacht]

As a workround, you can use preclear option. Please see #270 (comment)