(I'm fully aware what cssu-devel means, and yes, once in a while i upgrade some of my packages from there. That was not my point, however, i expected some things to break one day. And i won't say it's in a messy state; neither have i changed any system scripts, nor messed with "manually" optifying, nor something else, thank you.)

What is instead my concern, could someone explain this (now even more convoluted) alarm behavior that Maemo is presenting us with? For a while now, several users were reporting silent alarms, and AFAIK we still haven't found the real reason behind. (@freeman?) That's why i documented my findings here; so that maybe the puzzle got some more pieces to link. My silent alarm issue too started way before i touched cssu-devel, just for the record; the symptoms just got more presence during this week.

So, what are the system's dependencies for
- creating / storing
- scheduling
- triggering
alarms, _with_ audio output? What libs / packages are related? How the "pipeline" (in absence of better describing terms) looks like? What are points of failure?

All my findings from this week don't convince me that other than by chance for a long time, how those bits are integrated in the system can considered being stable.