Description of problem: Reproduce by hitting ESC, then Ctr+W as long as the window is still visible Version-Release number of selected component: pavucontrol-4.0-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: pavucontrol crash_function: Gtk::Main::quit executable: /usr/bin/pavucontrol journald_cursor: s=9ab075a8acbb4eb4b6a3a53fc1c0f04f;i=ad06;b=ffd9e28417b54e5e83792b7924c3deca;m=9aad06d27;t=58c629ffefcf9;x=7600c3fc118f05ea kernel: 5.0.17-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 Gtk::Main::quit at main.cc:383 #1 MainWindow::on_key_press_event at mainwindow.cc:224 #2 Gtk::Widget_Class::key_press_event_callback at widget.cc:4482 #3 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:129 #4 _g_closure_invoke_va at ../gobject/gclosure.c:873 #7 gtk_widget_event_internal at gtkwidget.c:7789 #9 propagate_event at gtkmain.c:2675 #10 gtk_main_do_event at gtkmain.c:1915 #12 _gdk_event_emit at gdkevents.c:73 #17 g_main_context_iteration at ../glib/gmain.c:3988
Created attachment 1585649 [details] File: backtrace
Created attachment 1585650 [details] File: cgroup
Created attachment 1585651 [details] File: core_backtrace
Created attachment 1585652 [details] File: cpuinfo
Created attachment 1585653 [details] File: dso_list
Created attachment 1585654 [details] File: environ
Created attachment 1585655 [details] File: exploitable
Created attachment 1585656 [details] File: limits
Created attachment 1585657 [details] File: maps
Created attachment 1585658 [details] File: mountinfo
Created attachment 1585659 [details] File: open_fds
Created attachment 1585660 [details] File: proc_pid_status
Similar problem has been detected: I see this in my notifications after booting up. reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: pavucontrol crash_function: Gtk::Main::quit executable: /usr/bin/pavucontrol journald_cursor: s=446c91a1a4ab40d39e0b35fe81e5240e;i=49b6e6;b=9f6ae003545d42fdaf572c652a7affd6;m=efb695f256;t=58f1bdb1b30d2;x=9b36ae44ce6d4fe6 kernel: 5.1.17-300.fc30.x86_64 package: pavucontrol-4.0-1.fc30 reason: pavucontrol killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: using control-w to exit pavucontrol always seg faults reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: pavucontrol crash_function: Gtk::Main::quit executable: /usr/bin/pavucontrol journald_cursor: s=5f0550a6c1b1410b88009511bfe7d6dd;i=1afa3;b=fe8ca46364c647f9aa4fd49322048bb6;m=4606617085;t=5937b8395823d;x=3a11f08bcd06bb80 kernel: 5.2.11-200.fc30.x86_64 package: pavucontrol-4.0-1.fc30 reason: pavucontrol killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: open pavucontrol hit Cntl W to exit window crashes *_every_* time. reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: pavucontrol crash_function: Gtk::Main::quit executable: /usr/bin/pavucontrol journald_cursor: s=4af4df580258432eb24376de3e5362bf;i=e844bf2;b=0e0db8f4ed7949a49882ebad4dc7d3b9;m=307d672a831;t=599cd55d17b6c;x=eadf9d80293fb851 kernel: 5.3.7-200.fc30.x86_64 package: pavucontrol-4.0-1.fc30 reason: pavucontrol killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1775553 has been marked as a duplicate of this bug. ***
First, this may be a (further) dupe of [bug 1703761]. Especially note, there was an explanation and patch offered: [bug 1703761 comment 13] Second, this still happens with Rawhide: PID: 231712 (pavucontrol) Signal: 11 (SEGV) Executable: /usr/bin/pavucontrol Stack trace of thread 231712: #0 0x00007f69f7fd6d15 Gtk::Main::quit() (libgtkmm-3.0.so.1 + 0x39dd15) #1 0x00005577756071f5 MainWindow::on_key_press_event(_GdkEventKey*) (pavucontrol + 0x4b1f5) #2 0x00007f69f8048379 Gtk::Widget_Class::key_press_event_callback(_GtkWidget*, _GdkEventKey*) (libgtkmm-3.0.so.1 + 0x40f379) #3 0x00007f69f75962fd _gtk_marshal_BOOLEAN__BOXEDv (libgtk-3.so.0 + 0x4032fd) #4 0x00007f69f714daf6 _g_closure_invoke_va (libgobject-2.0.so.0 + 0x13af6) #5 0x00007f69f7165f67 g_signal_emit_valist (libgobject-2.0.so.0 + 0x2bf67) #6 0x00007f69f7166d93 g_signal_emit (libgobject-2.0.so.0 + 0x2cd93) #7 0x00007f69f753f324 gtk_widget_event_internal.part.0 (libgtk-3.so.0 + 0x3ac324) #8 0x00007f69f73ee161 propagate_event (libgtk-3.so.0 + 0x25b161) #9 0x00007f69f73efd83 gtk_main_do_event (libgtk-3.so.0 + 0x25cd83) #10 0x00007f69f6aaf029 _gdk_event_emit (libgdk-3.so.0 + 0x3d029) #11 0x00007f69f6b10336 gdk_event_source_dispatch (libgdk-3.so.0 + 0x9e336) #12 0x00007f69f706276f g_main_context_dispatch (libglib-2.0.so.0 + 0x5276f) #13 0x00007f69f7062af8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52af8) #14 0x00007f69f7062bc3 g_main_context_iteration (libglib-2.0.so.0 + 0x52bc3) #15 0x00007f69f67d282d g_application_run (libgio-2.0.so.0 + 0xe582d) #16 0x00005577755f4fe9 main (pavucontrol + 0x38fe9) #17 0x00007f69f6c04052 __libc_start_main (libc.so.6 + 0x27052) #18 0x00005577755f50fe _start (pavucontrol + 0x390fe) Stack trace of thread 231715: #0 0x00007f69f6cd39af __poll (libc.so.6 + 0xf69af) #1 0x00007f69f7062a8d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52a8d) #2 0x00007f69f7062e0b g_main_loop_run (libglib-2.0.so.0 + 0x52e0b) #3 0x00007f69f680f7aa gdbus_shared_thread_func (libgio-2.0.so.0 + 0x1227aa) #4 0x00007f69f708c652 g_thread_proxy (libglib-2.0.so.0 + 0x7c652) #5 0x00007f69f62de462 start_thread (libpthread.so.0 + 0x9462) #6 0x00007f69f6cdeb53 __clone (libc.so.6 + 0x101b53) Stack trace of thread 231713: #0 0x00007f69f6cd39af __poll (libc.so.6 + 0xf69af) #1 0x00007f69f7062a8d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52a8d) #2 0x00007f69f7062bc3 g_main_context_iteration (libglib-2.0.so.0 + 0x52bc3) #3 0x00007f69f7062c11 glib_worker_main (libglib-2.0.so.0 + 0x52c11) #4 0x00007f69f708c652 g_thread_proxy (libglib-2.0.so.0 + 0x7c652) #5 0x00007f69f62de462 start_thread (libpthread.so.0 + 0x9462) #6 0x00007f69f6cdeb53 __clone (libc.so.6 + 0x101b53) Stack trace of thread 231716: #0 0x00007f69f6cd39af __poll (libc.so.6 + 0xf69af) #1 0x00007f69f7062a8d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52a8d) #2 0x00007f69f7062bc3 g_main_context_iteration (libglib-2.0.so.0 + 0x52bc3) #3 0x00007f69f430801d dconf_gdbus_worker_thread (libdconfsettings.so + 0xb01d) #4 0x00007f69f708c652 g_thread_proxy (libglib-2.0.so.0 + 0x7c652) #5 0x00007f69f62de462 start_thread (libpthread.so.0 + 0x9462) #6 0x00007f69f6cdeb53 __clone (libc.so.6 + 0x101b53) rpm -q pulseaudio pavucontrol > pulseaudio-13.99.1-1.fc33.x86_64 > pavucontrol-4.0-3.fc32.x86_64
$ rpm -qf /usr/lib64/libgtkmm-3.0.so.1 gtkmm30-3.24.2-2.fc32.x86_64
Same here on Fedora 31 (4.0-2.fc31) and 32 (4.0-3.fc32), MATE Desktop. Ctrl+W or Ctrl+Q causes it to crash every time.
The patch by Alexey does fix this issue. If nobody beats me to it, I'll try to apply it in Fedora using my provenpackager access and submit an update for F31+ once the Fedora services are back online. It really has been languishing for too long. Lennart, are you still interested in maintaining this package?
In the meantime, you can get the package with the patch applied from my copr: https://copr.fedorainfracloud.org/coprs/rathann/pavucontrol-bug1725150/ .
FEDORA-2020-c49209d211 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c49209d211
FEDORA-2020-f044a9e79c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f044a9e79c
pavucontrol-4.0-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f044a9e79c
pavucontrol-4.0-4.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c49209d211
FEDORA-2020-f044a9e79c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-c49209d211 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days