Diodon often shows my clipboard history as 'empty'

Strange I haven't seen this before.

When it shows empty: when you close Diodon and open it is it then still empty?

If yes you can do the following:

1. close diodon
2. open a terminal
3. run G_MESSAGES_DEBUG=all diodon > diodon_debug.txt
4. when it is then still empty you can attach the debug log to this question.

Alright. So, this is what the terminal outputs (it only would work with sudo):

mateus@Mateus--Ubuntu:~$ sudo G_MESSAGES_DEBUG=all diodon > diodon_debug.txt
[sudo] password for mateus:

** (diodon:226332): WARNING **: 19:42:02.353: zeitgeist-clipboard-storage.vala:84: Could not connect to blacklist interface: Failed to execute child process “dbus-launch” (No such file or directory)

** (diodon:226332): CRITICAL **: 19:42:02.355: file log.c: line 1128: unexpected error: Failed to execute child process “dbus-launch” (No such file or directory) (g-exec-error-quark, 8)

And this is is the return from the .txt file:

(diodon:226332): GLib-GIO-DEBUG: 19:42:02.313: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
(diodon:226332): GLib-DEBUG: 19:42:02.348: unsetenv() is not thread-safe and should not be used after threads are created
** (diodon:226332): DEBUG: 19:42:02.349: main.vala:86: Activate DiodonApplication (Version 1.12.0)
(diodon:226332): GLib-GIO-DEBUG: 19:42:02.350: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(diodon:226332): dconf-DEBUG: 19:42:02.350: watch_fast: "/net/launchpad/diodon/clipboard/" (establishing: 0, active: 0)
(diodon:226332): dconf-DEBUG: 19:42:02.350: watch_fast: "/net/launchpad/diodon/plugins/" (establishing: 0, active: 0)
(diodon:226332): GLib-DEBUG: 19:42:02.351: setenv()/putenv() are not thread-safe and should not be used after threads are created
(diodon:226332): dconf-DEBUG: 19:42:02.351: watch_established: "/net/launchpad/diodon/clipboard/" (establishing: 1)
(diodon:226332): dconf-DEBUG: 19:42:02.351: watch_established: "/net/launchpad/diodon/plugins/" (establishing: 1)

If and when it starts working again (and I notice it), I'll run the same command one more time.
Thanks!

Thanks for your additional information.

It is not a good idea to run Diodon with sudo as it will mess up the permission and not bring the correct debug result.

What was the issue when you run it with normal user? One thing which is really important is to stop diodon otherwise it won't work.

Following commands in a terminal might be clearer:

killall diodon
killall zeitgeist-daemon
G_MESSAGES_DEBUG=all diodon > diodon_debug.txt

Check diodon and see whether it is empty. If yes then press Ctrl+C and attach the debug log here.

The thing is - it wouldn't generate that log without sudo for some reason. It wouldn't even create the .txt file. That was the last time it wasn't working properly; and also the last time that it would spit any kind of error message.
But well... Seems like Diodon is a bit of a prankster, isn't it? Since then, it's been running trouble-free; no issues whatsoever.
I appreciate your help tho! Thanks!

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Alright. It eventually happened again. Here's the output:

** (diodon:3630765): WARNING **: 11:29:54.976: 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 ~9 events).

** (diodon:3630765): WARNING **: 11:30:07.102: 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 ~10 events).

What would be the resolution for this problem?

Cool that you were able to reproduce it again. In the Diodon preferences have you enabled the option “Add images to clipboard history”?

If enabled, this might be an option which could cause this error. If not, we will have to look further.

Everything indicates that that was it. There were some screenshots on the clipboard. When I set the 'number of recent items' to a certain threshold that contained more images than it could handle, the clipboard was shown as 'empty' and the error message showed up on the terminal. Since I use those clipboard images often, I'll keep that feature enabled but now I'll know how to circumvent the problem. Thanks a lot!

Just wanted a follow up on this question. As discovered in #1981964 this is actually a regression since version 1.12.0.

What you can do to avoid it is running the following command:

echo "ZEITGEIST_DATABASE_PATH=:memory:" >> ~/.pam_environment

Logout/Login the user session and even large amount of data should be shown in clipboard history again.

I will look into this and will track the status in bug #1981964