I think, I found better workaround: after I changed lightdm configuration using 'lightdm greeter settings', I don't face this bug anymore
I think, I found better workaround: after I changed lightdm configuration using 'lightdm greeter settings', I don't face this bug anymore