I don't travel much with my laptop so my home network connection remains more or less static. Nonetheless I have noticed for some time that the nm-applet does not appear in my system tray. Manually launching nm-applet succeeds and the icon appears in the tray.
Eventually I traced the problem to the desktop file:
NotShowIn=KDE;GNOME;
Removing the 'KDE' directive allows nm-applet to launch in TDE. The problem with that is KDE has its own NetworkManager front-end and nm-applet is not needed. So the KDE directive is needed.
The mystery is why is TDE interpreting 'KDE' to mean 'TDE'?
This seems like a bug but perhaps there is an explanation I am not seeing.
I found a list discussion from about 10 years ago that seemed similar. In that discussion nm-applet was launching but the icon was not displaying correctly. In my case nm-applet is not launching unless I remove the 'KDE' directive from the desktop file.
I know about tdenetworkmanager. Not important to this discussion. I first want to understand why TDE is incorrectly interpreting 'KDE' as 'TDE' or acting as though TDE is KDE.
Thanks.
On 4/18/25 7:58 PM, Darrell Anderson via tde-users wrote:
I don't travel much with my laptop so my home network connection remains more or less static. Nonetheless I have noticed for some time that the nm-applet does not appear in my system tray. Manually launching nm-applet succeeds and the icon appears in the tray.
Eventually I traced the problem to the desktop file:
NotShowIn=KDE;GNOME;
Removing the 'KDE' directive allows nm-applet to launch in TDE. The problem with that is KDE has its own NetworkManager front-end and nm-applet is not needed. So the KDE directive is needed.
The mystery is why is TDE interpreting 'KDE' to mean 'TDE'?
This seems like a bug but perhaps there is an explanation I am not seeing.
I found a list discussion from about 10 years ago that seemed similar. In that discussion nm-applet was launching but the icon was not displaying correctly. In my case nm-applet is not launching unless I remove the 'KDE' directive from the desktop file.
I believe the problem is related to this bug report:
https://mirror.git.trinitydesktop.org/gitea/TDE/tdelibs/issues/188
Darrell Anderson via tde-users wrote:
I believe the problem is related to this bug report:
https://mirror.git.trinitydesktop.org/gitea/TDE/tdelibs/issues/188
the question is if it is a proper bug report.
why one would expect that TDE should handle anything in $HOME/.config/autostart/. There is ~/.trinity/Autostart/
while some XDG aspects are repsected in TDE, I have not heard of commitment to implement all
On 4/19/25 2:01 PM, deloptes via tde-users wrote:
the question is if it is a proper bug report.
why one would expect that TDE should handle anything in $HOME/.config/autostart/. There is ~/.trinity/Autostart/
while some XDG aspects are repsected in TDE, I have not heard of commitment to implement all
I suspect many people using TDE only use TDE and don't experience much outside that walled garden. I have no issue with that, but TDE should be as XDG compliant as practical.
Many people have multi-user computers and have multiple desktop environments installed. My experience is TDE does not play well in such mixed environments. When the day arrives when TDE can be installed in /usr rather than /opt/trinity purgatory, then TDE will be required to be XDG compliant. One way or another TDE needs to recognize and honor files in $HOME/.config/autostart.
Darrell Anderson via tde-users wrote:
I suspect many people using TDE only use TDE and don't experience much outside that walled garden. I have no issue with that, but TDE should be as XDG compliant as practical.
Many people have multi-user computers and have multiple desktop environments installed. My experience is TDE does not play well in such mixed environments. When the day arrives when TDE can be installed in /usr rather than /opt/trinity purgatory, then TDE will be required to be XDG compliant. One way or another TDE needs to recognize and honor files in $HOME/.config/autostart.
IMO the problem is that there is limited development contingent to handle all those issues. I believe it will take time to get there. But the community is free to log requests,issues etc and someone takes care of it.
On 4/20/25 7:28 AM, deloptes via tde-users wrote:
IMO the problem is that there is limited development contingent to handle all those issues. I believe it will take time to get there. But the community is free to log requests,issues etc and someone takes care of it.
I agree there is limited support. I have open bug reports from the beginning of the TDE project. Many days have passed where I wished I understood C++. I don't and I have tried. If I did I would be whacking away at these bugs in rapid fashion.
If the lead developers disagreed with this specific issue they would have tagged the report as invalid or won't fix. They didn't.
Browsing the code indicates there is already support for autostarting anything in $HOME/.config/autostart. Seems then the bug is valid. :)
On 4/19/25 2:03 PM, deloptes via tde-users wrote:
nm-applet
tde network manager should be equivalent - you are mixing too many things on the computer and complain that this or that does not work.
Try using ~/.trinity/Autostart/
I mentioned in the bug report that I did test in $TDEHOME/Autostart to partly resolve the issue, but the fact remains that TDE is not honoring files in $HOME/.config/autostart.
I mentioned in this list that I am aware of tdenetworkmanager. I installed the package but that does not eliminate the need to fix the underlying problem. Refer to my previous list reply about multi-user environments. TDE does not play well on computers with mixed environments. This bug is a case in point.
-
Darrell Anderson -
deloptes