search

wwmm / easyeffects

Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
GNU General Public License v3.0
6.57k stars 270 forks source link

PulseEffects doesn't run #363

Closed jotape1960 closed 5 years ago

jotape1960 commented 6 years ago

Hi!

I use UbuntuStudio 18.04.1 LTS installed in 3 computers, 2 desktops and 1 laptop. Both desktops are identical machines (MSI-7788 motherboard, with Intel i5).

The issue is that PulseEffects doesn't run in one of the desktop computers, even the fact both are the same machine and have the same system!

BTW, PulseEffects runs so fine in the other desktop and in the laptop.

The message I get, when I try to run PulseEffects from a Terminal command line is:

Assertion 'o' failed at pulse/operation.c:133, function pa_operation_get_state(). Aborting. Abortado (`core' generado)

I don't have any clue about what that message means!

I'm adding more information now:

UBUNTUSTUDIO 18.04.1 LTS plus GNOME DESKTOP ENVIRONMENT.

PULSEEFFECTS WAS INSTALLED FROM THE STANDARD UBUNTU REPOSITORY PACKAGE.

WHEN I OPEN PULSEEFFECTS FROM A TERMINAL SESSION, WITH SUDO FULL PRIVILEGE, THE PROGRAM RUNS SO FINE. WHEN I TRY TO OPEN IT WITH THE STANDARD PROCEDURE (DESKTOP AND/OR MENU ICON), PROGRAM DOESN'T RUN.

OUTPUT FROM pactl list short:

0 module-device-restore
1 module-stream-restore
2 module-card-restore
3 module-augment-properties
4 module-switch-on-port-available
5 module-switch-on-connect
6 module-udev-detect
8 module-alsa-card device_id="0" name="pci-0000_00_1b.0" card_name="alsa_card.pci-0000_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1"
9 module-alsa-card device_id="2" name="usb-Burr-Brown_from_TI_USB_Audio_CODEC-00" card_name="alsa_card.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1"
10 module-jackdbus-detect channels=2
11 module-bluetooth-policy
12 module-bluetooth-discover
13 module-bluez5-discover
14 module-esound-protocol-unix
15 module-native-protocol-unix
16 module-gconf
17 module-default-device-restore
18 module-rescue-streams
19 module-always-sink
20 module-intended-roles
21 module-suspend-on-idle
22 module-console-kit
23 module-systemd-login
24 module-position-event-sounds
25 module-role-cork
26 module-snap-policy
27 module-filter-heuristics
28 module-filter-apply
29 module-x11-publish display=:0.0
30 module-x11-cork-request display=:0.0
31 module-x11-xsmp display=:0.0 session_manager=local/jjpg-MS-7788:@/tmp/.ICE-unix/3663,unix/jjpg-MS-7788:/tmp/.ICE-unix/3663
36 module-null-sink sink_name=PulseEffects_apps sink_properties=device.description="PulseEffects(apps)"device.class="sound" channels=2 rate=48000
37 module-null-sink sink_name=PulseEffects_mic sink_properties=device.description="PulseEffects(mic)"device.class="sound" channels=2 rate=48000 0 alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.iec958-stereo module-alsa-card.c s16le 2ch 48000Hz SUSPENDED 5 PulseEffects_apps module-null-sink.c s16le 2ch 48000Hz RUNNING 6 PulseEffects_mic module-null-sink.c s16le 2ch 48000Hz SUSPENDED 0 alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.iec958-stereo.monitor module-alsa-card.c s16le 2ch 48000Hz SUSPENDED 1 alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.iec958-stereo module-alsa-card.c s16le 2ch 48000Hz SUSPENDED 6 PulseEffects_apps.monitor module-null-sink.c s16le 2ch 48000Hz IDLE 7 PulseEffects_mic.monitor module-null-sink.c s16le 2ch 48000Hz SUSPENDED 15 5 13 protocol-native.c s16le 2ch 48000Hz 0 module-systemd-login.c (null) 1 protocol-native.c xfce4-volumed 2 protocol-native.c pasystray 6 module-x11-xsmp.c (null) 13 protocol-native.c mscore 21 protocol-native.c pactl 0 alsa_card.pci-0000_00_1b.0 module-alsa-card.c 1 alsa_card.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00 module-alsa-card.c

OUTPUT FROM pacmd list-sink: The PulseAudio daemon isn't executed, or is not executed like a session daemon.

OUPUT FROM pacmd list-sink-inputs:

OUTPUT FROM pacmd list-sources: OUTPUT FROM pacmd list-source-outputs: OUTPUT FROM pulseaudio --dump-conf: daemonize = no fail = yes high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 allow-module-loading = yes allow-exit = yes use-pid-file = yes system-instance = no local-server-type = user cpu-limit = no enable-shm = yes flat-volumes = no lock-memory = no exit-idle-time = 20 scache-idle-time = 20 dl-search-path = /usr/lib/pulse-12.2/modules default-script-file = /etc/pulse/default.pa load-default-script-file = yes log-target = log-level = notice resample-method = auto avoid-resampling = yes enable-remixing = yes remixing-use-all-sink-channels = yes enable-lfe-remixing = yes lfe-crossover-freq = 0 default-sample-format = s16le default-sample-rate = 48000 alternate-sample-rate = 48000 default-sample-channels = 2 default-channel-map = front-left,front-right default-fragments = 4 default-fragment-size-msec = 25 enable-deferred-volume = yes deferred-volume-safety-margin-usec = 1 deferred-volume-extra-delay-usec = 0 shm-size-bytes = 0 log-meta = no log-time = no log-backtrace = 0 rlimit-fsize = -1 rlimit-data = -1 rlimit-stack = -1 rlimit-core = -1 rlimit-rss = -1 rlimit-as = -1 rlimit-nproc = -1 rlimit-nofile = 256 rlimit-memlock = -1 rlimit-locks = -1 rlimit-sigpending = -1 rlimit-msgqueue = -1 rlimit-nice = 31 rlimit-rtprio = 9 rlimit-rttime = 200000 Even the fact that it seems like PulseAudio would not be running, IT IS ALREADY RUNNING! (I can confirm that because I can run any other apps with pulseaudio working so fine!) So... Some idea how can I try to work around this? Greetings from Chile!
wwmm commented 6 years ago

Try to get the segmentation fault core dump as described in Reporting-Bugs

jotape1960 commented 6 years ago

I added the information you asked from me. Please, help!!!

wwmm commented 6 years ago

In this case the core dump will be more useful. The log you added above will not help to find the source of a segmentation fault

jotape1960 commented 6 years ago

???

Sorry, but... I don't know how to perform that "core dump" process you wrote about. Can you guide me, please?

wwmm commented 6 years ago

It is simple. After a crash follow the steps in the Getting Coredumps at the bottom of Reporting-Bugs

jotape1960 commented 6 years ago

I tried it, but... I got the message: "sudo: coredumpctl order not found". So... How can I do it???

wwmm commented 6 years ago

hummm... What is the output of ls /var/lib/systemd/coredump?

jotape1960 commented 6 years ago

The output of that command is nothing. There is nothing to show it. What does it mean? ???

jotape1960 commented 6 years ago

BTW: I can see my system doesn't have the "coredump" utility package installed by default. I can install it by hand, but... when I try to install it the system asks me to uninstalled the "Apport" package (which I don't have any clue if it is an important part of the system). So... I don't know what to do!!!

jotape1960 commented 6 years ago

I discovered this file into the "var/crash" directory:

/var/crash/_usr_bin_pulseeffects.1000.crash

_usr_bin_pulseeffects.1000.txt

Maybe... It is a helpful data... I hope so!!!

wwmm commented 6 years ago

It seems your system does not use systemd or has customized it in a way that its behavior is very different from the one I have in Arch Linux. In this case I don't know what would be the easy way to get the core dump.

The file you uploaded has a line with CoreDump: base64. So it seems that the core dump is there. The problem is that the output is encrypted in base64. I can not read it like this. I imagine that the utility that created this file has a way to properly output the saved core dump.

wwmm commented 6 years ago

I have just read the info you added in the top post. Running as root should not be necessary.

jotape1960 commented 6 years ago

I see, but... I don't know how to help you to about that. Why this computer, only, has this problem? How can I fix it? Should I installed all the system, from zero, again? ???

wwmm commented 6 years ago

There is no need to reinstall. You just have to find out how to get crash core dumps in UbuntuStudio 18.04.1 LTS. As I use Arch Linux I have no idea

jotape1960 commented 6 years ago

I see. I'm asking some help from Ask Ubuntu Forum about that. When I can get that "core dump", I will post it here. Thank you so much for your time!!!

Blahpunkt commented 6 years ago

@jotape1960 you can use a tool called coredumpctl to catch the messages. At least I used that program to catch mine when I had the same problem (see issue #345)

jotape1960 commented 6 years ago

Blahpunkt I did what you told me and I just get this:

Mon 2018-11-05 16:38:18 -03 11745 1000 1000 6 present /usr/bin/pulseeffects

I don't know if that is some useful data...

jotape1960 commented 6 years ago

I performed a new test today and I get the following crash report:

_usr_bin_pulseeffects.1000.txt

I hope it can be useful data!!!

wwmm commented 6 years ago

I think you misunderstood the wiki. The output of coredumpctl list is used to get the process PID. Based on your post above this PID value is 11745. Now that you have the PID of the process that crashed run: sudo coredumpctl info 11745

Put here its output

betterphp commented 6 years ago

I've installed from the PPA in the wiki and also getting a segfault, here's my dump incase it helps

           PID: 15033 (pulseeffects)
           UID: 1000 (jacek)
           GID: 1000 (jacek)
        Signal: 11 (SEGV)
     Timestamp: Tue 2018-11-06 10:00:28 GMT (58s ago)
  Command Line: pulseeffects
    Executable: /usr/bin/pulseeffects
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (jacek)
       Boot ID: 686772764ec84892944f8758c03d0280
    Machine ID: eea1c4afe0287570a9a9d6cc555cc707
      Hostname: jacek-work-desktop
       Storage: /var/lib/systemd/coredump/core.pulseeffects.1000.686772764ec84892944f8758c03d0280.15033.1541498428000000.lz4
       Message: Process 15033 (pulseeffects) of user 1000 dumped core.

                Stack trace of thread 15033:
                #0  0x000056074a8f4687 n/a (pulseeffects)
                #1  0x000056074a8f4c7e n/a (pulseeffects)
                #2  0x000056074a8def3a n/a (pulseeffects)
                #3  0x000056074a89ebfa n/a (pulseeffects)
                #4  0x00007f6f45ad6add _ZN3Gio17Application_Class16startup_callbackEP13_GApplication (libgiomm-2.4.so.1)
                #5  0x00007f6f4785810d g_closure_invoke (libgobject-2.0.so.0)
                #6  0x00007f6f4786b09e n/a (libgobject-2.0.so.0)
                #7  0x00007f6f47873685 g_signal_emit_valist (libgobject-2.0.so.0)
                #8  0x00007f6f4787409f g_signal_emit (libgobject-2.0.so.0)
                #9  0x00007f6f46a3e1a2 g_application_register (libgio-2.0.so.0)
                #10 0x00007f6f46a3e9b7 n/a (libgio-2.0.so.0)
                #11 0x00007f6f45ad66ab _ZN3Gio11Application24local_command_line_vfuncERPPcRi (libgiomm-2.4.so.1)
                #12 0x00007f6f45ad68ed _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi (libgiomm-2.4.so.1)
                #13 0x00007f6f46a3ed46 g_application_run (libgio-2.0.so.0)
                #14 0x000056074a899b3c main (pulseeffects)
                #15 0x00007f6f43aaab97 __libc_start_main (libc.so.6)
                #16 0x000056074a89a76a n/a (pulseeffects)

                Stack trace of thread 15034:
                #0  0x00007f6f43b9dbf9 __GI___poll (libc.so.6)
                #1  0x00007f6f47d68439 n/a (libglib-2.0.so.0)
                #2  0x00007f6f47d6854c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f6f47d68591 n/a (libglib-2.0.so.0)
                #4  0x00007f6f47d8fe85 n/a (libglib-2.0.so.0)
                #5  0x00007f6f43e816db start_thread (libpthread.so.0)
                #6  0x00007f6f43baa88f __clone (libc.so.6)

                Stack trace of thread 15036:
                #0  0x00007f6f43b9dbf9 __GI___poll (libc.so.6)
                #1  0x00007f6f47d68439 n/a (libglib-2.0.so.0)
                #2  0x00007f6f47d6854c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f6f3901536d n/a (libdconfsettings.so)
                #4  0x00007f6f47d8fe85 n/a (libglib-2.0.so.0)
                #5  0x00007f6f43e816db start_thread (libpthread.so.0)
                #6  0x00007f6f43baa88f __clone (libc.so.6)

                Stack trace of thread 15035:
                #0  0x00007f6f43b9dbf9 __GI___poll (libc.so.6)
                #1  0x00007f6f47d68439 n/a (libglib-2.0.so.0)
                #2  0x00007f6f47d687d2 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007f6f46a6af66 n/a (libgio-2.0.so.0)
                #4  0x00007f6f47d8fe85 n/a (libglib-2.0.so.0)
                #5  0x00007f6f43e816db start_thread (libpthread.so.0)
                #6  0x00007f6f43baa88f __clone (libc.so.6)

                Stack trace of thread 15037:
                #0  0x00007f6f43b9dbf9 __GI___poll (libc.so.6)
                #1  0x00007f6f48064481 n/a (libpulse.so.0)
                #2  0x00007f6f48055e40 pa_mainloop_poll (libpulse.so.0)
                #3  0x00007f6f480564d0 pa_mainloop_iterate (libpulse.so.0)
                #4  0x00007f6f48056560 pa_mainloop_run (libpulse.so.0)
                #5  0x00007f6f480643c9 n/a (libpulse.so.0)
                #6  0x00007f6f4385d238 n/a (libpulsecommon-12.2.so)
                #7  0x00007f6f43e816db start_thread (libpthread.so.0)
                #8  0x00007f6f43baa88f __clone (libc.so.6)
betterphp commented 6 years ago

This also might be useful

jacek@jacek-work-desktop: $ G_MESSAGES_DEBUG=pulseeffects pulseeffects
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.532: application: PE version: 4.3.9
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.534: pulse_manager: context is connecting
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: context is authorizing
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: context is setting name
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: context is ready
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: connected to: unix:/run/user/1000/pulse/native
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: protocol version: 32
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: Pulseaudio version: 11.1
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: default pulseaudio source: bluez_sink.00_16_94_25_DB_E8.a2dp_sink.monitor
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: default pulseaudio sink: bluez_sink.00_16_94_25_DB_E8.a2dp_sink
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.535: pulse_manager: loading Pulseeffects applications output sink...
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: default pulseaudio sink sampling rate: 44100 Hz
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: default pulseaudio sink audio format: s16le
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: sink loaded
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: loading Pulseeffects microphone output sink...
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: default pulseaudio source sampling rate: 44100 Hz
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: default pulseaudio source audio format: s16le
(pulseeffects:16917): pulseeffects-DEBUG: 10:25:54.536: pulse_manager: sink loaded
Segmentation fault (core dumped)
jotape1960 commented 6 years ago

I performed what you asked for me and I got this:

From sudo coredumpctl info 11745:

        PID: 11745 (pulseeffects)
       UID: 1000 (jjpg)
       GID: 1000 (jjpg)
    Signal: 6 (ABRT)
 Timestamp: Mon 2018-11-05 16:38:17 -03 (23h ago)

Command Line: pulseeffects Executable: /usr/bin/pulseeffects Control Group: /user.slice/user-1000.slice/session-4.scope Unit: session-4.scope Slice: user-1000.slice Session: 4 Owner UID: 1000 (jjpg) Boot ID: 4c33e5c1d335424aa8050147fbbd2a0f Machine ID: 064a71b34b9545f784220fa8007d9de1 Hostname: jjpg-MS-7788 Storage: /var/lib/systemd/coredump/core.pulseeffects.1000.4c33e5c1d335424 Message: Process 11745 (pulseeffects) of user 1000 dumped core.

            Stack trace of thread 11745:
            #0  0x00007f503bd6ee97 __GI_raise (libc.so.6)
            #1  0x00007f503bd70801 __GI_abort (libc.so.6)
            #2  0x00007f50402fdf23 pa_operation_get_state (libpulse.so.0)
            #3  0x000055f3b0b0c489 n/a (pulseeffects)
            #4  0x000055f3b0b325eb n/a (pulseeffects)
            #5  0x000055f3b0af0bfa n/a (pulseeffects)
            #6  0x00007f503dd7dadd _ZN3Gio17Application_Class16startup_callb
            #7  0x00007f503faff10d g_closure_invoke (libgobject-2.0.so.0)
            #8  0x00007f503fb1209e n/a (libgobject-2.0.so.0)
            #9  0x00007f503fb1a685 g_signal_emit_valist (libgobject-2.0.so.0
            #10 0x00007f503fb1b09f g_signal_emit (libgobject-2.0.so.0)
            #11 0x00007f503ece51a2 g_application_register (libgio-2.0.so.0)
            #12 0x00007f503ece59b7 n/a (libgio-2.0.so.0)
            #13 0x00007f503dd7d6ab _ZN3Gio11Application24local_command_line_
            #14 0x00007f503dd7d8ed _ZN3Gio17Application_Class33local_command
            #15 0x00007f503ece5d46 g_application_run (libgio-2.0.so.0)
            #16 0x000055f3b0aebb3c main (pulseeffects)
            #17 0x00007f503bd51b97 __libc_start_main (libc.so.6)
            #18 0x000055f3b0aec76a n/a (pulseeffects)

            Stack trace of thread 11746:
            #0  0x00007f503be44bf9 __GI___poll (libc.so.6)
            #1  0x00007f504000f439 n/a (libglib-2.0.so.0)
            #2  0x00007f504000f54c g_main_context_iteration (libglib-2.0.so.
            #3  0x00007f504000f591 n/a (libglib-2.0.so.0)
            #4  0x00007f5040036e85 n/a (libglib-2.0.so.0)
            #5  0x00007f503c1286db start_thread (libpthread.so.0)
            #6  0x00007f503be5188f __clone (libc.so.6)

            Stack trace of thread 11747:
            #0  0x00007f503be44bf9 __GI___poll (libc.so.6)
            #1  0x00007f504000f439 n/a (libglib-2.0.so.0)
            #2  0x00007f504000f7d2 g_main_loop_run (libglib-2.0.so.0)
            #3  0x00007f503ed11f66 n/a (libgio-2.0.so.0)
            #4  0x00007f5040036e85 n/a (libglib-2.0.so.0)
            #5  0x00007f503c1286db start_thread (libpthread.so.0)
            #6  0x00007f503be5188f __clone (libc.so.6)

            Stack trace of thread 11749:
            #0  0x00007f503be44bf9 __GI___poll (libc.so.6)
            #1  0x00007f504030b481 n/a (libpulse.so.0)
            #2  0x00007f50402fce40 pa_mainloop_poll (libpulse.so.0)
            #3  0x00007f50402fd4d0 pa_mainloop_iterate (libpulse.so.0)
            #4  0x00007f50402fd560 pa_mainloop_run (libpulse.so.0)
            #4  0x00007f50402fd560 pa_mainloop_run (libpulse.so.0)
            #5  0x00007f504030b3c9 n/a (libpulse.so.0)
            #6  0x00007f503bb04238 n/a (libpulsecommon-12.2.so)
            #7  0x00007f503c1286db start_thread (libpthread.so.0)
            #8  0x00007f503be5188f __clone (libc.so.6)

            Stack trace of thread 11748:
            #0  0x00007f504005239d g_variant_type_info_get (libglib-2.0.so.0
            #1  0x00007f504004b129 n/a (libglib-2.0.so.0)
            #2  0x00007f5040047df4 g_variant_builder_end (libglib-2.0.so.0)
            #3  0x00007f503ed0ad01 g_dbus_message_to_blob (libgio-2.0.so.0)
            #4  0x00007f503ecff3ec n/a (libgio-2.0.so.0)
            #5  0x00007f503ed00856 n/a (libgio-2.0.so.0)
            #6  0x00007f503ed038b2 g_dbus_connection_send_message_with_reply
            #7  0x00007f503ed03c7a n/a (libgio-2.0.so.0)
            #8  0x00007f503ed06445 g_dbus_connection_call (libgio-2.0.so.0)
            #9  0x00007f5030f6026f n/a (libdconfsettings.so)
            #10 0x00007f504000f0f5 g_main_context_dispatch (libglib-2.0.so.0
            #11 0x00007f504000f4c0 n/a (libglib-2.0.so.0)
            #12 0x00007f504000f54c g_main_context_iteration (libglib-2.0.so.
            #13 0x00007f5030f6036d n/a (libdconfsettings.so)
            #14 0x00007f5040036e85 n/a (libglib-2.0.so.0)
            #15 0x00007f503c1286db start_thread (libpthread.so.0)
            #16 0x00007f503be5188f __clone (libc.so.6)

lines 64-86/86 (END)

Now, I tested this issue today, again and I got this:

From sudo coredumpctl list:

TIME PID UID GID SIG COREFILE EXE Tue 2018-11-06 16:33:28 -03 12373 1000 1000 6 present /usr/bin/pulseeffects

From sudo coredumpctl info 12373:

       PID: 12373 (pulseeffects)
       UID: 1000 (jjpg)
       GID: 1000 (jjpg)
    Signal: 6 (ABRT)
 Timestamp: Tue 2018-11-06 16:33:27 -03 (7min ago)

Command Line: pulseeffects Executable: /usr/bin/pulseeffects Control Group: /user.slice/user-1000.slice/session-4.scope Unit: session-4.scope Slice: user-1000.slice Session: 4 Owner UID: 1000 (jjpg) Boot ID: e7a6dc02fe2047e3bf8decdd792bcee6 Machine ID: 064a71b34b9545f784220fa8007d9de1 Hostname: jjpg-MS-7788 Storage: /var/lib/systemd/coredump/core.pulseeffects.1000.e7a6dc02fe2047e Message: Process 12373 (pulseeffects) of user 1000 dumped core.

            Stack trace of thread 12373:
            #0  0x00007f820c803e97 __GI_raise (libc.so.6)
            #1  0x00007f820c805801 __GI_abort (libc.so.6)
            #2  0x00007f8210d92f23 pa_operation_get_state (libpulse.so.0)
            #3  0x000055f0b1eae489 n/a (pulseeffects)
            #4  0x000055f0b1ed45eb n/a (pulseeffects)
            #5  0x000055f0b1e92bfa n/a (pulseeffects)
            #6  0x00007f820e812add _ZN3Gio17Application_Class16startup_callb
            #7  0x00007f821059410d g_closure_invoke (libgobject-2.0.so.0)
            #8  0x00007f82105a709e n/a (libgobject-2.0.so.0)
            #9  0x00007f82105af685 g_signal_emit_valist (libgobject-2.0.so.0
            #10 0x00007f82105b009f g_signal_emit (libgobject-2.0.so.0)
            #11 0x00007f820f77a1a2 g_application_register (libgio-2.0.so.0)
            #12 0x00007f820f77a9b7 n/a (libgio-2.0.so.0)
            #13 0x00007f820e8126ab _ZN3Gio11Application24local_command_line_
            #14 0x00007f820e8128ed _ZN3Gio17Application_Class33local_command
            #15 0x00007f820f77ad46 g_application_run (libgio-2.0.so.0)
            #16 0x000055f0b1e8db3c main (pulseeffects)
            #17 0x00007f820c7e6b97 __libc_start_main (libc.so.6)
            #18 0x000055f0b1e8e76a n/a (pulseeffects)

            Stack trace of thread 12375:
            #0  0x00007f820c8d9bf9 __GI___poll (libc.so.6)
            #1  0x00007f8210aa4439 n/a (libglib-2.0.so.0)
            #2  0x00007f8210aa47d2 g_main_loop_run (libglib-2.0.so.0)
            #3  0x00007f820f7a6f66 n/a (libgio-2.0.so.0)
            #4  0x00007f8210acbe85 n/a (libglib-2.0.so.0)
            #5  0x00007f820cbbd6db start_thread (libpthread.so.0)
            #6  0x00007f820c8e688f __clone (libc.so.6)

            Stack trace of thread 12376:
            #0  0x00007f820f794405 n/a (libgio-2.0.so.0)
            #1  0x00007f820f795856 n/a (libgio-2.0.so.0)
            #2  0x00007f820f7988b2 g_dbus_connection_send_message_with_reply
            #3  0x00007f820f798c7a n/a (libgio-2.0.so.0)
            #4  0x00007f820f79b445 g_dbus_connection_call (libgio-2.0.so.0)
            #5  0x00007f82019f526f n/a (libdconfsettings.so)
            #6  0x00007f8210aa40f5 g_main_context_dispatch (libglib-2.0.so.0
            #7  0x00007f8210aa44c0 n/a (libglib-2.0.so.0)
            #8  0x00007f8210aa454c g_main_context_iteration (libglib-2.0.so.
            #9  0x00007f82019f536d n/a (libdconfsettings.so)
            #10 0x00007f8210acbe85 n/a (libglib-2.0.so.0)
            #11 0x00007f820cbbd6db start_thread (libpthread.so.0)
            #12 0x00007f820c8e688f __clone (libc.so.6)

            Stack trace of thread 12377:
            #0  0x00007f820c8d9bf9 __GI___poll (libc.so.6)
            #1  0x00007f8210da0481 n/a (libpulse.so.0)
            #2  0x00007f8210d91e40 pa_mainloop_poll (libpulse.so.0)
            #3  0x00007f8210d924d0 pa_mainloop_iterate (libpulse.so.0)
            #4  0x00007f8210d92560 pa_mainloop_run (libpulse.so.0)
            #5  0x00007f8210da03c9 n/a (libpulse.so.0)
            #6  0x00007f820c599238 n/a (libpulsecommon-12.2.so)
            #7  0x00007f820cbbd6db start_thread (libpthread.so.0)
            #8  0x00007f820c8e688f __clone (libc.so.6)

            Stack trace of thread 12374:
            #0  0x00007f820c8d9bf9 __GI___poll (libc.so.6)
            #1  0x00007f8210aa4439 n/a (libglib-2.0.so.0)
            #2  0x00007f8210aa454c g_main_context_iteration (libglib-2.0.so.
            #3  0x00007f8210aa4591 n/a (libglib-2.0.so.0)
            #4  0x00007f8210acbe85 n/a (libglib-2.0.so.0)
            #5  0x00007f820cbbd6db start_thread (libpthread.so.0)
            #6  0x00007f820c8e688f __clone (libc.so.6)

lines 60-82/82 (END)

I hope all data will be helpful to fix the issue!!!

wwmm commented 6 years ago

PE 4.4.0 has a few changes that should help with this problem. I don't know if it is already available in your repository

jotape1960 commented 6 years ago

I see. But... What is the specific problem??? Why it happens only in one of two computers if both are exactly the same machines and system???

wwmm commented 6 years ago

It is hard to say. This feels like a bug in Pulseaudio that is triggered by something very specific in the users system that I do not have here. The fact is that only in the computer of a few people one of the Pulseaudio's functions I need to use is returning a null value for some reason that is not clear. Because of this null value that the function pa_operation_get_state is crashing. What I did in PE 4.4.0 is checking if the returned value is null. In case it is I do not call pa_operation_get_state. But this isn't really a solution. I do not see a reason for Pulseaudio to give a null value in the first place.

jotape1960 commented 6 years ago

I see! BTW: I've tried to change the PulseEffects parameters, opening it with sudo privileges (which is the only way the app works), and I tested all the possible combinations and... Nothing!!! I tried with black theme, I tried with all the input and output devices, I tried with default parameters... NOTHING!!! The app only works if I use full sudo privileges. Please!!! Try to find a final solution!!! This app is absolutely important to me (because my life is about record, edit and playback audio!!!)

wwmm commented 6 years ago

This is a good question. I have never executed PulseEffects as root. So I am not aware of the consequences. If it only works with sudo some file must have been taken by the root user. Did you try to create a new user and test PulseEffects with it? This would help to know if the problem is only with the current user or in the whole system

aldevel commented 6 years ago

KDE neon 5.14 based on Ubuntu 18.04 | KDE Frameworks Verion 5.51.0 | Qt Version 5.11.2 | Kernel Version 4.15.0-38-generic For me, it's started several times then it's just stop starting. Altough there were no sound when it's started and I wasn't able to solve that. Anyway it's not even starting now. I found this searching by journalctl -ex:

flatpak-com.github.wwmm.pulseeffects-19477.scope: Failed to add PIDs to scope's control group: Permission denied

Is it related maybe? https://github.com/flathub/org.gimp.GIMP/issues/23 Anyway, after I put systemd.legacy_systemd_cgroup_controller=1 into grub it won't start either. I got these line related to this I think:

xdg-desktop-por[4012]: Error getting permissions: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for notification
org.freedesktop.impl.portal.desktop.kde[2099]: xdp-kde-notification: AddNotification called with parameters:
org.freedesktop.impl.portal.desktop.kde[2099]: xdp-kde-notification:     app_id:  "com.github.wwmm.pulseeffects"
org.freedesktop.impl.portal.desktop.kde[2099]: xdp-kde-notification:     id:  "reset"
org.freedesktop.impl.portal.desktop.kde[2099]: xdp-kde-notification:     notification:  QMap(("body", QVariant(QString, "It is recommended to reset its configuration after an update. Do you want to do this?"))("buttons", QVariant(QDBusArgument, ))("priority", QVariant(QString, "normal"))("title", QVariant(QString, "PulseEffects was updated")))

Also I tried to start pulseeffects like this without success:

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=pulseeffects --socket=pulseaudio --device=all --filesystem=xdg-run/dconf --filesystem=~/.config/dconf:ro --talk-name=ca.desrt.dconf --env=DCONF_USER_CONFIG_DIR=.config/dconf com.github.wwmm.pulseeffects @@ %F @@

Any suggestion? Thanks!

wwmm commented 6 years ago

I know nothing about flatpak. So I do not know if this error has any side effect to PulseEffects. What is printed in the terminal when you run PE in debug mode G_MESSAGES_DEBUG=pulseeffects pulseeffects? This will have to be adjusted to the flatpak way of starting apps

aldevel commented 6 years ago

Wow that was a quick response. It says

(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.832: application: PE version: 4.3.8
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: context is connecting
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: context is authorizing
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: context is setting name
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: context is ready
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: connected to: unix:/run/user/1000/pulse/native
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: protocol version: 32
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: Pulseaudio version: 11.1
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: default pulseaudio source: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: default pulseaudio sink: PulseEffects_mic
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: loading Pulseeffects applications output sink...
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: default pulseaudio sink sampling rate: 44100 Hz
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.833: pulse_manager: default pulseaudio sink audio format: s16le
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.834: pulse_manager: loading Pulseeffects microphone output sink...
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.834: pulse_manager: default pulseaudio source sampling rate: 44100 Hz
(pulseeffects:3): pulseeffects-DEBUG: 21:55:53.834: pulse_manager: default pulseaudio source audio format: s16le
Assertion 'o' failed at ../../src/pulse/operation.c:133, function pa_operation_get_state(). Aborting.

I just realized that I'm not in thread of the Flatpak's PulseEffects. Is my bug Flatpak related instead and should I report this issue here https://github.com/flathub/com.github.wwmm.pulseeffects/issues or my bug could be application related issue directly?

wwmm commented 6 years ago

Do not report it in the flatpak package page. Other users have had this problem too and this bug is either in PulseEffects or in Pulseaudio. PulseEffects 4.4.0 has a few changes that should avoid this crash. In case this version is not available in flatpak yet try to do a reset dconf reset -f /com/github/wwmm/pulseeffects/. Sometimes it helps

aldevel commented 6 years ago

Thanks, dconf reset -f /com/github/wwmm/pulseeffects/ solved it indeed, gui is starting again. Yes, Flatpak version is still 4.3.8 so that's an older one. Also I have the module-device-manager issue. How can I set this permanently to make it work till KDE neon update to newer pulseadio version because it's still 1:11.1-1 on its packaging?

hadware commented 6 years ago

I also get a segfault when starting it. Installed it from PPA, ubuntu 18.04. I gest the same debugging messages as the one cited previously. I'll check the coredump later to get a stacktrace.

btw, dconf reset doesn't work with me.

aldevel commented 6 years ago

I'll avoid PPAs especially in KDE neon installations. Till PulseAudio 12 won't come to neon, I just startup a script with dconf reset -f /com/github/wwmm/pulseeffects/ and it works great. Although PulseEffect from Flatpak won't startup, simple I make it startup in plasma settings that's all. Now it works for me. Awesome application, I really love it, thanks for the help and for the software!

wwmm commented 6 years ago

@aldevel the problems with module-device-manager are only solved if you use Pulseaudio 12. If you have an older Pulseaudio you will need to unload this module before executing PulseEffects

@hadware the output of the coredump would be welcome. This way I can know where the segfault is happening. If we are lucky we will not have this problem in PE 4.4.0. In any case I should ask the Pulseaudio developers about this. The crash is happening because Pulseaudio is returning a null pointer in a function where I think it should not be doing this. And to make things even more odd this does not happen to everybody. It never happens in my computer =/

Blahpunkt commented 6 years ago

And to make things even more odd this does not happen to everybody. It never happens in my computer =/

looking at the comments it mainly seems to happen with Ubuntu

hadware commented 6 years ago

@hadware the output of the coredump would be welcome. This way I can know where the segfault is happening. If we are lucky we will not have this problem in PE 4.4.0. In any case I should ask the Pulseaudio developers about this. The crash is happening because Pulseaudio is returning a null pointer in a function where I think it should not be doing this. And to make things even more odd this does not happen to everybody. It never happens in my computer =/

As mentioned before, it seems that get_pa_operation_state is behaving unexpectedly, but are you sure it's returning a null pointer? I mean, how can a pa_operation object have a null pointer for its attribute state when it's supposed to be a pa_operation_state_t?

I mean, my C is rusty but I don't see how can this function is able to return a null pointer:

pa_operation_state_t pa_operation_get_state(pa_operation *o) {
    pa_assert(o);
    pa_assert(PA_REFCNT_VALUE(o) >= 1);

    return o->state;
}

BTW, i'll get my core dump in about an hour. Stay tuned

hadware commented 6 years ago

Alright, here it is... no pa_operation_get_state in there it seems 

PID: 8583 (pulseeffects)
           UID: 1000 (hadware)
           GID: 1000 (hadware)
        Signal: 11 (SEGV)
     Timestamp: Fri 2018-11-09 21:14:24 CET (4min 6s ago)
  Command Line: /usr/bin/pulseeffects --gapplication-service
    Executable: /usr/bin/pulseeffects
 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
          Unit: user@1000.service
     User Unit: dbus.service
         Slice: user-1000.slice
     Owner UID: 1000 (hadware)
       Boot ID: 2267ec44bad44d3ab69b7fb22e8934ac
    Machine ID: 0205981fc38a4217a177484c630003ea
      Hostname: hadware-t450
       Storage: /var/lib/systemd/coredump/core.pulseeffects.1000.2267ec44bad44d3ab69b7fb22e8934ac.8583.1541794464000000.lz4
       Message: Process 8583 (pulseeffects) of user 1000 dumped core.

                Stack trace of thread 8583:
                #0  0x0000562f8965f687 n/a (pulseeffects)
                #1  0x0000562f8965fc7e n/a (pulseeffects)
                #2  0x0000562f89649f3a n/a (pulseeffects)
                #3  0x0000562f89609bfa n/a (pulseeffects)
                #4  0x00007ffbc5484add _ZN3Gio17Application_Class16startup_callbackEP13_GApplication (libgiomm-2.4.so.1)
                #5  0x00007ffbc720610d g_closure_invoke (libgobject-2.0.so.0)
                #6  0x00007ffbc721909e n/a (libgobject-2.0.so.0)
                #7  0x00007ffbc7221685 g_signal_emit_valist (libgobject-2.0.so.0)
                #8  0x00007ffbc722209f g_signal_emit (libgobject-2.0.so.0)
                #9  0x00007ffbc63ec1a2 g_application_register (libgio-2.0.so.0)
                #10 0x00007ffbc63ec9b7 n/a (libgio-2.0.so.0)
                #11 0x00007ffbc54846ab _ZN3Gio11Application24local_command_line_vfuncERPPcRi (libgiomm-2.4.so.1)
                #12 0x00007ffbc54848ed _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi (libgiomm-2.4.so.1)
                #13 0x00007ffbc63ecd46 g_application_run (libgio-2.0.so.0)
                #14 0x0000562f89604b3c main (pulseeffects)
                #15 0x00007ffbc3458b97 __libc_start_main (libc.so.6)
                #16 0x0000562f8960576a n/a (pulseeffects)

                Stack trace of thread 8587:
                #0  0x00007ffbc354bbf9 __GI___poll (libc.so.6)
                #1  0x00007ffbc7716439 n/a (libglib-2.0.so.0)
                #2  0x00007ffbc771654c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007ffbc7716591 n/a (libglib-2.0.so.0)
                #4  0x00007ffbc773de85 n/a (libglib-2.0.so.0)
                #5  0x00007ffbc382f6db start_thread (libpthread.so.0)
                #6  0x00007ffbc355888f __clone (libc.so.6)

                Stack trace of thread 8588:
                #0  0x00007ffbc354bbf9 __GI___poll (libc.so.6)
                #1  0x00007ffbc7716439 n/a (libglib-2.0.so.0)
                #2  0x00007ffbc77167d2 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007ffbc6418f66 n/a (libgio-2.0.so.0)
                #4  0x00007ffbc773de85 n/a (libglib-2.0.so.0)
                #5  0x00007ffbc382f6db start_thread (libpthread.so.0)
                #6  0x00007ffbc355888f __clone (libc.so.6)

                Stack trace of thread 8589:
                #0  0x00007ffbc354bbf9 __GI___poll (libc.so.6)
                #1  0x00007ffbc7716439 n/a (libglib-2.0.so.0)
                #2  0x00007ffbc771654c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007ffbb3bf036d n/a (libdconfsettings.so)
                #4  0x00007ffbc773de85 n/a (libglib-2.0.so.0)
                #5  0x00007ffbc382f6db start_thread (libpthread.so.0)
                #6  0x00007ffbc355888f __clone (libc.so.6)

                Stack trace of thread 8590:
                #0  0x00007ffbc354bbf9 __GI___poll (libc.so.6)
                #1  0x00007ffbc7a12481 n/a (libpulse.so.0)
                #2  0x00007ffbc7a03e40 pa_mainloop_poll (libpulse.so.0)
                #3  0x00007ffbc7a044d0 pa_mainloop_iterate (libpulse.so.0)
                #4  0x00007ffbc7a04560 pa_mainloop_run (libpulse.so.0)
                #5  0x00007ffbc7a123c9 n/a (libpulse.so.0)
                #6  0x00007ffbc320b238 n/a (libpulsecommon-12.2.so)
                #7  0x00007ffbc382f6db start_thread (libpthread.so.0)
                #8  0x00007ffbc355888f __clone (libc.so.6)
wwmm commented 6 years ago

@hadware the problem is not in pa_operation_get_state but in the operation given to it as argument. This one is null in the machines when the segault is caused by a crash in pa_operation_get_state. If you take a look at the file pulse_manager.cpp you will see that there are a lot of pulseaudio functions that return an pa_operation pointer so we can wait for an operation to be done. I know these pointers can be null in a few situations. But I do not see why the output of functions like pa_context_get_sink_info_by_name are returning null operation pointers only for some people

Your core dump seems to have other source. And the crash seems to be happening a lot faster than in the other cases. What is printed in the terminal when PE is run in debug mode? G_MESSAGES_DEBUG=pulseeffects pulseeffects

hadware commented 6 years ago

There you go:

(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.547: application: PE version: 4.3.9
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.560: pulse_manager: context is connecting
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.560: pulse_manager: context is authorizing
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.561: pulse_manager: context is setting name
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.561: pulse_manager: context is ready
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.561: pulse_manager: connected to: unix:/run/user/1000/pulse/native
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.561: pulse_manager: protocol version: 32
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: Pulseaudio version: 11.1
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: default pulseaudio source: alsa_input.pci-0000_00_1b.0.analog-stereo
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: default pulseaudio sink: bluez_sink.E4_22_A5_BD_52_5F.a2dp_sink
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: loading Pulseeffects applications output sink...
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: default pulseaudio sink sampling rate: 44100 Hz
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.562: pulse_manager: default pulseaudio sink audio format: s16le
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.592: pulse_manager: sink loaded
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.592: pulse_manager: loading Pulseeffects microphone output sink...
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.592: pulse_manager: default pulseaudio source sampling rate: 44100 Hz
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.592: pulse_manager: default pulseaudio source audio format: s16le
(pulseeffects:15647): pulseeffects-DEBUG: 03:51:10.593: pulse_manager: sink loaded
Erreur de segmentation (core dumped)
hadware commented 6 years ago

Btw, I don't get it, it says "pulsaudio version 11.1" in the debug messages, whereas apt-cache policy pulsaudio tells me it's 12.2. How is that possible?

Another issue (i have no idea if related, but still, mentioning it here) I have is that I seem to be unable to load many pulseaudio modules. I tried achieving what pulseeffects does by other means by using module-ladspa-sink and a module-loopback but was unable to load said modules (they don't appear in the list returned by pactl list modules).

wwmm commented 6 years ago

Take a look at #365. A bad Pulseaudio upgrade can cause that. After reinstalling Pulseaudio everything worked.

jotape1960 commented 6 years ago

I tried the main solution showed at #365 (to erase the bin and reinstall pulseaudio)... It didn't work for me!!! BTW: I discovered something I forgot to comment... The Ubuntu Studio system of this computer was upgraded from old Ubuntu Studio versions (16 and 15 release). The other computers have Ubuntu Studio systems installed "from the scratch". Could it be the reason???

wwmm commented 6 years ago

I think that most if not all of the segmentation faults I received in the last months are somehow caused by problems in the Pulseaudio installation after upgrades. This would explain why I was never able to reproduce this issue in any of my computers. That being said PE 4.4.0 has a few work arounds that should help. Is this version available to you?

jotape1960 commented 6 years ago

Not, that last version of PulseEffects is not available in the official Ubuntu repository. BTW: There was a very rare behaviour when I tried to upgrade from Ubuntu Studio 16.xxx to 17.xxx. Short history: it was not possible (error in the middle of the upgrading process). SO... I decided to wait up the 18.xxx version and...It was a successful upgrading process!!! I'm not a programmer, but I guess something from that could be the cause... Maybe???

hadware commented 6 years ago

Take a look at #365. A bad Pulseaudio upgrade can cause that. After reinstalling Pulseaudio everything worked.

It worked for me. Thanks a lot. I submitted a bug to the pulseaudio package team on launchpad, but they're trying to divert the problem.

mikhailnov commented 5 years ago

@jotape1960 @hadware PulseEffects PPA has a newer PulseAudio than official ubuntu 18.04 repository. Because pulseeffects has problems with older pulseaudio. Don't forget to sudo apt dist-upgrade and reboot

mikhailnov commented 5 years ago

I've made a manual: https://github.com/wwmm/pulseeffects/wiki/Reporting-Bugs#how-to-quickly-make-a-coredump-on-ubuntu

jotape1960 commented 5 years ago

Today I upgrade the system (as usual) and... I got the new 4.4.0 version!!! Now all is working so fine, here!!! Thanks a lot for the new version!!! But... Even the fact that I'm not a programmer... I'd really want to know what was the problem, here... Something related with PulseAudio, only??? ...??? BTW: How can I put a "Solved" mark in this issue???

wwmm commented 5 years ago

Closing the issue is enough :)

Like I said a few posts above version 4.4.0 has a few workarounds to avoid the crash. Not a solution. Whatever is broken in Pulseaudio is still broken. That is assuming that you restarted your computer in the previous updates. Sometimes the cause of the crash is not rebooting after upgrading Pulseaudio