Can you add more information? The following keys are currently
defined:
description - a description of the peer in a format and
language that is understood by the user.
You are sending obexd stub, but we need something about the remote
OBEX peer, like the
I have a new theory. Mainly since I haven't found the same problem
anywhere else online.
I think that months ago I compiled syncevolution from source over
the .deb that had previously been installed. When the .deb got updated,
it updated most things but may not have overwritten the custom
id is set to BT MAC address + channel number, which could identify
the remote OBEX peer uniquely.
I was about to ask about the format when I saw you example below. Can
we make it slightly more machine readable, perhaps like this?
00:0A:94:03:EB:E5+16
Please put it into
http://bugzilla.moblin.org/show_bug.cgi?id=6457
--- Comment #14 from yongsheng zhu yongsheng@intel.com 2009-10-19
00:33:05 ---
Either we write suppressions for these problems or we must configure valgrind
to only
trace our binary (might be hard).
We have to add *too many*
http://bugzilla.moblin.org/show_bug.cgi?id=6840
pohly patrick.o...@intel.com changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://bugzilla.moblin.org/show_bug.cgi?id=6672
pohly patrick.o...@intel.com changed:
What|Removed |Added
Resolution|FIXED |INTEGRATED
--- Comment
