Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pulseaudio pulseaudio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 897
    • Issues 897
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 57
    • Merge requests 57
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PulseAudioPulseAudio
  • pulseaudiopulseaudio
  • Merge requests
  • !663

bluez5: do NameHasOwner before using org.bluez

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Wim Taymans requested to merge wtaymans/pulseaudio:bluez-owner-check into master Nov 17, 2021
  • Overview 7
  • Commits 1
  • Pipelines 1
  • Changes 1

We should not be using org.bluez when the bluetooth service is not running or else we might try to activate it. The activation of the bluetooth service should be done at boot time.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: bluez-owner-check