On 4/6/26 4:55 PM, dep via tde-users wrote:
i have*no* idea how the system tray thing works. so i do not have the first clue in tracking it down. anybody know what's necessary to get an application to register there and do what it's supposed to do? if I have a sense of that, i can try to work backwards and sort it.
The systray functionality is simply a small window compiled into the protonvpn program that is triggered when the close or minimize button is clicked instead of closing or minimizing to kicker. The application handles identifying itself as a systray app internally.
See:
https://api.kde.org/legacy/3.5-api/kdelibs-apidocs/kdeui/html/classKSystemTr...
There are only two possibilities, the first being the more likely,
1. there were changes in protonvpn so the systray functionality of the application is no longer seen by TDE, or 2. there were changes to TDE.
I'd start by double-checking with the protonvpn folks, or finding the git repo and looking at the commits between when it last worked and when it no longer worked for hints.
It may also be worth looking at the TDE logs or xsession-errors and see if anything is being reported as failing.
Sorry no solutions, but this hopefully gives a sense to how the ksystray works from the application standpoint.