Package Details: alarm-clock-applet 1.0.1-5

Git Clone URL: (read-only, click to copy)
Package Base: alarm-clock-applet
Description: A fully-featured alarm clock for GTK panel
Upstream URL:
Keywords: alarm applet clock desktops for gtk
Licenses: GPL2
Submitter: gwash
Maintainer: linuxergr
Last Packager: linuxergr
Votes: 102
Popularity: 0.088301
First Submitted: 2008-08-23 19:27 (UTC)
Last Updated: 2020-12-16 11:55 (UTC)

Latest Comments

LeSnake commented on 2021-07-27 13:07 (UTC)

Fixed libunique, now it should work

LeSnake commented on 2021-07-26 18:03 (UTC)

Just realised what went wrong. Gonna fix it asap (currently traveling, give me 1-3 days)

linuxergr commented on 2021-07-26 14:49 (UTC) (edited on 2021-07-26 14:55 (UTC) by linuxergr)

Add the libunique from the repo indicated below, there is no need to build it from AUR.

If the problem still persists, let me know.

mrpg commented on 2021-07-26 12:46 (UTC)

This is completely broken due to an error in libunique's pkgrel. In fact, /var/lib/pacman/local/libunique-1.1.6-9/files does not contain anything (ls /usr/lib/libunique* doesn't find anything either). That's why alarm-clock-applet doesn't build. More info here:

Build libunique manually and install the pkgrel 8 one, which is strangely also built. Then everything works.

LeSnake commented on 2021-07-21 22:11 (UTC)

added libunique back to aur linking from artixlinux archive, but build cannot find it for some reason

linuxergr commented on 2021-04-12 10:44 (UTC)

Download and install libunique from

LeSnake commented on 2021-04-12 08:26 (UTC) (edited on 2021-04-12 08:31 (UTC) by LeSnake)

libunique was removed from AUR :/ There is a libunique3 but also the code wants libunique, so just fixing the pkgbuild doesnt work

linuxergr commented on 2020-12-16 11:49 (UTC) (edited on 2020-12-16 12:10 (UTC) by linuxergr)

Hi @mrpg,

Added as an optional dependency, because not all users use those sounds.


mrpg commented on 2020-12-16 08:32 (UTC)

I figured it out. gnome-control-center provides the sounds and should be added as a (maybe optional) dependency.

mrpg commented on 2020-12-16 08:24 (UTC)

Thanks for this wonderful application!

One quick question though: After I reinstalled my system, I no longer have access to the sounds (such as the bark, etc.). Which package provides these sounds, and could this package be added as a dependency? Thanks.

linuxergr commented on 2020-11-22 13:59 (UTC)

@irvineHimselh, thanks for the detailed explanation.

I use namcap as a linter for my PKGBUILDs, and such an issue was never reported from it.

In any case, and ever since is not hard for me to shift it from /usr/local to /usr, I provide an updated PKGBUILD

But, in any case namcap should provide that info, if it is a strict line, otherwise is considered as a soft one.


IrvineHimself commented on 2020-11-22 13:17 (UTC) (edited on 2020-11-22 13:50 (UTC) by IrvineHimself)

I think what people are trying to say is that:

1) /usr        ->   all resources managed by pacman

2) /usr/local  ->   all resources *not* managed by pacman

For example, an overview of the contents of my /usr/local dir:

a) /usr/local/bin             ->  symlinks to my own executables and scripts in /usr/local/lib

b) /usr/local/bin/FjSymlinks  ->  symlinks to automatically enable firejail

c) /usr/local/lib             ->  folders containing my own executables

d) /usr/local/share           ->  shared non-executable resources, eg wallpapers, icons, audio alarms... etc

The reason for this arrangement is because it is more secure than keeping these resources in my ${HOME} dir, and makes for easy maintenance.

To the best of my knowledge, this is the intended use of /usr/local, and, as such, installing externally maintained packages here seriously screws up the structure.

A point to note is that, if I was to publish my own executables and was careless with the pre-publication clean up, then the package would point to /usr/local :)

Hope this helps


EDIT: A further point to note is that, since /usr/local/bin is the first item in the ${PATH}, it is fairly easy to intercept a call to a pacman maintained binary. This is not the case if said binary is not installed to /usr/bin.

linuxergr commented on 2020-11-22 10:59 (UTC)

What is the difference between manual build and my PKGBUILD? No need to change it.

kyechou commented on 2020-11-22 07:29 (UTC) (edited on 2020-11-22 07:45 (UTC) by kyechou)

Also, I don't think /usr/local is any safer than /usr if all packages are managed by pacman. Please correct me if I misunderstood.

kyechou commented on 2020-11-22 07:25 (UTC)

I think for Arch, /usr/local is supposed to be used for manually-built applications, as indicated in the link provided by @mojo-hakase, and /usr for pacman-managed packages.

linuxergr commented on 2020-11-22 01:02 (UTC)

Why it should not?

/usr/local is safer than /usr and is the default of alarm-clock-applet installation

check the build() function which is the default one.

mojo-hakase commented on 2020-11-21 23:15 (UTC)

The package installs all files under /usr/local which it shouldn't. The call to configure should be changed to ./configure --prefix=/usr

linuxergr commented on 2020-09-19 21:27 (UTC)

The project is been officially forked and so it is going to be maintained by me, as also the PKGBUILD.

Note that the build has been corrected alone with the code.

I wish that this very nice applet, will keep on existing, as already works with libindicator-gtk3, in our Linux Desktops

Jakeukalane commented on 2020-06-04 02:51 (UTC) (edited on 2020-06-04 02:51 (UTC) by Jakeukalane)

I have the same error as vishnu.

vishnu commented on 2020-05-21 13:35 (UTC)

Getting these errors

/usr/bin/ld: alarm-gconf.o:(.bss+0x0): multiple definition of app_command_map'; alarm-applet.o:(.bss+0x0): first defined here /usr/bin/ld: ui.o:(.bss+0x0): multiple definition ofapp_command_map'; alarm-applet.o:(.bss+0x0): first defined here /usr/bin/ld: alarm-actions.o:(.bss+0x0): multiple definition of app_command_map'; alarm-applet.o:(.bss+0x0): first defined here /usr/bin/ld: alarm-list-window.o:(.bss+0x0): multiple definition ofapp_command_map'; alarm-applet.o:(.bss+0x0): first defined here /usr/bin/ld: alarm-settings.o:(.bss+0x0): multiple definition of app_command_map'; alarm-applet.o:(.bss+0x0): first defined here /usr/bin/ld: prefs.o:(.bss+0x10): multiple definition ofapp_command_map'; alarm-applet.o:(.bss+0x0): first defined here

JohnRobson commented on 2017-09-26 03:18 (UTC)

@danscava Thank you very much '--enable-compile-warnings=no' works! This is the best Alarm for Linux

JohnRobson commented on 2017-09-17 19:43 (UTC)

CC alarm-actions.o util.c: In function ‘get_alarm_timestamp’: util.c:57:31: error: ‘%c’ yields only last 2 digits of year in some locales [-Werror=format-y2k] strftime (tmp, sizeof (tmp), "%c", tm); ^~~~ cc1: some warnings being treated as errors make[3]: *** [Makefile:474: util.o] Error 1

fennectech commented on 2017-06-02 08:58 (UTC)

util.c: In function ‘get_alarm_timestamp’: util.c:57:31: error: ‘%c’ yields only last 2 digits of year in some locales [-Werror=format-y2k] strftime (tmp, sizeof (tmp), "%c", tm); ^~~~

danscava commented on 2016-05-28 06:21 (UTC)

To get rid of the -Werror=format-y2k. Just edit the PKGBUILD and put "--enable-compile-warnings=no" at the end of the ./configure line on build()

thetotalchaos commented on 2016-05-19 23:38 (UTC)

The installation failed ;-( ... In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-applet.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^~~~~~~ CC player.o CC util.o util.c: In function ‘get_alarm_timestamp’: util.c:57:31: error: ‘%c’ yields only last 2 digits of year in some locales [-Werror=format-y2k] strftime (tmp, sizeof (tmp), "%c", tm); ^~~~ cc1: some warnings being treated as errors Makefile:474: recipe for target 'util.o' failed make[3]: *** [util.o] Error 1 make[3]: Leaving directory '/tmp/yaourt-tmp-biser/aur-alarm-clock-applet/src/alarm-clock-applet-0.3.4/src' Makefile:494: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/yaourt-tmp-biser/aur-alarm-clock-applet/src/alarm-clock-applet-0.3.4/src' Makefile:411: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-biser/aur-alarm-clock-applet/src/alarm-clock-applet-0.3.4' Makefile:350: recipe for target 'all' failed make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Jesse2004 commented on 2015-09-10 06:48 (UTC)

Installing gst-plugins-good solves the problem. Might be a good candidate for optdepends?

Jesse2004 commented on 2015-09-10 06:17 (UTC)

I'm trying to use this package in mate desktop. It works except no sound. Running in terminal gives the following errors: ** (alarm-clock-applet:19532): WARNING **: AlarmApplet: Could not locate sounds! ** (alarm-clock-applet:19532): WARNING **: AlarmApplet: Could not locate sounds! ** (alarm-clock-applet:19532): CRITICAL **: Could not create player. ** (alarm-clock-applet:19532): CRITICAL **: Alarm(0x1a0ccf0) #0: alarm_error: #1: Could not create player! Please check your sound settings. Maybe some dependencies are missing?

ckafi commented on 2014-02-19 23:00 (UTC)

I've recently adopted this package and have rewritten some parts of the PKGBUILD. As I don't like making silent changes, I've bumped the release number to 2.

prestomadcat commented on 2014-02-19 22:35 (UTC)

Why has this been recently changed to 0.3.3-2? The last revision I can see is 227 made on 2013-03-11

snoxu commented on 2012-06-03 21:34 (UTC)

0.3.3 is out

habtool commented on 2011-03-17 16:47 (UTC)

Hi @ alessandro_ufms I have installed the new version, all is great again, thanks for your prompt help! Stay Well

commented on 2011-03-17 14:13 (UTC)

@habtool: fixed this issue

habtool commented on 2011-03-17 11:29 (UTC)

There seems to be a issue with libnotiy: The missing /usr/bin/ is the issue here I will update here if I see a solution on the thread

habtool commented on 2011-03-17 08:48 (UTC)

It appears that a update to dependency has broken alarm-clock-applet. I think it may be libnotify If I run from a terminal: $ alarm-clock-applet alarm-clock-applet: error while loading shared libraries: cannot open shared object file: No such file or directory If I try to reinstall alarm-clock-applet with yaourt/clyde I get this near the end: alarm-applet.h:46:14: warning: array ‘supported_sound_mime_types’ assumed to have one element CCLD alarm-clock-applet ui.o: In function `alarm_applet_notification_show': ui.c:(.text+0x51d): undefined reference to `notify_notification_new_with_status_icon' collect2: ld returned 1 exit status make[3]: *** [alarm-clock-applet] Error 1

dkorzhevin commented on 2010-09-27 13:27 (UTC)

Very good remind program for GNOME!