Waybar: Stopped showing up

Created on 4 Apr 2020 · 7Comments · Source: Alexays/Waybar

I'm using Arch Linux with Sway and all packages are up-to-date. Yesterday all worked fine, but now Waybar stopped showing up even if launching it manually. I tried to rename my config files, so Waybar used default ones, but it didn't help. The command line output is something like:
[2020-04-05 00:19:20.046] [info] Resources files: /home/begs/.config/waybar/config, /home/begs/.config/waybar/style.css [2020-04-05 00:19:20.060] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
and it always been this

Source

Begggs

👍8

Most helpful comment

gtk3 is the culprit. I downgraded it to 3.24.16-1 and it solved the issue.

scrufulufugus on 4 Apr 2020

👍15

All 7 comments

Yes, me too! Arch Linux, all packages up to date.

Output of waybar -l debug:

[2020-04-04 14:28:24.833] [info] Resources files: /home/jwinnie/.config/waybar/config, /home/jwinnie/.config/waybar/style.css
Unknown option -l
[2020-04-04 14:28:24.836] [debug] Output detected: HDMI-A-1 (Dell Inc. DELL U2715H)

And then nothing shows up. The waybar process keeps running without errors, though.

jwinnie on 4 Apr 2020

Maybe it has something to do with another package/dependency being updated? I can't find anything that might break waybar in the recent updates list, though... https://www.archlinux.org/packages/?sort=-last_update

jwinnie on 4 Apr 2020

gtk3 is the culprit. I downgraded it to 3.24.16-1 and it solved the issue.

scrufulufugus on 4 Apr 2020

👍15

So a GTK3 point release is a breaking change? That's pretty bad design...

jwinnie on 5 Apr 2020

Breaking GTK3 commit is https://gitlab.gnome.org/GNOME/gtk/-/commit/7f12dc2b66bba15b2e1c0ca077fa4ae58962ec0f

hpidcock on 5 Apr 2020

👍4

I can report the same experience on Void. I'm trying to check my update logs now to see but I too believe the culprit to be a gtk3 package upgrade. Going to try to roll back to 3.24.16

Edit: rolling back to 3.24.16 did indeed fix this issue, both for waybar and coincidentally, wofi as well. I'm going to see about reporting this there. Nice find!

Double Edit: This looks to be a duplicate of #645 and should probably be closed as such?