From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4
Description of problem:
When trying to set up syncing with my Palm V using gnome-pilot teh Palm thinks it worked but the Gnome Pilot Settings won't allow me to continue.
Everything is fine right up until it tells me to press the Hot Sync button. One ot two seconds later my Palm bleeps and says it was successful. However Gnome Pilot Settings just sits there forever (well 1/2 an hour or more) and the Forward button never becomes active.
I've tried it as root and it still won't work
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Hook up Palm V
2. Start GnomePilot Settings
3. Go step by step
4. Can't continue
Actual Results: Gnome Pilot Settings just sits there. The Palm V thinks it was successful.
Expected Results: I'd expect to be able to set up Evolution to sync with my Palm.
I have this problem with FC4 final. Adding myself to root group temporarily got
me sent to the preferences screen instead of initial setup, but I cannot now
duplicate this behavior; adding my pilot manually using the info from
install-user -p produced the same Palm-thinks-it-worked-but-nothing-happened
results as before. Installing gnome-pilot-conduits did not seem to help
try updated packages, or search for the packages based on patches by Mark Adams.
I got myself set up with Mark Adams's packages a while back and don't know if
this has been fixed in Core or not. I hope it gets taken care of for FC5 at least.
Does this bug still exist in Fedora Core 6 using gnome-pilot-2.0.15?
It seems to have been resolved. Be aware that I am not running a clean install
of FC6 but an upgraded FC5. gnopme-pilot, however, is version 2.0.15-1.fc6, so
everything looks good. I haven't tried syncing yet, as I don't have time right
now, but the setup works -- which is what this bug was referring to anyway. Cheers!
Thanks for the reply. I'll presume it's fixed and close this bug then. But
feel free to re-open this if you run into the same problem again in Fedora Core 6.