Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 581
    • Issues 581
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #502
Closed
Open
Issue created Dec 22, 2020 by Bao, Huang-Huang@eh5Contributor

Unhandled dbus signals on bluez service in bluez5 plugin

https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/8bc711ce4dfdb063507c374bf9fb71a5555af8e3/spa/plugins/bluez5/bluez5-dbus.c#L1580-1586

It causes A2DP profiles unable to reconnect if dbus interfaces on bluez has been removed or changed.

For example, bluez would release A2DP endpoints and remove interfaces during system hibernating, it's not possible to reconnect A2DP profiles after system resuming because A2DP endpoints has not been re-registered.

Edited Dec 22, 2020 by Bao, Huang-Huang
Assignee
Assign to
Time tracking