| Summary: | Most tray icons for running applications not shown at all | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | TraceyC <kdedev> |
| Component: | System Tray widget | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | cwo.kde, kde, materka, nate, zxvb12z |
| Priority: | HI | Keywords: | regression |
| Version First Reported In: | 6.4.80 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Solus | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=499892 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
TraceyC
2025-06-02 18:26:19 UTC
. I can sort of reproduce. No auto-started SNIs appear in the tray, ever. Apps launched after system startup show their tray icons as expected. I don't think expanding the tray matters, but I'll try it again. Disabling then enabling the icon again in settings also gets them to show up Tested with KeepassXC, Yakuake, Nheko, and Neochat. (I don't have the other apps). System log shows messages like: Jun 02 23:42:07 X260 keepassxc[2047]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CUR> Jun 02 23:41:33 X260 xwaylandvideobridge[2029]: kf.statusnotifieritem: KDE platform plugin is loaded but SNI unavailable Jun 02 23:41:32 X260 yakuake[2043]: kf.statusnotifieritem: KDE platform plugin is loaded but SNI unavailable This seems relevant - maybe something is delaying StatusNotifierWatcher startup until after the autostarted apps launch? There doesn't seem to be any code change in the systemtray applet since 6.3.80, and StatusNotifierWatcher even longer. In any case, this is very noticeable (for people who use app tray icons) so it seems HI priority material. More digging. nheko seems to work for me even in autostart, but it opens as the last one so whatever it is that breaks early on might have already fixed itself at that point. The problem is that for autostarted apps, the dbus registration with the StatusNotifierWatcher fails, early on - the dbus call to get the protocol version times out. On the KStatusNotifierWatcher that's just a "return 0;" so not something that can time out itself, so it seems to be dbus calls in general that break. I did put some debug output into it, and it's loaded and running when the apps try to access it, that does not seem to be the problem. DBus breaking would also explain some of the other weird messages (and completely non-functional akonadi) that I got since yesterday. (The system was up for a few days before that, and worked perfectly with regard to that, so it must be a recent regression within the last week or so... could of course also be a different cause). At this point I'm stumped on how to debug it further. Also, the autostarted KDE apps are the system versions and not the kde/usr versions, but I'm not sure if that's related - it also breaks for things where I only have the distro version. They're also loaded very early, the autostarted NeoChat doesn't use my accent color for some reason, and sometimes (not always though) KeepassXC fails to be in dark mode at all. >and its not just autostart applications for me, tray icon for any application i open after a fresh boot will be missing
When you're in this state can you run:
pgrep kded6
qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher org.kde.StatusNotifierWatcher.IsStatusNotifierHostRegistered
(In reply to David Edmundson from comment #4) ~ pgrep kded6 1229 ~ qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher org.kde.StatusNotifierWatcher.IsStatusNotifierHostRegistered true Do the ones that fail to show appear when you disable and enable the tray icon in their settings dialogs? I don't know about Discord but in nheko you can toggle it. (In reply to cwo from comment #6) > Do the ones that fail to show appear when you disable and enable the tray > icon in their settings dialogs? Yes. I tested with KeepassXC, Nheko and Yakuake. I deleted ~/kde/usr and rebuilt everything (left kde/build in place though) and that seems to have fixed the issue for me (and akonadi also works again). (In reply to cwo from comment #8) > I deleted ~/kde/usr and rebuilt everything (left kde/build in place though) > and that seems to have fixed the issue for me (and akonadi also works again). This fixed the issue for me as well Seems like this was caused by stale installed files. It's a good idea to clean out ~/kde/usr at least monthly (if not more frequently; I do it weekly). to prevent build gremlins like these from showing up. |