Diodon doens't start on ubuntu 20.04

[David Lippi]

$ diodon

$ echo $?
0

$ cat /var/log/syslog
[...]
Jun 25 09:31:22 SFPO-NB-TEC007 diodon[6115]: gtk_menu_popup: assertion 'GTK_IS_MENU (menu)' failed

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$ dpkg -l | grep diodon
ii diodon 1.10.0~ubuntu20.04.1 amd64 GTK+ Clipboard manager
ii libdiodon0:amd64 1.10.0~ubuntu20.04.1 amd64 GTK+ Clipboard manager (main library)

[Oliver Sauder (sao)]

When looking at your output I have a feeling Diodon is already running.

Because when running Diodon a second time when it is already running it is trying to open a popup and this because of a race condition doesn't always work as of bug #1630375

But once Diodon is running you should see a paper clip in the top right corner which you can use to access the history. Or is this by any chance not there on Ubuntu 20.04? Are you using another shell than Gnome Shell?

What you can do to be sure is to run `killall diodon` and then start Diodon through the Shell again.

[David Lippi (david.lippi)]

Thanks for your reply Oliver.

I have used diodon since a long time and i'm used to see the clipboard manager in my top bar.

I recently updated from ubuntu 18.04 to 20.04, and from some weeks diodon stop to work for me.

You was right, diodon already run on my machine, so, with
$ killall diodon
and then
$ diodon
i can see the true reason because it doesn't work:

$ killall diodon
$ diodon

** (diodon:30605): WARNING **: 09:33:42.591: zeitgeist-clipboard-storage.vala:80: Could not connect to blacklist interface: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was reached

** (diodon:30605): CRITICAL **: 09:34:07.623: log.vala:102: Unable to connect to Zeitgeist: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was reached

** (diodon:30605): CRITICAL **: 09:34:32.651: index.vala:61: Unable to connect to Zeitgeist FTS: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was reached

So the problem are with the zeitgeist service...

[Oliver Sauder (sao)]

Thanks for the update. This makes more sense.

Not sure whether this is a general issue with Zeitgeist on 20.04 or you might have a corrupted database.

Could you try the following:

killall zeitgeist-daemon
killall diodon
mv .local/share/zeitgeist/ .local/share/zeitgeist.old
diodon

and see whether this solves the issue?

[David Lippi (david.lippi)]

Yes, it works!

Files in .local/share/zeitgeist/ was very big (more than 1GB) maybe this was the problem?

Thanks a lot,
David

[Oliver Sauder (sao)]

Great! This can very well be that the time to load the database took to long and therefore ended in a timeout.

What you can do to avoid this in the future is to use the `activity-log-manager` where you can clear usage data by time.

Closing this issue as solved.