Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-68911

QLowEnergyController blocking on second connect attempt

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P1: Critical
    • Resolution: Done
    • Affects Version/s: 5.11.0
    • Fix Version/s: 5.11.2
    • Labels:
      None
    • Environment:
      Linux
      BlueZ 5.42 or later

      Description

      Qt 5.11 uses a new Central role implementation on BlueZ versions 5.42+. When the first instance off an application successfully connects to the remote peripheral via QLEController::connectToDevice() and is subsequently killed with CTRL+C or similar signals the connection tot the peripheral remains open. It is managed by bluetoothd.

      The next time QLEController::connectToDevice() is called, the connect never succeeds because the already open connection is not properly handled.

      The cause of the problem is a missing connected() signal emission.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              ablasche Alex Blasche
              Reporter:
              ablasche Alex Blasche
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes