KNotify should not use notify-osd as a notification backend, because it does not support actions

I don't think KNotify can present things as message boxes. Whatever's presenting them on the Gnome side is presenting it as a message box.

thank you for your bug report, that's not a bug though but a design decision to not support actions in notification with notify-osd, the software should check the notification service capabilities before using those

KNotify is unable to hide its actions, as it does not define the actions itself, it allows its applications to define them.

If notify-osd isn't able to display those actions, I think another way of displaying notifications should be added that does support actions. The current knotify->notify-osd behaviour is unacceptable, and can't be fixed in knotify itself. (and even if it could, we all know how those bugreports go on bugs.kde.org, they get buried and never looked at again.)

I'm prepared to do the required changes myself in either notify-osd, knotify or somewhere else, but I want to know where to fix this bug.

don't reopen this bug as said that's not a notify-osd bug but a design decision, the caller can query the daemon capabilities so whatever is using libnotify to send the bubble there should be checking what the server can do before sending requests

closing the notify-osd task too

closing the notify-osd task too

sorry launchpad is acting weird

Reporting this bug back to kdebase-runtime. I had a chat with Sebastien Bacher. We both agree that notify-osd behaviour isn't what it should be, but this is by design, since notify-osd doesn't support actions. KNotify *does* support actions, and as such, it should either:
* tell applications not to send actions if it uses notify-osd (see below)
* remove the actions itself
* not use notify-osd as a backend.

I opt for option three, therefore I will rename this bug to "KNotify should not use notify-osd as a notification backend, because it does not support actions."

For reference; Sebastien and I agree that this bug should actually be fixed deeply in knotify, because it has no API to tell applications what its notification backend supports. By default, it supports everything including actions, therefore it should not use notify-osd as a backend.

Notify-osd is working as a frontend in this case. I can't see why notify-osd can't just remove the actions itself, as the notifications knotify sends are completely compliant with the FD.o spec.

Not a bug with KNotify. The Colibri implementation of the FD.o notification system, for example, has no such trouble stripping the actions, and invasive patches to the core KDE packages (that won't be accepted by upstream) on the doorstep of an LTS are not an issue. Notify OSD should just be fixed.

Notify-osd can not tell the difference between actions which can easily be stripped and those that are critical for the user to see. So it must have some sort of fallback mechanism. It would be better if KDE base would detect whether actions were supported by the front end and not send them if not.

I fixed this bug in kdebase-runtime by making sure the notification backend KNotify uses, supports the capabilities used in the popup; otherwise the popup is simplified. It's been committed to trunk and I'll try backporting it into the 4.5 release. See http://reviewboard.kde.org/r/4555/ for more information.