Diodon stopped run. I run it from the command line and got the error

Asked by neo

Diodon stopped run. I run it from the command line and got the error

~$ diodon

(diodon:11922): GLib-CRITICAL **: 03:29:17.670: g_compute_checksum_for_string: assertion 'length == 0 || str != NULL' failed
Segmentation fault (core dumped)

A few times I reinstalled diodon, updated all the system to the latest. it doesn't help. So what is the problem, I didn't remember when it stopped working.

Question information

Language:
English Edit question
Status:
Solved
For:
Diodon Edit question
Assignee:
No assignee Edit question
Solved by:
neo
Solved:
Last query:
Last reply:
Revision history for this message
Oliver Sauder (sao) said :
#1

Thanks for reporting. This is odd, it seems that in your clipboard history there is an item which is an empty string, which should not happen.

To check further, could you create a debug log file with the following commands and attach it:

killall diodon
G_MESSAGES_DEBUG=all diodon > diodon_debug.txt

Thanks.

Revision history for this message
neo (neovich) said :
#2
Revision history for this message
Oliver Sauder (sao) said :
#3

Looks all good. Strange. I assume most likely the error is in the database, which might be corrupt.

What you can do to test this is the following:

killall diodon
killall zeitgeist-daemon
mv ~/.local/share/zeitgeist/activity.sqlite ~/.local/share/zeitgeist/activity.sqlite.backup

and then start diodon again to see whether it works.

Let me know how it goes. If it works, we know there is an error in our code which does not handle such erroneous data cases gracefully.

Revision history for this message
neo (neovich) said :
#4

after
killall zeitgeist-daemon
it works.

There is empty folder ~/.local/share/zeitgeist.
Yesterday I removed it and tried to run diodon, it didn't work.
killall zeitgeist-daemon helped. It works.

Revision history for this message
neo (neovich) said :
#5

Problem solved

Revision history for this message
Oliver Sauder (sao) said :
#6

OK great. In case this error occurs again, please let me know, so we can take a closer look.