.arg is unnecessary and in various cases can cause i18n() errors; just do it inline: notification->setText(i18n("Error: %1", body));

Also for short strings like this, it's nice to add some context for translators.

Are there more user-friendly and actionable strings we could for these error messages? I have no idea what this means specifically and would read it as "there was some gobbeldygook error."

While I agree, I haven't been able to see what's the right way to get a more specific error message. Other implementations are doing the same.

I guess we can go with this and if we ever find a better way to get information, we include it.

This should be its own event, not abusing the "notification" one

Is the "Error" even needed?

You probably want dialog-error

You sure this is needed to be high?

I don't know if the comments are used in the Notifications KCM, but even if not, I would use a different one, maybe something like: A portal implementation integrated into KDE Plasma desktop.

Opinions?

Does it need to be specified if you have Urgency=Normal set in the notifyrc file? I believe if you don't specify it, it will use the default urgency, which will be taken from the notifyrc file.

"Normal" is the default and doesn't need specifying anywhere

I think this should remain as xdg-desktop-portal-kde - doesn't this also have implications on i18n?