From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] pavucontrol segfaults on volume change
Date: Thu, 23 Jan 2020 22:30:20 +0100 [thread overview]
Message-ID: <20200123213020.H8x6P3RgSfkl3fDkJCQR0zvl9i17VwYdde7CFC8lbuQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15505@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3450 bytes --]
Closed issue by jnbr on void-packages repository
https://github.com/void-linux/void-packages/issues/15505
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.2.18_1 x86_64-musl GenuineIntel uptodate rFFFFFFFFFFFFFFFFFFF
* package:
pavucontrol-4.0_1
### Expected behavior
pavucontrol should be able to change the output volume
### Actual behavior
segfaults:
```
#0 0x00007ffff56da4dc in _XInternAtom (dpy=dpy@entry=0x5555555f38d0, name=name@entry=0x55555566a900 "_NET_WM_DESKTOP", onlyIfExists=onlyIfExists@entry=0, psig=psig@entry=0x7fffffffdee8,
pidx=pidx@entry=0x7fffffffdee0, pn=pn@entry=0x7fffffffdee4) at IntAtom.c:84
#1 0x00007ffff56da9ab in XInternAtom (dpy=0x5555555f38d0, name=name@entry=0x55555566a900 "_NET_WM_DESKTOP", onlyIfExists=onlyIfExists@entry=0) at IntAtom.c:175
#2 0x00007ffff6006d70 in gdk_x11_atom_to_xatom_for_display (atom=0x50, display=0x555555629040) at gdkproperty-x11.c:115
#3 gdk_x11_atom_to_xatom_for_display (display=0x555555629040, atom=0x50) at gdkproperty-x11.c:96
#4 0x00007ffff727e34f in window_get_desktop (w=0x555555afe550, d=0x555555629040) at canberra-gtk.c:188
#5 ca_gtk_proplist_set_for_widget (p=0x555555d34be0, widget=widget@entry=0x555555bd3420) at canberra-gtk.c:271
#6 0x00007ffff727ed4a in ca_gtk_play_for_widget (w=0x555555bd3420, id=id@entry=2) at canberra-gtk.c:445
#7 0x0000555555595f5d in SinkWidget::executeVolumeUpdate (this=<optimized out>) at /usr/include/gtkmm-3.0/gtkmm/hvbox.h:112
#8 SinkWidget::executeVolumeUpdate (this=<optimized out>) at sinkwidget.cc:89
#9 0x0000555555590356 in DeviceWidget::timeoutEvent (this=<optimized out>) at devicewidget.cc:175
#10 0x00007ffff74ea082 in sigc::slot0<bool>::operator() (this=<error reading variable: value has been optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/slot_base.h:335
#11 (anonymous namespace)::glibmm_source_callback (data=<error reading variable: value has been optimized out>) at main.cc:243
#12 0x00007ffff6857464 in g_timeout_dispatch (source=0x555555be24a0, callback=<optimized out>, user_data=<optimized out>) at ../glib/gmain.c:4668
#13 0x00007ffff685c42e in g_main_dispatch (context=0x55555563a320) at ../glib/gmain.c:3179
#14 g_main_context_dispatch (context=context@entry=0x55555563a320) at ../glib/gmain.c:3844
#15 0x00007ffff685e310 in g_main_context_iterate (context=context@entry=0x55555563a320, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:3917
#16 0x00007ffff685e34f in g_main_context_iteration (context=context@entry=0x55555563a320, may_block=may_block@entry=1) at ../glib/gmain.c:3978
#17 0x00007ffff589664d in g_application_run (application=0x5555555f9210, argc=argc@entry=1, argv=argv@entry=0x7fffffffe508) at ../gio/gapplication.c:2559
#18 0x00007ffff760e471 in Gio::Application::run (this=this@entry=0x7fffffffe3a0, argc=argc@entry=1, argv=argv@entry=0x7fffffffe508) at ../giomm/application.h:283
#19 0x00007ffff7cd2565 in Gtk::Application::run (this=this@entry=0x7fffffffe3a0, argc=argc@entry=1, argv=argv@entry=0x7fffffffe508) at application.cc:137
#20 0x000055555558bf69 in main (argc=1, argv=0x7fffffffe508) at pavuapplication.cc:182
```
### Steps to reproduce the behavior
change output volume in pavucontrol
prev parent reply other threads:[~2020-01-23 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 21:06 [ISSUE] " voidlinux-github
2019-10-20 18:19 ` voidlinux-github
2020-01-18 5:51 ` voidlinux-github
2020-01-18 6:47 ` voidlinux-github
2020-01-23 20:07 ` voidlinux-github
2020-01-23 20:19 ` voidlinux-github
2020-01-23 20:24 ` voidlinux-github
2020-01-23 20:26 ` voidlinux-github
2020-01-23 21:30 ` voidlinux-github [this message]
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=20200123213020.H8x6P3RgSfkl3fDkJCQR0zvl9i17VwYdde7CFC8lbuQ@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).