Hey, thanks for the rsponce,
as of about 1-15-09, the critical failing has been resolved in the latest
git version. ( i wrote an git ebuild )
my current major roadblock happens to be the permissions, as msynctool cant
do anything right now, i have been playing with the udev rules, but have not
found where it goes wrong. i checked the product and vendor id, and they
match the ones in the script (the productid is 8004). i also do not get an
/dev/bb-* symlink.
On Tue, Jan 20, 2009 at 8:59 PM, Chris Frey <cdf...@foursquare.net> wrote:
> On Thu, Dec 25, 2008 at 04:29:09PM -0600, Nils wrote:
> > Hey everyone, I am currently running into two different issues.
>
> Hi Nils, welcome to Barry!
>
> (If you've been reading the list, you can see that I'm still catching up
> on a mail backlog. Apologies for the delay.)
>
>
> > december 11. when i run barrybackup without sudo it gives me the
> > Usb::Error caught: (-1, error sending control message: Operation not
> > permitted): Probe: GetConfiguration failed
> > error, and btool and others give the same.
>
> This is a permissions problem that should be handled with the udev script,
> which should be part of your binary install. You say you're using Gentoo,
> so I took a quick peek at the ebuild script. It appears to be installing
> the 10-blackberry.rules script properly, but you'll want to double check
> this.
>
> Note that different versions of udev require slightly different udev
> syntax,
> and there are two versions of the udev rules provided in the Barry sources.
> I don't know offhand which version is most appropriate for Gentoo.
>
> Also, it may be that your account is not a part of the plugdev group.
>
>
> > btool -l finds one blackberry device as
> > Device ID: 0x661680. PIN: 2576c6be, Description: RIM BlackBerry Device
> >
> > then i run btool -S and see Address Book among others, so i try to dump
> it
> > and i get:
> > Blackberry devices found:
> > Device ID: 0x6616d0. PIN: 2576c6be, Description: RIM BlackBerry Device
> > Using device (PIN): 2576c6be
> > Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
> > 00000000: 00 00 1a 00 09 ff 00 07 52 49 4d 20 44 65 73 6b
> ........RIM
> > Desk
> > 00000010: 74 6f 70 00 00 00 00 00 02 00 top.......
> >
> > Barry::Error caught: Bad packet size. Packet: 26. DataSize(): 26.
> Required
> > size: 44
>
> This should only happen if btool or one of the applications doesn't exit
> properly. The only solution for it so far is to replug the device, or
> try the 'breset' program.
>
>
> > when i run it with sudo it
> > appears for aout a second and then disappears returning a memory
> corruption
> > (see attached barrybackup file)
> >
> > sometimes i also get:
> > Blackberry devices found:
> > Device ID: 0x6616d0. PIN: 2576c6be, Description: RIM BlackBerry Device
> > Using device (PIN): 2576c6be
> > btool: symbol lookup error: btool: undefined symbol:
> > _ZN5Barry7Contact11ParseFieldsERKNS_4DataERm
>
> These looks like fundamental library and compile problems, and should be
> sorted out before any of the others.
>
> You're running 64bit, so perhaps there is a conflict somewhere between
> 32 and 64bit? Are there any old libraries lying around that could be
> interfering?
>
> I'm a little surprised that you get the PIN information before the
> undefined symbol. I would have thought the undefined symbol would
> stop btool from loading altogether.
>
>
> > And as one last thing, I was interested in helping the developement,
> > starting with a command line backup tool. :)
>
> Excellent! There are two options for you.
>
> 1) Look at the perlbarry package under contrib/ which was written by
> Ashley Willis. There are some pretty useful tools under there,
> which could be incorporated into the main tools/ area if someone
> has time. There's even a perl script that handles Windows backup
> files.
>
> 2) Alternatively, you could start porting the C++ code into a command line
> tool. The code should come apart fairly easily, removing the GUI-
> specific stuff. Ideally, if you go this route, I'd like to split
> the code so that it is possible to compile a command line version
> and the existing GUI version based on the same underlying backup
> and restore code, to prevent as much code duplication as possible.
>
> Let me know if you have questions about the code.
>
> - Chris
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
