[bluez/bluez] b7dfcc: doc: sco.rst: BT_PHY is read-only

[bluez/bluez] b7dfcc: doc: sco.rst: BT_PHY is read-only

[BluezTestBot]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: b7dfccf0e52aa4628a731dd555f038d18ddd42fe
      https://github.com/bluez/bluez/commit/b7dfccf0e52aa4628a731dd555f038d18ddd42fe
  Author: ValdikSS <iam@valdikss.org.ru>
  Date:   2025-06-11 (Wed, 11 Jun 2025)

  Changed paths:
    M doc/sco.rst

  Log Message:
  -----------
  doc: sco.rst: BT_PHY is read-only

The kernel is missing BT_PHY setsockopt support, as of 6.16-rc1.


  Commit: 883c1c11c6448e7f0ca04e523a5ac2030d7f161c
      https://github.com/bluez/bluez/commit/883c1c11c6448e7f0ca04e523a5ac2030d7f161c
  Author: Andrew Sayers <kernel.org@pileofstuff.org>
  Date:   2025-06-11 (Wed, 11 Jun 2025)

  Changed paths:
    M obexd/client/pbap.c
    M obexd/plugins/bluetooth.c
    M obexd/src/logind.c
    M obexd/src/logind.h

  Log Message:
  -----------
  obexd: Pass at_(un)register value to logind callbacks

Logind (un)registers callbacks that it calls when the user's state changes.
Callbacks may also be called during (un)registration.
Clients may need to handle those initial/final calls specially.

Pass an argument indicating whether this is being called during
(un)registration, and modify existing callbacks to ignore that argument.


  Commit: df0036d9e41fc4bb0fe8839b7833bac16359396b
      https://github.com/bluez/bluez/commit/df0036d9e41fc4bb0fe8839b7833bac16359396b
  Author: Andrew Sayers <kernel.org@pileofstuff.org>
  Date:   2025-06-11 (Wed, 11 Jun 2025)

  Changed paths:
    M obexd/client/pbap.c

  Log Message:
  -----------
  pbap: use the public DBus connection

PBAP must not use its own private DBus connection, as it needs to
receive messages sent to the bus name of the public connection.

PBAP must not unregister itself when the program is exiting, as it might
cause a long delay.  Unregistering at exit is redundant anyway, as the
service will be implicitly unregistered when the connection is closed.

But PBAP must unregister itself when the user becomes inactive mid-session,
so systems with multiple users logged in at once can share bluetooth.

Use the public DBus connection instead of a private one,
and explicitly unregister the profile if appropriate.

Thanks Pauli Virtanen for pointing out the exit issue:
https://lore.kernel.org/linux-bluetooth/ae15a9fa4bf0bd509dd3d44f1f364e241e50956c.camel@iki.fi/

Reported-by: Frédéric Danis <frederic.danis@collabora.com>
Closes: https://lore.kernel.org/linux-bluetooth/333ad76e-0aba-4f93-b141-8e69fb47535f@collabora.com/
Suggested-by: Pauli Virtanen <pav@iki.fi>


  Commit: aea0f46f173f85a71908452b0c6ed16f647f6117
      https://github.com/bluez/bluez/commit/aea0f46f173f85a71908452b0c6ed16f647f6117
  Author: Andrew Sayers <kernel.org@pileofstuff.org>
  Date:   2025-06-11 (Wed, 11 Jun 2025)

  Changed paths:
    M obexd/src/main.c
    M obexd/src/obexd.h

  Log Message:
  -----------
  Revert "obexd: Support creating private system/session bus connections"

This reverts commit 237d818ef294e22be87fba69b3cdd79c75c201e7,
which encouraged the use of private DBus connections.
Doing so caused a bug, so it's better to remove the temptation for now
and re-add it if a legitimate use case is ever found.


Compare: https://github.com/bluez/bluez/compare/95b72bbf1fe4...aea0f46f173f

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications