Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94299 - gnome-pilot fails to sync on first try, but is then able to on following tries
Summary: gnome-pilot fails to sync on first try, but is then able to on following tries
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo PDA project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-28 09:09 UTC by Rémi Cardona (RETIRED)
Modified: 2006-07-20 03:40 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rémi Cardona (RETIRED) gentoo-dev 2005-05-28 09:09:39 UTC
I'm using gnome-pilot to sync a Sony Cli
Comment 1 Rémi Cardona (RETIRED) gentoo-dev 2005-05-28 09:09:39 UTC
I'm using gnome-pilot to sync a Sony Clié PEG-T625C with evolution-1.4

I added a gnome-pilot applet on my gnome bar so that gpilotd is launched when I
log in.

When I dock my clié and then try to sync it (dock button or HotSync application
on PalmOS) the first try fails 99% of the time. USB0 and USB1 both show up in
/dev/tts/ but the sync times out about a minute later.

If I try again right after, everything works fine. Since USB0 and 1 are still
not gone, the visor module adds USB2 and 3. (my gpilot conf has two entries for
both USB1 and 3)

here is the output of lsof :

stratos root # lsof /dev/tts/USB*
COMMAND   PID USER   FD   TYPE DEVICE SIZE  NODE NAME
gpilotd 11180 remi   38u   CHR  188,1      19347 /dev/tts/USB1
stratos root # killall gpilotd
stratos root # killall gpilotd
gpilotd: no process killed
stratos root # lsof /dev/tts/USB*
lsof: status error on /dev/tts/USB*: No such file or directory
lsof 4.73
 [snip ...]

And here is some dmesg output from the first and second tries:

usb 1-2.2: new full speed USB device using uhci_hcd and address 5
usb 1-2.2: palm_os_4_probe - error -32 getting connection info
visor 1-2.2:1.0: Handspring Visor / Palm OS converter detected
usb 1-2.2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 1-2.2: Handspring Visor / Palm OS converter now attached to ttyUSB1
usb 1-2.4: 400mA over 100mA budget!
hub 1-2:1.0: 200mA over power budget!
usb 1-2.2: gpilotd timed out on ep0in
usb 1-2.2: USB disconnect, address 5
visor 1-2.2:1.0: device disconnected
usb 1-2.2: new full speed USB device using uhci_hcd and address 6
usb 1-2.2: palm_os_4_probe - error -32 getting connection info
visor 1-2.2:1.0: Handspring Visor / Palm OS converter detected
usb 1-2.2: Handspring Visor / Palm OS converter now attached to ttyUSB2
usb 1-2.2: Handspring Visor / Palm OS converter now attached to ttyUSB3
usb 1-2.4: 400mA over 100mA budget!
hub 1-2:1.0: 200mA over power budget!
usb 1-2.2: USB disconnect, address 6
visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2
visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3
visor 1-2.2:1.0: device disconnected


Reproducible: Always
Steps to Reproduce:
1. Dock clié
2. try to sync
3. wait for it to timeout
4. try to sync again

Actual Results:  
All the syncs following that first try work as expected, even after killing
gpilotd. However, the first sync will fail after a reboot.


[ebuild   R   ] sys-kernel/gentoo-sources-2.6.11-r9  -build -doc -symlink
(-ultra1) 0 kB
[ebuild   R   ] app-pda/gnome-pilot-2.0.10-r1  -debug 0 kB
[ebuild   R   ] app-pda/gnome-pilot-conduits-2.0.10-r1  -debug 381 kB

(duron 700, running x86 except for select packages)
Comment 2 Rémi Cardona (RETIRED) gentoo-dev 2005-06-27 14:05:32 UTC
I reported this bug over a month ago.

Has anyone looked at this? Should I file it upstream myself?
Comment 3 Stian Skjelstad 2005-06-27 14:37:38 UTC
Try upstream. Don't know how many developers (if any) that have the requested
hardware or simular.
Comment 4 Rémi Cardona (RETIRED) gentoo-dev 2005-06-27 15:35:57 UTC
ok, i'll file upstream

If I manage to turn debugging on with useful info, I'll try to figure out what's
wrong
Comment 5 Alastair Tse (RETIRED) gentoo-dev 2005-07-08 03:57:07 UTC
yeah, unfortunately, i don't have similar hardware to test it on. it is better if you report it upstream. be 
sure to include a link to their bugzilla/bug tracking entry so we can keep track of it. thanks!
Comment 6 Chris White (RETIRED) gentoo-dev 2006-02-03 14:57:18 UTC
Judging from the dmesg, it looks like your USB power is having issues.  This is causing USB to not follow over the connection, thus disconnecting your device.  Try with another cable?  Does it work with another system?
Comment 7 Alastair Tse (RETIRED) gentoo-dev 2006-07-20 03:40:35 UTC
Closing as I can't find this upstream reported anywhere.