[jp] update to my inability to update

Paul King sciguy at vex.net
Sat Jun 14 08:17:10 EDT 2008

I found out that the reason it was syncing was because gpilotd was
running. When I killed it, jpilot went back to its "normal", totally
nonfunctioning self. Syncs don't work in either direction, with my palm
pilot giving up early (within a fraction of a second), and the message

dlp_ReadSysInfo error
Exiting with status SYNC_ERROR_PI_CONNECT

seen in the console. Running jpilot as root doesn't change anything.

The reason I don't use gpilot is because the mere detection of my m105
causes gpilot to crash. gpilotd works quite well, though.

Paul King

On Sat, 2008-06-14 at 07:58 -0400, Paul King wrote:
> If I run jpilot from the console, and sync it with the palm before I
> push the button on the cradle, I get:
> Unable to open log file
> Unable to open log file
> Unable to open log file
> Unable to open log file
> If I press the button on the cradle, the palm begins and ends syncing
> within a fraction of a second, and I get an error message (connection
> between handheld and desktop was lost). Then, after a couple of minutes
> of hanging, I get the following on the console:
> dlp_ReadSysInfo error
> Unable to open log file
> Exiting with status SYNC_ERROR_PI_CONNECT
> Unable to open log file
> Finished
> If I go the other way around, and press the cradle button without doing
> anything on jpilot, it syncs normally, but no updates are transferred
> from jpilot to the palm. The palm still lacks schedule entries that are
> on jpilot.
> Paul King
> _______________________________________________
> Public archival of this list without permission is prohibited.
> http://lists.jpilot.org/mailman/listinfo/jpilot
> e

More information about the Jpilot mailing list