[Bug 20989] New: korganizer-conduit corrupts datebookdb

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Wed Dec 14 12:36:49 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=20989
Ubuntu | kpilot

           Summary: korganizer-conduit corrupts datebookdb
           Product: Ubuntu
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: kpilot
        AssignedTo: jriddell at ubuntu.com
        ReportedBy: jochen-jansen at freenet.de
         QAContact: kubuntu-bugs at lists.ubuntu.com


When synchronizing my PalmOS-device (Sony Clie NX70-V, PalmOS 5) with kpilot
(4.6.0 blivit, Pilot-Link Version: 0.11.8, KDE Libraries Version: 3.5.0, Qt
Version: 3.3.4), the Korganizer conduit *always* corrupts my datebookbd on the
handheld, no matter  wether the conduit is set to "palm overrides pc" or not.
After the hotsync, the datebook on the handheld always reports that several
datebook-entries have been fixed due to invalid ending-time entries. Then,
repeating events have no more duration (that means, they do not longer last from
eg. 9-17, but are now *at* 9:00), while on the PC these repeating events last
from the first throughout the last entry (That means: Not 5 events a week from
9-17, but now one event from monday 7 to friday 17). And even worse: several old
repeating events (eg from July!) appear in this week again. Both the datebook on
the handheld as well as the calenderfile on the PC are affected. Both the
calenders on handheld and pc are so garbled and messed up, that they have to be
deleted.
Kpilot therefore is unusable!
Note: Using evolution and its conduit works perfectly well. I noticed a check
box in gnome-pilots calendar-conduit "split multi-day events".

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kubuntu-bugs mailing list