Oliver, since I started Diodon with G_MESSAGES_DEBUG=all diodon > diodon_debug.txt, I was no longer able to reproduce the bug.
However, I did a restart of the system, with Diodon launching automatically at boot, and now the clipboard history can not be cleared. So, could it be that Diodon is affected by being launched on startup vs. manually launching it? And, in doing so, does it make a difference if it is launched from Unity or the command-line? I am going to stop Diodon now, and continue to work with it based on the G_MESSAGES_DEBUG=all diodon > diodon_debug.txt launch approach. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383013 Title: Diodon on 14.10 does not clear history consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1383013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
