[Bug 67077] Re: After one sync, connections to a Tungsten T3 device fails

[JoelParke]

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 <joel at parke.ods.org>

-- 
After one sync, connections to a Tungsten T3 device fails
https://launchpad.net/bugs/67077