Created attachment 178193 [details] before restart SUMMARY Icons of running applications are not displayed in the system tray before session restart. At the same time, applications that auto start will continue to run. Tested: CopyQ, KeePassXC, pamac-manager STEPS TO REPRODUCE 1. Start session 2. see that applications started via auto start are working but not displayed in the system tray 3. restart session and see that applications started via auto start displayed in the system tray. OBSERVED RESULT applications started via auto start are working but not displayed in the system tray EXPECTED RESULT applications started via auto start displayed in the system tray. SOFTWARE/OS VERSIONS Linux: Manjaro 25.0 KDE Plasma Version: 6.3, wayland KDE Frameworks Version: 6.10 Qt Version: 6.8.2 Nvidia video driver: 570.86.16 witch close kernel module
Created attachment 178194 [details] after restart
Autostart was added via system settings
This issue first appeared in Plasma 6.3 beta 2. In version 6.2.5 and 6.3 beta 1 everything worked correctly
not sure i fully understood: are you saying that right after system boot those icons are not shown then after logging out/relogging in they show up correctly? or are you just restarting plasmashell?
Created attachment 178358 [details] "leave", then "log out" I have to choose "leave", then "log out" and log in to the session again. Maybe restart plasmashell will work too, I haven’t checked this yet. Sorry, if I make mistakes, English is not my native language
plasmashell --replace Does not fix the problem
I'm unable to reproduce this issue. After restarting the system, autostarted apps with system tray icons (tested KeepassXC, CopyIQ, and Discord) show their tray icons as expected. Does the issue continue to reproduce for you in a new clean user account? Have you (or your distro) disabled Plasma's Systemd integration feature?
(In reply to Nate Graham from comment #7) > Does the issue continue to reproduce for you in a new clean user account? I'll check it > Have you (or your distro) disabled Plasma's Systemd integration feature? Probably not, because everything worked for version 6.2.5 and 6.3.0 beta 1. How can I verify this for sure?
(In reply to orangeanatola from comment #8) > Probably not, because everything worked for version 6.2.5 and 6.3.0 beta 1. > How can I verify this for sure? Look in ~/.config/startkderc or /etc/xdg/startkderc. If it's disabled, you'll see "systemdBoot=false" in there.
(In reply to Nate Graham from comment #9) > (In reply to orangeanatola from comment #8) > > Probably not, because everything worked for version 6.2.5 and 6.3.0 beta 1. > > How can I verify this for sure? > > Look in ~/.config/startkderc or /etc/xdg/startkderc. If it's disabled, > you'll see "systemdBoot=false" in there. it seems these files do not exist on my system. I tried to create a new user, this partially solved the problem: copyq, KeePassXC now displayed in the tray immediately, but Yakuake and pamac-tray-plasma still require end session and start new one to appear. Is there any way to debug this?
Is it consistently in that different state in the new user account? Or does the behavior change if you restart again? It might be a race condition that results in different outcomes based on timing.
(In reply to Nate Graham from comment #11) > Is it consistently in that different state in the new user account? Or does > the behavior change if you restart again? It might be a race condition that > results in different outcomes based on timing. This behavior is repeated every time.
I think I’ve found a strange pattern for a new user. If disable auto start opensnitch system tray settings (Previously try disabled via plasma auto start settings, but not through opensnitch settings) The system tray will load all applications at once. But this only works for new user, if I try to do it for the my old user, it won’t change anything. It seems, opensnitch does not appear to be the real source of the problem, but demonstrates its existence. Have there been any changes in the system tray between versions 6.3.0 beta 1 and beta 2 ? Because everything worked in beta 1, but not in beta 2. also, may be this related to this bug report: https://bugs.kde.org/show_bug.cgi?id=425315 but he wrote that for him the list of applications is random, for me it’s not. But it is still possible that applications try to display their icons before starting the plasmashell
I also tried to test the script from this comment, but it seems to no longer work https://bugs.kde.org/show_bug.cgi?id=425315#c7
It seems that the reason is really that applications start faster than plasma, using: bash -c 'sleep 130 && ProgramName' as the auto start command can bypass this problem, but this is a temporary solution
some of my applications start through /etc/xdg/autostart/*.desktop. Is there an analog to X-GNOME-Autostart-Delay=130, but for KDE ? Of course I can edit Exec= to bash -c "sleep 130 && myapp", but there may be another way ?
after removing /home/username/.local/share/kactivitymanagerd/ plasma is launched on time and no longer needs to add delay when running external applications. but I guess this does not solve the source of the problem that applications try to run before the plasma is launched. If in the future the plasma launch is delayed again for some reason it will happen again.
So either it's a new issue, or Bug 425315 was never fully fixed.
So what’s next ? I leave this discussion as it is or finish it?