Version-Release number of selected component: pulseaudio-10.0-4.fc26 Additional info: reporter: libreport-2.9.0 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: io_callback executable: /usr/bin/pulseaudio global_pid: 1178 kernel: 4.11.0-0.rc1.git0.1.fc26.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 io_callback at pulsecore/protocol-esound.c:1289 #1 dispatch_pollfds at pulse/mainloop.c:655 #2 pa_mainloop_dispatch at pulse/mainloop.c:898 #3 pa_mainloop_iterate at pulse/mainloop.c:929 #4 pa_mainloop_run at pulse/mainloop.c:944
Created attachment 1263810 [details] File: backtrace
Created attachment 1263811 [details] File: cgroup
Created attachment 1263812 [details] File: core_backtrace
Created attachment 1263813 [details] File: dso_list
Created attachment 1263814 [details] File: environ
Created attachment 1263815 [details] File: exploitable
Created attachment 1263816 [details] File: limits
Created attachment 1263817 [details] File: maps
Created attachment 1263818 [details] File: mountinfo
Created attachment 1263819 [details] File: namespaces
Created attachment 1263820 [details] File: open_fds
Created attachment 1263821 [details] File: proc_pid_status
Created attachment 1263822 [details] File: var_log_messages
Similar problem has been detected: Installed Fedora 26 Cinnamon spin under Oracle Virtualbox (Windows 10 host). Underlying hardware is Dell. Upgrades installed. I don't know (yet) if problem will persist. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: io_callback executable: /usr/bin/pulseaudio journald_cursor: s=9ae95b74024045b8a41daa5a41221654;i=1b11;b=cac0dc46f90246c29a7788f589dcd735;m=17505233;t=54c5aa8f2a1f7;x=81f3d6d11cf29376 kernel: 4.11.0-0.rc4.git0.1.fc26.x86_64 package: pulseaudio-10.0-4.fc26 reason: pulseaudio killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
I use Fedora Rawhide MATE-Compiz in host mode (no virtualization). The system is usable, but sometimes before shutdown appears a popup of this error message near the application bar.
Similar problem has been detected: 1.install Fedora 26 as a virtual machine with sound device using KVM 2.log in to GNOME session reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: io_callback executable: /usr/bin/pulseaudio journald_cursor: s=3a9c6a6973964da7aa82020d20de1fc9;i=79a;b=8afb38b2175144dea63441b01f6bc9f1;m=6142c6f8;t=54ca79ded17cf;x=72e00928d287fdae kernel: 4.11.0-0.rc5.git0.1.fc26.x86_64 package: pulseaudio-10.0-4.fc26 reason: pulseaudio killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1272666 [details] coredumpctl file pulseaudio-10.0-4.fc26.x86_64 kernel-4.11.0-0.rc6.git0.1.fc26.x86_64
Created attachment 1280749 [details] pulse audio coredumpctl stack trace Still happening. pulseaudio-10.0-4.fc26.x86_64 4.11.1-300.fc26.x86_64
*** Bug 1440021 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Tried to start Wayland session with freshly installed EasyScreenCast extension. reporter: libreport-2.9.1 backtrace_rating: 3 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: io_callback executable: /usr/bin/pulseaudio journald_cursor: s=8fdd1e861bdf468e8ab5afbfc990ba01;i=4a07d;b=114b77ebfe8c4445bfcac14ae234e254;m=8abfe24ec;t=5518a3f947db1;x=d95d19392c7770c0 kernel: 4.11.3-300.fc26.x86_64 package: pulseaudio-10.0-4.fc26 reason: pulseaudio killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
This crash occurs every time I log out of KDE Plasma (but not if I just reboot or power off).
What have i done: 1. Logout from user1; 2. Login as user2; 3. Logout from user2; 4. Login as user1. Result: recieved popup message about crasg when MATE has loaded.
Same here, Xorg MATE session. kernel-4.11.9-300.fc26.x86_64 pulseaudio-10.0-4.fc26.x86_64
GNOME crashed pulseaudio-10.0-4.fc26.x86_64 kernel-4.11.11-300.fc26.x86_64
I disabled 'PulseAudio Sound System' in Startup Applications. Audio still works, so I assume it is no longer needed. This avoids the crash after login.
(In reply to johan from comment #25) > I disabled 'PulseAudio Sound System' in Startup Applications. > Audio still works, so I assume it is no longer needed. > This avoids the crash after login. How exactly did you disable it? On Fedora 26, there is nothing in GNOME Tweak Tool's Startup Applications. There's just the /etc/xdg/autostart/pulseaudio.desktop file.
Using Cinnamon. Menu->Preferences->Startup Applications. Or taskbar right-click System Settings->Startup Applications. Persisted in files under .config/autostart
(In reply to johan from comment #27) > Using Cinnamon. Menu->Preferences->Startup Applications. Or taskbar > right-click System Settings->Startup Applications. Persisted in files under > .config/autostart OK. That doesn't apply to GNOME/KDE, and there's nothing in ~/.config/autostart/ in the GNOME and KDE versions. Anyway, the problem occurs in KDE all the time but not so much in GNOME. It seems unlikely, but if you have something in ~/.config/autostart/ which *prevents* something about PulseAudio from starting, can you please provide that information/file?
I diffed ~/.config/autostart/pulseaudio.desktop against /etc/xdg/autostart/pulseaudio.desktop, they are (were) the same. Now that Cinnamon disabled it, the ~/.config/autostart version contains extra lines: X-GNOME-Autostart-enabled=false Hidden=true Nothing abnormal, pulseaudio still works.
Just re-enabled autostart of pulseaudio, and the problem reappears immediately after login. (reported as https://bugzilla.redhat.com/show_bug.cgi?id=1433081) Probably should not start pulseaudio twice in the same manner.
(In reply to johan from comment #29) > I diffed ~/.config/autostart/pulseaudio.desktop against > /etc/xdg/autostart/pulseaudio.desktop, they are (were) the same. > Now that Cinnamon disabled it, the ~/.config/autostart version contains > extra lines: > X-GNOME-Autostart-enabled=false > Hidden=true > Nothing abnormal, pulseaudio still works. I tried adapting that for KDE, but it didn't work. However, at least for KDE, I find that the workaround of forcibly stopping PulseAudio by issuing pulseaudio --kill on logout prevents the crashes. Similarly for bug #1385199 and bug #1461661.
(In reply to johan from comment #29) > I diffed ~/.config/autostart/pulseaudio.desktop against > /etc/xdg/autostart/pulseaudio.desktop, they are (were) the same. > Now that Cinnamon disabled it, the ~/.config/autostart version contains > extra lines: You disabled it not cinnamon, did you use cinnamon-settings startup apps? > X-GNOME-Autostart-enabled=false > Hidden=true > Nothing abnormal, pulseaudio still works.
I meant to say that I used Cinnamon's System Settings->Startup Applications to disable pulseaudio. The ~/.config/autostart/pulseaudio.desktop file changed as a consequence.
Just happened to me. I had a problem with nvidia akmod after upgrade/reboot, and had to recompile the kmod. To reload, did a modprobe and an user logout. After the new login, the error happened. Note: I use XFCE, with Gnome extensions enabled, and use desktop auto-login. Not sure about any other change that could specifically affect the problem.
It's crashing here: pa_core_set_current_client(c->protocol->core, c->client); do_work(c); ==> pa_core_set_current_client(c->protocol->core, NULL); From looking at the disassembly I infer that c->protocol was NULL before the second call to pa_core_set_current_client(). It must have become NULL in do_work() because if it were NULL from the start, the segfault would occur before the first call to pa_core_set_current_client(). The calls to pa_core_set_current_client() are not in upstream pulseaudio. They are added by 0013-core-add-current_client.patch in Fedora. Let's reassign to Wim, the author of the patch.
It is possible for do_work(c) to call connection_unlink(c), invalidating the connection object.
Just happened to me while unlocking the user session. It caused shutdown of the session.
Is there any progress in fixing this PA crash - is 135 CC people still too low to get attention?
I have fresh installed Gnome Fedora 26. Pulse audio crashed after login / fres boot. For the sake of curiosity i disabled AlsaMixer Shell Extension and after reboot im free of pulseaudio crash. Maybe it will help somebody.
Similar problem has been detected: Reboot after updates on 2017-10-26 into Mate desktop. Error appeared. reporter: libreport-2.9.1 backtrace_rating: 3 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: io_callback executable: /usr/bin/pulseaudio journald_cursor: s=afcf4fd6115a40bc81a41e5ffc5353e3;i=7a18;b=dff397cc51824255b2966d447fe62824;m=222c22a4d;t=55c7dd1608df3;x=bec90919d48b3c7d kernel: 4.13.5-200.fc26.x86_64 package: pulseaudio-10.0-4.fc26 reason: pulseaudio killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.