Bug 167097
Summary: | gpilotd will not accept port of net:any | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jake Gage <jake> | ||||
Component: | gnome-pilot | Assignee: | Matthew Barnes <mbarnes> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | CC: | andrewz, mcdavey, tjb | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | gnome-pilot-2.0.15-1.fc6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-12-13 20:10:04 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jake Gage
2005-08-30 10:01:57 UTC
I got this to work somewhat. Device settings in gpilotd file that worked for me were these: [Device0] type=1 name=LifeDrive device=net:any speed=115200 timeout=10 See also bug #161824. The workaround above only works with a usb-cable connected device. It 'wakes' gpilotd with via usb, and gpilotd then completes the sync by passing the net:any device to pilot-link. gnome-pilot doesn't listen correctly for network packets at the moment. I have a patched version available, from http://www.inference.phy.cam.ac.uk/mcdavey/downloads.html if you would like to assist with testing. I had to rebuild from the src rpm since I'm on x86_64. Once I got past the crasher on trying to set it to be a network sync from "Pilot Settings" caplet (I'll include a bt next), grepped the source to find out that network sync was type 4, set it by hand in ~/.gnome2/gnome-pilotd.d/gpilotd, it then seemed to sync fine. It doesn't seem to list the evolution pilot conduits in "Pilot Settings" but I'll rebuild evolution with the new -devel to see if that restores them. Created attachment 123291 [details]
gdb backtrace of crash when hitting OK after setting sync type to network
A rebuilt evolution does not make the evolution conduits seen. Any hints? With out the evo conduits, netsync is a lot less exciting. P.S. The correct URL for the patch is http://www.inference.phy.cam.ac.uk/mcdavey/downloads (drop the .html) Sorry for the delay getting back to you (I hadn't added myself to the cc list). The evolution package puts the .conduit files into /usr/lib/gnome-pilot/ conduits. Move them into /usr/share/gnome-pilot/conduits and the evo conduits should show up. I've added a note to the download page. Thanks for the bug report and workaround. Smells like a buffer overrun? I'd better try running with valgrind. I think the new 2.0.14 version (released Sept 8) fixes this problem. I built and installed pilot-link 2.0.14 for Fedora Core 5, and I can confirm it solves this issue. Now the sync over the network does work. gnome-pilot-2.0.15 is now in Fedora Core 6. Closing this bug based on comment #8 and comment #9. Please re-open this bug if you find that the problem still exists. |