Notification Logging is turned on by setting "Log notifications" to "always". Notifications from KDE Connect are display correctly. But these notifications are not logged.
I've just come across the same issue with another project that uses KDEs KNotification service. The problem is that KNotification sends notifications with the "transient" flag, which causes xfce-notifyd to not log it.
So far the bug has been ignored at kde. Any chance, we could convince xfce-notifyd to ignore the transient flag for specific apps (in my case I think it is highly unintuitive that I can not log messages from some applications when I switch on "log all messages from all applications").
Maybe it's easier to just hack one line in xfce-notifyd for a quick fix?
I'm not happy that this issue has not received any attention on the kde side either, but I feel like talking about hacking together a workaround is premature.
Also, this bug potentially effects all other notification services aswell, so better fix it properly.
I'll try and poke some random people in the kde irc channels.
Though if we don't get this fixed in the next few months, I agree we have to work around it.
Just checked situation in cinnamon: They have a switch for "Ignore transient notifications" that is on by default - maybe we should copy that behavior?
However, there is real no notification log at all in cinnamon - but it remembers a transient notification when you didn't click it away, so you can recheck which is maybe all you need.
I can't recall the exact behavior in cinnamon.
In the meantime, I gave kde as an environment a spin after 10 years on xfce. The notifications work well, but the rest is painful (how can a DE be so buggy?) - so I am happy to be back.
Could we as a workaround create another service that just listens for notifications with transient flag and resends them without it? Could that be scripted easily? We might be even able to filter just kde-connect messages and repost these.
Just running dbus-monitor "interface='org.freedesktop.Notifications'" for now to see what I can actually get. Maybe there is a more straight forward way to do that in python.
Thanks for taking another look and checking on the kde side of things.
Let's hope, some people answer (the one on gitlab seems promising) - @Zauberfisch did you reach anybody on IRC? I will be busy with class prep until Tuesday anyways now, so I will not build an intermediate service until then - let's see if there is some kind of reaction before that.
However monitoring dbus looks pretty promising and building some very customizable filter mechanisms for notifications might be still worth investigating. Also looking at dunst and dunstify (https://dunst-project.org/), using it to replace or better augment xfce's notification daemon could become an option.
As long as nobody answers and this patch would solve the issue, we (or I) could then maybe try to offer an AUR package for knotify based on your patch. That would then solve the issue for arch based distributions and give us some leverage to get a PR upstream.
Ah, was just looking at your patch while you sent your last answer, so please share your ideas what else might be strange on knotify's side.
I've not have time to do anything, but someone else did take care of it and removed the flag in a patch a few weeks ago. I just confirmed that my use-case is fixed now.