Notification Age

Help
1

I have not been able to find a solution.

The notification age is missing from the dialog. It showed the timestamp of the notification. (It was located on the top right corner, next to the X) Is there a setting to being it back?

Thanks,

2

hi, welcome.

the age of a notification popup (time before disappearing) is usually determined by the application that calls them… if the application does not give you an age setting, that’s probably a sign that the age is hard coded and not adjustable.

3

No, not the time before disappearing. The text in the Notification header, next to the close {x} button, which shows the time of the notification. The widget would show notifications which have not been dismissed with the timestamp. I no longer see the timestamp. KDE Plasma version: 6.5.1 (Arch) Sorry, if not clear.

See link for reference:

Age, the time since this notification happend.

community.kde. org/File:Notification_Popup.png

community.kde. org/Plasma/Notifications

4

ah, i get it now.

so are you talking about the notification pop up itself or the notification history when you click on the bell icon in the system tray?

because if just type notify-send "hello" into a terminal a pop up will show without a time stamp.

but if a view the history from the system tray i see this

Screenshot_20251109_074920
Screenshot_20251109_074920441×437 21 KB

5

Correct, the notification history. I do not have the text as shown in your screenshot.

Screenshot_20251109_180750
Screenshot_20251109_180750441×402 35.9 KB

6

there is something borked about your install then or it’s a bug in plasma 6

the screenshot i showed was from plasma 5

7

Hm, thanks for assistance. It may be somthing with Plasma 6. Tried with a fresh Endeavour OS install in a VM environment. Live Disk works as intended. After install and updates (Using arch Repo), the timestamp is missing in the notification. Shirely, I cannot be the only one.

Operating System: EndeavourOS
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-arch1-1 (64-bit)
Graphics Platform: Wayland

8

it often feels that way…and stop call me Shirely.

if you want to try a new user on your existing install, that will tell if you if it’s something in your dotfiles or if it’s deeper than that.

it a new user works as intended, then you have some digging to do using the brute force approach to triage.

# brute force troubleshooting...
mv ~/.config ~/.configBORKED
mv ~/.local ~/.localBORKED
# logout and log back in again to force plasma to recreate the folders with default settings
# open split views of the folders for comparison and file copy
dolphin --split ~/.config ~/.configBORKED
dolphin --split ~/.local ~/.localBORKED
# copy back half of the BORKED folder contents at a time and relog to see if issue returns
# if it does, then delete the folder again, relog, and only copy half of that previous half
# repeat until the culprit is found, then finally, copy back everything BUT that culprit bit
9

A new user won’t fix it, it’s simply https://bugs.kde.org/show_bug.cgi?id=511908

10

All, thanks all. Mystery solved.