typing break does not reset timer after resuming from suspend/hibernate

[Matthias Meulien]

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.

[Richard Hughes (richard-hughes)]

gnome-typing-monitor needs to monitor gnome-screensaver for idle time detection.

[Basilio Kublik (sourcercito)]

Hi Matthias
Thanks for your report, this issue is already known upstream and the developers are working on it, you can check the status of this bug or make your comments at http://bugzilla.gnome.org/show_bug.cgi?id=430797

[Roger Binns (ubuntu-rogerbinns)]

It always worked for me in Feisty and Gutsy and after having just upgraded to Hardy I am now seeing this problem.

[Roger Binns (ubuntu-rogerbinns)]

Still broken in Intrepid

[Jan (jan-redhat-bugs)]

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.

[Aldy (aldy-redhat-bugs)]

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.

[JanS (jans-redhat-bugs)]

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

[JanS (jans-redhat-bugs)]

Same issue on Fedora 11

[Hamish Downer (mishd)]

There is a patch available on the upstream bug. I would try it but suspend/resume is broken for me at the moment :( Anyone else want to try it?

About the patch: https://bugzilla.gnome.org/show_bug.cgi?id=430797#c22

The patch itself: http://bugzilla-attachments.gnome.org/attachment.cgi?id=144099

[Bug (bug-redhat-bugs)]

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

[Jan (jan-redhat-bugs)]

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.

[Ray (ray-redhat-bugs)]

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.

[Ray (ray-redhat-bugs)]

Given this was committed a week ago, it will roll into the next stable control center release, which we'll push to Fedora 12.

[Matthias (matthias-redhat-bugs)]

*** Bug 564202 has been marked as a duplicate of this bug. ***

[Wayno (ichabod)]

Linux Phoenix 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:52 UTC 2010 i686 GNU/Linux

nwayno@Phoenix:~$ which gnome-typing-monitor
/usr/bin/gnome-typing-monitor
nwayno@Phoenix:~$ gnome-typing-monitor

the gnome-typing-monitor does NOT display an ICON in the system notification area, in 32 bit Lucid Lynx (ubuntu 10.4) -- works fine in previous release (9.10)

Wayno

[Hamish Downer (mishd)]

@Wayno - the bug you are experiencing is not this bug, but bug #533775

Basically you need to right click on the panel, select Add to Panel and choose the "Indicator Applet" - then you should have a working typing break icon. If you have any follow up comments, please add then to bug #533775.

[Bug (bug-redhat-bugs)]

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

[Bug (bug-redhat-bugs)]

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.

[Sebastien Bacher (seb128)]

typing break has been deprecated in GNOME3, closing that bug