Bug 363460

Summary: Crash in korganizer prevents Kontact from starting
Product: [Frameworks and Libraries] frameworks-kcalendarcore Reporter: clivejo <clivejo>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description clivejo 2016-05-24 10:24:24 UTC 
System: Kubuntu 16.10 (Yakkety Yak) + Frameworks 5.22 + Plasma 5.6.4
TimeZone : British Summer Time (BST) / Irish Summer Time (IST)

When I log into plasma the KOrganizer Daemon Reminder crashes.  A back trace seems to indicate the problem is:

KCalCore::ICalTimeZoneData::ICalTimeZoneData (this=0x5623445a0ce0, rhs=..., tz=..., earliest=...) at /build/kcalcore-yvIebH/kcalcore-16.04.1/src/icaltimezones.cpp:708

Any suggestions as to what is wrong?
Comment 1 clivejo 2016-05-24 21:45:37 UTC 
This seems to be related to my Kolab account.  When I remove it, Kontact runs fine, as soon as I add it back, korganizer crashes.
Comment 2 clivejo 2016-05-25 14:22:06 UTC 
(gdb) bt
#0  0x00007ffff2402418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007ffff240401a in __GI_abort () at abort.c:89
#2  0x00007ffff244472a in __libc_message (do_abort=do_abort@entry=1, 
    fmt=fmt@entry=0x7ffff255bc7f "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
#3  0x00007ffff24e589c in __GI___fortify_fail (msg=<optimised out>, 
    msg@entry=0x7ffff255bc61 "stack smashing detected") at fortify_fail.c:37
#4  0x00007ffff24e5840 in __stack_chk_fail () at stack_chk_fail.c:28
#5  0x00007ffff6b98c43 in KCalCore::ICalTimeZoneData::ICalTimeZoneData (this=0x5555559e6760, rhs=..., tz=..., 
    earliest=...) at /build/kcalcore-yvIebH/kcalcore-16.04.1/src/icaltimezones.cpp:708
#6  0x7f7f7f7f7f7f7f7f in ?? ()
#7  0x7f7f7f7f7f7f7f7f in ?? ()
#8  0x7f7f7f7f7f7f7f7f in ?? ()
#9  0x7f7f7f7f7f7f7f7f in ?? ()
#10 0x7f7f7f7f7f7f7f7f in ?? ()
#11 0x7f7f7f7f7f7f7f7f in ?? ()
#12 0x7f7f7f7f7f7f7f7f in ?? ()
#13 0x7f7f7f7f7f7f7f7f in ?? ()
#14 0x0000000000000000 in ?? ()
Comment 3 Andrew Crouthamel 2018-11-01 13:49:02 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!