Created attachment 186669 [details] screenshot of notification entries, with some showing a timestamp and others not SUMMARY In plasma 6.4, I remember seeing timestamps (on the right) for each and every notification in the Notifications widget. Now, it seems to be only shown for some of the notifications. Is this intentional (I didn't find any commit message matching such a feature)? Would be good to have a toggle, even if it is. STEPS TO REPRODUCE 1. Cause a notifications from different types of event 2. Look at the notification entry in the notifications widget - Look at the location on the screen where the timestamp field is expected to be. Usually, right next to the 'close' button of the notification. OBSERVED RESULT - Dolphin 'copied' notification seems to give the timestamp - KDED USB device detected notification gave a timestamp 4 out of 10 times. (for the same device) - No timestamp on KTorrent notifications - `notify-send --hint=string:desktop-entry:org.kde.konversation "$(date)"` gave no timestamp (other than the output of $(date) that goes in the message EXPECTED RESULT Timestamp shows up on every notification entry SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.5.1 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 64 GiB of RAM (62.7 GiB usable) Graphics Processor: AMD Radeon RX 7600
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5993
Git commit f2e88391b601675bcec3e0ff2193560d95cfffc6 by Joshua Goins. Committed on 11/11/2025 at 20:10. Pushed by redstrate into branch 'master'. applets/notifications: Fix notification time labels This was introduced in 9f9b96e1e443d8f4c5636ef99976674267c508d3 it seems, due to the fact that the logic which decides which timestamp to use (created or updated) depends on the property being nullable. However, when we don't use var but a specified property type it doesn't become nullable - just a regular invalid JS Date object. We can use isNaN here while keeping the existing required property intact and that fixes the issue. FIXED-IN: 6.5.3 M +1 -1 applets/notifications/FullRepresentation.qml M +1 -1 applets/notifications/global/Globals.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/f2e88391b601675bcec3e0ff2193560d95cfffc6
Git commit 05ca09077db885ecc570bb7fa4db05213702e865 by Joshua Goins. Committed on 11/11/2025 at 20:11. Pushed by redstrate into branch 'Plasma/6.5'. applets/notifications: Fix notification time labels This was introduced in 9f9b96e1e443d8f4c5636ef99976674267c508d3 it seems, due to the fact that the logic which decides which timestamp to use (created or updated) depends on the property being nullable. However, when we don't use var but a specified property type it doesn't become nullable - just a regular invalid JS Date object. We can use isNaN here while keeping the existing required property intact and that fixes the issue. FIXED-IN: 6.5.3 (cherry picked from commit f2e88391b601675bcec3e0ff2193560d95cfffc6) Co-authored-by: Joshua Goins <josh@redstrate.com> M +1 -1 applets/notifications/FullRepresentation.qml M +1 -1 applets/notifications/global/Globals.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/05ca09077db885ecc570bb7fa4db05213702e865