Bug 176566 - KOrganizer aborts on startup of KDE 4.1
Summary: KOrganizer aborts on startup of KDE 4.1
Status: RESOLVED DOWNSTREAM
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) (show other bugs)
Version: 4.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 176607 176768 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-30 19:48 UTC by Michael Henatsch
Modified: 2008-12-04 16:58 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Henatsch 2008-11-30 19:48:35 UTC
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    SuSE RPMs

After KDE 4.1 has started the crash handler brind up a window "A fatal error has occurred ... ". It provides the details below.

This may be due to an update performed from the SuSE repositories just before this problem started to occur.

Application: KOrganizer Reminder Daemon (korgac), signal SIGABRT
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb57d38e0 (LWP 3955)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb60d4900 in raise () from /lib/libc.so.6
#8  0xb60d6238 in abort () from /lib/libc.so.6
#9  0xb60cd70e in __assert_fail () from /lib/libc.so.6
#10 0xb6433e7c in icalerror_set_errno () from /usr/lib/libical.so.0
#11 0xb642f50e in icalcomponent_get_first_property ()
   from /usr/lib/libical.so.0
#12 0xb63ddc1c in KCal::ICalTimeZoneSource::parse () from /usr/lib/libkcal.so.4
#13 0xb63ded08 in KCal::ICalTimeZoneSource::parse () from /usr/lib/libkcal.so.4
#14 0xb6370a4a in KCal::Calendar::Private::timeZoneIdSpec ()
   from /usr/lib/libkcal.so.4
#15 0xb6370b8e in KCal::Calendar::setTimeZoneId () from /usr/lib/libkcal.so.4
#16 0xb637634a in KCal::Calendar::Calendar () from /usr/lib/libkcal.so.4
#17 0xb63c2916 in KCal::CalendarResources::CalendarResources ()
   from /usr/lib/libkcal.so.4
#18 0x08059792 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 1 Christophe Marin 2008-11-30 20:08:59 UTC
This may be a dup of bug 175345. 

Can you please install the kdepim4-debuginfo and kdepim4-debuginfo packages to get a better backtrace ?

Comment 2 Christophe Marin 2008-11-30 21:22:04 UTC
Pasting the BT I received directly (no it's not the correct way :)) :

Here's what the crash handler delivered after I installed kde4-debuginfo:

QUOTE
Application: KOrganizer Reminder Daemon (korgac), signal SIGABRT
[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb57f28e0 (LWP 3920)]
[KCrash handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb60f3900 in raise () from /lib/libc.so.6
#8  0xb60f5238 in abort () from /lib/libc.so.6
#9  0xb60ec70e in __assert_fail () from /lib/libc.so.6
#10 0xb6452e7c in icalerror_set_errno () from /usr/lib/libical.so.0
#11 0xb644e50e in icalcomponent_get_first_property ()
   from /usr/lib/libical.so.0
#12 0xb63fcc1c in KCal::ICalTimeZoneSource::parse () from 
/usr/lib/libkcal.so.4
#13 0xb63fdd08 in KCal::ICalTimeZoneSource::parse () from 
/usr/lib/libkcal.so.4
#14 0xb638fa4a in KCal::Calendar::Private::timeZoneIdSpec ()
   from /usr/lib/libkcal.so.4
#15 0xb638fb8e in KCal::Calendar::setTimeZoneId () from /usr/lib/libkcal.so.4
#16 0xb639534a in KCal::Calendar::Calendar () from /usr/lib/libkcal.so.4
#17 0xb63e1916 in KCal::CalendarResources::CalendarResources ()
   from /usr/lib/libkcal.so.4
#18 0x08059792 in KOAlarmClient (this=0x806c428, parent=0x0)
    at /usr/src/debug/kdepim-4.1.3/korganizer/korgac/koalarmclient.cpp:73
#19 0x08050bc6 in ReminderDaemonApp::newInstance (this=0xbf8465b8)
    at /usr/src/debug/kdepim-4.1.3/korganizer/korgac/korgacmain.cpp:51
#20 0xb7a357f6 in ?? () from /usr/lib/libkdeui.so.5
#21 0xb7a339fe in ?? () from /usr/lib/libkdeui.so.5
#22 0xb6578dd1 in ?? () from /usr/lib/libQtDBus.so.4
#23 0xb6579f47 in ?? () from /usr/lib/libQtDBus.so.4
#24 0xb657a451 in ?? () from /usr/lib/libQtDBus.so.4
#25 0xb657a94a in ?? () from /usr/lib/libQtDBus.so.4
#26 0xb7287449 in QObject::event () from /usr/lib/libQtCore.so.4
#27 0xb72773cb in QCoreApplication::event () from /usr/lib/libQtCore.so.4
#28 0xb67e1176 in QApplication::event () from /usr/lib/libQtGui.so.4
#29 0xb67db82c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#30 0xb67e36ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb7a2c31d in KApplication::notify () from /usr/lib/libkdeui.so.5
#32 0xb7277a71 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#33 0xb72786e5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#34 0xb72788dd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb72a25bf in ?? () from /usr/lib/libQtCore.so.4
#36 0xb5beb2d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb5bee85b in ?? () from /usr/lib/libglib-2.0.so.0
#38 0xb5bee9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#39 0xb72a2208 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#40 0xb6874885 in ?? () from /usr/lib/libQtGui.so.4
#41 0xb727614a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#42 0xb727630a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#43 0xb72789a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#44 0xb67db6a7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#45 0x08050b3a in main (argc=3, argv=0xbf8466e4)
    at /usr/src/debug/kdepim-4.1.3/korganizer/korgac/korgacmain.cpp:90
#0  0xffffe430 in __kernel_vsyscall ()


Comment 3 Volker Köhler 2008-12-01 11:35:44 UTC
Hello,

same error here.

ciao
   Volker...
Comment 4 Will Stephenson 2008-12-01 15:39:34 UTC
We (openSUSE) just patched internal libical out of KDE 4.1 as has been done in KDE trunk.  Therefore this is a downstream problem.  Please can you report this at bugzilla.novell.com, and install the debuginfo rpms for kdepim4 and libical and redo the backtrace?
Comment 5 Kevin Kofler 2008-12-01 18:45:04 UTC
But I'm pretty sure it also affects upstream 4.2, doesn't it? I suspect it's a libical bug.

We had this in Rawhide too:
https://bugzilla.redhat.com/show_bug.cgi?id=469228
We reverted to the builtin libical for the Fedora 10 release to work around this for now, but this really ought to be fixed in time for 4.2.
Comment 6 Will Stephenson 2008-12-02 14:59:56 UTC
Our BR for this: https://bugzilla.novell.com/show_bug.cgi?id=450659
Comment 7 Allen Winter 2008-12-02 15:11:50 UTC
If you are trying to use the external version of libical (I strongly recommend version 0.42) then you MUST make sure to backport the numerous related fixes to the kcal library in kdepimlibs.

I haven't yet backported everything from trunk to the 4.1 branch.
So, you'll need to do the diffs yourself.
Comment 8 Allen Winter 2008-12-02 15:13:20 UTC
*** Bug 176607 has been marked as a duplicate of this bug. ***
Comment 9 Will Stephenson 2008-12-02 16:51:32 UTC
FYI, fixed by backporting r879190 - don't crash when timezone info is NULL.
Comment 10 Christophe Marin 2008-12-03 14:13:07 UTC
*** Bug 176768 has been marked as a duplicate of this bug. ***
Comment 11 enthalpie 2008-12-04 16:27:40 UTC
Yes with libical 0.40.2-1 it is working again but WHY there is no automatic dependencies with this package ???

regards
Comment 12 Kevin Kofler 2008-12-04 16:45:57 UTC
Huh? The fix is a kdepimlibs fix, not a libical one, so I don't see how a libical package upgrade would have fixed it for you.
Comment 13 enthalpie 2008-12-04 16:55:18 UTC
well I have updated (changed) libical version 0.24-rc4 to libical0 version 0.40-2.1 and the problem is solved. i do that because i read that in comment 7 

it is the only thing i have changed
Comment 14 Kevin Kofler 2008-12-04 16:58:19 UTC
Oh, well, it can't work with 0.24 as it needs at least 0.33.