Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=485588.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-02-14T22:58:12+00:00 Jan wrote: Description of problem: When typing break is enabled (Main menu->System->Preferences->Hardware->Keyboard), it does not count the time during which the system has been suspended. When it is "almost" before the typing break should occur, and the laptop is supsended, after the resume it requests a typing break almost immediately, even though the system has been suspended for several hours. Version-Release number of selected component (if applicable): control-center-2.24.0.1-11.fc10.x86_64 How reproducible: 100 % Steps to Reproduce: 0. have a laptop with working suspend-to-RAM 1. enable the typing break in Main menu->System->Preferences->Hardware->Keyboard 2. use the computer for some time, until it is almost the time for a typing break (the notification area applet starts blinking) 3. suspend to RAM, wait an hour (or whatever) 4. resume and use the computer, unless the typing break is requested Actual results: the typing break occurs almost immediately, as if the laptop has not been suspended. Expected results: after the resume, the typing break applet should restart its timer from zero. Additional info: x86_64 system, but I don't think it is arch-specific. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/5 ------------------------------------------------------------------------ On 2009-04-06T13:38:08+00:00 Aldy wrote: Is there an ETA on a fix for this? It would seem that we could either trap on a suspend and reset the timer, or just check the system time every few seconds. I trigger this bug virtually every day, as I frequently just suspend when I need a break. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/6 ------------------------------------------------------------------------ On 2009-04-06T15:45:43+00:00 JanS wrote: This bug has a long history. I have found _many_ duplicates of this bug on different bugzillas, with the oldest from beginning of 2007. It is curious because it seem as very simple bug to fix. I think the main discussions is now on Gnome bugzilla, here: http://bugzilla.gnome.org/show_bug.cgi?id=430797 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/7 ------------------------------------------------------------------------ On 2009-09-09T06:53:22+00:00 JanS wrote: Same issue on Fedora 11 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/8 ------------------------------------------------------------------------ On 2009-11-18T11:06:39+00:00 Bug wrote: This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/10 ------------------------------------------------------------------------ On 2009-11-18T11:22:01+00:00 Jan wrote: Dear bug zapper and dear package maintainer, do you actually read the comments? The comment #3 clearly says that the problem is still present in F11. This bug Version tag should have been changed to F11 two months ago. Additionally, I have just verified that the bug is still present in F12. There apparently exists an upstream fix, it is described in the upstream bug entry, mentioned in comment #2. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/11 ------------------------------------------------------------------------ On 2009-11-18T15:57:14+00:00 Ray wrote: Hi, The "bag zapper" is an automated message. The person who triggered the message sent it to thousands of bugs at the same time. He's not reading this report specifically right now. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/12 ------------------------------------------------------------------------ On 2009-11-18T16:03:01+00:00 Ray wrote: Given this was committed a week ago, it will roll into the next stable control center release, which we'll push to Fedora 12. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/13 ------------------------------------------------------------------------ On 2010-02-15T05:55:41+00:00 Matthias wrote: *** Bug 564202 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/14 ------------------------------------------------------------------------ On 2010-11-04T11:30:56+00:00 Bug wrote: This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/17 ------------------------------------------------------------------------ On 2010-12-05T07:01:04+00:00 Bug wrote: Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/122038/comments/18 ** Changed in: gnome-control-center (Fedora) Status: In Progress => Won't Fix ** Changed in: gnome-control-center (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/122038 Title: typing break does not reset timer after resuming from suspend/hibernate Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in Debian: Fix Released Status in gnome-control-center package in Fedora: Won't Fix Bug description: Binary package hint: gnome-power-manager As you may know, gnome-typing-monitor automatically lock the screen at regular intervals, for typing break. After hibernation the work interval is not initialized. So coming back from a long restful walk the user can be imposed a break interval after 2 minutes of work... This is not the expected behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/122038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
