Bug#888480: Still a Problem - Gets Worse

[Barak A. Pearlmutter]

This is still a problem.
And here's a scenario where it's worse! Which happened to me.

User "helena" is marked admin. But has never logged in, so as yet has
no password set.

User "barak" is logged in, and wants to run synaptic. That user is set
up to allow sudo with no password.

But oops, synaptic wants him to fill in helena's password. Which does not exist.

And the authentication dialog has grabbed everything: cannot exit or
abort, cannot switch virtual consoles. Completely unresponsive. Only
options are to hit the power button, or log in from another host via
ssh and figure out which is the bad process and kill it. Neither of
these are things we should require from a normal user.