Found a workaround for this today - the problem occurs because the Headers table in the /home/user/.rtcom-eventlogger/el-v1.db becomes corrupt. Happily this is repairable, on the device:

First gain root access:
..then switch to the target directory:
Now dump the contents of the existing database to a raw SQL file:
Restore the SQL to a new database:
You may ignore SQL errors at this stage; they occur due to corruption in the source.

Now overwrite the broken DB (you may wish to back up the original file):
Finally, ensure that the file is owned by 'user' and is in the 'users' group so it may be read by Conversations
Now close and re-open your Conversations app - the changes should be immediate!

Hope this helps,

Alex