From: blehel <blehel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pavucontrol: segfault when exiting with CTRL-Q
Date: Thu, 25 Mar 2021 16:35:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29751@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
New issue by blehel on void-packages repository
https://github.com/void-linux/void-packages/issues/29751
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.11.9_1 x86_64 GenuineIntel notuptodate rrFFF
* package: pavucontrol-4.0_1
### Expected behavior
Pressing CTRL-Q exits cleanly.
### Actual behavior
Closing the window works without problem.
Pressing CTRL-Q to exit triggers a segfault.
Running through gdb:
```
Thread 1 "pavucontrol" received signal SIGSEGV, Segmentation fault.
0x00007ffff7e00a01 in Gtk::Main::quit() () from /usr/lib/libgtkmm-3.0.so.1
>(gdb) bt
#0 0x00007ffff7e00a01 in Gtk::Main::quit() () from /usr/lib/libgtkmm-3.0.so.1
#1 0x000055555559df4a in ?? ()
#2 0x00007ffff7e6a845 in Gtk::Widget_Class::key_press_event_callback(_GtkWidget*, _GdkEventKey*) () from /usr/lib/libgtkmm-3.0.so.1
#3 0x00007ffff747b6b8 in ?? () from /usr/lib/libgtk-3.so.0
#4 0x00007ffff70452ee in ?? () from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff705d1b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff705e04f in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff74259a4 in ?? () from /usr/lib/libgtk-3.so.0
#8 0x00007ffff72d891f in ?? () from /usr/lib/libgtk-3.so.0
#9 0x00007ffff72da463 in gtk_main_do_event () from /usr/lib/libgtk-3.so.0
#10 0x00007ffff69af785 in ?? () from /usr/lib/libgdk-3.so.0
#11 0x00007ffff69e32d2 in ?? () from /usr/lib/libgdk-3.so.0
#12 0x00007ffff6f54cfb in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff6f54fa8 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff6f5505f in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007ffff6684785 in g_application_run () from /usr/lib/libgio-2.0.so.0
#16 0x000055555558bf69 in main ()
```
next reply other threads:[~2021-03-25 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:35 blehel [this message]
2021-03-25 15:49 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29751@inbox.vuxu.org \
--to=blehel@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).