Version: unspecified (using Devel) OS: Linux I'm KDE SC 4.7 RC2. Some SVG icons are rendered too small in notifications if passed as image_path. If passed as app_icon, the same icon is rendered in correct size. Reproducible: Always Steps to Reproduce: 1. Grab the SVG icon I attached. 2. Run the following command: $ notify-send --icon='/path/to/offline.svgz' 'Good' 'The icon is OK :-)' 3. Now run another one: $ notify-send --hint='string:image_path:/path/to/offline.svgz' 'Bad' 'The icon is too small :-(' Actual Results: Icon in point 3. is rendered too small. Expected Results: The notification from point 3. has icon of the same size as the one from point 2.
Created attachment 62224 [details] example icon which triggers the bug
The other thing is that that icon is probably somehow broken as Eye of GNOME renders it differently than Gwenview, but still the behavior of KNotify is inconsistent.
Are you using Plasma notifications, the old-style notifications, or a third party notification tools, such as Ayatana notifications?
Created attachment 62232 [details] screenshot with bug I'm using KDE default - I think this is Plasma but not really sure, so I'm attaching a screenshot.
Yep, that's Plasma, reassigning.
Created attachment 77050 [details] screenshow with bug in 4.10 I checked whether this got fixed in the new notifications in 4.10. Now it looks like it is initially rendered small and then scaled up to a bigger size. It looks very pixelated. Attaching new screenshot.
Since the Notification widget was replaced with a newer QML-based one, the previous versions are now considered unmaintained. There will be no more code contribution to the older versions. Please only report bugs and wishes to the new version, available since KDE 4.10
Myriam, I think you missed my last comment. I'm reopening this. It's still an issue in KDE SC 4.10.2.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham