Description of problem: Parole player was running a vid and pavu crashed while opening it. Version-Release number of selected component: pavucontrol-2.0-4.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: pavucontrol crash_function: pa_atomic_load executable: /usr/bin/pavucontrol kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 pa_atomic_load at pulsecore/atomic.h:57 #1 pa_memblock_unref at pulsecore/memblock.c:597 #2 pstream_free at pulsecore/pstream.c:320 #3 pa_pstream_unref at pulsecore/pstream.c:970 #4 do_pstream_read_write at pulsecore/pstream.c:207 #5 dispatch_func at pulse/glib-mainloop.c:584 #10 gtk_main at gtkmain.c:1158 #11 Gtk::Main::run at main.cc:399
Created attachment 843025 [details] File: backtrace
Created attachment 843026 [details] File: cgroup
Created attachment 843027 [details] File: core_backtrace
Created attachment 843028 [details] File: dso_list
Created attachment 843029 [details] File: environ
Created attachment 843030 [details] File: exploitable
Created attachment 843031 [details] File: limits
Created attachment 843032 [details] File: maps
Created attachment 843033 [details] File: open_fds
Created attachment 843034 [details] File: proc_pid_status
Created attachment 843035 [details] File: var_log_messages
Another user experienced a similar problem: après mise à jour du système par fedup reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: pavucontrol crash_function: pa_atomic_load executable: /usr/bin/pavucontrol kernel: 3.12.8-300.fc20.i686+PAE package: pavucontrol-2.0-4.fc20 reason: pavucontrol killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
It is happening to me. I just upgraded to new kernel, but it is still crashing PA volume control on 3.14.3-200.fc20.x86_64 #1 SMP . I am running MATE desktop. when I click on the PA volume control in the soiund menu, it crashes and I lose sound until I log out & back in ( not sure how to restart whatever is brokenO
To be perfectly honest, pulse audio is pretty worthless. There is no stability with it at all. Making it all worse is the fact that Fedora kernel as pretty buggy.
Another user experienced a similar problem: menu- pulseaudio volume control. every time I call it, it kills my sound until I reboot. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: pavucontrol crash_function: pa_atomic_load executable: /usr/bin/pavucontrol kernel: 3.14.4-200.fc20.x86_64 package: pavucontrol-2.0-4.fc20 reason: pavucontrol killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.