diodon will not start

Asked by Spiv

I installed Diodon from KDE Konsole, installation was ok.
Diodon is not visible in the App Launcher.

After typing diodon in Konsole, I get:
spiv@Ultra:~$ diodon
diodon: error while loading shared libraries: libpeas-1.0.so.0: cannot open shared object file: No such file or directory

Can anyone suggest a fix please?

Question information

Language:
English Edit question
Status:
Answered
For:
Diodon Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

You probably need to install a software package that contains libpeas-1.0.so.0

On Ubuntu this would be done with
sudo apt install libpeas-1.0-0

Revision history for this message
Spiv (spiv13) said :
#2

After I run
   sudo apt install libpeas-1.0-0

This is what I got:
   libpeas-1.0-0 is already the newest version (1.26.0-2).
libpeas-1.0-0 set to manually installed.
The following package was automatically installed and is no longer required:
  libappindicator3-1
Use 'sudo apt autoremove' to remove it.
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

Then typing diodon returned:
~$ diodon
diodon: error while loading shared libraries: libpeas-1.0.so.0: cannot open shared object file: No such file or directory

I am running Kubuntu (KDE) 20.04.
Diodon was working on a previous installation, but since I reinstalled the OS to clean my machine,I have not been able to get it to work...

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

For further diagnostics, what is the output of the commands

uname -a
lsb_release -crid
ls -l /usr/lib/*/libpeas-1.0.so.0*
ldd `which diodon`

Revision history for this message
Spiv (spiv13) said :
#4

Thank you for your time, I really appreciate it!!

Here are the answers:

spiv@spiv-Ultra:~$ uname -a
Linux spiv-Ultra 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
spiv@spiv-Ultra:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
spiv@spiv-Ultra:~$ ls -l /usr/lib/*/libpeas-1.0.so.0*
ls: cannot access '/usr/lib/*/libpeas-1.0.so.0*': No such file or directory
spiv@spiv-Ultra:~$ ldd `which diodon`
        linux-vdso.so.1 (0x00007ffeaf6ac000)
        libdiodon.so.0 => /lib/x86_64-linux-gnu/libdiodon.so.0 (0x00007f399469d000)
        libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f39944bc000)
        libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f399445c000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f3994333000)
        libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x00007f3993b82000)
        libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x00007f3993a7d000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3993889000)
        libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007f3993861000)
        libpeas-1.0.so.0 => not found
        libpeas-gtk-1.0.so.0 => not found
        libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007f3993724000)
        libXtst.so.6 => /lib/x86_64-linux-gnu/libXtst.so.6 (0x00007f399351e000)
        libzeitgeist-2.0.so.0 => not found
        libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f3993516000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f39934fa000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f39934f4000)
        libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007f3993494000)
        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f3993469000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f399344b000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f3993428000)
        libffi.so.7 => /lib/x86_64-linux-gnu/libffi.so.7 (0x00007f399341c000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f39933a9000)
        libpangocairo-1.0.so.0 => /lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007f3993397000)
        libXi.so.6 => /lib/x86_64-linux-gnu/libXi.so.6 (0x00007f3993385000)
        libXfixes.so.3 => /lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f399337b000)
        libcairo-gobject.so.2 => /lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x00007f399336f000)
        libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x00007f399324c000)
        libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007f3993222000)
        libatk-bridge-2.0.so.0 => /lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x00007f39931eb000)
        libepoxy.so.0 => /lib/x86_64-linux-gnu/libepoxy.so.0 (0x00007f39930b8000)
        libfribidi.so.0 => /lib/x86_64-linux-gnu/libfribidi.so.0 (0x00007f3993099000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3992f4a000)
        libpangoft2-1.0.so.0 => /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007f3992f31000)
        libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007f3992ee2000)
        libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f3992ddd000)
        libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f3992d96000)
        libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f3992cd5000)
        libXinerama.so.1 => /lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007f3992cd0000)
        libXrandr.so.2 => /lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007f3992cc3000)
        libXcursor.so.1 => /lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f3992cb6000)
        libXcomposite.so.1 => /lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007f3992cb1000)
        libXdamage.so.1 => /lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f3992cac000)
        libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007f3992c68000)
        libwayland-cursor.so.0 => /lib/x86_64-linux-gnu/libwayland-cursor.so.0 (0x00007f3992c5d000)
        libwayland-egl.so.1 => /lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007f3992c58000)
        libwayland-client.so.0 => /lib/x86_64-linux-gnu/libwayland-client.so.0 (0x00007f3992c47000)
        libXext.so.6 => /lib/x86_64-linux-gnu/libXext.so.6 (0x00007f3992c32000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f3992c27000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f39946e6000)
        libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f3992bfb000)
        libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f3992ba4000)
        libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f3992b14000)
        libpixman-1.so.0 => /lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007f3992a6d000)
        libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f3992a33000)
        libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007f3992a2e000)
        libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007f3992a1f000)
        libXrender.so.1 => /lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f3992815000)
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f39927c4000)
        libatspi.so.0 => /lib/x86_64-linux-gnu/libatspi.so.0 (0x00007f399278d000)
        libthai.so.0 => /lib/x86_64-linux-gnu/libthai.so.0 (0x00007f3992780000)
        libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007f3992753000)
        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f3992725000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f399271c000)
        libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007f3992716000)
        libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f399270c000)
        libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f399265f000)
        libdatrie.so.1 => /lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007f3992655000)
        libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f399263b000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f3992614000)
        liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f39925f1000)
        libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f39924d3000)
        libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f39924b0000)

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

Quote:
        libpeas-1.0.so.0 => not found
        libpeas-gtk-1.0.so.0 => not found
ls: cannot access '/usr/lib/*/libpeas-1.0.so.0*': No such file or directory

It seems that something went wrong with the installation of libpeas-1.0-0

Try
sudo apt install --reinstall libpeas-1.0-0
ls -l /usr/lib/*/libpeas-1.0.so.0*

if this still doesn't find the files, then please provide the output of the command

apt-cache policy libpeas-1.0-0

Revision history for this message
Spiv (spiv13) said :
#6

It seems that the file is installed, but Diodon still refuse to work....:

spiv@spiv-Ultra:~$ sudo apt install --reinstall libpeas-1.0-0
[sudo] password for spiv:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 1 to reinstall, 0 to remove and 1 not to upgrade.
Need to get 0 B/60.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 253879 files and directories currently installed.)
Preparing to unpack .../libpeas-1.0-0_1.26.0-2_amd64.deb ...
Unpacking libpeas-1.0-0:amd64 (1.26.0-2) over (1.26.0-2) ...
Setting up libpeas-1.0-0:amd64 (1.26.0-2) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
spiv@spiv-Ultra:~$ ls -l /usr/lib/*/libpeas-1.0.so.0*
lrwxrwxrwx 1 root root 23 Mar 10 2020 /usr/lib/x86_64-linux-gnu/libpeas-1.0.so.0 -> libpeas-1.0.so.0.2600.0
-rw-r--r-- 1 root root 100584 Mar 10 2020 /usr/lib/x86_64-linux-gnu/libpeas-1.0.so.0.2600.0

spiv@spiv-Ultra:~$ diodon
diodon: error while loading shared libraries: libzeitgeist-2.0.so.0: cannot open shared object file: No such file or directory

spiv@spiv-Ultra:~$ apt-cache policy libpeas-1.0-0
libpeas-1.0-0:
  Installed: 1.26.0-2
  Candidate: 1.26.0-2
  Version table:
 *** 1.26.0-2 500
        500 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
spiv@spiv-Ultra:~$

Also, Diodon doesn't show in the Application Launcher BUT it shows as 'Installed' in Discover (Software Centre).

Revision history for this message
Manfred Hampl (m-hampl) said :
#7

The error message has changed!

Now it complains about libzeitgeist-2.0.so.0 and the libpeas files seem ok now.

sudo apt install --reinstall libzeitgeist-2.0-0

I am puzzled by the following:
There are two directories for shared libraries on Ubuntu: /lib and /usr/lib
Most of the shared libraries required by diodon are in /lib, just libpeas, libpeas-gtk and libzeitgeist usually are in /usr/lib. Just these were missing. Are you aware of any problem with the /usr or /usr/lib directories on your system?

Revision history for this message
Spiv (spiv13) said :
#8

This is what happened:

spiv@spiv-Ultra:~$ sudo apt install --reinstall libzeitgeist-2.0-0
[sudo] password for spiv:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 1 to reinstall, 0 to remove and 0 not to upgrade.
Need to get 0 B/115 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 253879 files and directories currently installed.)
Preparing to unpack .../libzeitgeist-2.0-0_1.0.2-3ubuntu2_amd64.deb ...
Unpacking libzeitgeist-2.0-0:amd64 (1.0.2-3ubuntu2) over (1.0.2-3ubuntu2) ...
Setting up libzeitgeist-2.0-0:amd64 (1.0.2-3ubuntu2) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
spiv@spiv-Ultra:~$ diodon

(diodon:67820): GLib-CRITICAL **: 00:36:44.949: g_file_test: assertion 'filename != NULL' failed

** (diodon:67820): WARNING **: 00:36:44.952: zeitgeist-clipboard-storage.vala:313: Get recent items not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:67820): WARNING **: 00:36:44.952: zeitgeist-clipboard-storage.vala:125: Could not determine state of privacy mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

You asked:
[Are you aware of any problem with the /usr or /usr/lib directories on your system?]

Well, I am not a full bottle.... so my answer might not make a lot of sense...
I use a Sumsung ultrabook NP540U3C
A friend helped me to install the OS on my 22GB SSD which is mounted from /dev/sdb2
While everthing else is on my 500GD HDD mounted from /dev/sda1

/lib, /usr, and /usr/lib are in my SSD

Revision history for this message
Manfred Hampl (m-hampl) said :
#9

Does it work now?

Revision history for this message
Spiv (spiv13) said :
#10

Unfortunately not.

Still not available in Launcher.
In the Software Centre is installed, but will not launch.
In Terminal I get:
spiv@spiv-Ultra:~$ diodon

(diodon:11846): GLib-CRITICAL **: 15:45:27.603: g_file_test: assertion 'filename != NULL' failed

** (diodon:11846): WARNING **: 15:45:27.605: zeitgeist-clipboard-storage.vala:313: Get recent items not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:11846): WARNING **: 15:45:27.606: zeitgeist-clipboard-storage.vala:125: Could not determine state of privacy mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:11846): WARNING **: 15:48:04.868: zeitgeist-clipboard-storage.vala:382: Add item items not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:11846): WARNING **: 15:48:10.344: zeitgeist-clipboard-storage.vala:382: Add item org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provi not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:11846): WARNING **: 15:48:16.758: zeitgeist-clipboard-storage.vala:382: Add item /lib, /usr, and /usr/lib are in my SSD not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

** (diodon:11846): WARNING **: 15:49:17.230: zeitgeist-clipboard-storage.vala:382: Add item ** (diodon:67820): WARNING **: 00:36:44.952: zeitgeist-clipboard-storage.vala:125: Could not determine state of privacy mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

 not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

So, it starts, but doesn't work.....

Additionally, I installed several programs from the Software Centre and they all work, just Diodon is playing up...
I have no idea on what the next step can be....

Revision history for this message
Manfred Hampl (m-hampl) said :
#11

Does diodon now run or not?

First lines in comment #10: "will not launch"
Lats lines in comment #10: "it starts"

What exactly happens when you try starting it (apart from those warnings about zeitgeist)

For further diagnostics please provide the output that you receive for the commands

uname -a
lsb_release-crid
apt-cache policy diodon diodon-dev gir1.2-diodon-1.0 libdiodon0

Revision history for this message
Spiv (spiv13) said :
#12

It starts, but doesn't work.
This is the error I get when I 'copy' some text:
** (diodon:27920): WARNING **: 21:52:41.746: zeitgeist-clipboard-storage.vala:382: Add item {Software Centre and they all work} not successful, error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.zeitgeist.Engine was not provided by any .service files

Note I inserted the { } to show what I copied.

I had the Diodon icon in the tray, but looking into it it is <empty>

This are the results of your queries:

spiv@spiv-Ultra:~$ uname -a
Linux spiv-Ultra 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

spiv@spiv-Ultra:~$ lsb_release-crid
lsb_release-crid: command not found

spiv@spiv-Ultra:~$ apt-cache policy diodon diodon-dev gir1.2-diodon-1.0 libdiodon0
diodon:
  Installed: 1.11.0~ubuntu20.04.1
  Candidate: 1.11.0~ubuntu20.04.1
  Version table:
 *** 1.11.0~ubuntu20.04.1 500
        500 http://ppa.launchpad.net/diodon-team/stable/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
     1.9.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
diodon-dev:
  Installed: (none)
  Candidate: 1.11.0~ubuntu20.04.1
  Version table:
     1.11.0~ubuntu20.04.1 500
        500 http://ppa.launchpad.net/diodon-team/stable/ubuntu focal/main amd64 Packages
     1.9.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gir1.2-diodon-1.0:
  Installed: (none)
  Candidate: 1.11.0~ubuntu20.04.1
  Version table:
     1.11.0~ubuntu20.04.1 500
        500 http://ppa.launchpad.net/diodon-team/stable/ubuntu focal/main amd64 Packages
     1.9.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
libdiodon0:
  Installed: 1.11.0~ubuntu20.04.1
  Candidate: 1.11.0~ubuntu20.04.1
  Version table:
 *** 1.11.0~ubuntu20.04.1 500
        500 http://ppa.launchpad.net/diodon-team/stable/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
     1.9.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
spiv@spiv-Ultra:~$

Revision history for this message
Manfred Hampl (m-hampl) said :
#13

Maybe there is another problem with zeitgeist

What is the output of the command

dpkg -l | grep zeitg

Revision history for this message
Spiv (spiv13) said :
#14

Sorry for log time to reply, I am in Australia..

spiv@spiv-Ultra:~$ dpkg -l | grep zeitg
ii libzeitgeist-2.0-0:amd64 1.0.2-3ubuntu2 amd64 library to access Zeitgeist - shared library
ii zeitgeist-core 1.0.2-3ubuntu2 amd64 event logging framework - engine
spiv@spiv-Ultra:~$

Revision history for this message
Manfred Hampl (m-hampl) said :
#15

Run the command

sudo apt install --reinstall libzeitgeist-2.0-0 zeitgeist-core

and then try starting diodon again.
Does this change anything?

Revision history for this message
Spiv (spiv13) said :
#16

That DID work!!

THANK YOU!!

Great I now can use Diodon, however, as soon as I close terminal, it closes Diodon :(.

Also, I still cannot find it in the App Launcher.
Is there a way to register it in the App Launcher, or get it to start on power up and replace the standard clipboard (as I had it before the re-install of the OS) ?

Revision history for this message
Manfred Hampl (m-hampl) said :
#17

Ok, glad to see that it is working again.

Summing up the problem and the steps for solution I have to say that there were very strange things happening on your system. Certain files were missing and could be restored only with reinstalling packages. It might well be that there are even more broken packages than the ones that you already have re-installed.

You might consider re-installing all packages that currently are installed on your system to make sure that no additional files are missing.

And for the App Launcher: Do you find diodon when you press the super key (windows key) and type diodon into the pop-up window?

Revision history for this message
Spiv (spiv13) said :
#18

Strange- in the App Launcher (or super key) if I type any thing shorter that the full 'Diodon', nothing, but if I type the full name, then I get "run Diodon", which works ok.

I found a list of 25 old clipboards saved in it, but they were old ones, from my previous OS install...obviously from my old backup files.

Diodon is running in parallel with the clipboard,they both save new clipboard content.

I couldn't find a way to replace the system 'clipboard' with Diodon, but I am sure that I did that before.
Do you know how to do that?

Revision history for this message
Manfred Hampl (m-hampl) said :
#19

I couldn't find a way to replace the system 'clipboard' with Diodon, but I am sure that I did that before.
Do you know how to do that?

Isn't that done in the diodon settings?

Revision history for this message
Spiv (spiv13) said :
#20

The preferences are unrelated to the os clipboard, except perhaps "Synchronise clipboards".

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

Thanks Manfred for helping Spiv13. Really appreciated.

In terms of why Diodon doesn't show up in the KDE App Launcher. This is deliberate as KDE Plasma already ships with a clipboard manager and some extra steps are needed so it does not interfere with Diodon. And Diodon afterall runs best on a GTK Desktop environment.

However you can still run Diodon on KDE Plasma. Simply edit the following file:

sudo vim /usr/share/applications/diodon.desktop

and remove the line:

NotShowIn=KDE;

To disable the KDE Plasma clipboard I have done some googling and it seems the following post might help you:

https://www.linuxquestions.org/questions/slackware-14/kde-plasma-5-clipboard-4175655887/

I have tested this on Kubuntu 20.04 on a virtual machine and it seems to work fine.

Revision history for this message
Spiv (spiv13) said :
#22

Hi Oliver,
Thank you for your help!

The command:
   spiv@spiv-Ultra:~$ sudo vim /usr/share/applications/diodon.desktop
Returned:
   [sudo] password for spiv:
   sudo: vim: command not found

However, I found the file in Dolphin, edited it with Kate and deleted line 60: NotShowIn=KDE;

Now Diodon is shown in the App Launcher, Thank you.

However, I followed that link, but I could not "You can disable the klipper widget (Plasma 5's clipboard widget) by right clicking the system tray (the drop down menu arrow on taskbar)>"
because I cannot find any drop down arrow to right click...
Right clicking the task bar brings up "Task Manager" but no option to "Configure system tray"

I could not find a way to "Configure system tray" anywhere.

Can you help with this problem?

Provide an answer of your own, or ask Spiv for more information if necessary.

To post a message you must log in.