It seems that blueproximity will call the unlock command even if there is activity that has nothing to do with bluetooth device proximity. For example, if a program that was on the locked screen died or some thing was changed on the screen via ssh, etc. To make it play well with other stuff on the computer, it should call the unlock script for one reason and one reason only, a configured bluetooth device appeared in proximity, nothing else. But I am finding it otherwise.
Can you please let me know if this is a bug or a feature? If a bug, I will be happy to provide additional information if you cannot reproduce it. If it is a feature, I request that you verify the bluetooth device proximity before calling the unlock command so that all other triggers are ignored.
Thanks for your wonderful program.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that blueproximity will call the unlock command even if there is activity that has nothing to do with bluetooth device proximity. For example, if a program that was on the locked screen died or some thing was changed on the screen via ssh, etc. To make it play well with other stuff on the computer, it should call the unlock script for one reason and one reason only, a configured bluetooth device appeared in proximity, nothing else. But I am finding it otherwise.
Can you please let me know if this is a bug or a feature? If a bug, I will be happy to provide additional information if you cannot reproduce it. If it is a feature, I request that you verify the bluetooth device proximity before calling the unlock command so that all other triggers are ignored.
Thanks for your wonderful program.