Re: [SyncEvolution] Syncevolution cant find evolution data
On Mi, 2011-08-10 at 10:36 +0200, Tobias Hägele wrote:
Am 2011-08-09 11:31, schrieb Patrick Ohly:
>> [INFO] /usr/libexec/syncevo-dbus-server: ready to run
>> [ERROR] The source 'tasks' is not usable
>> [ERROR] cannot detach from resource that client is not attached to
>> [...]
>> [ERROR] cannot detach from resource that client is not attached to
>> [ERROR] 'Blubber' has no 'calendar+todo' source
>> [...]
>
> Can you describe step-by-step what you see in the UI and what you try to
> do?
sync-ui
Sync service ändern/bearbeiten
scroll down to my phone
expand
sub section "sync" The check boxes for which part should be synced
aren't shown.
but sometimes it works.
Hmm. Looks like an issue for Jussi.
>> [INFO] calendar: adding "x.x.x. Pr�fung"
>> ==5424== Invalid read of size 1
>> ==5424== at 0x42E5FD7: g_variant_is_trusted (gvariant-core.c:600)
>> ==5424== by 0x42E5179: g_variant_valist_new (gvariant.c:4093)
>> ==5424== by 0x42E53E7: g_variant_new_va (gvariant.c:4248)
>> ==5424== by 0x42E5494: g_variant_new (gvariant.c:4188)
>> ==5424== by 0x5FEA58E: e_gdbus_cal_call_create_object_sync
>> (e-gdbus-egdbuscal.c:3342)
>
> This looks very much like:
> https://bugzilla.gnome.org/show_bug.cgi?id=628299
>
> Note that the word Prüfung seems to have an invalid UTF-8 encoding.
>
> Can you run the sync with a higher log level and then send the -log.html
> file to me? Run:
> $ syncevolution --daemon=no loglevel=4 blubber calendar
I'll send it to you directly.
The log file showed that libecal/gdbus fail because a string is not in
UTF-8. They definitely shouldn't crash in this case, but that's a
different issue.
The solution in SyncEvolution is to convert from the phone's character
set. Now I remember that this came up before, and I have a work item for
fixing it in my backlog - sorry for not getting to it sooner:
https://bugs.meego.com/show_bug.cgi?id=14414
I got the impression that you have a Sony Ericsson phone. Is that right?
I'll try to prepare an experimental release with a fix for this today or
tomorrow.
--
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.