This question has been asked a couple of times also on AskUbuntu so I thought it is worth a blog post to elaborate on why in certain circumstances Diodon doesn’t save anything to the clipboard history and what you can do about it.
Since version 1.1.0 the way how Diodon stores its clipboard storage has changed – it used to be that the history was simply stored in the storage.xml file located in ~/.local/share/diodon/. This was fairly simple but had the limitation that the clipboard history was limited to a certain number of entries. If we wanted to increase this number but still using the single xml file Diodon would consume way too much memory and would have become too slow as well. To overcome this limitation have we moved away from this xml file and integrated a library called Zeitgeist.
Quick quote what Zeitgeist actually is:
Zeitgeist is a service which logs the users’ activities and events, anywhere from files opened to websites visited and conversations had.
As Diodon pretty much records users’ copy events is using Zeitgeist service a really good match. Besides recording Zeitgeist also provides a simple way to search certain activities and managing history which gives Diodon beside an infinitive clipboard history many more opportunities read more about it here.
But let’s get back to our initial question on why Diodon does not save anything to the clipboard history. For this we have to know that Zeitgeist has a privacy feature so it is possible to disable recording of any users’ events. This option is to be found in your “System Settings” -> “Security & Privacy” -> “Files & Applications” where it says “Record file and application usage”. When you turn this option off no users’ events will be recorded including copy events by Diodon. This means you can still access previous copy events recorded before disabling this option but no new items will be added. You properly ask yourself now how you can simply allow Diodon to save copy events but disable other applications from recording anything?
This is possible but at this stage not as apparent as it could be. In the same Security & Privacy dialog from above there is the possibility to enable recording but only including certain activities. Unfortunately is there no entry to simply include Clipboard. This is something we would really like to see in the future and are working on it – you can follow progress in this bug report. For now as a workaround to still allow Diodon to save copy events is to at least allow activity “Documents” to be recorded.
This could look like the following:
When this option is set you should be good to go and Diodon should start adding clipboard items to the history again.
I am glad to announce that another Diodon version has been released today with mainly changes underneath the surface such as improving API for plugin developers but also fixing some annoying bugs.
Here in detail what has changed:
- Fixed issue which could cause Diodon not starting when upgrading to a newer version (#1347181)
- Fixed issue that under certain desktop environments Diodon was not always added as startup application (#1348989)
- Improved plugin API (#1323947, #1309893, #1324309)
- Cleaning up dependencies for easier integration into other distributions (#1348994, #1310360)
- Updated translations
You can either download the new Diodon as a tarball or if you use Ubuntu or an Ubuntu based distribution use the stable ppa by running following commands:
sudo apt-add-repository ppa:diodon-team/stable
sudo apt-get update
sudo apt-get install diodon
# and for all Unity users there is also a scope
sudo apt-get install unity-scope-diodon
Thanks to everyone involved who made this release happen providing translations, reporting bugs, working on packaging, contributing source code or just simply using and advocating Diodon. Hope to see many more releases ahead.
You might have been using Diodon for a while and are wondering why there is no monochrome icon in your panel but instead a colored fish?
This could look like the following:
The icon does look a bit out of place in this specific theme. Unfortunately is it impossible to create an icon which suits every theme very well and if we would use a monochrome icon as the default it might not even show up on certain themes. That’s why we have decided to have a colored fish as the default panel icon as it is at least visible on all themes. For some commonly used themes we made some exceptions to use the monochrome icons directly.
However, in case you use a completely different theme and you would still like to have a Diodon monochrome icon there is a fairly quick way to do it.
You can use following command if you have a dark theme:
sudo ln -sf /usr/share/icons/ubuntu-mono-dark/status/22/diodon-panel.svg /usr/share/icons/[MYTHEME]/status/22/diodon-panel.svg
or this command with a light theme:
sudo ln -sf /usr/share/icons/ubuntu-mono-light/status/22/diodon-panel.svg /usr/share/icons/[MYTHEME]/status/22/diodon-panel.svg
In both cases replace [MYTHEME] with whatever theme you are using.
And last you need to update the cache of your theme with the following:
sudo gtk-update-icon-cache /usr/share/icons/[MYTHEME]/
Done. When you now close Diodon and open it up again a monochrome should be shown in your panel.
What I would recommend you though if you want to have a more permanent solution: Get in touch with your theme author and ask whether he would be willing to ship a monochrome icon for Diodon. In the end does the author know best what suits its theme and when the Diodon icons are shipped with the theme itself all users will benefit.
I have finally made it to migrate from my old webhosting provider to a new one. Nothing really to bother you about it but I am actually quite excited about my new webhosting and the many possibilities it gives me – so if you are looking for a new webhoster yourself you might want to have a look here .
While I was in the migration process have I changed a couple of thing which might be noteworthy. For all readers of “The Esite Code Log”-Blog, nothing has really changed for you though, beside a new look and feel. The blog and its philosophy remains the same as before. You can read more about it here.
More has changed for our CleverCleaner users though. Up to this point I maintained a single blog only for the CleverCleaner project. For simplicity and maintenance reasons have I decided though to consolidate the CleverCleaner blog with The Esite Code Log. So CleverCleaner is now treated as any other open source project I am involved in such as Diodon. This means there will be no more German translation of my blog posts for CleverCleaner (of course the German translation of the CleverCleaner tool itself remains as before) and all blog posts respectively news concerning CleverCleaner are tagged with clevercleaner on this blog.
So if as before you just want to subscribe to CleverCleaner news per RSS you can use this feed (just as a side node you can also use the same link and replace tag name clevercleaner with whatever tag you want to subscribe to, quite handy…). Beside news for CleverCleaner have I moved all more in depth descriptions and support information to the SourceForge project side mainly its wiki.
As it has been pretty quiet on this blog for a while do I hope that this change will decrease the time I need for maintenance and actually gives me more time to program on the different open source projects and in the end be able to post about it here…
So therefore stay tuned.
I am happy to announce another Diodon milestone 1.1.0 being released today.
You can download it as tarball here or if you use Ubuntu simply install it with the stable ppa:
sudo add-apt-repository ppa:diodon-team/stable
sudo apt-get update
sudo apt-get install diodon unity-scope-diodon
Due to changed dependencies will this version only be available for Saucy 13.10 and Trusty 14.04. Of course for older flavors there will still be an older version available in the ppa and also as tarballs.
This new version finally removes the limitation of maximum 100 items in the clipboard history and therefore brings with it a much more powerful Unity Scope integration and lots more.
If you want to know more in detail what has changed read the following posts:
This milestone is only a start creating the foundation for future improvements such as better integration into other desktop environments and more. I keep you posted.
With this in mind… Happy copying.