I believe this is causing loads of reports against gnome-settings-daemon's cursor plugin.
In some cases, the device will become active again before we have a chance to install a "became-active" watch on it, and we'll never receive an alarm saying that it became active.
I believe this is causing loads of reports against gnome-settings-daemon's cursor plugin.
In some cases, the device will become active again before we have a chance to install a "became-active" watch on it, and we'll never receive an alarm saying that it became active.