I am wonder if Klipper some **** child/ no maintainer or what. The main thing is, is I've been getting tons of the same error message that that's been an issue of Klipper for several years now. The error I am referring to is dbusmenu disabled for klipper (bug report https://bugs.kde.org/show_bug.cgi?id=260830). From what I've been able to find on the web, dbus was disabled on klipper a while ago as a workaround for another issue. So after about 3+ years from that bug report; there has been no action on actualy fixing the problem or completely removing the dbus code from issue entirely (so the error message won't be an issue). I'm aware, this message is pretty much harmless, in functional wise; except it's starting to be a huge issue when my .xsession log is getting bloated up over 20+ MB with over 80% being the same message over and over. Yes, I use copy and paste and highlighting stuff heavily(which issues the same message for each action every time), and I don't generaly reboot my system/log off much. A typical uptime/logged in is over 20-90 days or more.

I admit, normaly I wouldn't care about the message; but when I need to troubleshoot some other issue, and I see a error log having a huge size I start investigating. Yes, closing and not klipper is a solution, but it's not fixing what the problem was to begin with. Hence why I am wondering if klipper is some forgotten side project, that no one is wanting to go and fix the underlying problem that the work-around was required to begin with.

Klipper appears to have no dedicated maintainer at this time - it is being maintained collectively by the community in the form of patches, etc as needed in effect.

In terms of the actual message itself, this is not the fault of Klipper - but really Plasma Desktop treating an issue which is minor as a warning level event. Unfortunately this means that short of recompiling the System Tray backend it will not be possible to disable this message i'm afraid.

The issue should ideally be properly fixed to eliminate the race condition between Plasma and Klipper, and to allow this spurious message to be disabled in Plasma - as the user will never have any control over this. Given that this has not yet been fixed, I suspect the issue is likely more difficult to solve than it seems.