Bug 510063 - Notifications with action sent by gdbus call are immediately closed, ignoring the timeout.
Summary: Notifications with action sent by gdbus call are immediately closed, ignoring...
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: 6.4.0
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-29 16:51 UTC by alex
Modified: 2025-09-30 18:38 UTC (History)
3 users (show)

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


Attachments
Output of dbus-monitor Plasma 6.4.5 (7.19 KB, text/plain)
2025-09-29 16:51 UTC, alex
Details
Output of dbus-monitor Plasma 6.3.5 (6.56 KB, text/plain)
2025-09-29 16:52 UTC, alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description alex 2025-09-29 16:51:18 UTC
Created attachment 185367 [details]
Output of dbus-monitor Plasma 6.4.5

SUMMARY
Starting with version 6.4.0, notifications created using gdbus call and containing an action button are closed immediately.
If I replace '["test", "ok"]' with '[]' in the command from STEPS TO REPRODUCE to remove the action, the notification is displayed correctly for the specified time.


STEPS TO REPRODUCE
1.  Run command: gdbus call --session --dest org.freedesktop.Notifications --object-path /org/freedesktop/Notifications --method org.freedesktop.Notifications.Notify -- test 0 '' 'test' 'test' '["test", "ok"]' '{"urgency": <byte 2>}' '30000'

OBSERVED RESULT
The notification is automatically closed immediately.

EXPECTED RESULT
The notification should appear for 30 seconds.

SOFTWARE/OS VERSIONS
This behavior is observed in all KDE Neon 6.4 live iso images including the latest unstable version:
KDE Plasma Version: 6.4.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
I recorded and attached the outputs of dbus-monitor on KDE Neon with Plasma 6.4.5 and 6.3.5. As you can see, on version 6.4, immediately after the notification is created, it is declared closed due to expiration:
---
method call time=1759099105.950824 sender=:1.455 -> destination=org.freedesktop.Notifications ...
signal time=1759099105.974725 sender=:1.34 -> destination=(null destination) serial=8245 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 127
   uint32 1
---
1759099105 = 1759099105
Comment 1 alex 2025-09-29 16:52:46 UTC
Created attachment 185368 [details]
Output of dbus-monitor Plasma 6.3.5

For example here in the output of dbus-monitor on Plasma 6.3.5
Comment 2 Kai Uwe Broulik 2025-09-29 16:59:11 UTC
That’s because we assume when the sender isn’t around anymore it will not be able to process the actions either.
Comment 3 Nate Graham 2025-09-29 17:21:18 UTC
So this is intentional/not a bug?
Comment 4 Kai Uwe Broulik 2025-09-29 18:07:46 UTC
We’re technically not in-spec here but that’s also fallout from the history stuff. When the application that sent a notification closed, it cannot receive the signal for when the user clicks the action, which is why the notification is probably closed.

I’d say this is a wontfix but I’ll leave the last word to Dominique