Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] pavucontrol segfaults on volume change
@ 2019-10-15 21:06 voidlinux-github
  2019-10-20 18:19 ` voidlinux-github
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: voidlinux-github @ 2019-10-15 21:06 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3338 bytes --]

New 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:  
  *output of ``xuname`` (part of xtools)*
* package:  
  *affected package(s) including the version*

### Expected behavior

### Actual behavior

```
#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



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
@ 2019-10-20 18:19 ` voidlinux-github
  2020-01-18  5:51 ` voidlinux-github
                   ` (6 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2019-10-20 18:19 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

New comment by jnbr on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-544277721

Comment:
Doesn't happen with xorg/i3, only with wayland/sway.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
  2019-10-20 18:19 ` voidlinux-github
@ 2020-01-18  5:51 ` voidlinux-github
  2020-01-18  6:47 ` voidlinux-github
                   ` (5 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-18  5:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 214 bytes --]

New comment by vpzomtrrfrt on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-575869746

Comment:
See https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/68

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change 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
                   ` (4 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-18  6:47 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

New comment by vpzomtrrfrt on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-575872582

Comment:
I think this is a libcanberra issue, it seems to be fixed upstream but without a release.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
                   ` (2 preceding siblings ...)
  2020-01-18  6:47 ` voidlinux-github
@ 2020-01-23 20:07 ` voidlinux-github
  2020-01-23 20:19 ` voidlinux-github
                   ` (3 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-23 20:07 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

New comment by jnbr on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-577853505

Comment:
Thank you for the link. Could you point me to the libcanberra source you are using?
The last commit on git://git.0pointer.de/libcanberra is from 2012.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
                   ` (3 preceding siblings ...)
  2020-01-23 20:07 ` voidlinux-github
@ 2020-01-23 20:19 ` voidlinux-github
  2020-01-23 20:24 ` voidlinux-github
                   ` (2 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-23 20:19 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

New comment by jnbr on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-577858060

Comment:
nvm, I didn't notice that this very commit from 2012 hasn't found it's way into a release yet.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
                   ` (4 preceding siblings ...)
  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 ` [ISSUE] [CLOSED] " voidlinux-github
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-23 20:24 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-577860105

Comment:
So let's merge this change

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
                   ` (5 preceding siblings ...)
  2020-01-23 20:24 ` voidlinux-github
@ 2020-01-23 20:26 ` voidlinux-github
  2020-01-23 21:30 ` [ISSUE] [CLOSED] " voidlinux-github
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-23 20:26 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 155 bytes --]

New comment by jnbr on void-packages repository

https://github.com/void-linux/void-packages/issues/15505#issuecomment-577860943

Comment:
Yes, I'm on it.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [ISSUE] [CLOSED] pavucontrol segfaults on volume change
  2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change voidlinux-github
                   ` (6 preceding siblings ...)
  2020-01-23 20:26 ` voidlinux-github
@ 2020-01-23 21:30 ` voidlinux-github
  7 siblings, 0 replies; 9+ messages in thread
From: voidlinux-github @ 2020-01-23 21:30 UTC (permalink / raw)
  To: ml

[-- 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

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2020-01-23 21:30 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-15 21:06 [ISSUE] pavucontrol segfaults on volume change 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 ` [ISSUE] [CLOSED] " voidlinux-github

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).