Bug 1520512

Created attachment 1362731 [details]
File: backtrace

Created attachment 1362732 [details]
File: cgroup

Created attachment 1362733 [details]
File: core_backtrace

Created attachment 1362734 [details]
File: cpuinfo

Created attachment 1362735 [details]
File: dso_list

Created attachment 1362736 [details]
File: environ

Created attachment 1362737 [details]
File: limits

Created attachment 1362738 [details]
File: maps

Created attachment 1362739 [details]
File: mountinfo

Created attachment 1362740 [details]
File: open_fds

Created attachment 1362741 [details]
File: proc_pid_status

Created attachment 1362742 [details]
File: var_log_messages

This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Similar problem has been detected:

I connected my bluetooth headphones (Bludio UFO) and attempted to use them. The sound test skipped and then they disconnected and the crash occured. The headphones worked just fine on the same hardware using Fedora 27

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=1b5b3f31fd484ec78d62643aca3ae4ff;i=9beb;b=ea692eb461b144849f4ca6d829fe0f14;m=4c1f4615;t=56b53b97ce861;x=f8034f5f40eb5755
kernel:         4.16.5-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Hi,

I am also facing the same problem.
My Bluetooth headset worked fine on Fedora 27. When I upgraded to Fedora 28, the Bluetooth crashes.

The error I get on my system is pm_writablesize_failed().

Please help us solve this error.

Thanks,
Mallikarjun

Similar problem has been detected:

Playing audio over a USB audio device. Then switched to bluetooth audio over a USB audio dongle. Worked with bad quality as HFP, crash occured when trying to switch to A2DP Sink mode.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=6202ff9b185d405789e768d173868934;i=bd46;b=d4eede0d9ce343e5b9b6e76988f903c3;m=226c38971;t=56b7943aaee6f;x=8bc66b57854b0de0
kernel:         4.16.5-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1576046 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Listening to Pithos 1.4.1 on Fedora 28 x64 with Bluetooth headphones.  Pithos threw an error that the next song couldn't be retrieved and headphones cut out.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=9bf90d355edf43f3babd7892d775b90e;i=77de5;b=c0b30ac90ded4108b98b11e04942c088;m=3e64dc176;t=56bc93ec09a9a;x=73c089bc43a7721f
kernel:         4.16.6-302.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Connected bluetooth headphones to my laptop, played some music. Stopped the music, switched bluetooth headphones off, then pulseaudio crashed.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=63b5bee277b64be3a2cf786fe9db6790;i=2d81;b=3a3c7470339844bcae210c11ae43571b;m=7a9dc211;t=56be309b20950;x=1f48c65791ec3038
kernel:         4.16.7-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

After starting Fedora 28 and a firefox session conntected to a distant session of octoprint (doing nothing), puleseaudio crashed.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=5eecd3fd967e4db39b167e23cdd3211c;i=c8be;b=923c80caf3c44e0e907dc21a791abc8c;m=12c2fad1d;t=56c164b6bc16f;x=72511e393aa0054f
kernel:         4.16.7-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Pulseaudio is crashing when I use bluethoot headphones.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=23ac742845444e82a9f4711e63b96cd5;i=12d72;b=0302837245a340d1a1668bd511dd4c99;m=3ed4fac3;t=56c299d62c6d9;x=3a6ae23085d5e4e3
kernel:         4.16.7-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            10000

Hi Fedora development team,

Can you please get this problem solved.
Bluetooth is working fine in Fedora 27 and it's failing in Fedora 28.

How can you release a new version of an operating system with bugs?

Also, can you please give a reply to all the users who have complained above.

Thanks,
Mallikarjun

Re: comment 22

there is a candidate fix in updates-testing, please do test and provide feedback,
https://bodhi.fedoraproject.org/updates/FEDORA-2018-87bbd4df6e

Similar problem has been detected:

I was listening to stream music service Yandex.Music (music.yandex.ru) through my Bluetooth headset. The music stopped after 1 minute and the error popped up in the notification bar. When I tried once more the same thing happend. The problem didn't occur when I was using Fedora 27, yesterday I updated it to 28 version.
Browser: Google Chrome Version 66.0.3359.117 (Official Build) (64-bit)

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --daemonize=no
crash_function: transport_state_changed_cb
executable:     /usr/bin/pulseaudio
journald_cursor: s=6f349036d70c4de08ed1bcd4853b89a0;i=26e1b;b=5a76183013774f518696ea0fc7bbb924;m=d071f8c;t=56c69b9950664;x=3c20c4168a92d54e
kernel:         4.16.8-300.fc28.x86_64
package:        pulseaudio-11.1-18.fc28
reason:         pulseaudio killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1582405 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.