On Fri, 2010-03-05 at 08:55 +0000, Pietro Battiston wrote:
> Il giorno ven, 05/03/2010 alle 09.41 +0100, Patrick Ohly ha scritto:
> > > pie...@vousci:~$ syncevolution nokia_7210c
> > > [ERROR] caught signal 11, shutting down
> > > Segmentation fault
> > 
> > That's probably one of the bugs in the OBEX transport which were fixed
> > in beta 2, and not related to your phone.
> 
> I'm using the package syncevolution-evolution 1:0.9.2+1.0beta2a-2 from
> [0], isn't it the one you're referring to?!

So you are up-to-date. Hmm, after looking at the stack trace again I see
that it jumps to address 0. That smells like a failure of the Bluetooth
compatibility layer - it does function address lookups.

What libbluetooth version(s) do you have installed?

$ ls /usr/lib/libbluetooth.so*
/usr/lib/libbluetooth.so  /usr/lib/libbluetooth.so.2  
/usr/lib/libbluetooth.so.2.11.2

Does it provide str2ba?

$ objdump -T /usr/lib/libbluetooth.so.? | grep str2ba
0000000000007b50 g    DF .text  00000000000000b3  Base        str2ba

We might be using an internal utility function which was removed from
the libbluetooth API, despite exporting it earlier.

As a workaround, you can specify the right channel in the SyncURL. Run
"sdptool search --bdaddr <mac address> SYNCML", note the channel number,
then append it to the syncURL with +<number>, like this:

$ sdptool search --bdaddr 00:0E:07:B1:90:17 SYNCML
Searching for SYNCML on 00:0E:07:B1:90:17 ...
Service Name: OBEX SyncML Client
Service RecHandle: 0x10007
Service Class ID List:
  UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 7
  "OBEX" (0x0008)

=> syncURL = obex-bt://00:0E:07:B1:90:17+7


-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to