Re: problem syncing on OpenSUSE 10.2

[Wendell MacKenzie <mackendw sympatico ca>]

More diagnostics...to rule it out as being gnome-pilot or
gnome-pilot-conduits on the OpenSUSE 10.2,
I grabbed the gnome-pilot-2.0.14 and gnome-pilot-conduits-2.0.14 from
the garnome-2.16.2 tree
and compiled these on my OpenSUSE 10.2 disk, installed them using the
configure option used for
the OpenSUSE 10.2 distribution as per the .spec file for each src pkg.

I then copied from my OpenSUSE 10.1 home directory
~/.gnome2/gnome-pilot.d/* to my OpenSUSE 10.2.

fired up the hotsync.sh script to launch the dund daemon and started
gpilotd -d in a term window.

It still crashes the phone.

So, what does gnome-pilot (ala gpilotd) rely on that could be hosing the
treo??

Matt/Nathan??

ideas...

Wendell MacKenzie wrote:
> OK, I decided to back out of OpenSUSE 10.2 for a moment and revert back
> to my old drive containing OpenSUSE 10.1
> where I had garnome 2.16.2 running out of my home directory.
>
> I fired up the gpilotd applet and my hotsync.sh which starts up the dund
> daemon and did a hotsync from the treo.
>
> Worked fine...!!!
>
> So, I can only explain the SNAFU I'm experiencing is being caused by the
> fact that I brought over my home directory
> from OpenSUSE 10.1 which garnome must have been diddling with that is
> affecting the behaviour gpilotd from working.
>
> So ...the big question is now, how do I recover and get a working pilot
> sync to work under OpenSUSE 10.2...
>
> thoughts anyone??
>
>
> Wendell MacKenzie wrote:
>   
>> Hi Matt:
>>
>>    Just had my phone replaced by bell with a freshly initialized one.  
>> setup the bluetooth sync
>> profile, conduit, etc. and did a copy_to_pilot sync type of my address
>> book from evolution-2.8.2.
>>
>>    Kabam.  Same reset after the e_address_conduit finishes its sole
>> operation.
>>
>>    Here are the diagnostics from gpilotd -d:
>>
>> gpilotd-Message: Watching Cradle (/dev/pilot)
>> gpilotd-Message: Watching Bluetooth (network)
>> gpilotd-Message: Woke on network: Bluetooth
>> gpilotd-Message: Device Bluetooth has 0 events
>> gpilotd-Message: Instantiating 1 conduits...
>> eaddrconduit-Message: in address's conduit_get_gpilot_conduit
>>
>> gpilotd-Message: Instantiated 0 backup conduits, 0 file conduits, 1
>> other conduits
>> gpilotd-Message: NetSync request detected, synchronizing PDA
>> gpilotd-Message: PDA ID is 1000, name is MacPalm, owner is Wendell MacKenzie
>> gpilotd-Message: Pilot has 0 entries in restore queue
>> gpilotd-Message: Pilot has 0 entries in conduit queue
>> eaddrconduit-Message:
>> ---------------------------------------------------------
>>
>> eaddrconduit-Message: pre_sync: Addressbook Conduit v.0.1.2
>> ...
>>
>> eaddrconduit-Message:     doing slow sync
>>
>> eaddrconduit-Message: beginning for_each
>> eaddrconduit-Message: iterating over 222 records
>> ...
>> ... a whack of local_record_to_pilot_record entries
>> ...
>>
>> eaddrconduit-Message: for_each ending
>> eaddrconduit-Message: post_sync: Address Conduit v.0.1.2
>> eaddrconduit-Message:
>> ---------------------------------------------------------
>>
>>
>> (gnome-pilot:14652): gpilotd-WARNING **: Unable to open conduit!
>> gpilotd-Message: Synchronization ended
>>
>> (gnome-pilot:14652): gpilotd-WARNING **: error -202 from pi_close.
>>
>>
>> Any ideas on what to try now? 
>>
>> thx.
>> Wendell
>>
>>
>> At this point, the treo reboots.
>>
>>
>>
>> Matt Davey wrote:
>>   
>>     
>>> On Mon, 2007-01-15 at 10:46 -0500, Wendell MacKenzie wrote:
>>>   
>>>     
>>>       
>>>> OK, some more debug info. 
>>>>
>>>> If I change the conduit's setup on the gpilot-control-applet to
>>>> Synchronize for address, contacts and
>>>> memos and do a sync, it doesn't crash the treo, but I get the below:
>>>>
>>>> Synchronization failed!
>>>>
>>>> message.   If I set either the address or contacts conduit to "Copy to
>>>> PDA", this will definitely cause
>>>> the treo to reset at what looks to be the same spot in the contacts or
>>>> calendar location.
>>>>
>>>> :(....
>>>>
>>>> The system error log on the treo is as follows:  (##3773 on keypad after
>>>> the reset occurs):
>>>>
>>>> A reset was caused on 15/1/07 at 10:31am while running "HotSync";
>>>>
>>>> DataMgr.c,Line:8898, dmWrite: DmWriteCheck failed
>>>>     
>>>>       
>>>>         
>>> I did a quick google for the above line, and came up with:
>>> http://treo.discussion.treocentral.com/showthread.php?t=69675
>>>
>>> "I had this happening with DateBk5 and it turns out that some
>>> applications leave the Calendar database dirty with undeleted records.
>>> DateBk5 distributes a utility called "dbscan" that will scan the PIM
>>> databases and delete bad records. My problems disappeared after using
>>> this utility."
>>>
>>> This sounds like a possible culprit.  If evo crashed, perhaps due to:
>>> http://bugzilla.gnome.org/show_bug.cgi?id=319076
>>> then I guess it might have left data on your treo in a corrupt state.
>>>
>>> :(
>>>
>>> Matt
>>>
>>> Matt Davey        	What the world needs is more good readers,
>>> mcdavey mrao cam ac uk 		not more good writers. -- Borges.	
>>> _______________________________________________
>>> gnome-pilot-list mailing list
>>> gnome-pilot-list gnome org
>>> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>>>                              
>>>
>>>   
>>>     
>>>       
>> _______________________________________________
>> gnome-pilot-list mailing list
>> gnome-pilot-list gnome org
>> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>>                              
>>
>>   
>>     
>
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>                              
>
>