search

swaywm / sway

i3-compatible Wayland compositor
https://swaywm.org
MIT License
14.59k stars 1.11k forks source link

swaybar/tray: error spamming journal (fcitx related) #6276

Open tobiasjakobi opened 3 years ago

tobiasjakobi commented 3 years ago

Sway Version: 1.6

Debug Log: [ERROR] [swaybar/tray/item.c:127] org.kde.StatusNotifierItem-1167-1/StatusNotifierItem IconPixmap: No such property ('org.kde.StatusNotifierItem.IconPixmap')

Description: On sway 1.5.x I had to disable fcitx since it would make sway unusable after a while, see issue swaywm/wlroots#2285 for reference. After upgrading to 1.6 I re-enabled fcitx to check if things improved. They did, but I still encountered a red frownie in the tray. This problem is documented in #4825 and #5645. The latter one suggested setting the icon theme for swaybar to Adwaita, which results in rendering a proper icon.

However the error messages, which are also documented in the two bugs, don't disappear. The message which I included above was printed 2546 times in the past 12 hours.

So, is this a fcitx problem? Or is swaybar just too verbose in this case?

I've already searched for org.kde.StatusNotifierItem.IconPixmap, but it's just the two sway issues popping up, and some Italian and Japanese forum entries (Ubuntu related). I puzzles me why fcitx would use something KDE specific (?) here.

Also I inspected the swaybar code, and get_property_callback() already does some log level manipulation magic when encounting a prop='IconThemePath'. So maybe prop='IconPixmap' should be handled the same way?

tobiasjakobi commented 3 years ago

This is with fcitx 4.2.9.8. Sadly Gentoo does not provide 5.x yet.