brettjenkins / teamshassbridge Goto Github PK

If you're logged into Teams, locked the computer and then the computer reboots to install updates, idle detection may not work properly until you lock and unlock the machine again.

This is because Teams never logged the Unlock event as it wasn't open when you unlocked the machine.

Probably not too hard to fix, listen for the start event and then reset the lock variable.

The idle time logs to the console at the moment. The intention is for this to be removed when completely stable

Only experienced this once, so will keep an eye on it, but if the teams log watcher is open and then you launch teams, it seems sometimes teams will quit a few seconds later. Closing the teams log watcher, launching teams and then opening the watcher again works fine.

Presumably an issue with teams trying to rotate log but can't when we have a lock on the file. Will investigate. In the meantime simple easy workaround.