-
-
Notifications
You must be signed in to change notification settings - Fork 750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tray module not visible after some time. No such object path '/StatusNotifierWatcher' #3468
Comments
Wait why these tags bot? Beacuse of the log? |
Waybar : v0.10.4 |
Same issue here unfortunately. I seem to get the |
I've been having a similar issue here that's been going on for a month of two now (~Since I started using Hyprland). I am using Hyprland on Arch. If I suspend/sleep my desktop, and then wake it again later, the tray no longer works. All the icons in it disappear, and programs can no longer run in the tray. E.g. if I play an audio file with VLC, instead of VLC starting in the tray, it'll open as a window. To fix this I have to reboot my PC (Although just restarting Hyprland may fix this but I haven't tested that yet). After the tray breaks, nothing can run trayed. Also, the tray does not break every time I suspend, but it does most of the time. I am also getting the Hyprland version: hyprland 0.41.2-3 My Waybar config: https://pastebin.com/srqbPLEq I also ran Waybar in a terminal a for a while. I suspended my PC for ~5-8 minutes and then the tray broke when I woke it. These are the logs I got after waking the desktop: https://pastebin.com/0U6ZeECT |
I also have Plasma 6 installed along with Sway. I suspect this has something to do with |
I've been trying to debug this issue and I think I have a better idea now. I've Plasma 6 installed along with Sway + Waybar. Here is what I've found so far, maybe this will help others facing similar issue.
EDIT : Disabling |
Amazing debugging skills @ShikharArvind 👏🏼👏🏼👏🏼 ! I myself have been trying to debug this for some time, but couldn't figure out for myself how kde6 owns the tray after killing waybar and/or suspending, and how to give ownership back to waybar. I also have KDE Plasma alongside hyprland, and this must be the issue. For the solution, is there some mechanism to ask for the ownership of a dbus service? AFAIK, there is not, since all notification daemons ask to kill any running notification daemon. Maybe waybar can check and kill |
Thanks! I'm out of my depth when it comes to C++ or just general D-Bus spec, so not sure if there is an elegant/idiomatic way to check for this by waybar itself. This is something for more knowledgeable people to check. In the mean time, I did come up with a quick and dirty workaround for this : https://github.com/ShikharArvind/check_waybar_tray . It seems to work fine for me but I have not tested it all that much. |
Seems good! I will check it out later |
@ShikharArvind thank you so much bro <3 |
This situation happened to me too. But when I look, I cannot find these services in my system. One of the apps I use must be triggering kded6 OS: Fedora 41
|
Thanks @ShikharArvind. Mine happened because I was curious and tested something and ran # terminates those
kquitapp6 kiod6
kquitapp6 kded6
pkill kioworker
# reloads waybar
pkill waybar
hyprctl dispatch exec waybar |
I uninstalled the KDE applications I was using along with their dependencies. And reinstalled this apps (dolphin, kate, okular etc.) without weak kde plasma dependencies. Problem solved. |
From my experiments (mainly trying to use Open as administrator in Dolphin provided by Instead of disabling permanently and facing unknown problems in KDE, I disabled kded6 only for Hyprland with these two lines, kded6 never start by itself 😄
|
Thanks @tomektom! Ooh, I like this approach a lot better than what I did.
I used Now one obvious drawback for I created a
And enable it by running the following commands:
I think this should cover 99% of the scenarios. I'm still testing this setup and will update the post if something breaks. |
After a few hours of logging into hyprland, the Tray Module does now show up after killing and launching waybar.
This does not happen before that point, I can kill waybar and start it again (via a keybind) and the tray and all its icons are still there. But after some time has passed, reloading waybar no longer shows the Tray Module, no matter how many times I reload.
But if I log out and login again, it immediately fixes the issue and the tray stays visible until the issue happens again.
Note that it never disappears automatically, only if I restart waybar.
Running waybar in terminal reveals the issue
EDIT: Following issue #3040, I have downgraded
libappindicator-gtk3
tov12.10.0.r296-1
with no successFull Log
The text was updated successfully, but these errors were encountered: