Closed ignamartinoli closed 10 months ago
I came across this open issue some weeks ago since it was also happening to me.
Yesterday I updated Hyprland to version "0.28.0" and Waybar to "0.9.20-61-g94c34a2" and it just doesn't happen to me anymore.
I have a similar issue with Waybar v0.9.20 (compiled with experimental features, including Cava and Hyprland) and latest hyprland
version from Git (0314a727eb27dd880b172b9ff2dc78c863f3ce5f
in my case).
For me I think it happens when my displays are removed and cava
is processing audio, at least from my guess from the stacktrace (without debug symbols).
I don't actually disconnect screens, but it happens if I leave my computer idle for a bit and DPMS shuts off the monitors.
coredumpctl info
I experience a segfault too when disconnecting a monitor and with wireplumber module enabled. But unlike everyone above, I am using sway. Seems like it's not related to the WM sway 1.8.1 waybar 0.9.22
I encountered the same issue. Waybar crashes when I unplug my HDMI monitor from laptop, if wireplumber plugin is enabled. This issue disappears when wireplumber plugin is not used.
sway 1.8.1
waybar 0.9.22
pipewire 0.3.80
wireplumber 0.4.14
Storage: /var/lib/systemd/coredump/core.waybar.1000.460e10aec1d54e3badb592420f5bd448.13>
Size on Disk: 1.8M
Message: Process 13501 (waybar) of user 1000 dumped core.
Stack trace of thread 13501:
#0 0x00007fda41965519 n/a (libpipewire-module-protocol-native.so + 0x15519)
#1 0x00007fda47a695b6 n/a (libspa-support.so + 0x85b6)
#2 0x00007fda463cd723 n/a (libwireplumber-0.4.so.0 + 0x20723)
#3 0x00007fda46550f19 n/a (libglib-2.0.so.0 + 0x59f19)
#4 0x00007fda465af2b7 n/a (libglib-2.0.so.0 + 0xb82b7)
#5 0x00007fda4654f112 g_main_context_iteration (libglib-2.0.so.0 + 0x58112)
#6 0x00007fda4680daf6 g_application_run (libgio-2.0.so.0 + 0xdfaf6)
#7 0x000055be6de88887 n/a (waybar + 0x4d887)
#8 0x000055be6de865b5 main (waybar + 0x4b5b5)
#9 0x00007fda45d58cd0 n/a (libc.so.6 + 0x27cd0)
#10 0x00007fda45d58d8a __libc_start_main (libc.so.6 + 0x27d8a)
#11 0x000055be6de8d755 n/a (waybar + 0x52755)
Some GDB output:
[2023-10-02 17:04:01.158] [info] Bar removed from output: HDMI-A-1
[Thread 0x7fffcaffd6c0 (LWP 13940) exited]
Thread 1 "waybar" received signal SIGSEGV, Segmentation fault.
0x00007ffff1d86519 in on_remote_data (data=0x5555557f6e60, fd=35, mask=<optimized out>)
at ../pipewire/src/modules/module-protocol-native.c:1011
1011 pw_loop_update_io(loop, impl->source,
I'm still getting this issue with the latest commit (6e12f812) from using the cava module with "method" set to pipewire in the config (doesn't happen with method set to pulse). Using the waybar-git aur package.
I'm also noticing some other strange behaviour. Certain CPU activity causes crackling/static noises in my audio (e.g when my wallpaper change animation plays), and right clicking the module to pause the cava thread causes my audio to completely freeze.
I am also still receiving (what looks like) the original crash on Arch Linux as well with the waybar-git
AUR package (version v0.9.24-146-gb6f4a0da
), though no Cava module for me:
Message: Process 15206 (waybar) of user 1000 dumped core.
Stack trace of thread 27394:
#0 0x00007103d29998b9 n/a (libpipewire-module-protocol-native.so + 0x158b9)
#1 0x00007103d8c90646 n/a (libspa-support.so + 0x8646)
#2 0x00007103d768f91d n/a (libpipewire-0.3.so.0 + 0x8c91d)
#3 0x00007103d6ea955a n/a (libc.so.6 + 0x8b55a)
#4 0x00007103d6f26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 15206:
#0 0x00007103d6eb6013 n/a (libc.so.6 + 0x98013)
#1 0x00007103d6eb7308 n/a (libc.so.6 + 0x99308)
#2 0x00007103d6eb7669 n/a (libc.so.6 + 0x99669)
#3 0x00007103d6eb9e93 __libc_free (libc.so.6 + 0x9be93)
#4 0x00007103d29b0e8a n/a (libpipewire-module-protocol-native.so + 0x2ce8a)
#5 0x00007103d299858b n/a (libpipewire-module-protocol-native.so + 0x1458b)
#6 0x00007103d764b8c4 n/a (libpipewire-0.3.so.0 + 0x488c4)
#7 0x00007103d767e798 pw_proxy_destroy (libpipewire-0.3.so.0 + 0x7b798)
#8 0x00007103d764bacc pw_core_disconnect (libpipewire-0.3.so.0 + 0x48acc)
#9 0x00005e8193f4facb n/a (waybar + 0x180acb)
#10 0x00005e8193f4d0c9 n/a (waybar + 0x17e0c9)
#11 0x00005e8193e879da n/a (waybar + 0xb89da)
#12 0x00005e8193e91ba0 n/a (waybar + 0xc2ba0)
#13 0x00005e8193e94b8b n/a (waybar + 0xc5b8b)
#14 0x00007103d8acb849 n/a (libglibmm-2.4.so.1 + 0x56849)
#15 0x00007103d77d8f69 n/a (libglib-2.0.so.0 + 0x59f69)
#16 0x00007103d78373a7 n/a (libglib-2.0.so.0 + 0xb83a7)
#17 0x00007103d77d7162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#18 0x00007103d7a0cb66 g_application_run (libgio-2.0.so.0 + 0xdfb66)
#19 0x00005e8193e2bd90 n/a (waybar + 0x5cd90)
#20 0x00005e8193e2a246 main (waybar + 0x5b246)
#21 0x00007103d6e43cd0 n/a (libc.so.6 + 0x25cd0)
#22 0x00007103d6e43d8a __libc_start_main (libc.so.6 + 0x25d8a)
#23 0x00005e8193e3e8b5 n/a (waybar + 0x6f8b5)
Hi, I am having this same issue.
I am using Waybar version
0.9.17
and Hyprland version0.24.1
.The module
wireplumber
is causing a crash when I disconnect a second monitor connected via HDMI.