James Tyrer posted on Sat, 31 Dec 2011 19:27:05 -0700 as excerpted: > When I start KAlarm, I get 3 error messages [see attached] for: > > template.ics expired.ics calendar.ics > > I tried following the instructions and the result is that the 2 alarms > are now in the KOrganizer calender. I found another small bug. A > reminder with length 0 at 12:00 AM is not visible in the: "Agenda". > > I tried resetting KAlarm by deleting: > > .../share/apps/kalarm .../share/config/kalarmrc > > Didn't work. So, the files no longer exist but the error messages still > persist. > > Tried making empty files. I still get the three error messages. > > Current status is that I am not able to create new alarms in KAlarm. > > KAlarm doesn't work. This appears to be a REGRESSION. Why isn't it a > show stopper?
kalarm is part of kdepim, meaning it's probably akonadi-based problems you're seeing (that dialog indicates a problem with the akonadi upgrade resource conversion process, as well). Based on my own experience with the akonadi based kdepim reliability downgrade masquerading as an upgrade (tho here I don't use kalarm/korganizer and it was akonadified kmail/ kaddressbook that I finally got fed up with), I'd recommend you find another solution and uninstall anything kdepim or akonadi related. Alternatively I'd suggest deleting that akonadi resource and recreating it. Hopefully new scheduled alarms work without issue, but the unreliability of the new akonadi database-backed services are why I recommend finding a different solution, thus relieving yourself of this headache entirely, and if you choose to stay with it, I'd caution you to expect unreliability and service interruptions until it's stable, which I don't expect until late 4.8 at the earliest, more likely 4.10 or never. Yet another alternative if you're going to try to keep akonadi is to try a different akonadi backend. Originally the mysql backend was the only one far enough developed and thus the default, but AFAIK, the sqlite backend is the newer default. However, existing user configurations will remain on the old one unless specifically changed, so unless you switched, you're probably still on mysql, which might be fine for dedicated-admin database-server applications where the admin expects to spend time tuning and tweaking, but wasn't designed for and isn't well suited to simple user usage scenarios, where it often produces problems that users are ill-equipped to handle. But I really do recommend switching to something else, preferably something without the database-managed complexity of akonadi and thus the new akonadi-based kdepim. Honestly, your data will probably be safer and thus your life far less stressful as a result. =:^0 Mine surely is! =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___________________________________________________ This message is from the kde-linux mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde-linux. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
