@Scott Kitterman
The bug was, as far as I could tell in alarm-clock, not some other package. which is why I changed the status. And if you'll look at the <http://www.alarm-clock.pl/> webpage, you'll see that a new version has been released which fixes this bug. So it was in fact a bug in alarm-clock.
Back on topic. I can confirm that version 0.9.19 fixes this bug. After installing, I did have to move the glade and scalable folders from /usr/local/share/alarm-clock/ to /usr/share/alarm-clock/ so that AlarmClock could find them.
@Scott Kitterman www.alarm- clock.pl/> webpage, you'll see that a new version has been released which fixes this bug. So it was in fact a bug in alarm-clock.
The bug was, as far as I could tell in alarm-clock, not some other package. which is why I changed the status. And if you'll look at the <http://
Back on topic. I can confirm that version 0.9.19 fixes this bug. After installing, I did have to move the glade and scalable folders from /usr/local/ share/alarm- clock/ to /usr/share/ alarm-clock/ so that AlarmClock could find them.