Red Hat Bugzilla – Bug 183563
gnome shutdown dialog timer does not count down
Last modified: 2007-11-30 17:11:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20060223 Fedora/18.104.22.168-5 Firefox/22.214.171.124
Description of problem:
I'm not sure I got the right component here.
If I click System -> Shut Down ... on the panel, the shutdown dialog pops up and says "This system will automatically shut down in 60 seconds". The timer does not count down. After approximately 60 seconds, the computer shuts down.
Under some conditions that I've not been able to pinpoint, the time will erratically count down (like changing 10 seconds at a time). It seems to be somewhat related to moving around windows.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. click system -> shut down
3. system shuts down without timer changing
Actual Results: timer did not count down
Expected Results: timer should count down to show time remaining
Created attachment 125507 [details]
the shut down dialog
the shut down dialog
It was changed to count 60, 50, 40, 30, 29, 28 ...
Thats what you may be seeing
Hmm. Interesting. What problem was being solved by having it count like that?
I find it confusing.
the problem of immediate user panic upon seeing the countdown
I laughed - then I realized you were serious.
what wbout the problem of immediate user panic when they think the machine has
stopped responding (no updates each second) for ten seconds.
Is this a fedora community changeable thing, or driven by upstream gnome or
IIRC, someone filed a bug in the fedora tracker and Matthias got things changed
to the current behavior upstream, but I might be wrong.
It's possible what we have now isn't the right interaction. This should
definitely be taken upstream though.
(In reply to comment #7)
> IIRC, someone filed a bug in the fedora tracker and Matthias got things changed
> to the current behavior upstream, but I might be wrong.
> It's possible what we have now isn't the right interaction. This should
> definitely be taken upstream though.
Is there a way to reduce the time take to logout? If so how?