Red Hat Bugzilla – Bug 161824
gnome-pilot doesn't work properly with shipped pilot-link
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
gnome-pilot as shipped doesn't work with the shipped pilot-link. See http://bugzilla.gnome.org/show_bug.cgi?id=274032 for all the gory details.
The attached patch updates gnome-pilot to work with the latest pilot-link API, and replaces the gnome-pilot-2.0.12-port-to-pilot-link-0.12.patch patch included in the .spec file.
Note that the patch presupposes the memory leak patch at http://bugzilla.gnome.org/show_bug.cgi?id=309077 although they're quite independent.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Try to sync. Watch it fail.
Created attachment 116025 [details]
Update gnome-pilot for latest pilot-link API
You may want to bump the pilot-link-version in configure to 0.12.preXXX, as this
patch doesn't compile successfully on pilot-link-version 0.11.xx.
I found a couple more bugs in the patch porting gnome-pilot to pilot-link 0.12,
so have re-created the patch and will attach below. In particular, the
gnome_pilot_compat_with_pilot_link_0_11 routines in
gpilotd/gnome-pilot-conduit-standard-abs.c had an incorrect check for the size
parameter being non-null, and was thus leading to uninit mem being used in
gnome-pilot-conduits (and some rather impressive crashes as it tried to allocate
a couple of gig of ram).
Created attachment 117005 [details]
Update porting patch to fix bugs in param checks
Any idea when these patches will make it into FC4 updates? I just "yum
check-update; yum update" yesterday and this is still very broken.
Another person here waiting for a working sync in FC4. When is this slated to
I'm having no luck with a LifeDrive, FC4 x86_64, and gnome-pilot. I've rebuilt
the gnome-pilot in updates-testing with the second patch provided by Mark above
but I still get this error:
(gpilotd:29010): gpilotd-WARNING **: An error occured while getting the pilot's
I can get syncing (at least backup) working on my laptop with FC4 (i686) but
that's not where I want to sync so it seems I'm having an x86_64 problem. Any ideas?
Try creating a dev entry under /etc/dev using mknod. At least in my case, it
solved the problem.
I tried that with a device in my home directory but it didn't help. I believe
the newer gnome-pilot in updates-testing deals with the slow creation of the
device. This seems to be a problem after communication has begun.
I actually have got network syncing working sporadically now with the LifeDrive.
I have hand modified the /.gnome2/gnome-pilot.d/gpilotd file to include
and syncing now seems to work sometimes. I had trouble repeating a sync but
after restoring the usb sync config directives, having that fail like #7 above,
and restoring the network sync config directives, I was able to repeat a sync.
So the error from #7 seems to be a communication problem as opposed to a
See my comment on #172670:
I think this issue is rooted in pilot-link post July 20th (as shipped in the
The issue _may_ be helped by setting a timeout=0 in the configuration.
The reason the config in comment #10 'works' is that it bypasses the
serial code in pilot-link, by using a network sync. By the way, I assume that
Thomas J. Baker can only use his workaround with a usb-connected device?
That would be because network syncing is not working properly at present in
gnome-pilot, and it needs the usb wakeup before passing the 'net:any' string
to pilot-link to connect via the network.
Yes, exactly true. It was working sporadically until I realized that I had to
attach the LifeDrive to the USB connector. Then it works, mostly, except when
you want to restore from backup :-(
WorksForMe using the packages from FC4 updates-testing:
Zire (m150) + FC4 PPC on iBook G3 600 (PowerBook4,1)
full package update on 2006-02-12 (from stable updates)
Great job - thanks a lot !!!
Is this bug still present in the latest Rawhide release?
Closing per comment #13 and lack of response for updated status. Feel free to
re-open this bug if you still encounter the problem in Fedora Core 6 or later.