Well, it's not "totally unusable" since you can still switch to another user. And there should be other users available if you're under a domain setup. The whole "account locking" AD feature is buggy, since every large AD domain user knows they can easily lock out someone else's account.
I guess in the end it all depends on how "being locked out" translates, since I can imagine a bug asking for the complete contrary of what you're asking.
In that discussion, it might be worth considering that Microsoft does not apply lockout policy to the "screen unlock" dialog: http://support.microsoft.com/kb/188700
Maybe gnome-screensaver's unlock screen dialog could be taught to recognize a specific "locked" error code, but I'm far from convinced we should do that.
Well, it's not "totally unusable" since you can still switch to another user. And there should be other users available if you're under a domain setup. The whole "account locking" AD feature is buggy, since every large AD domain user knows they can easily lock out someone else's account.
I guess in the end it all depends on how "being locked out" translates, since I can imagine a bug asking for the complete contrary of what you're asking.
In that discussion, it might be worth considering that Microsoft does not apply lockout policy to the "screen unlock" dialog: http:// support. microsoft. com/kb/ 188700
Maybe gnome-screensaver's unlock screen dialog could be taught to recognize a specific "locked" error code, but I'm far from convinced we should do that.