Thanks for following up. Closing the bug.
** Changed in: gnome-pilot (Ubuntu)
Status: Needs Info => Fix Released
--
After one sync, connections to a Tungsten T3 device fails
https://bugs.launchpad.net/bugs/67077
You received this bug notification because you are a member of Ubuntu
Desktop
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 v
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 'u
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/
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
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 whethe
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 gpilo
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
(
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 /
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:', et
10 matches
Mail list logo
