unattended upgrades did an upgrade this morning:
libgdm1
That could be the reason for this issue. Eventually, a restart of the display manager would have avoided this issue after the update.
I'll track this issue for some time and see if it reappears after a reboot and in regular execution (without update behind the scenes).
unattended upgrades did an upgrade this morning:
libgdm1
That could be the reason for this issue. Eventually, a restart of the display manager would have avoided this issue after the update.
I'll track this issue for some time and see if it reappears after a reboot and in regular execution (without update behind the scenes).