[SyncEvolution] Syncing to Memotoo w SyncEvolution post-Fedora 37 upgrade (fwd)

[Max Pyziur]

Greetings,

Is this list still active, and is SyncEvolution still maintained?

If not, what other ways can there be of syncing my Evolution PIM data with 
Memotoo.

Thank you,

Max Pyziur
pyz at brama.com

---------- Forwarded message ----------
Date: Thu, 9 Feb 2023 13:29:03 -0500 (EST)
From: Max Pyziur <pyz at brama.com>
To: syncevolution at lists.freedesktop.org
Subject: [SyncEvolution] Syncing to Memotoo w SyncEvolution post-Fedora 37
     upgrade


Greetings,

I've been trying to sync my Evolution data with memotoo, and I keep getting
failure notices.

My attention to this has been occasional since there have been other more
pressing matters to resolve. But I would like to see if this can be fixed.

I'm using both the UI as well as the CLI. I'm not sure how to check the error or
problem.

When using the CLI, here is my output:
syncevolution --run  --sync refresh-from-local memotoo
[INFO] memo: inactive
[INFO] todo: inactive
[ERROR syncevo-dbus-server] child process quit because of signal 11
[ERROR] The connection is closed

Not knowing if this is material, checking via ps waux:
~> ps waux | grep sync
pyz         4617  0.0  0.3 527156 28108 ?        Ssl  15:40   0:00
/usr/libexec/syncevo-dbus-server
pyz         4829  0.0  0.0 222024  2088 pts/1    S+   15:42   0:00 grep
--color=auto sync


I can access my data on the memotoo website. It appears to sync with my phone.

I recently upgraded (in the last two weeks) to F37. I don't know if this is the
first sync that I have tried since, however.

When using coredumpctl the relevant syncevolution information that comes up is:

> coredumpctl | grep sync
Thu 2023-02-09 13:11:15 EST  26270 1000 1000 SIGSEGV present
/usr/libexec/syncevo-dbus-helper           3.3M

I am submitting an automated report using Fedora's Problem Reporting 1.4.2; that
process is continuing to run.

I've been told that a Fedora ABRT report with a backtrace would be useful.
However, I don't know how to generat that.

Much thanks,

Max Pyziur
pyz at brama.com


Problem Reporting log:
--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No',
a stack trace will be generated locally. (It may download a huge amount of
data). 'YES'
Querying server settings
Preparing an archive to upload
Uploading 2.6 MiB
Upload successful
Retrace job #285613797 started
Analyzing crash data
...