Bug 1094829 - [abrt] pulseaudio: pa_asyncmsgq_get(): pulseaudio killed by SIGABRT
Summary: [abrt] pulseaudio: pa_asyncmsgq_get(): pulseaudio killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e83fbdc7414b8fe5f4b0d0501db...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-06 14:50 UTC by Steven Stern
Modified: 2015-06-29 20:29 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 20:29:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (57.79 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: cgroup (172 bytes, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: core_backtrace (16.71 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: dso_list (8.29 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: environ (1.49 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: limits (1.29 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: maps (39.23 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: open_fds (2.70 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: proc_pid_status (958 bytes, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details
File: var_log_messages (3.63 KB, text/plain)
2014-05-06 14:50 UTC, Steven Stern
no flags Details

Description Steven Stern 2014-05-06 14:50:21 UTC
Description of problem:
Turned off bluetooth device while playing music

Version-Release number of selected component:
pulseaudio-4.0-13.gitf81e3.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start
crash_function: pa_asyncmsgq_get
executable:     /usr/bin/pulseaudio
kernel:         3.14.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 pa_asyncmsgq_get at pulsecore/asyncmsgq.c:177
 #3 pa_asyncmsgq_flush at pulsecore/asyncmsgq.c:338
 #4 pa_thread_mq_done at pulsecore/thread-mq.c:152
 #5 stop_thread at modules/bluetooth/module-bluez5-device.c:1304
 #6 set_profile_cb at modules/bluetooth/module-bluez5-device.c:1574
 #7 pa_card_set_profile at pulsecore/card.c:275
 #8 transport_state_changed_cb at modules/bluetooth/module-bluez5-device.c:1760
 #9 pa_hook_fire at pulsecore/hook-list.c:106
 #10 transport_state_changed at modules/bluetooth/bluez5-util.c:186
 #11 endpoint_clear_configuration at modules/bluetooth/bluez5-util.c:1410

Comment 1 Steven Stern 2014-05-06 14:50:27 UTC
Created attachment 892915 [details]
File: backtrace

Comment 2 Steven Stern 2014-05-06 14:50:29 UTC
Created attachment 892916 [details]
File: cgroup

Comment 3 Steven Stern 2014-05-06 14:50:31 UTC
Created attachment 892917 [details]
File: core_backtrace

Comment 4 Steven Stern 2014-05-06 14:50:33 UTC
Created attachment 892918 [details]
File: dso_list

Comment 5 Steven Stern 2014-05-06 14:50:36 UTC
Created attachment 892919 [details]
File: environ

Comment 6 Steven Stern 2014-05-06 14:50:38 UTC
Created attachment 892920 [details]
File: limits

Comment 7 Steven Stern 2014-05-06 14:50:40 UTC
Created attachment 892921 [details]
File: maps

Comment 8 Steven Stern 2014-05-06 14:50:42 UTC
Created attachment 892922 [details]
File: open_fds

Comment 9 Steven Stern 2014-05-06 14:50:43 UTC
Created attachment 892923 [details]
File: proc_pid_status

Comment 10 Steven Stern 2014-05-06 14:50:45 UTC
Created attachment 892924 [details]
File: var_log_messages

Comment 11 Joao Carlos Mendes Luis 2015-02-20 14:15:39 UTC
Another user experienced a similar problem:

disconnected a bluetooth audio device

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start --log-target=syslog
crash_function: pa_asyncmsgq_get
executable:     /usr/bin/pulseaudio
kernel:         3.18.7-100.fc20.x86_64
package:        pulseaudio-5.0-25.fc20
reason:         pulseaudio killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            40024

Comment 12 Fedora End Of Life 2015-05-29 11:46:45 UTC
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.

Comment 13 Fedora End Of Life 2015-06-29 20:29:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.