Hi everybody,
Some component of my "Alarms" functionality seems to have been hosed in the last major update: every time I try to access the Alarm Settings dialog, the entire Alarm/Clock application quits, with the delightfully vague complaint that there was some sort of "Internal Error." I'm hoping this is just a simple matter of a corrupt config file (since the alarms still work - I just can't configure them). Consequently, I'm wondering if anyone knows where the clock/alarm application stores its config files, and how I might restore them to factory defaults. Alternatively, if anyone can think of an alternative approach to fixing this problem (short of reflashing), I'd love to hear it.
Thanks!
Hi everybody,
Some component of my "Alarms" functionality seems to have been hosed in the last major update: every time I try to access the Alarm Settings dialog, the entire Alarm/Clock application quits, with the delightfully vague complaint that there was some sort of "Internal Error." I'm hoping this is just a simple matter of a corrupt config file (since the alarms still work - I just can't configure them). Consequently, I'm wondering if anyone knows where the clock/alarm application stores its config files, and how I might restore them to factory defaults. Alternatively, if anyone can think of an alternative approach to fixing this problem (short of reflashing), I'd love to hear it.
Thanks!
One config file is:
/var/cache/alarmd/alarm_queue.ini
