First time running, does not show any items in popup

[Thierry]

I am running Debian jessie/testing.

Here is scenario to reproduce:
1. choose a system where diodon has never been run/installed
2. compile/install diodon
3. launch diodon
4. hit Ctrl+C on several items
5. hit diodon keyboard shortcut <Ctrl><Alt>V. This brings the popup, but nothing in the history
6. kill/stop diodon
7. launch again diodon
8. hit diodon keyboard shortcut <Ctrl><Alt>V. This brings the popup, with the history filled from step 4. above

What I was expecting is that at step 5. I was able to see the history.
I have confirmed this bug on my system, *and* on an empty VM with Debian jessie.

[Oliver Sauder (sao)]

This issue is related to Bug 1383013 as it seems Zeitgeist service doesn't notify Diodon about changes in some circumstances.

[Thierry (thdox)]

Bug 1383013 is at boot time. This bug 1435033 is whenever you run diodon for the first time. Only the first time, second run, third run with some reboot in between will not reproduce the bug.

I can see that you are not able to reproduce the duplicated Bug 1383013. But this bug can be reproduced on a virgin Virtual Machine with Debian jessie, using your building instructions from question 263240.

Did you tried to reproduce ?

[Oliver Sauder (sao)]

I misunderstood the bug report than as I thought this happens every time after boot up - removed duplicate again then.

As you already have a VM could I ask you to reproduce this issue again and the first time start Diodon the following way:

G_MESSAGES_DEBUG=all diodon > diodon_debug.log

when error is still reproducible when running this comment please attach diodon_debug.log to this bug. Thanks.

[Oliver Sauder (sao)]

Seems Ubuntu 15.04 is also suffering from this error.

[Oliver Sauder (sao)]

This issue can be reproduced by resetting the zeitgeist database and start diodon again.

First time Diodon runs now nothing gets added. When closing and opening again, all items are now shown.

Seems to be an Zeitgeist bug it seems. Have to see whether there might be a workaround in Diodon for this.

[Oliver Sauder (sao)]

Forgot, steps to reproduce:
killall zeitgeist-daemon zeitgeist-datahub zeitgeist-fts diodon
rm ~/.local/share/zeitgeist
diodon

[Oliver Sauder (sao)]

This issue is not major as there is an easy workaround. It seems though from feedback many users when first installing Diodon think it is not working and simply uninstall Diodon again.

So therefore I did some investigation into this. Per default libzeitgeist opens a local db reader. The very first time the database file is not created on the file system yet, the local zeitgeist database reader simply reads from a empty database ending up without results. The second run from Diodon the database file will be there and from there onward it works.

It is actually possible to disable a local reader (which I think is dangerous anyway) by setting `ZEITGEIST_LOG_DIRECT_READ` to `0`. I added a patch that Diodon does this internally.

This will be soon available in the daily ppa for testing.

[c4pp4 (c4pp4)]

The same bug appears again:

zeitgeist_1.0.4-5ubuntu1
diodon_1.13.0-1

I think the problem is that file.query_exists() (see libdiodon/zeitgeist-clipboard-storage.vala #74) is TRUE even if it runs for the first time, because .local/share/zeitgeist/activity.sqlite file already exists.