Hi Chris -

Thanks for your help.  This was a very big help in pushing me up the
learning curve on Barry.

Incidentally, in the debugging process, I realized that my recurring
appointments were causing problems (and may have been the original
culprit).  I ended up clearing out the entire calendar on both Evolution
and the Blackberry and did some testing one record at a time to no
avail.  I looked around the mail history and couldn't find much about
the recurring appointments, so I'm assuming it is not supported in
either Barry or the current Opensync module.  Is this true? 

Thanks


-----Original Message-----
From: barry-devel-requ...@lists.sourceforge.net
Reply-to: barry-devel@lists.sourceforge.net
To: barry-devel@lists.sourceforge.net
Subject: Barry-devel Digest, Vol 43, Issue 13
Date: Sun, 13 Dec 2009 06:34:19 +0000


Send Barry-devel mailing list submissions to
        barry-devel@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/barry-devel
or, via email, send a message with subject or body 'help' to
        barry-devel-requ...@lists.sourceforge.net

You can reach the person managing the list at
        barry-devel-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Barry-devel digest..."


Today's Topics:

   1. Re: Syncing a Curve 8520 on Kubuntu Karmic (Chris Frey)
   2. Re: Mapping Write Error (Chris Frey)
   3. Re: Modem tethering issue under UBUNTU 9.10 (Michael L. Stokes)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Dec 2009 18:10:20 -0500
From: Chris Frey <cdf...@foursquare.net>
Subject: Re: [Barry-devel] Syncing a Curve 8520 on Kubuntu Karmic
To: Barry project development discussion
        <barry-devel@lists.sourceforge.net>
Message-ID: <20091211231020.ga23...@foursquare.net>
Content-Type: text/plain; charset=us-ascii

On Fri, Dec 11, 2009 at 08:47:20AM -0500, Rene Vergara wrote:
> Then I tried to sync with KDEPIM, but it didn't work right. I saw a lot of 
> transactions scroll by, then it stopped at one and I had to Ctrl+C out of it.

Opensync 0.22 has trouble sometimes, when syncing in both directions at
once.  And hangs like this are familiar, unfortunately.

If you can do the first sync in one direction only (such as KDEPIM empty,
or the blackberry empty), things will usually behave more smoothly.

It seems like you had more success on the second attempt, so keep trying
that first, but if you keep hitting the hang, try a one-way sync only.


> The previous synchronization was unclean. Slow-syncing

Similar warnings go for slow-syncing.


> Error writing entry 0PAh0FiPnR to member 1 (barry-sync): This object type is 
> disabled in the barry-sync config

This is likely the cause of the trouble.  Both calendar and contacts are
being synced, from the opensync side, but the Barry plugin is only configured
for one of them.

Look for the following line in your barry-sync plugin config:

        Device 3009efe3 1 1

Make sure the last two numbers are both 1, and try again.  This will enable
both object types to sync.

- Chris






------------------------------

Message: 2
Date: Fri, 11 Dec 2009 18:24:03 -0500
From: Chris Frey <cdf...@foursquare.net>
Subject: Re: [Barry-devel] Mapping Write Error
To: Barry project development discussion
        <barry-devel@lists.sourceforge.net>
Message-ID: <20091211232403.ga23...@foursquare.net>
Content-Type: text/plain; charset=us-ascii

On Fri, Dec 11, 2009 at 06:45:01PM +0100, LAUGHLIN, Bill wrote:
> Hi -
> 
> I'm hoping someone has had this problem and can help me debug.  I'm
> using a Curve 8310 (4.5.0.153) on Ubuntu Karmic with barry version
> 0.16-2009120724 syncing with Evolution.  Sync was working fine, however
> now I'm getting this error:
> 
> Mapping Write Error: unable to get state table index for RecordId: 17

Hi Bill,

Thanks for the report.

To help see what's happening exactly, could you turn on opensync tracing?
Set the environment variable OSYNC_TRACE to an empty directory before
running your sync.

Then grep the logs for "GetMappedRecordId" to find which log matters.
Open that log file, and search backwards through the log until you find
one what reports something about 17.

I'm looking for one of the following messages:

        found existing uid in map:
        parsed uid as:
        parsed uid already exists in map, skipping
        made new record id:

Also, try the following commands: (they display the Record State Table for
each specified database)

        btool -T Calendar
        btool -T "Address Book"

And look in the RecordId column for a value of 0x00000011 (17 in hex).

That might help narrow things down.

Thanks!
- Chris






------------------------------

Message: 3
Date: Sun, 13 Dec 2009 00:33:59 -0600
From: "Michael L. Stokes" <sto...@aris.net>
Subject: Re: [Barry-devel] Modem tethering issue under UBUNTU 9.10
To: Barry project development discussion
        <barry-devel@lists.sourceforge.net>
Message-ID: <4b248ad7.6070...@aris.net>
Content-Type: text/plain; charset="iso-8859-1"

I ran the modemtest program and scripted the sesson (attached file).
It looks like it ran without error.  I also ran the backup and that seemed
to work OK except that it reported a fews records that needed help
from the group to figure out.

I was successful at building barry myself, but thinking that there might 
have been
some issues, I grabbed the built barry binaries that Chris recommended, 
and it
acts just like the version I built.  I added the password to the 
barry-verizon ppp
option file, otherwise I made no other changes from the distribution.

When I run pon barry-verizon (both with sudo and as root), after around 
15 secs
the script quits with a chat script error of 0x3, and pppob hangs.  It 
consumes
a processor until I kill it off.

I believe there is an something that is not working properly and I would 
very much
like to continue to work with the developers to identify and correct 
this problem.

Thanks
Mike

Chris Frey wrote:
> On Wed, Dec 09, 2009 at 06:46:39AM -0600, Michael L. Stokes wrote:
>   
>> No ideas huh?
>>     
>
> Heh... unfortunately, none yet. :-)
>
>
>   
>> Is there a way to test if pppob is working?  Any other tests I should run?
>>     
>
> There is a script by Andy Herkey in the contrib/ directory of the source
> tree call modemtest.rb.  This tests pppob and the modem functionality
> of various commands.  You might try this first.
>
> - Chris
>
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: typescript
Type: application/octet-stream
Size: 48300 bytes
Desc: not available

------------------------------

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev


------------------------------

_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel


End of Barry-devel Digest, Vol 43, Issue 13
*******************************************
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to