Bug 183563
| Summary: | gnome shutdown dialog timer does not count down | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernard Johnson <bjohnson> | ||||
| Component: | gnome-panel | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | nphilipp | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-03-02 14:00:03 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Bernard Johnson
2006-03-02 00:24:20 UTC
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 whatever ? 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? Shan. |