Summary: | bluetooth devices are not closed when the user is switched away from the seat | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Felipe Sateler <fsateler> |
Component: | modules | Assignee: | pulseaudio-bugs |
Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | betaev, bigon, jan, jure, lennart, mboquien, sam |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
See Also: | https://launchpad.net/bugs/1703415 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Felipe Sateler
2016-10-07 14:04:40 UTC
I wonder; is failure to close the device really the problem? Or is it that the second pulseaudio instance (the user's actual login) has trouble with bluetooth discovery and so never sees the bluetooth device (and thus logs no errors about failing to open it)? I haven't looked into this very much, but I would expect both instances to see the bluetooth devices. The communication with bluetoothd happens over D-Bus, and getting a list of devices should succeed for any number of simultaneous clients. It's only setting up the audio transport that can cause conflicts. I can confirm that the second instance *can* see the device. A common situation (see https://askubuntu.com/questions/765233/pulseaudio-fails-to-set-card-profile-to-a2dp-sink-how-can-i-see-the-logs-and for workarounds people came up with) is that the other (i.e. actual logged in user) session can use the low-quality sink, but not the high-quality A2DP one. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/303. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.