gnome-pilot and Palm Sync problem

[Helker]

Hi,

I have a problem with my Palm Handheld not syncing with gnome-pilot. I tried everything I found on the Internet, but still no luck.

The device works fine with j-pilot, but I could not make it work with gnome-pilot. You may say that since j-pilot is working, why bother with gnome-pilot? Good question, but I need my handheld to sync with Evolution. Therefore, I either make gnome-pilot to work, or I have to find a way to make j-pilot sync with Evolution...

I tried modifying the udev rules, but it did not work... The command

$ pilot-xfer -p /dev/pilot -l

just sits with this output and does nothing:

Listening for incoming connection on /dev/pilot...

I also tried with root, but with the same results....

I don't know what else to try...

Please help!

Update:
I was able to make the pilot-xfer command to work.... I had to run the hotsync on the palm and then launch the command... But gnome-pilot still does not work...

Uhm... After several tries I was able to make the first-time sync to work and it registered the palm, but now how do I make it to sync with Evolution?

It seems to me that has some timing issue where the hotsync button and the sync on the computer has to be run in a specific order... All what I am able to get now is the gnome-pilot settings window with my device listed...

[A.Serbinski]

On some palm devices (ie treo 600/650), USB sync is very timing dependent. The reason for this is that the device is only created for a brief moment after the hotsync button is pressed, it then disappears. You would think that pilot-link would listen for the device to appear and then make use of it, but no, it checks if the device is present and fails if it isn't. The best solution is to forget about the USB wire and perform a network sync (ie, over bluetooth if this is an option).

Regarding syncing with evolution, in gnome-pilot, select the "conduits" tab and enable the conduits that you want to sync.

[Helker]

Originally Posted by A.Serbinski

On some palm devices (ie treo 600/650), USB sync is very timing dependent. The reason for this is that the device is only created for a brief moment after the hotsync button is pressed, it then disappears. You would think that pilot-link would listen for the device to appear and then make use of it, but no, it checks if the device is present and fails if it isn't. The best solution is to forget about the USB wire and perform a network sync (ie, over bluetooth if this is an option).

Regarding syncing with evolution, in gnome-pilot, select the "conduits" tab and enable the conduits that you want to sync.

My Palm only has the cable and the IR port, but my PC does not have the IR port. Therefore, I'm stuck with the USB cable...

I already checked the conduits to sync on the preferences, but nothing happens...

I'll try to hit both button (on the Palm and on the PC at the same time

[Helker]

Blast it!

I started the "Bluetooth" service (hcid, sdpd) and it worked... sort of... It crashed and it opened a bug-reporting window... now it does not work anymore


Update:
I was able to start the sync two more times just by trying over and over the syncronization, and it always crashed at the same time syncing the "ToDo's". Here is the bug report generated: (see attachment)

I disabled the ToDo conduit, and after trying several dozen times to sync, I was able to sync my palm... finally...

Something should be done to solve this problem with the device being created for just a split second...

[A.Serbinski]

This isn't the right place to submit bug reports. These are the places; bugzilla.redhat.com, bugzilla.gnome.org (gpilotd is part of gnome), and I'm not sure how pilot-link likes their bug reports, but their website is here; www.pilot-link.org