See below Reproducible: Always Steps to Reproduce: 1. Use KDE Connect (there is a reason for this, see below) 2. Ensure that SMS notifications are configured in KDE Connect, your phone is paired, etc. 3. Send yourself an SMS 4. Wait for the notification popup to disappear 5. Hopefully, you will see one more notification in the notification history 6. Click on the notifications icon on the system tray, so that the notification opens Actual Results: You see the title of the notification. Expected Results: You should be able to see the *actual content* of the notification. There is hardly any point in saying "Oh, you got an SMS" if it's not going to tell me what the SMS says. The user scenario here is that I use KDE Connect to copy authorisation codes from SMS into my browser. This used to work beautifully well with KDE4 and I was really proud of that feature. For the test, I would have suggested other ways of generating a notification, but those seem to hit bug #358978
Thanks for the report Storing the body of a persistant notification is of course done and works fine here. Can you please post a screenshot of the notification bubble and then of the notification applet popup after it is in?
I think I found the problem, investigating.
Created attachment 97009 [details] Notifications panel notify-send -t 0 "Hello" "World"
Created attachment 97010 [details] Notifications panel, with more than one notification Interestingly, it does show the body for a second notification (but still not for the first). Also, try sending repeated notifications, such as: notify-send -t 0 "Hello" "World" notify-send -t 0 "Hello" "Planet" notify-send -t 0 "Hello" "Habitat" Anything amiss?
Created attachment 97012 [details] Works fine here.
I think this issue got fixed together with bug 35898. Please retest with that patch in (5.5.4 release or git master)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!