Red Hat Bugzilla – Bug 469228
Korganizer Reminder Daemon crashes on boot and cannot be started
Last modified: 2009-01-08 01:10:26 EST
Description of problem:
When the system boots, a message appears, after login, that the korganizer reminder daemon has crashed.
Version-Release number of selected component (if applicable):
Log in and the daemon will crash.
Steps to Reproduce:
2.Message appears stating daeom crashed
Daemon crashes and it is impossible to start it by manually opening korganizer. It never appears in the system tray and reminders don't remind any longer, as they did a couple of days ago.
Can you please install kdepim-debuginfo and kdepimlibs-debuginfo and gdb and obtain a stack trace? (If the daemon doesn't use KCrash, please run it in gdb to get the backtrace.)
And if possible, attach your korganizer file(s) in use here (can send privately if you prefer).
I am installing the required 150MB of debug rpms presently. Upon reboot, I should, hopefully be able to obtain a "stack trace". And Rex, which korganizer files are you referring to?
Created attachment 322147 [details]
This is the backtrace.
I'm just going to send that for now, as the std.ics has all of my personal information in it. I would have to do extensive editing before I could send it.
Hmmm, that's deep in KCal code, looks like fallout from the system libical patch. :-(
I guess we should revert it for F10.
Can you please try downgrading to kdepimlibs-4.1.2-2.fc10 from:
(using rpm -Uvh --oldpackage) and tell us if that fixes it?
Shall do tout de suite! Then reboot. Be right back.
kdepimlibs-4.1.2-2.fc10.i386 solved it! Upon login, the reminders of the day appeared, the reminder daemon docked into the systray, and all appears normal once again.
Now I can stop worrying about forgetting one of those birthdays that would be embarassing to forget. Thanks!
So I'm now building a 4.1.2-4.fc10 with the change from 4.1.2-3.fc10 (use of the system libical) reverted. That change will need more bugfixing and we don't have the time for f10-final.
You can try 4.1.2-4.fc10 to be sure:
but it should be essentially identical to 4.1.2-2.fc10.
I updated and rebooted. Daemon is in tray (no reminders triggered at boot, but there aren't any right now) and no crash message. Looks good.
This has been tagged f10-final long ago.
We still need to fix the underlying libical bug, but at least we have a non-crashing KOrganizer now (even if it uses a private libical). ;-)
*** Bug 471744 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=450659#c11 claims there's a fix for it now. We may want to snatch that fix and reenable system libical.
From the upstream report:
--- Comment #9 from Will Stephenson 2008-12-02 16:51:32 ---
FYI, fixed by backporting r879190 - don't crash when timezone info is NULL.
FYI, the fix for this has already been backported to 4.1:
So we can enable the system libical in the 4.1.4 update.