Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 113230 - gpilotd fails to sync MemoFile
gpilotd fails to sync MemoFile
Status: CLOSED DUPLICATE of bug 125350
Product: Fedora
Classification: Fedora
Component: gnome-pilot (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Malcolm
Depends On:
  Show dependency treegraph
Reported: 2004-01-09 19:46 EST by Robert Locke
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:00:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Locke 2004-01-09 19:46:31 EST
Description of problem:
The memo_file directory in the home directory remains empty even
though there are several memos on the pilot.

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

How reproducible:

Steps to Reproduce:
1. Enable MemoFile conduit
2. Set one time action of Copy from Pilot
3. Perform HotSync


Actual Results:  None of the memos appear in the memo_file directory.

Additional info:

This has been an outstanding problem with the counduit with a patch
dating back to last summer.  The patch apparently needs to be applied
to gnome-pilot package, not the gnome-pilot-conduits package.  See:

This behavior has also been exhibited in RHEL3.
Comment 1 Dave Malcolm 2004-09-21 17:56:18 EDT
I'm sorry that this bug has gone for so long without activity.

It looks like the patch you refer to has been partially applied
upstream, and updated gnome-pilot and gnome-pilot-conduits packages
are available in Rawhide (2.0.12).

Do these packages fix the problem for you?
Comment 2 Robert Locke 2004-09-21 20:10:55 EDT

*** This bug has been marked as a duplicate of 125350 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:00:42 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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