Bug 211747 - Backup/HotSync with Palm Tungsten deletes Location in Appointments on Palm
Summary: Backup/HotSync with Palm Tungsten deletes Location in Appointments on Palm
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim   
(Show other bugs)
Version: 6
Hardware: All Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-21 18:43 UTC by David W. Legg
Modified: 2008-05-06 16:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 16:31:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description David W. Legg 2006-10-21 18:43:45 UTC
Description of problem:
kpilot/kpilotDaemon deletes Location field when syncing with Palm Tungsten.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start kpilot
2. Choose File/Backup or Hotsync
3. Press Hotsync button on Palm
4. Wait for sync to happen

Actual results:
Palm syncs ok, but Location fields in its calendar app are blanked/deleted, ie.
rooms or addresses associated appointment are deleted.

Expected results:
Data that form part of an appointment on the Palm should not normally be deleted
on a sync.

Additional info:
I have a Palm Tungsten T3.

Comment 1 David W. Legg 2006-11-06 19:06:46 UTC
This is still a problem in kdepim-3.5.5-0.1.fc5.
Since it has goen into FC6 too, I am changing the affected build to FC6.

Comment 2 Bug Zapper 2008-04-04 04:03:11 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 3 Bug Zapper 2008-05-06 16:31:18 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.