SUMMARY After about a month of uptime, KDE notifications start showing seemingly random images from unrelated software in notifications. Specifically, I see Discord user profile images as seen in the attached screenshot. STEPS TO REPRODUCE 1. Use Discord. 2. Get about 25 days of uptime. 3. Generate new notifications. OBSERVED RESULT Notifications have unrelated Discord profile picture images. EXPECTED RESULT I expected to see images related to the software generating the notification. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.17.9-zen1-1-zen (64-bit) ADDITIONAL INFORMATION I've noticed this bug for some time, possibly as long as 6 months ago. The image I attached might be confusing, so here's what happened: 1. I got a Teams message in Firefox. The left blurred out name is from Teams, the right blurred out image is a Discord user. 2. I then took a screenshot and noticed that it has a different (unblurred) Discord user's profile pic as the image. 3. The notification did not automatically go away as it should, it was up for 9 minute until it was manually closed. Also worth noting is that relogging my plasma session fixes the issue for about another month. I suspend every night when sleeping.
This bug report kept failing with the image so I thought I'd submit it and then attach the image, but then I accidentally deleted it and can't recreate the issue after clearing my notifications. Now notifications from Teams are showing no image at all and they are going away automatically as they should. I'll attach a screenshot as soon as I'm able to.
Created attachment 188300 [details] Screenshot of the screenshot notification which also has the incorrect image. This is a screenshot of the screenshot notification. The bottom blurred message is from a Teams user in Firefox, but the image to the right is of an unrelated discord user. Above that, the screenshot notification shows another unrelated discord user.
Fascinating. Reminds me of a similar older Qt bug: https://qt-project.atlassian.net/browse/QTBUG-65145