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 689082 - Alarm and timer doesn't work if I close the main gnome-clocks window
Alarm and timer doesn't work if I close the main gnome-clocks window
Status: RESOLVED DUPLICATE of bug 735869
Product: gnome-clocks
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Clocks maintainer(s)
Clocks maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-26 13:08 UTC by Elad Alfassa
Modified: 2016-05-29 22:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Elad Alfassa 2012-11-26 13:08:07 UTC 
I'd expect gnome-clocks to be the UI for viewing and starting alarms and timers, and that they would work even if I close the window. Right now, this is not the case, and it makes Clocks much less useful.
Comment 1 Matthias Clasen 2012-11-26 22:07:06 UTC 
Doing this properly needs something like the new notification api that I've proposed on gtk-devel-list a while ago
Comment 2 Elad Alfassa 2013-04-06 18:03:28 UTC 
When this is implemented, it will also makes sense to show some indicator (say, next to the clock on the top bar) so you'll know there's a timer running or an alarm set, like Android does.

Any idea when this new notification API will be available for use? Until it's available, Clocks could simply hide its window on close and keep running in the background until it's time for the timer to end or the alarm to sound.
Comment 3 Robert Roth 2015-01-03 00:09:30 UTC 
Any progress on the new notification API? What do you think about Elad's suggestion until it gets available?
Comment 4 Cédric Bellegarde 2015-09-22 09:18:43 UTC 
Using systemd timers seems a good idea, no?
Comment 5 Paolo Borelli 2015-09-22 09:55:04 UTC 
(In reply to Cédric Bellegarde from comment #4)
> Using systemd timers seems a good idea, no?

Yes, at this point I am open to any solution that works, but I do not have time to tackle it myself
Comment 6 Alexandre Franke 2015-11-04 14:44:06 UTC 

*** This bug has been marked as a duplicate of bug 735869 ***
Comment 7 dev 2016-05-29 22:09:35 UTC 
Using Fedora 23 with Gnome 3.18 and this problem happen to me too