Bug 176607

Summary:	korganizer reminder module crashes kde-session start
Product:	[Applications] korganizer	Reporter:	Wolfgang Weich <weich>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	Regnaron, winter
Priority:	NOR
Version:	4.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Wolfgang Weich 2008-12-01 08:10:08 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

When starting kde 4.1 session with korganizer module autostart it crashes and gives the following report:

Anwendung: KOrganizer-Erinnerungsmodul (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 0x7fb736d0c700 (LWP 4028)]
(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]
#5  0x00007fb72e88a5c5 in raise () from /lib64/libc.so.6
#6  0x00007fb72e88bbb3 in abort () from /lib64/libc.so.6
#7  0x00007fb72e8831e9 in __assert_fail () from /lib64/libc.so.6
#8  0x00007fb72f86e10a in icalerror_set_errno () from /usr/lib64/libical.so.0
#9  0x00007fb72f869ebc in icalcomponent_get_first_property ()
   from /usr/lib64/libical.so.0
#10 0x00007fb72f3fa865 in KCal::ICalTimeZoneSource::parse ()
   from /usr/lib64/libkcal.so.4
#11 0x00007fb72f3fb85a in KCal::ICalTimeZoneSource::parse ()
   from /usr/lib64/libkcal.so.4
#12 0x00007fb72f395392 in KCal::Calendar::Private::timeZoneIdSpec ()
   from /usr/lib64/libkcal.so.4
#13 0x00007fb72f39547e in KCal::Calendar::setTimeZoneId ()
   from /usr/lib64/libkcal.so.4
#14 0x00007fb72f39aa9b in KCal::Calendar::Calendar ()
   from /usr/lib64/libkcal.so.4
#15 0x00007fb72f3e1013 in KCal::CalendarResources::CalendarResources ()
   from /usr/lib64/libkcal.so.4
#16 0x00000000004135a9 in _start ()
#0  0x00007fb72e8fa230 in nanosleep () from /lib64/libc.so.6

Comment 1 Oliver Putz 2008-12-02 09:39:55 UTC

Hello,

Thanks for your report. It sounds as if you are able to reproduce the crash. So could you please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, install the debugging packages for your distribution and post a more detailed backtrace?

Comment 2 Allen Winter 2008-12-02 15:13:20 UTC


*** This bug has been marked as a duplicate of bug 176566 ***