gksu blocks screensaver and does not timeout

Bug #258156 reported by Daryl Lublink on 2008-08-15
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)

Bug Description

Tested in Hardy :

When I choose any option for the administration menu, a window popups up asking me to enter my password (gksu), if I enter nothing it stays there. If I enter nothing for 4 hours it stays there, the screen saver never starts.

This dialogue should not prevent the screensaver from running. Perhaps the dialogue should timeout after 2 of inactivity? Leaving the window open should not stop screensaver.

Daryl Lublink (dlublink) wrote :

Sorry, it was tested in hardy, not intrepid. My bad.

Michael Rooney (mrooney) on 2008-08-15
description: updated
Michael Rooney (mrooney) wrote :

Hi dlublink, thanks for using Ubuntu and thanks for taking the time to file this bug report! I edited the description to reflect Hardy; in the future you can edit the title and description instead of using comments to make corrections.

I can confirm this issue in Hardy as well, although I don't think a timeout is necessarily a good option because it assumes the gksu was initiated by the user and the user is at the computer. However it is possible that a background process or other event could trigger this, and the user may not be around. Timing out would cause whatever wanted privileges to fail to get them, leaving the user clueless that anything even wanted them or that something is potentially wrong.

However that said, there doesn't seem to be any theoretical reason the screensaver couldn't come on, revealing the gksu window when the user returns.

Changed in gksu:
importance: Undecided → Low
status: New → Confirmed
Daryl Lublink (dlublink) wrote :

I think it blocks the screen saver because it might cause user suspicion to see a password dialogue when stopping the screen saver.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers