crash when quitting pavucontrol on wayland + swaywm on Archlinux
Howdie, I hope you are well
I did see #49 (closed) and #68 , but this seemed different enough to warrant a separate issue
I use the Control+Q keyboard shortcut to quit pavucontrol, and from my logs this causes it to crash
Aug 28 05:36:00 hellmouth systemd-coredump[2990]: [🡕] Process 2349 (pavucontrol) of user 60222 dumped core.
Stack trace of thread 2349:
#0 0x00007fd344081851 _ZN3Gtk4Main4quitEv (libgtkmm-3.0.so.1 + 0x368851)
#1 0x0000557735d8d0c6 n/a (pavucontrol + 0x480c6)
#2 0x00007fd3440eb218 _ZN3Gtk12Widget_Class24key_press_event_callbackEP10_GtkWidgetP12_GdkEventKey (libgtkmm-3.0.so.1 + 0x3d2218)
#3 0x00007fd3432e4249 n/a (libgtk-3.so.0 + 0x83249)
#4 0x00007fd34323880a g_signal_emit_valist (libgobject-2.0.so.0 + 0x2f80a)
#5 0x00007fd343238980 g_signal_emit (libgobject-2.0.so.0 + 0x2f980)
#6 0x00007fd3435a9705 n/a (libgtk-3.so.0 + 0x348705)
#7 0x00007fd343442eb2 n/a (libgtk-3.so.0 + 0x1e1eb2)
#8 0x00007fd34344413d gtk_main_do_event (libgtk-3.so.0 + 0x1e313d)
#9 0x00007fd342ba5863 n/a (libgdk-3.so.0 + 0x3c863)
#10 0x00007fd342bd9bc4 n/a (libgdk-3.so.0 + 0x70bc4)
#11 0x00007fd34313243c g_main_context_dispatch (libglib-2.0.so.0 + 0x5243c)
#12 0x00007fd3431801d9 n/a (libglib-2.0.so.0 + 0xa01d9)
#13 0x00007fd343131221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
#14 0x00007fd3428e7c9e g_application_run (libgio-2.0.so.0 + 0xcac9e)
#15 0x0000557735d7b7e4 main (pavucontrol + 0x367e4)
#16 0x00007fd342ceb152 __libc_start_main (libc.so.6 + 0x28152)
#17 0x0000557735d7b8be n/a (pavucontrol + 0x368be)
Stack trace of thread 2356:
#0 0x00007fd342db846f __poll (libc.so.6 + 0xf546f)
#1 0x00007fd343180168 n/a (libglib-2.0.so.0 + 0xa0168)
#2 0x00007fd343130c03 g_main_loop_run (libglib-2.0.so.0 + 0x50c03)
#3 0x00007fd34291d1a8 n/a (libgio-2.0.so.0 + 0x1001a8)
#4 0x00007fd34315a511 n/a (libglib-2.0.so.0 + 0x7a511)
#5 0x00007fd3427fd3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007fd342dc3293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 2357:
#0 0x00007fd342db846f __poll (libc.so.6 + 0xf546f)
#1 0x00007fd343180168 n/a (libglib-2.0.so.0 + 0xa0168)
#2 0x00007fd343131221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
#3 0x00007fd34049ae5e n/a (libdconfsettings.so + 0x4e5e)
#4 0x00007fd34315a511 n/a (libglib-2.0.so.0 + 0x7a511)
#5 0x00007fd3427fd3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007fd342dc3293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 2354:
#0 0x00007fd342db846f __poll (libc.so.6 + 0xf546f)
#1 0x00007fd343180168 n/a (libglib-2.0.so.0 + 0xa0168)
#2 0x00007fd343131221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
#3 0x00007fd343131272 n/a (libglib-2.0.so.0 + 0x51272)
#4 0x00007fd34315a511 n/a (libglib-2.0.so.0 + 0x7a511)
#5 0x00007fd3427fd3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007fd342dc3293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 2349 (pavucontrol) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Process 2349 (pavucontrol) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Aug 28 05:36:00 hellmouth systemd[1]: systemd-coredump@0-2989-0.service: Succeeded.
I wasn't sure whether this was benign or whether there might be something serious that needed a look, hence the report
Otherwise, pavucontrol serves me well, thanks for sharing it :)