Alarm Clock is a fully-featured alarm clock for use with an AppIndicator implementation.
Home Page: https://alarm-clock-applet.github.io
License: GNU General Public License v2.0
with the new notification system introduced in jaunty which does not allow any input from the user,
the notification window which appears is very confusing.
attaching the screenshot. It would be wonderful if we could improve the window layout.
with the new notification system introduced in jaunty which does not allow any input from the user,
the notification window which appears is very confusing.
attaching the screenshot. It would be wonderful if we could improve the window layout.
libnotify 0.7.0 includes a number of API changes:
notify_notification_new_with_status_icon is gone
notify_notification_attach_to_status_icon is gone
notify_notification_attach_to_widget is gone
notify_notification_set_geometry_hints is gone
notify_notification_new has lost its 'widget' argument
The attached patch makes alarm-clock-applet 0.3.1 build again, but I'm not sure if I did the right thing. I guess I should call notify_notification_new instead of just removing notify_notification_new_with_status_icon.
Ubuntu has two applications called "Alarm Clock":
App. A: LP:alarmclock, pkgname: alarm-clock, maintained by Tomasz Sałaciński, http://www.alarm-clock.pl
App. B: LP:alarm-clock, pkgname: alarm-clock-applet, maintained by Johannes H. Jensen, http://alarm-clock.pseudoberries.com
Three things:
Naming is emotional, and I guess each of you has his reasons to believe he was there in the first place but please, there must be a solution. Shutter and Pidgin (formerly GScrot and GAIM) did it very successfully (although for different reasons), you should be able to do it too.
Alarm Clock uses the now deprecated libgnomeui. This dependency should be removed.
We only use libgnomeui for handling icons through the gnome_icon_lookup() function.
If I set the sound_repeat option of an alarm, when the alarms triggers the sound is just played once.
Furthemore, when creating the alarm, if a press the play button while having checked the repeat sound checkbox, the
sound just plays once.
This used to work in 11.10
I've tried to obtain a debug log, but it seems that this is not possible now. Starting alarm-clock-applet from
shell yields zero output.
[Test Case]
[Regression potential]
I don't see any.
I would like to make a suggestion that the applet would follow the system icon scheme I have set up. It could have used the stock_alarm.svg / clock.svg / appointment.svg / sleep.svg icons or at least one from the Gnome Colors, Tango or Mist packs. Now the icon is really standing out. :)
Thanks.
Hi.
I saw your applet and I decided to create en ebuild for it in order to add it to portage tree.
ATM it's currently hosted on gentoo-sunrise overlay (if you want to check it out please visit: https://bugs.gentoo.org/283022).
Ebuild system, during compiling process, claims about what it describe as 'poor programming practices'.
This means that your code could be improved in order to fit Gentoo QA.
Would be really nice if you fix your code in order to make it compile properly and better.
fine but exhibit random runtime failures.
Furthermore I saw a lot of "unused variables" in the code. You should removed them before releasing a final version. Just my advice.
Let me know something and keep going on with this brilliant applet :)
Fabiano 'elbryan' Francesconi
start alarm-clock-applet 0.3.2 on xubuntu 11.04 and the alarm list window has no title bar neither controls (close, minimize ..).
the attachment show what I get on my system
PS the debug log isn't useful to determine the cause of this behaviour
[Test Case]
Ubuntu has two applications called "Alarm Clock":
App. A: LP:alarmclock, pkgname: alarm-clock, maintained by Tomasz Sałaciński, http://www.alarm-clock.pl
App. B: LP:alarm-clock, pkgname: alarm-clock-applet, maintained by Johannes H. Jensen, http://alarm-clock.pseudoberries.com
Three things:
Naming is emotional, and I guess each of you has his reasons to believe he was there in the first place but please, there must be a solution. Shutter and Pidgin (formerly GScrot and GAIM) did it very successfully (although for different reasons), you should be able to do it too.
Error output when I try to make version 0.2.1: (I've used apt-get to get all listed dependencies; if you want any particular output please let me know what command to run)
test_alarm.c: In function ‘test_alarm_props’:
test_alarm.c:102: error: expected expression before ‘==’ token
test_alarm.c:103: error: expected expression before ‘==’ token
test_alarm.c:104: error: expected expression before ‘==’ token
test_alarm.c:105: error: expected expression before ‘==’ token
test_alarm.c:106: error: expected expression before ‘==’ token
test_alarm.c:107: error: expected expression before ‘==’ token
test_alarm.c:108: error: expected expression before ‘==’ token
test_alarm.c:109: error: expected expression before ‘==’ token
test_alarm.c:110: error: expected expression before ‘==’ token
test_alarm.c:111: error: expected expression before ‘==’ token
test_alarm.c:112: error: expected expression before ‘==’ token
test_alarm.c:113: error: expected expression before ‘==’ token
test_alarm.c:114: error: expected expression before ‘==’ token
test_alarm.c:115: error: expected expression before ‘==’ token
test_alarm.c:124: error: expected expression before ‘==’ token
test_alarm.c:125: error: expected expression before ‘==’ token
test_alarm.c:126: error: expected expression before ‘==’ token
test_alarm.c:127: error: expected expression before ‘==’ token
test_alarm.c:128: error: expected expression before ‘==’ token
test_alarm.c:129: error: expected expression before ‘==’ token
test_alarm.c:130: error: expected expression before ‘==’ token
test_alarm.c:131: error: expected expression before ‘==’ token
test_alarm.c:132: error: expected expression before ‘==’ token
test_alarm.c:133: error: expected expression before ‘==’ token
test_alarm.c:134: error: expected expression before ‘==’ token
test_alarm.c:135: error: expected expression before ‘==’ token
test_alarm.c:136: error: expected expression before ‘==’ token
test_alarm.c:137: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_type’:
test_alarm.c:151: error: expected expression before ‘==’ token
test_alarm.c:152: error: expected expression before ‘==’ token
test_alarm.c:155: error: expected expression before ‘==’ token
test_alarm.c:156: error: expected expression before ‘==’ token
test_alarm.c:157: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_notify_type’:
test_alarm.c:171: error: expected expression before ‘==’ token
test_alarm.c:172: error: expected expression before ‘==’ token
test_alarm.c:175: error: expected expression before ‘==’ token
test_alarm.c:176: error: expected expression before ‘==’ token
test_alarm.c:177: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_list’:
test_alarm.c:223: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signal_alarm’:
test_alarm.c:241: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signal_error’:
test_alarm.c:253: error: expected expression before ‘==’ token
test_alarm.c:254: error: expected expression before ‘==’ token
test_alarm.c:255: error: expected expression before ‘==’ token
test_alarm.c:256: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signals’:
test_alarm.c:288: error: expected expression before ‘==’ token
test_alarm.c:298: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_notify’:
test_alarm.c:353: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c: In function ‘test_alarm_timers’:
test_alarm.c:411: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c:414: error: expected expression before ‘==’ token
test_alarm.c:430: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c:433: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_repeat’:
test_alarm.c:461: error: expected expression before ‘==’ token
test_alarm.c:475: error: expected expression before ‘==’ token
test_alarm.c:485: error: expected expression before ‘==’ token
test_alarm.c:490: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_bind’:
test_alarm.c:510: error: expected expression before ‘==’ token
test_alarm.c: In function ‘main’:
test_alarm.c:527: error: expected expression before ‘AlarmFixture’
test_alarm.c:528: error: expected expression before ‘AlarmFixture’
test_alarm.c:529: error: expected expression before ‘AlarmFixture’
test_alarm.c:530: error: expected expression before ‘AlarmFixture’
test_alarm.c:533: error: expected expression before ‘AlarmFixture’
test_alarm.c:534: error: expected expression before ‘AlarmFixture’
test_alarm.c:535: error: expected expression before ‘AlarmFixture’
test_alarm.c:536: error: expected expression before ‘AlarmFixture’
test_alarm.c:537: error: expected expression before ‘AlarmFixture’
make[3]: *** [test_alarm.o] Error 1
make[3]: Leaving directory /home/harv/Downloads/alarm-clock-0.2.1/src/tests' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /home/harv/Downloads/alarm-clock-0.2.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/harv/Downloads/alarm-clock-0.2.1'
make: *** [all] Error 2
In the alarm list of alarm-clock 0.3.0, when I double-click on an alarm, sometimes the time/duration of the alarm changes.
See the following screencast, http://dl.dropbox.com/u/368761/bugreport/alarmclock-bug-dblclickchangestime.ogv , showing that:
ProblemType: Bug
Architecture: i386
Date: Thu Apr 8 12:47:11 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: alarm-clock-applet 0.3.0-1+joh1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic-pae
SourcePackage: alarm-clock
Uname: Linux 2.6.31-21-generic-pae i686
Originally from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587454:
After creating a new alarm of type 'Alarm Clock', the alarm is not enabled. For
a new user, this is not immediately clear (there is no label for the
corresponding check boxes). Thus, I have already created an alarm that should
have gone of some time ago but didn't. Also, there is no option in the creation
dialog to enable the alarm, causing an odd extra action to be needed to set an
alarm; first create, then enable.
Please consider enabling these alarms upon creation.
[Test Case]
[Regression Potential]
There is a slight behavioural change as a result of the change specific to this bug report: Newly created alarms and edited alarms are now automatically enabled by default.
When I put a "&" in the label for an alarm the hint bubble (while the mouse is floating on the applet icon) is empty.
Hi,
Sound playing doesn't stop when changing Notification type from Play sound to Start application.
Here's the steps to reproduce this:
It should stop because the button is now grey and so there is no (at least no easy) way to stop it.
Error output when I try to make version 0.2.1: (I've used apt-get to get all listed dependencies; if you want any particular output please let me know what command to run)
test_alarm.c: In function ‘test_alarm_props’:
test_alarm.c:102: error: expected expression before ‘==’ token
test_alarm.c:103: error: expected expression before ‘==’ token
test_alarm.c:104: error: expected expression before ‘==’ token
test_alarm.c:105: error: expected expression before ‘==’ token
test_alarm.c:106: error: expected expression before ‘==’ token
test_alarm.c:107: error: expected expression before ‘==’ token
test_alarm.c:108: error: expected expression before ‘==’ token
test_alarm.c:109: error: expected expression before ‘==’ token
test_alarm.c:110: error: expected expression before ‘==’ token
test_alarm.c:111: error: expected expression before ‘==’ token
test_alarm.c:112: error: expected expression before ‘==’ token
test_alarm.c:113: error: expected expression before ‘==’ token
test_alarm.c:114: error: expected expression before ‘==’ token
test_alarm.c:115: error: expected expression before ‘==’ token
test_alarm.c:124: error: expected expression before ‘==’ token
test_alarm.c:125: error: expected expression before ‘==’ token
test_alarm.c:126: error: expected expression before ‘==’ token
test_alarm.c:127: error: expected expression before ‘==’ token
test_alarm.c:128: error: expected expression before ‘==’ token
test_alarm.c:129: error: expected expression before ‘==’ token
test_alarm.c:130: error: expected expression before ‘==’ token
test_alarm.c:131: error: expected expression before ‘==’ token
test_alarm.c:132: error: expected expression before ‘==’ token
test_alarm.c:133: error: expected expression before ‘==’ token
test_alarm.c:134: error: expected expression before ‘==’ token
test_alarm.c:135: error: expected expression before ‘==’ token
test_alarm.c:136: error: expected expression before ‘==’ token
test_alarm.c:137: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_type’:
test_alarm.c:151: error: expected expression before ‘==’ token
test_alarm.c:152: error: expected expression before ‘==’ token
test_alarm.c:155: error: expected expression before ‘==’ token
test_alarm.c:156: error: expected expression before ‘==’ token
test_alarm.c:157: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_notify_type’:
test_alarm.c:171: error: expected expression before ‘==’ token
test_alarm.c:172: error: expected expression before ‘==’ token
test_alarm.c:175: error: expected expression before ‘==’ token
test_alarm.c:176: error: expected expression before ‘==’ token
test_alarm.c:177: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_list’:
test_alarm.c:223: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signal_alarm’:
test_alarm.c:241: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signal_error’:
test_alarm.c:253: error: expected expression before ‘==’ token
test_alarm.c:254: error: expected expression before ‘==’ token
test_alarm.c:255: error: expected expression before ‘==’ token
test_alarm.c:256: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_signals’:
test_alarm.c:288: error: expected expression before ‘==’ token
test_alarm.c:298: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_notify’:
test_alarm.c:353: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c: In function ‘test_alarm_timers’:
test_alarm.c:411: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c:414: error: expected expression before ‘==’ token
test_alarm.c:430: warning: passing argument 2 of ‘g_timeout_add’ from incompatible pointer type
test_alarm.c:433: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_repeat’:
test_alarm.c:461: error: expected expression before ‘==’ token
test_alarm.c:475: error: expected expression before ‘==’ token
test_alarm.c:485: error: expected expression before ‘==’ token
test_alarm.c:490: error: expected expression before ‘==’ token
test_alarm.c: In function ‘test_alarm_bind’:
test_alarm.c:510: error: expected expression before ‘==’ token
test_alarm.c: In function ‘main’:
test_alarm.c:527: error: expected expression before ‘AlarmFixture’
test_alarm.c:528: error: expected expression before ‘AlarmFixture’
test_alarm.c:529: error: expected expression before ‘AlarmFixture’
test_alarm.c:530: error: expected expression before ‘AlarmFixture’
test_alarm.c:533: error: expected expression before ‘AlarmFixture’
test_alarm.c:534: error: expected expression before ‘AlarmFixture’
test_alarm.c:535: error: expected expression before ‘AlarmFixture’
test_alarm.c:536: error: expected expression before ‘AlarmFixture’
test_alarm.c:537: error: expected expression before ‘AlarmFixture’
make[3]: *** [test_alarm.o] Error 1
make[3]: Leaving directory /home/harv/Downloads/alarm-clock-0.2.1/src/tests' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /home/harv/Downloads/alarm-clock-0.2.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/harv/Downloads/alarm-clock-0.2.1'
make: *** [all] Error 2
Update Alarm Clock to use GNOME 3 technology: http://developer.gnome.org/Gnome3PortingGuide/
when i try to check the checkbox in Repeat once field in alarm edit, the checkbox for monday, tuesday ... nothing happens i.e.
the checkbox is not checked.
I have a recurring alarm at night to remind me to leave work on time to pick-up my daughter at school (I can be quite involved in my work and forget about the clock...). Anyway, it also happens that I actually watch the clock and turn of my computer a bit before the alarm goes on. In that case, not only the alarm starts the next day when I turn on the computer, but if I turn it off it also cancels the alarm-to-come for that day, which is unexpected.
De-activating the recurring alarm and re-activating it right away allows to get everything back to normal, but this is a bit annoying...
using revision 121.
$ make test
TEST: test_alarm... (pid=7606)
/alarm/type: OK
/alarm/nofity_type: OK
/alarm/list: ** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: alarm_dispose (0x805c820)
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: alarm_dispose (0x805c880)
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: alarm_dispose (0x805c8e0)
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: alarm_dispose (0x805c940)
** (test_alarm:7606): DEBUG: alarm_get_list: found VALID /apps/alarm-clock/alarm8 #8
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: ref = 1
** (test_alarm:7606): DEBUG: append ref = 1
** (test_alarm:7606): DEBUG: alarm_get_list: found VALID /apps/alarm-clock/alarm123 #123
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: ref = 1
** (test_alarm:7606): DEBUG: append ref = 1
** (test_alarm:7606): DEBUG: alarm_get_list: found VALID /apps/alarm-clock/alarm0 #0
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: ref = 1
** (test_alarm:7606): DEBUG: append ref = 1
** (test_alarm:7606): DEBUG: alarm_get_list: found VALID /apps/alarm-clock/alarm3 #3
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: ref = 1
** (test_alarm:7606): DEBUG: append ref = 1
** (test_alarm:7606): DEBUG: alarm_get_list: found VALID /apps/alarm-clock/alarm5 #5
** (test_alarm:7606): DEBUG: set_property gconf-dir
** (test_alarm:7606): DEBUG: set_property id
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: set_property active
** (test_alarm:7606): DEBUG: ref = 1
** (test_alarm:7606): DEBUG: append ref = 1
** ERROR:test_alarm.c:223:test_alarm_list: assertion failed (a->id == eq): (0 == 3)
FAIL
GTester: last random seed: R02Seb743778ee4548fdc82251eed3795260
/bin/sh: line 1: 7659 Terminated gtester --verbose test_alarm test_player test_list_entry test_util test_alarm glade_view test_gconf_recursive
make: *** [test] Error 143
btw, this file doesn't exist on my system: file:///usr/share/sounds/generic.wav
$ gdb alarm-clock-applet
GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /home/yoan/soft/alarm-clock/src/alarm-clock-applet
[Thread debugging using libthread_db enabled]
[New Thread 0xb6cc76d0 (LWP 7664)]
Program exited with code 01.
(gdb) bt
No stack
Regards,
Originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=615699
architecture: i686
Attached file: backtrace
cmdline: alarm-clock-applet
comment: Produce every time that I do it.
component: gnome-applet-alarm-clock
crash_function: raise
executable: /usr/bin/alarm-clock-applet
global_uuid: 56c5c6b2a18bcab58c465dbef4803dcc98c5d39b
kernel: 2.6.32.16-141.fc12.i686.PAE
package: gnome-applet-alarm-clock-0.3.1-1.fc12
rating: 4
reason: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
1.Open the applet
2.Right click the applet then select Preference
3.Check the box of "Start automatically at login"
And here is a dump that I got running the applet in command line with the same
actions as above.
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart get_state for file (nil)
** (alarm-clock-applet:2125): DEBUG: AlarmAction: toggle autostart to 1
** (alarm-clock-applet:2125): DEBUG: AlarmAction: set autostart to 1!
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart get_state for file (nil)
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart ENABLE!
** (alarm-clock-applet:2125): WARNING **: Preferences: Could not copy '/usr/share/applications/alarm-clock-applet.desktop' to user config dir: Error opening file '/home/chanueting/.config/autostart/alarm-clock-applet.desktop': No such file or directory
(alarm-clock-applet:2125): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: No such file or directory
** (alarm-clock-applet:2125): WARNING **: Preferences: Error when enabling autostart-file '/home/chanueting/.config/autostart/alarm-clock-applet.desktop': \xf0\xc5\u0008 \xb0SI
Segmentation fault (core dumped)
I have installed the alarm clock applet on two hardy machines. On the first one the applet is working fine - on the other one I do not get the notification bubble and some icons are missing. What can be the problem? Perhaps wrong GNOME theme (human-clearlooks)? Is there a possibility to get a log from a GNOME applet?
i am unable to unable to set the alarm beyond 13:49:49.
if i type anything more than 13 in hrs and 49 in min and seconds, as soon as i press enter the time automatically is set as 13 in hrs and 49 in min and sec.
i am using 0.2.4 on jaunty fully updated as on 24th Feb.
i am adding the screenshot....
Alarm Clock uses the now deprecated gnome-vfs to handle files and mime-types/icons. We should move this to the replacement library gio.
We only use GnomeVFS for loading the stock sounds with mime-types and icons.
Binary package hint: alarm-clock-applet
Package version: 0.2.6-1
Release: Ubuntu 9.10
What happens:
When I set up and start a timer, the clock on the applet appears frozen even thought the countdown is in progress, e.g. if I started a 6-minute timer, the panel applet if frozen at 00:06:00.
When I place the mouse cursor over the applet, the tooltip shows the countdown in parenthesis.
What I expected to happen:
If there is a timer countdown going on, it should be reflected on the applet.
Alarm Clock uses the now deprecated libgnomeui. This dependency should be removed.
We only use libgnomeui for handling icons through the gnome_icon_lookup() function.
Alarm Clock uses the now deprecated gnome-vfs to handle files and mime-types/icons. We should move this to the replacement library gio.
We only use GnomeVFS for loading the stock sounds with mime-types and icons.
say you have alarms in the alarms window. be them timers or alarm clock.
and activated with countdown running.
if you delete them with the shred icon, they disapear from the alarm window so you can think there is no more any alarm running.
this is wrong. because they all continue to run (countdown to ...) and will ring at the specified time.
Is this a bug or a feature ?
the bug is that you can't stop the first alarm that will ring because you can't stop it from the alarm window because it is not there anymore.
and even the stop all alarmsin the systray icon does n't the ringing alarm.
so you have to close alarm-clock-applet to stop this alarm
is this yet another invalid bug ? ;-)
Alarm Clock's gconf settings should be moved out of the applet gconf directory and into /apps/alarm-clock
The display preferences which affect the applet only should still be stored on a per-applet settings, as you might want different display settings on multiple applet instances.
See blueprint @ https://blueprints.launchpad.net/alarm-clock/+spec/global-gconf-settings
Update Alarm Clock to use GNOME 3 technology: http://developer.gnome.org/Gnome3PortingGuide/
I have five different alarms set for various days/times to reflect my class schedule, and after the alarm went off for this morning, I cleared it, and it should have started counting down to the "end of class" alarm for this evening, but it started counting to the next alarm in the group for this morning (i.e. 10:00 AM two days from now).
Sometimes I come back to my computer after leaving it for a bit to find the Alarm Clock icon flashing. Naturally I left-click on it to see what I missed, except that doing this snoozes all the alarms I missed. I'd prefer left-clicking to bring up the list to show me what I missed - I generally expect left-clicking an active icon to show me what it's blinking/active about, not perform an action.
Other people may work differently, so maybe this could be a Preference setting? "When alarm icon is active clicking it a. snoozes alarm b. shows alarm list."
Thanks for a great app!
Alarm Clock should configure itself as an application indicator, if installed and running. Ubuntu lucid+1 plans to drop support for the notification-area, and the app-indicator helps with the overall panel consistency.
See https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators
When you snooze an alarm, say in the evening, and shutdown your computer. then boot in the morning, the snoozed alarm will kick in, nonetheless almost 8 hours have past.
when i try to check the checkbox in Repeat once field in alarm edit, the checkbox for monday, tuesday ... nothing happens i.e.
the checkbox is not checked.
When an alarm is set before a daylight savings time change to a
time after the time change, the alarm will go off at a time one hour off.
I'd suspect it checks how long it is until the next alarm and sleeps (sets an alarm) in that many seconds. And when the time left changes in the middle of it the original calculation will be wrong.
If I set the sound_repeat option of an alarm, when the alarms triggers the sound is just played once.
Furthemore, when creating the alarm, if a press the play button while having checked the repeat sound checkbox, the
sound just plays once.
This used to work in 11.10
I've tried to obtain a debug log, but it seems that this is not possible now. Starting alarm-clock-applet from
shell yields zero output.
[Test Case]
[Regression potential]
I don't see any.
Currently, the positioning of the alarms list window is left to the window manager.
This is annoying if you like to have it set to a specific place (for example, I'd like it to stay near my notification icon so that, after clicking the notification icon, I have less mouse distance to travel from the icon to the alarm list)
If, for some reason (monitor setup change, resolution change) the remembered position doesn't exist in the current setup, it should be brought back to something sane like (30,30).
[Test Case]
[Regression potential]
Unlikely.
For some reason, the MediaPlayer randomly emits critical messages when playing. This seems only to happen when in loop mode.
src/tests$ ./test_player file:///usr/share/sounds/gnome/default/alerts/drip.ogg
** (:8283): DEBUG: State changed to PLAYING [2], data is 'test data'
(:8283): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
(:8283): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
(:8283): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed
Backtrace with G_DEBUG=fatal_warnings:
GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
aborting...
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb64fdb70 (LWP 8412)]
0x0096b422 in __kernel_vsyscall ()
(gdb) bt
#0 0x0096b422 in __kernel_vsyscall ()
#1 0x005544d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0x00557932 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0x00153046 in g_logv () from /lib/libglib-2.0.so.0
#4 0x00153076 in g_log () from /lib/libglib-2.0.so.0
#5 0x001532db in g_return_if_fail_warning () from /lib/libglib-2.0.so.0
#6 0x0036535b in g_object_ref () from /usr/lib/libgobject-2.0.so.0
#7 0x00367668 in ?? () from /usr/lib/libgobject-2.0.so.0
#8 0x004dbff3 in gst_structure_id_set_valist () from /usr/lib/libgstreamer-0.10.so.0
#9 0x004dc133 in gst_structure_id_new () from /usr/lib/libgstreamer-0.10.so.0
#10 0x004b8200 in gst_message_new_stream_status () from /usr/lib/libgstreamer-0.10.so.0
#11 0x006f802a in ?? () from /usr/lib/gstreamer-0.10/libgstpulse.so
#12 0x0074062f in ?? () from /usr/lib/libpulse.so.0
#13 0x007437b6 in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
#14 0x00743c31 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#15 0x00743cf4 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#16 0x00754bc3 in ?? () from /usr/lib/libpulse.so.0
#17 0x007a1ac2 in ?? () from /usr/lib/libpulsecommon-0.9.19.so
#18 0x001cc80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#19 0x005f67ee in clone () from /lib/tls/i686/cmov/libc.so.6
This might be a GStreamer or pulseaudio bug...
When I use "Stop all alarms" from the notification area icon's menu, the main interface of the application doesn't show that the alarm has actually stopped. Then, when selecting an alarm and clicking "Stop" in the main UI, the tray icon begins to blink. Using "Stop all alarms" again finally causes the tray icon to cease blinking. Interestingly, this only occurs when "Repeat Sound" is unchecked in the alarm- or timer-specific options.
Steps to reproduce:
Kill and restart applet.
Create a timer named "test2", with a delay of 5 seconds, playing the sound sonar.ogg, and uncheck "repeat sound".
Start the timer from the main UI.
Wait 5 seconds.
Right-click the notification icon, and select "Stop all alarms".
Observe that while the icon stops blinking, the alarm "test2" is still enabled and blinking in the main UI.
Disable "test2" by selecting it and using the Stop button.
Observe that the notification icon begins blinking again.
Finally, access the "Stop all alarms" notification icon menu function again to stop the tray icon blinking.
Repeat the process with "Repeat Sound" enabled in the timer or alarm's options dialog, and observe the bug does not occur.
Debug output from the applet is attached.
Alarm Clock should configure itself as an application indicator, if installed and running. Ubuntu lucid+1 plans to drop support for the notification-area, and the app-indicator helps with the overall panel consistency.
See https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators
Alarm Clock's gconf settings should be moved out of the applet gconf directory and into /apps/alarm-clock
The display preferences which affect the applet only should still be stored on a per-applet settings, as you might want different display settings on multiple applet instances.
See blueprint @ https://blueprints.launchpad.net/alarm-clock/+spec/global-gconf-settings
i am unable to unable to set the alarm beyond 13:49:49.
if i type anything more than 13 in hrs and 49 in min and seconds, as soon as i press enter the time automatically is set as 13 in hrs and 49 in min and sec.
i am using 0.2.4 on jaunty fully updated as on 24th Feb.
i am adding the screenshot....
Please sort the alarm list on alarm time. This makes it easy to manage daily alarms.
Originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=615699
architecture: i686
Attached file: backtrace
cmdline: alarm-clock-applet
comment: Produce every time that I do it.
component: gnome-applet-alarm-clock
crash_function: raise
executable: /usr/bin/alarm-clock-applet
global_uuid: 56c5c6b2a18bcab58c465dbef4803dcc98c5d39b
kernel: 2.6.32.16-141.fc12.i686.PAE
package: gnome-applet-alarm-clock-0.3.1-1.fc12
rating: 4
reason: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
1.Open the applet
2.Right click the applet then select Preference
3.Check the box of "Start automatically at login"
And here is a dump that I got running the applet in command line with the same
actions as above.
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart get_state for file (nil)
** (alarm-clock-applet:2125): DEBUG: AlarmAction: toggle autostart to 1
** (alarm-clock-applet:2125): DEBUG: AlarmAction: set autostart to 1!
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart get_state for file (nil)
** (alarm-clock-applet:2125): DEBUG: Preferences: Autostart ENABLE!
** (alarm-clock-applet:2125): WARNING **: Preferences: Could not copy '/usr/share/applications/alarm-clock-applet.desktop' to user config dir: Error opening file '/home/chanueting/.config/autostart/alarm-clock-applet.desktop': No such file or directory
(alarm-clock-applet:2125): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: No such file or directory
** (alarm-clock-applet:2125): WARNING **: Preferences: Error when enabling autostart-file '/home/chanueting/.config/autostart/alarm-clock-applet.desktop': \xf0\xc5\u0008 \xb0SI
Segmentation fault (core dumped)
In the alarm list of alarm-clock 0.3.0, when I double-click on an alarm, sometimes the time/duration of the alarm changes.
See the following screencast, http://dl.dropbox.com/u/368761/bugreport/alarmclock-bug-dblclickchangestime.ogv , showing that:
ProblemType: Bug
Architecture: i386
Date: Thu Apr 8 12:47:11 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: alarm-clock-applet 0.3.0-1+joh1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic-pae
SourcePackage: alarm-clock
Uname: Linux 2.6.31-21-generic-pae i686
It made sense for 0.2.x versions to start hidden because it was a panel applet: once added to the GNOME panel, it started automatically, and when you needed to activate an alarm, you had to click the applet icon.
Now, with 0.3.x being a standalone application, it no longer makes sense to start hidden. Starting the application is a declaration of intent from the user: "I want to set up an alarm clock, and for this I want to see my alarms list". Why forcing him to do the additional step of double-clicking the notification icon to reveal the alarm list?
The alarms list window shouldn't be minimized when Alarm Clock is launched, it should be put to front.
I have installed the alarm clock applet on two hardy machines. On the first one the applet is working fine - on the other one I do not get the notification bubble and some icons are missing. What can be the problem? Perhaps wrong GNOME theme (human-clearlooks)? Is there a possibility to get a log from a GNOME applet?
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: - 1...
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: alarm() DING!
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: alarm() Repeating...
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: update_timestamp_full: 23:0:0
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: set_timestamp (23, 0, 0, 0)
** (alarm-clock-applet:13079): DEBUG: Closest WDAY = 3
** (alarm-clock-applet:13079): DEBUG: Alarm is in 1 days.
** (alarm-clock-applet:13079): DEBUG: Alarm will trigger at Ter 10 Ago 2011 23:00:00 WEST
** (alarm-clock-applet:13079): DEBUG: Setting to 1313013600
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: set timestamp=1313013600
** (alarm-clock-applet:13079): DEBUG: AlarmApplet: Alarm 'Alarm!' timestamp changed
** (alarm-clock-applet:13079): DEBUG: AlarmListWindow alarm_update: 0x6e71b0 (Alarm!)
** (alarm-clock-applet:13079): DEBUG: Alarm(0x6e71b0) #1: alarm() Start player
** (alarm-clock-applet:13079): CRITICAL **: Could not create player.
Program received signal SIGSEGV, Segmentation fault.
0x0000000000409fde in media_player_start ()
(gdb) bt
#0 0x0000000000409fde in media_player_start ()
#1 0x000000000040c38c in ?? ()
#2 0x00007ffff6f5f1fe in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0x00007ffff6f6f815 in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff6f797aa in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff6f79952 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#6 0x000000000040b7ba in ?? ()
#7 0x00007ffff7b36b9b in ?? () from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff7b3529d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff7b35a78 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff7b360ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff75f81a7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x0000000000409072 in main ()
(gdb)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.