After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 357762 - Gpilotd does not reply to all sync request
Gpilotd does not reply to all sync request
Status: RESOLVED NOTGNOME
Product: gnome-pilot
Classification: Other
Component: gpilotd
2.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-26 08:19 UTC by Daniel Holbach
Modified: 2006-09-29 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Daniel Holbach 2006-09-26 08:19:34 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/62310


Here is the output :

LC_ALL=C gpilotd -d -d -d
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)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=115200

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

(gnome-pilot:15026): gpilotd-WARNING **: pi_accept_to: timeout was 10 secs

Extracts fom dmesg :
[17185973.152000] usb 1-1.2: new full speed USB device using ohci_hcd and address 3
[17185973.280000] usb 1-1.2: configuration #1 chosen from 1 choice
[17185973.468000] usbcore: registered new driver usbserial
[17185973.468000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[17185973.468000] usbcore: registered new driver usbserial_generic
[17185973.468000] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[17185973.476000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
[17185973.476000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
[17185973.476000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0
[17185973.480000] visor 1-1.2:1.0: Handspring Visor / Palm OS converter detected
[17185973.480000] usb 1-1.2: Handspring Visor / Palm OS converter now attached to ttyUSB0
[17185973.480000] usb 1-1.2: Handspring Visor / Palm OS converter now attached to ttyUSB1
[17185973.484000] usbcore: registered new driver visor
[17185973.484000] drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
[17186038.996000] usb 1-1.2: USB disconnect, address 3
[17186038.996000] visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
[17186038.996000] visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
[17186038.996000] visor 1-1.2:1.0: device disconnected

The next try, in the same gpilotd process works :

gpilotd-Message: setting PILOTRATE=115200
gpilotd-Message: Device Cradle has 0 events
gpilotd-Message: Instantiating 5 conduits...
...
gpilotd-Message: Synchronization ended
** Message: time_file: destroying time conduit

The next try gives :
gpilotd-Message: setting PILOTRATE=115200

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

(gnome-pilot:15026): gpilotd-WARNING **: pi_accept_to: timeout was 10 secs



It is a Palm Tungsten T3
Comment 1 Matt Davey 2006-09-27 21:22:33 UTC
Not sure what's causing this problem.

Here's one thing to test:
kill gpilotd (you may need to remove the pilot applet from the panel, and then do 'killall gpilotd' from a terminal window).

Now try running pilot-xfer:
pilot-xfer -p /dev/pilot -l
(or /dev/ttyUSB0, or /dev/ttyUSB1, I'm not sure which is right for the T3)

Does pilot-xfer work reliably, or do you have the same problems as with gnome-pilot?  If it is just as unreliable, then I'd recommend bugging
the pilot-link people:
    http://www.pilot-link.org/mailman/listinfo/pilot-link-general
It's just possible that you're getting a regression with the new pilot-link
major version, 0.12.
Comment 2 Olivier Blanc 2006-09-29 16:02:19 UTC
I updated https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/62310
it seems to me that it was due to udev...

Comment 3 Matt Davey 2006-09-29 16:36:28 UTC
closing as 'not gnome'.
feel free to reopen if the problem recurs.
Comment 4 Daniel Holbach 2006-09-29 16:58:43 UTC
Thanks again, Matt. I added your notes to http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines