user data migration from ring to jami takes forever when database is corrupted by an older version of ring
[account@box:~] $ jami
** Message: 21:16:52.743: Jami GNOME client version: b784e232f8412135d76bd643baec14ef9ff0940a
** Message: 21:16:52.744: git ref: unknown
Migrate "/home/account/.local/share/gnome-ring" / "." to "/home/account/.local/share/jami/."
Migrate "/home/account/.local/share/gnome-ring" / ".." to "/home/account/.local/share/jami/.."
Migrate "/home/account/.local/share/gnome-ring" / "profiles" to "/home/account/.local/share/jami/profiles"
Migrate "/home/account/.local/share/gnome-ring" / "ring.db" to "/home/account/.local/share/jami/ring.db"
Migrate "/home/account/.local/share/gnome-ring" / "vCard" to "/home/account/.local/share/jami/vCard"
database "/home/account/.local/share/jami/ring.db" version set to: "1.1"
Migrating account: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." ...
database "/home/account/.local/share/jami/Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken./history.db" version set to: "1"
Look at the unexpected /home/account/.local/share/jami/Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken./history.db
file path.
Edit: migration takes forever.