Public bug reported:

When running a utility that requires adiminstrative priviliges, gksu (I
think) tries to lock the screen, but if there is a menu open at the itme
(for example when I launch one utility and opens the menu again to
launch another utility) then gksu fails to lock the screen and shows an
error dialog instead, which has the following text:

Could not grab your mouse.
A malicious client may be eavesdropping on your session or you may have just 
clicked a menu or some application just decided to get focus.
Try again.

This is unnecesarily scary, especially as the more common situation is
the open menu while that situation is explained last. The casual user
would just read the first few words and possibly panic. I think the text
could be easily restructured to better represent the more common use
case, while still providing enough information about malicious clients,
for example:

Could not lock the screen.
This is probably due to a menu that is was open at the time, if this is the 
case you may try to run the program again. If this message repeats itself, it 
may mean that there is a malicious program that is trying to listen to your 
pasword.

Or maybe even:

Could not lock the screen.
Locking the screen is required to run administrative actions in order to make 
sure that no malicious software can listen to your password, but locking the 
screen may also fail if there is a menu open. 
If the latter is the case then you should try to run the program again.

(granted the last one doesn't actually solve the problem of the more
common case being described last, but it is more friendly, IMHO).

** Affects: gksu (Ubuntu)
     Importance: Undecided
         Status: New

-- 
User authentication dialog's failure to lock the screen has an error that is 
unnecesarily scary
https://bugs.launchpad.net/bugs/134474
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to