This is not so much a KDE Plasma 5 issue, but more an issue of legacy applications still not supporting a reasonable systray protocol (SNI).
There are workarounds like [sni-qt](https://launchpad.net/sni-qt), but this won't help with crippled/statically linked applications like Skype.
I'm undecided whether distributions should really put effort in workarounds for legacy apps or instead should put pressure on the upstream of those projects to finally adopt SNI.
- In one case, the user experience might suffer when a user expects an application to continue to work as "it always did"
- In the other case, it keeps the whole ecosystem from finally adopting modern best practices and communicates to upstream projects "it's fine to use outdated technologies".
This is not so much a KDE Plasma 5 issue, but more an issue of legacy applications still not supporting a reasonable systray protocol (SNI). /launchpad. net/sni- qt), but this won't help with crippled/statically linked applications like Skype.
There are workarounds like [sni-qt](https:/
For more details on what's going on here, see this blog post by KDE's kwin developer Martin Gräßlin: http:// blog.martin- graesslin. com/blog/ 2014/06/ where-are- my-systray- icons/
I'm undecided whether distributions should really put effort in workarounds for legacy apps or instead should put pressure on the upstream of those projects to finally adopt SNI.
- In one case, the user experience might suffer when a user expects an application to continue to work as "it always did"
- In the other case, it keeps the whole ecosystem from finally adopting modern best practices and communicates to upstream projects "it's fine to use outdated technologies".