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 689266 - per-alarm configuration
per-alarm configuration
Status: RESOLVED FIXED
Product: gnome-clocks
Classification: Applications
Component: alarms
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Clocks maintainer(s)
Clocks maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-29 11:18 UTC by Matthias Clasen
Modified: 2020-11-24 12:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2012-11-29 11:18:59 UTC 
There's a few things that I would expect to be able to configure per alarm:

 - alarm tone
 - volume of alarm
 - snooze/escalation/...

my simple phone alarm also has vibrate, I guess that is not so relevant here...
Comment 1 Paolo Borelli 2013-01-05 16:33:04 UTC 
I agree, at the very least on alarm tone. This is blocking on

 - design of how these additional params should be specified
 - figure out how to have different tones/volume with canberra
Comment 2 Daniel van Eeden 2014-02-23 12:01:37 UTC 
I think these could be helpful:
- repeating sound for the timer
- a visual alarm (flashing window)

Both are for using the timer when I'm not constantly behind the computer.
Comment 3 Alexandre Franke 2020-11-24 12:52:35 UTC 
Alarms now have individual settings. While they don’t have all the fields requested in this report, those could now be added. There are also other reports at gitlab for things like setting up custom tone. Please reassess the relevance of the settings you asked for and, if needed, open new reports at gitlab. Considering this fixed as the general request has been addressed.