Created attachment 127052 [details] Telegram's system tray icon with Plasma Style "Breeze Dark" and Color Scheme "Breeze Light" The recent update https://bugs.kde.org/show_bug.cgi?id=417583 introduced monochrome system tray icons for Telegram. Whether the dark or bright one is chosen seems to depend on the current color scheme. However I use a bright color scheme together with a dark Plasma style. This seems to result in the wrong system tray icon being chosen which in this case is the dark one that is barely visible on the dark panel (see attachment). When I temporarily set a dark color scheme and restart Telegram the bright monochrome icon is chosen which I is more easily visible. This is my first time interacting with this bug tracker and I apologize if I missed some guide line, related issue or if this is entirely the wrong place. I am happy to address any questions or feedback. STEPS TO REPRODUCE 1. In System Settings > Plasma Style: set Plasma style to a dark theme, e.g. "Breeze Dark" 2. In System Settings > Colors: set color scheme to a bright one, e.g. "Breeze Light" 3. Close and restart Telegram OBSERVED RESULT The dark monochrome icon is displayed for Telegram's system tray which is barely visible on the dark background. EXPECTED RESULT The bright monochrome icon should be chosen to achieve a higher contrast to the background. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.5.11-1-MANJARO OS Type: 64-bit ADDITIONAL INFORMATION Telegram Desktop Version: 1.9.21
Created attachment 127054 [details] Telegram's system tray icon after switching to Color Scheme "Breeze Dark"
> This is my first time interacting with this bug tracker and I apologize if I > missed some guide line, related issue or if this is entirely the wrong > place. I am happy to address any questions or feedback. Looks like an excellent bug report to me. Just that it’s already fixed, for the next release. :) *** This bug has been marked as a duplicate of bug 418996 ***
I'm not sure how I missed that one. Anyway, great to hear that this has already been addressed and sorry for the unnecessary noise on my part!