On Wed, 2012-08-22 at 15:43 -0600, Jeremy Whiting wrote:
> Ok, I've taken your last comments into account, and also have a log
> with debugging turned on to try to figure out the gvariant error. As
> can be seen in the pbaplog.txt PullAll takes a string filename as
> argument, and returns an object and an a{sv} of properties, so where
> is the gvariant error in the dbuscallback coming from?I'm out of ideas. The next step will have to be to debug what the content of that GVariant really is and figure out how the code arrived at that point. We know the source file and line, so I would run under gdb and set a breakpoint. If you don't beat me to it, then I'll try it myself today. -- 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
