Version: 1.0.8 (using KDE Devel) Installed from: Compiled sources OS: Linux After installation of kalarm, to the Sharp Zaurus, at various points, the clock time is reset to a few hours ahead of actual time. This bug prevents the alarm from activating at the appropriate time. Also no audio alarm sounds. The only action that happens is the screen activates if previously off. I am not sure as to its intention but it needs to sound the alarm or at the very least flash one the lights (preferably both audio and visual alarms) to be considered an alarm.
I have the same problem with my Sharp ROM SL5500. The events are as follows: 1) Change/add an event with alarm 2) Alarm Daemon reloads the "mycalendar.ics" file. 3) The displayed clock time in the bottom-right corner switches to UTC time. 4) The "date" command reports the correct time in CST. 5) The "date -u" command reports the UTC time which is now showing in the bottom-right corner. I've been tinkering with the "config_korganizerrc" file by adding "QString,Time & Date/TimeZoneId,US/Central" . But, no luck yet.
I copied and renamed "/usr/bin/zoneinfo/america/San_Antonio" to "/etc/localtime" because of the following code. KOrganizer no longer sets my time to UTC. The Alarm Daemon sill does not wake up the Zaurus or beep. The alarms do pop-up when I turn the Zaurus on. void KOPrefs::setTimeZoneIdDefault() { QString zone; char zonefilebuf[100]; int len = readlink("/etc/localtime",zonefilebuf,100); if (len > 0 && len < 100) { zonefilebuf[len] = '\0'; zone = zonefilebuf; zone = zone.mid(zone.find("zoneinfo/") + 9); } else { tzset(); zone = tzname[0]; } kdDebug () << "----- time zone: " << zone << endl; mTimeZoneId = zone; }
Fixed in KO/Pi 1.6.1. Get KO/Pi at www.pi-sync.net