search

Alexays / Waybar

Highly customizable Wayland bar for Sway and Wlroots based compositors. :v: :tada:
MIT License
6.69k stars 712 forks source link

Some modules crash, when i click on it #859

Closed DjinNO closed 4 years ago

DjinNO commented 4 years ago

Upper right corner image Click on network module => and now: image

Arch Linux Waybar v0.9.3

Alexays commented 4 years ago

Seems to be the same screenshot, no?

DjinNO commented 4 years ago

Sorry. Fixed. network and two my custom modules (vpn, bluetooth) crashed, after i tried to click on volume module I tried to run waybar with debug mod, but debug show nothing

w1ll-i-code commented 4 years ago

I tried to run waybar with debug mod, but debug show nothing

I got some warnings which may help...

[2020-09-21 12:31:46.665] [info] Resources files: /home/will/.config/waybar/config, /home/will/.config/waybar/style.css [2020-09-21 12:31:46.678] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity

(waybar:22892): WARNING : 12:31:46.710: gtk-layer-shell was not compiled with support for GTK v3.24.23, program may crash

(waybar:22892): WARNING : 12:31:46.712: gtk-layer-shell was not compiled with support for GTK v3.24.23, program may crash

(waybar:22892): Gdk-WARNING **: 12:31:50.110: Couldn't map window 0x5610edd18b70 as subsurface because its parent is not mapped.

(waybar:22892): WARNING : 12:31:50.110: gtk-layer-shell was not compiled with support for GTK v3.24.23, program may crash

wmww commented 4 years ago

I doubt this is GTK Layer Shell related. gtk-layer-shell was not compiled with support for GTK v3.24.23, program may crash looks scary, but I tested and there doesn't seem to be any relevant GTK changes recently so I doubt that's the cause. Regardless I just updated master so if you pull the latest GTK Layer Shell you shouldn't get that. The Couldn't map window 0x5610edd18b70 as subsurface because its parent is not mapped. warning is harmless but I haven't figured out how to suppress it yet.

wmww commented 4 years ago

Just to be sure, someone who experiences the Waybar crash could try running gtk-layer-demo (You'll probably need build GTK Layer Shell yourself so you can configure it with the -Dexamples=true option). If clicking the popup menu works there then it's not a GTK Layer Shell issue.

EDIT: oh, if it's just modules crashing and not all of Waybar, checking this isn't necessary.

0xC0ncord commented 4 years ago

I'm having a similar issue. In my case I am using the custom/mpd example module as seen here.

When I click on the module, it performs the command in on-click, in this case, mpc toggle which succeeds. At the same time, the module disappears from waybar and I have to restart it in order for the module to reappear. Clicking on it again has the same effect, toggling the state of mpd and then causing the module to disappear again.

0xC0ncord commented 4 years ago

I just also noticed that of the modules that die when this happens, if there are multiple present at the same time and any one of them dies in this way, all other custom modules die as well.

0xC0ncord commented 4 years ago

Here is a quick video demonstrating the problem: https://imgur.com/a/J3cuMyp

I show three custom modules that are affected by this: the custom/mpd module on the left, custom/notifications (the bell), and custom/screenrecord (video camera). As soon as I click the custom/notifications module, all three of these modules die.

DjinNO commented 4 years ago

@0xC0ncord Which tool you used to record this gif?

0xC0ncord commented 4 years ago

@0xC0ncord Which tool you used to record this gif?

wf-recorder, but Imgur converted the original mp4 to gif.

DjinNO commented 4 years ago

After last pacman -Syu on my Arch Linux problem was fixed