KEYWORDS: Palm, Handspring, Visor, Treo, Ximian Evolution, sync, synchronize, gpilotd, gpilotd-control-applet, /dev/pilot
I've been trying for a few days to get gpilotd-control-applet to configure gpilotd so that I can sync with Ximian Evolution, to no avail.
pilot-xfer works
jpilot works
Ximian Evolution (gpilotd*) does NOT work at all.
So just for good measure I start from scratch by running:
Code:
rm -f /dev/pilot
chown root.root /dev/ttyUSB*
chmod 666 /dev/ttyUSB*
ln -s //dev/ttyUSB1 /dev/pilot
I did the chown/chmod because before I tried anything, the devices looked like this:
Quote:
crw-rw-rw- 1 root root 188, 1 Aug 28 22:43 /dev/ttyUSB1
|
While after they looked like this:
Quote:
crw------- 1 joeuser uucp 188, 1 Aug 28 22:43 /dev/ttyUSB1
|
So I wanted to make sure that I was starting from scratch again.
Also, for those who are wondering, I have all othe mods loaded, though that's a bit obvious otherwise pilot-xfer would choke:
Code:
lsmod | sort
[...]
usbcore 79040 1 [visor usbserial hid usb-uhci ehci-hcd]
usbserial 22108 0 [visor]
usb-uhci 26412 0 (unused)
visor 12232 0
[...]
Then, a reboot for good measure.
Now, I tried running gpilotd-control-applet from the command line so that I can see all of STDOUT and STDERR right on the terminal and I get the following (the part in bold is the output immediately following the connection attempt on /dev/pilot in order to get username and id):
Quote:
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Initing gnome vfs
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-WARNING **: Number of devices is configured to 0
gpilotd-WARNING **: No accessible devices available
gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Exiting (caught SIGTERM)...
gpilotd-WARNING **: gnome-pilot-client.gob:786: Caught exception: IDL mg.org/CORBA/COMM_FAILURE:1.0
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
GLib-CRITICAL **: file ghash.c: line 295 (g_hash_table_foreach): assertion `hash_table != NULL' failed.
GLib-CRITICAL **: file ghash.c: line 99 (g_hash_table_destroy): assertion `hash_table != NULL' failed.
|
(Note that these messages appear to be the same whether I have the treo/visor attempting to connect (syncing) or not).
OK, so I figure that maybe gpilotd needs to be running and I fire it up in the background and then retry:
Quote:
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Initing gnome vfs
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Exiting (caught SIGTERM)...
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-WARNING **: Could not open device Cradle (/dev/pilot): reason: "No such device".
gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: gpilotd: corba: get_user_info(cradle=Cradle,survival=0,timeout=0)
gpilotd-Message: gpilotd: assigned handle num 11
gpilotd-Message: FISK: OST
gpilotd-Message: gpilotd: gpc_queue_purge_request()
gpilotd-Message: Exiting (caught SIGTERM)...
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-WARNING **: Number of devices is configured to 0
gpilotd-WARNING **: No accessible devices available
gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
GLib-CRITICAL **: file ghash.c: line 295 (g_hash_table_foreach): assertion `hash_table != NULL' failed.
GLib-CRITICAL **: file ghash.c: line 99 (g_hash_table_destroy): assertion `hash_table != NULL' failed.
|
Interesting, at least the error message changed. So I do an "ls -ld /dev/pilot /dev/ttyUSB1 /dev" for a sanity check:
Code:
drwxr-xr-x 21 root root 118784 Aug 29 10:50 /dev
lrwxrwxrwx 1 root root 12 Aug 29 10:46 /dev/pilot -> /dev/ttyUSB1
crw------- 1 joeuser uucp 188, 1 Aug 28 22:43 /dev/ttyUSB1
HMM... I don't know what it was thinking, but it sure looks like it 's there to me. And there's joeuser again, and I don't know what's up with that, but oh well.
Now I just make sure that pilot-xfer still works without doing anything else, by running "pilot-xfer -p /dev/pilot -b treobackup/2003.08.29" and it works beautifully.
So now I have to ask myself:
"What the &%#$&%#$ am I doing wrong?!?!?!"
I LOVE Linux, but sometimes it makes me want to pull out my hair and bang my head against the wall...
-A desperate G.
Additional info:
When I run gpilotd-control-applet as root it starts up gpilotd just fine for me and I walk through the initial sync steps until I get to the retreive userid/username when I get an error dialog:
Quote:
Unknown pilot - no pilots matches[sic] ID 25973
Use gnomecc to set pilot's ID
|
and the term output looks like this:
Quote:
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Initing gnome vfs
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-WARNING **: Number of devices is configured to 0
gpilotd-WARNING **: No accessible devices available
gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Exiting (caught SIGTERM)...
gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: Watching Cradle (/dev/pilot)
gpilotd-Message: Woke on Cradle
gpilotd-Message: setting PILOTRATE=57600
gpilotd-Message: Cradle Cradle has 0 events
gpilotd-WARNING **: Unknown pilot, no userID/username match 25973
gpilotd-Message: gpilotd: corba: get_user_info(cradle=Cradle,survival=0,timeout=0)
gpilotd-Message: gpilotd: assigned handle num 1
gpilotd-Message: FISK: OST
gpilotd-Message: gpilotd: gpc_queue_purge_request()
Message: No pilot userid/username information located
Message: Unable to load pilot id/username, assuming unset
Message: No pilot cradle information located
Message: Unable to load pilot cradle info, assuming unset
GLib-CRITICAL **: file ghash.c: line 295 (g_hash_table_foreach): assertion `hash_table != NULL' failed.
GLib-CRITICAL **: file ghash.c: line 99 (g_hash_table_destroy): assertion `hash_table != NULL' failed.
|