Description of problem:
I'm synchronising my palm (a tungsten T3) with evolution over USB,
using gpilot. I've set the conduits to always overwrite the desktop
entries, using the palm. Whenever I synchronize the palm, my machine
(i686) grinds down to a halt - but doesn't actually freeze. It's
almost unusable. I tried it in a much more beefier machine A64, and
narrowed the problem down to the following: It's ECalendar. Disabling
all other conduits appart from ECalendar and running gpilotd from the
command line (so that I can see the output), shows gpilotd running
Ecalendar to completion (I think - the last line i see is
ecalconduit-Message: post_sync: Calendar Conduit v.0.1.6
after a lot of ecalconduit-Message: add_record
but then top shows that gpilod gradually devours all the memory in my
machine (endless loop), which makes it grind to a halt. It also
doesn't release the Palm, which eventually times out. This problem
didn't happen (with the same machines and palm) with FC1 or 2.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure palm with gpilot
2. Enable ECalendar and set it to overwrite desktop from palm
3. Hit hotsync
Machine grinds to a halt, gpilotd devours all the memory, palm times out.
Synchronisation complete, and gpilotd back to idle.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Is this problem still present in Fedora Core 6?
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report. If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Closing as INSUFFICIENT_DATA.