Hello,

lately, my custom udev rule, residing in /etc/udev/rules.d/90-yubikey.rules,
which tracks, whether a Yubikey attached to the system has been removed, yields
contradicting results to a custom script run to lock the screen in the event of
the Yubikey removal. To avoid the coincidence of locking the screen, just by
reloading the KeepassXC challenge response module, a lsusb query is processed
at this stage. 
Unfortunately, this lsusb seems to return the Yubikey as attached to the
system, even though it has been removed ahead of script execution.
Running journalctl -e shows, that the services corresponding to the Yubikey,
such as the smart card daemon, stopped after removing the key. dmesg does not
offer any output, with regards to the removal steps and only hints at attaching
the Yubikey to the USB.
I currently don't quite have an idea, where to look first, when it comes to the
resolution of this problem. Thus, any help would be appreciated. 

Kind regards

Thomas