Bug 451192 - Connecting to KNotification::activated before doing setActions does not work
Summary: Connecting to KNotification::activated before doing setActions does not work
Status: REPORTED
Alias: None
Product: frameworks-knotifications
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.91.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-06 09:01 UTC by Bhushan Shah
Modified: 2022-03-06 14:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bhushan Shah 2022-03-06 09:01:30 UTC 
SUMMARY

If you do connection to activated before doing setActions, slot does not trigger, I verified using dbus-monitor that related dbus signal is emitted but not the lambda slot.

See https://invent.kde.org/plasma-mobile/plasma-dialer/-/merge_requests/85

Question is, if is it expected? If so it should be possibly documented?
Comment 1 Kai Uwe Broulik 2022-03-06 14:36:59 UTC 
It should definitely work no matter the order, that said I cannot reproduce in a minimal example