After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 145869 - gnome-pilot doesn't allow network sync
gnome-pilot doesn't allow network sync
Status: RESOLVED DUPLICATE of bug 328396
Product: gnome-pilot
Classification: Other
Component: applet
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-19 16:34 UTC by andreas-lorenz
Modified: 2006-02-08 13:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description andreas-lorenz 2004-07-08 20:41:32 UTC
Distribution: SuSE Linux 9.1 (i586)
Package: gnome-pilot
Severity: major
Version: GNOME2.4.1 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: gnome-pilot doesn't allow network sync
Bugzilla-Product: gnome-pilot
Bugzilla-Component: applet
Bugzilla-Version: unspecified
Description:
Description of Problem:
It is impossible for me to configure gnome-pilot/gpilotd to sync my Sony
Palm via Network. JPilot and pilot-xfer do this task easily and without
any problem, but gnome-pilot doesn't work, when set to "Network"
mode!!!!

Steps to reproduce the problem:
1. Start gpilotd-control-applet and select "Network" from the possible
choices
2. You are not able to enter any valid information and therefore cannot
continue with NEXT button (greyed out)
3. Hotsync doesn't work, even when configuration is edited manually to
file: .gnome/gnome-pilot.d/gpilotd

Actual Results:
Hotsync doesn't work! 

Expected Results:
Palm Pilot connects to gpilotd and sync (to Evolution) works 

How often does this happen?
ALWAYS!


Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 16:41 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-pilot".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was andreas-lorenz@gmx.de.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Subodh Soni 2005-06-28 09:57:05 UTC
Thanks for taking the time to report this bug. This bug report isn't very useful
because it doesn't describe the bug well. If you have time and can still
reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add
a more useful description to this bug.
Comment 2 Sebastien Bacher 2005-08-18 15:27:15 UTC
gentoo has some patches for this:
https://bugs.gentoo.org/show_bug.cgi?id=84890
https://bugs.gentoo.org/show_bug.cgi?id=88511
Comment 3 Simon Major 2006-02-08 01:06:14 UTC
Please close this as a duplicate of bug 330330 (I do not have privs to close this myself)
Comment 4 Matt Davey 2006-02-08 13:03:21 UTC
There are two issues here.

First, the problems with the GUI, as mentioned also in #330330.  This prevents necessary configuration params being set that may, in certain cases, allow successful netsyncing with gp <= 2.0.13.  (unverified by myself, opinions
seem to differ...).

Second, the problem that gnome-pilot <= 2.0.13 netsync mode listened only for incoming UDP (PNRP 'palm name resolution protocol') packets, and so could never successfully sync in the situations in which UDP packets are never sent and the sync proceeds straight to TCP.

Both of these problems are fixed in CVS, and should appear in version 2.0.14.
Marking this as a duplicate of 328396.

*** This bug has been marked as a duplicate of 328396 ***