timed login countdown is set to 30 after making action

Bug #241966 reported by Oleg Vaskevich
2
Affects Status Importance Assigned to Milestone
gdm
Expired
Medium
gdm (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Hello, I'm using Ubuntu 8.04 (upgraded from 7.10) with gdm version 2.20.6-0ubuntu2.

To reproduce this bug, change the Timed Login value to 10, for example, and logout. The timer does start down from 10, but make any action such as a keypress or clicking on the screen and the timer starts back at 30. Instead, it should start at 10 again.

Oleg Vaskevich (olegv)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=545292

Changed in gdm:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Triaged
Changed in gdm:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream comment

"This seems a feature of GDM rather than a bug.

For gdmlogin, refer to the code gdm/gui/gdmlogin.c in the function
gdm_timer_up_delay

For gdmgreeter, refer to the code gdm/gui/greeter/greeter_item_timed.c in the
function in a similar function gdm_timer_up_delay.

It seems that GDM assumes that if you start typing, that it should reset the
timer to at least 30 seconds to give the user a more reasonable chance to
successfully interact with the dialogs.

I don't feel strongly that this "feature" is meaningful. If someone wanted to
rewrite this code so that it is smarter or works better, we can discuss. Also
might be nice to move such common code into the gdm/gui/gdmcommon.c file rather
than having duplicate code in both the gdmlogin and gdmgreeter codebase."

do you really consider the behaviour as buggy?

Revision history for this message
Oleg Vaskevich (olegv) wrote :

Well, if the user set it to 10 secs they probably want it to be 10 seconds.

Also, the actual timing is off. For example during the countdown, gdm auto logs the user in after 8 seconds, so the timing is still off.

Revision history for this message
Sebastien Bacher (seb128) wrote :

users want 10 seconds in standard case, but if they decide to start typing an username that's probably not to a race against the counter, some setups have a 3 seconds timer there which is an almost autologin but let the user do an action in case he wants to choise an another user for example, thinking about it your suggestion doesn't seem to make really sense and would break such usecases

Changed in gdm:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue in karmic or lucid?

Changed in gdm:
importance: Unknown → Medium
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.