After one sync, connections to a Tungsten T3 device fails

Thanks for the bug report. Can you try this:
   1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
   2. Now try running pilot-xfer: pilot-xfer -p /dev/pilot -l (or '-p /dev/ttyUSB0', or '-p /dev/ttyUSB1', or '-p net:', etc)
   3. If that doesn't work, then you have most likely got a problem with your kernel/udev/usb/cables, etc, not gnome-pilot.

It can also be useful to see the output from the gpilotd daemon. To do this:
   1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
   2. Restart gpilotd.

Hi Daniel,

I did one sync which worked fine. Then as usuall, the second one
failed. So I killed gpilotd after removing the pilot applet from the
panel.
I then realized that pilot-xfer was not on my sytem and installed
pilot-link.

pilot-xfer -p /dev/pilot -l complained with
sudo pilot-xfer -p /dev/pilot -l
   Unable to bind to port: /dev/pilot
   Please use --help for more information
and there are no ttyUSB0 or 1 devices.

? so what did I miss? - Sorry that I didn't get further.

Running gpilotd gives:
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Cradle (/dev/pilot)

Thanks,
Joel Parke

On Fri, 2006-10-20 at 09:44 +0000, Daniel Holbach wrote:

> Thanks for the bug report. Can you try this:
> 1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
> 2. Now try running pilot-xfer: pilot-xfer -p /dev/pilot -l (or '-p /dev/ttyUSB0', or '-p /dev/ttyUSB1', or '-p net:', etc)
> 3. If that doesn't work, then you have most likely got a problem with your kernel/udev/usb/cables, etc, not gnome-pilot.
>
> It can also be useful to see the output from the gpilotd daemon. To do this:
> 1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
> 2. Restart gpilotd.
>
> ** Changed in: gnome-pilot (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>

--
Joel Parke <email address hidden>

I thought about my last post some more and thought, perhaps it would be more helpful to load gpilod, then add the applet and then sync twice and record the output. See the attaced file 1 below for the First Sync.

After that Sync - the only output was:

gpilotd-Message: setting PILOTRATE=115200

(gnome-pilot:17960): gpilotd-WARNING **: pi_accept_to returned -202: No such file or directory

(gnome-pilot:17960): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs

AND of course the second sync failed.

I hope this helps.

Thanks for all the hard work - this is a great release!
Joel Parke

Now, with all the updates, running directly from the panel, there is never any connection to the T3. BUT if I kill the gpilot-applet, and then start gpliotd on the command line with no arguments, and then start the gpilot-applet, I can sync as many times as I want.

? what arguments does the gpilot-applet pass to gpilotd when it needs to start it if it is not already running?

Thanks,
Joel

Joel,
silly question, but there isn't any chance you've got two versions of gpilotd on your system: one that you run from the command line and one that the applet finds? There aren't any arguments that I can think of that would affect the behaviour as you describe.

One thing to check is whether your /dev/pilot symlink always points to the right ttyUSBx device. I've a vague notion I've come across cases where it sometimes gets confused, pointing to either ttyUSB1 or ttyUSB0, but not consistently. If this is the case you may want to try configuring gpilotd to use the correct ttyUSBx device rather than relying on /dev/pilot. Either that, or configure pilot-link for libusb syncing (search around for the howto) and then you can use the "usb:" pseudo device.

Hi Matt,

Indeed I only have one gpilotd. I attempted to get libusb working. -
that seems fine as i got
pilot-xfer -p usb: -l
to work. But I did have a question about
~/.gnome2/gnome-pilot.d/gpilot
I could not figure out what to set /dev/pilot to?
I tried device=/dev/bus/usb/002/001 which is the actual Palm usb device,
and that didn't work.
Any ideas?

One thing I did notice is that when gpilotd is run at the command line
is says:
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]

(gnome-pilot:21866): gpilotd-WARNING **: Number of devices is configured
to 0

(gnome-pilot:21866): gpilotd-WARNING **: No accessible devices available

(gnome-pilot:21866): gpilotd-WARNING **: Number of PDAs is configured to
0
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0

Which seems to imply that it doesn't read the same config as when the
applet runs gpilotd. Could that be the problem since sync works after
this if I run the applet and then sync?

Thanks,
Joel

One more attempt by deleting the gpilotd config file caused the applet
to reconfigure the gpilot. I attempted to set it to usb; but that
complained with the visor module still running. So I selected the
dev/ttyUSB1 which sync'd correctly and repeatedly.

I have put visor in both
/etc/modprobe.d/blacklist-palm
/etc/hotplug/blacklist

So I will now reboot to make sure that the visor module doesn't get
loaded.

Thanks,
Joel

--
Joel Parke <email address hidden>

Joel:

> Indeed I only have one gpilotd. I attempted to get libusb working. -
> that seems fine as i got
> pilot-xfer -p usb: -l
> to work. But I did have a question about
> ~/.gnome2/gnome-pilot.d/gpilot
> I could not figure out what to set /dev/pilot to?

You should be able to set it to 'usb:' using the config applet. It should even be one of the options in the drop down list.

> One thing I did notice is that when gpilotd is run at the command line
> is says:
[...]
> (gnome-pilot:21866): gpilotd-WARNING **: Number of devices is configured to 0
[...]
> Which seems to imply that it doesn't read the same config as when the
> applet runs gpilotd. Could that be the problem since sync works after
> this if I run the applet and then sync?

Have you edited your ~/.gnome2/gnome-pilot.d/gpilot?
Is it possible that it's been mucked up so that gpilotd can't parse it?

I can't think of a good reason to edit that file by hand, at least with pilot-link 0.12 and gp 2.0.14.

You could try removing or moving your ~/.gnome2/gnome-pilot.d directory altogether and trying the config steps again.

Matt

Hi Matt,

Now all is well - although there still seems to be a bug related to
visor and being confused as you suspected about which usb device to use.
I have deleted just the gpilotd config which causes the applet to
re-inquire and setup again.
Now USB is working and much faster as well - since visor is slow.
Thanks for all you help!
If there ever is a bug fix for visor related to the confusions about usb
device, I could check that again by un-blacklisting visor, etc.

Joel

--
Joel Parke <email address hidden>

Thanks for following up. Closing the bug.