Bug 150626

Summary: Task time is sometimes set to 00:00 (with shared folders on Kolab IMAP resource)
Product: [Applications] kontact Reporter: Martin Honermeyer <maze>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: vanmeeuwen
Priority: NOR    
Version: 1.2.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
See Also: https://bugzilla.kolabsys.com/show_bug.cgi?id=838
Latest Commit: Version Fixed In:

Description Martin Honermeyer 2007-10-09 15:40:22 UTC 
Version:           1.2.4 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
Compiler:          gcc-Version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)
 i486-linux-gnu
OS:                Linux

We are using Kontact in conjunction with the Kolab 2 groupware server. The Kolab mailbox is, as normal, set up as a dimap resource. There are different shared folders with tasks and calendars. On this client ((K)Ubuntu Feisty) the following happens:

I create a task and set a due date, leaving the time unset (checkbox unchecked). Before closing Kontact, I make sure the mailbox gets synchronized (using "send/receive" in the KMail kpart). After restarting kontact, the time checkbox for this task is set and the time is set to 00:00 (before synchronizing!). Synchronizing the folders now doesn't change anything - it stays with the time set. 

This happens _often_ with many tasks, but not every time and not with every task.

I justed this with Kontact 1.2.5 on my OpenSUSE 10.1 machine. The same problem there!

Seems to be a general Kontact problem - does it always write the time to the task xml?

 <due-date>2007-10-19T22:00:00Z</due-date>
Comment 1 mds 2009-01-17 10:09:34 UTC 
Hi, I can reproduce this on Ubuntu Intrepid Ibex w/ Kontact 1.3 using Gnome desktop- both on the 64bit and 32bit Version.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-06-08 13:37:52 UTC 
This is a calendar format issue within Kolab, allowing Zulu datetime stamps only, instead of date stamps, and as such not a valid KDE bug.

The original upstream issue is targeted to be resolved with a new version of the Kolab format, for which I've created a ticket on your behalf(s), ensuring the issue will not reoccur.