After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 339116 - Typing Break: Forcing, then canceling a break causes reminders
Typing Break: Forcing, then canceling a break causes reminders
Status: RESOLVED DUPLICATE of bug 134595
Product: gnome-control-center
Classification: Core
Component: [obsolete] Typing break
2.14.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-20 05:41 UTC by Richard Laager
Modified: 2007-03-02 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Richard Laager 2006-04-20 05:41:26 UTC 
Please describe the problem:
If you right-click on the typing break indicator and choose "Take a Break", the
change your mind and hit "Postpone break", the reminders start immediately.

Steps to reproduce:
1. Right-click on the typing break indicator in the notification area
2. Choose "Take a Break"
3. Click "Postpone Break"


Actual results:
After 3 minutes, I get a reminder.

Expected results:
The same behavior as if I hadn't completed these steps -- I should get the break
after my normal timer expires, and reminders if and only if I postpone that break.

Does this happen every time?
Yes.

Other information:
Make sure you have it set to allow you to postpone breaks, or this isn't
relevant, and thus not reproducible. :)
Comment 1 Thomas Wood 2007-02-10 01:41:52 UTC 
I've had this problem too, which is especially annoying when hitting "Take a break" by accident.

Basically, if a user triggers a break, it should have a Cancel rather than Postpone option.
Comment 2 Jens Granseuer 2007-03-02 20:07:40 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 134595 ***