TooManyResults error results in empty history

Could it be that the following question/answer solves your issue?

https://answers.launchpad.net/diodon/+question/701738

> Could it be that the following question/answer solves your issue?

“Add images to clipboard history” is not enable in my options.

OK to analyze your issue then we need a debug log.

Could you do the following:

1. close diodon
2. open a terminal
3. run following command: G_MESSAGES_DEBUG=all diodon > diodon_debug.txt
4. check that the history is empty
5. go back to terminal and close with Ctrl+C
6. Attach diodon_debug.txt here

For now my history came back ??!! Maybe because I change the number of copy/paste in the history? I tried to add more than 25 and the history disappear again.
I think this is the problem.

I cannot reproduce this on my machine. Could you increase the number of items then and if the history is actually empty create a debug log file following the steps above comment 3? Thanks.

G_MESSAGES_DEBUG=all diodon > diodon_debug.txt

** (diodon:51102): WARNING **: 08:48:11.365: zeitgeist-clipboard-storage.vala:317: Get recent items not successful, error: GDBus.Error:org.gnome.zeitgeist.DataModelError.TooManyResults: Query exceeded size limit of 4MiB (roughly ~29 events).

** (diodon:51102): WARNING **: 08:48:11.541: zeitgeist-clipboard-storage.vala:317: Get recent items not successful, error: GDBus.Error:org.gnome.zeitgeist.DataModelError.TooManyResults: Query exceeded size limit of 4MiB (roughly ~29 events).

The limit is 33.

Interesting, the error you have is the same as in the referenced question.

Could it be that you have a few items in your history where you have copied a large amount of files?

The reason this error occurs is, because DBus has a limitation on data being transferred. We call Zeitgeist with a DBus Service and that is why this error occurs.

Not quite sure how to handle such errors. But a first best fix could be that this error is shown to the user instead of just an empty history. Open for suggestions for other ideas how to go about it.

I have done some more research on this and it seems this is a regression since version 1.12.0.

See change here https://github.com/diodon-dev/diodon/commit/8ea13ecd747ea001c8214b5e959d3c6413924038

I will look into this what you can do as a workaround is running the following command:

echo "ZEITGEIST_LOG_DIRECT_READ=1" >> ~/.pam_environment

Logout and Login and it should work again even with large amount of data in history.

The issue should be fixed and a test version available in the daily ppa soon.

https://code.launchpad.net/~diodon-team/+archive/ubuntu/daily

How I fixed it is that ZEITGEIST_LOG_DIRECT_READ is now only set when the zeitgeist database does not exist. This fixes the issue that the history remains empty on the very first start. But when the sql database already exists the env variable won't be set so it will work as before.