From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] de6ced: obexd: Pass at_(un)register value to logind callbacks
Date: Tue, 03 Jun 2025 08:35:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/968319/000000-022aba@github.com> (raw)
Branch: refs/heads/968319
Home: https://github.com/bluez/bluez
Commit: de6ced6bf6fe97b23cc2bb72f67cc5b9cfdc43b8
https://github.com/bluez/bluez/commit/de6ced6bf6fe97b23cc2bb72f67cc5b9cfdc43b8
Author: Andrew Sayers <kernel.org@pileofstuff.org>
Date: 2025-06-03 (Tue, 03 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.
Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
Commit: cfd2117ffd837f4a010569573a39c4c778c6e4f0
https://github.com/bluez/bluez/commit/cfd2117ffd837f4a010569573a39c4c778c6e4f0
Author: Andrew Sayers <kernel.org@pileofstuff.org>
Date: 2025-06-03 (Tue, 03 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>
Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
Commit: 022aba4af5ce76618fa3612352c0d9ac0b60e353
https://github.com/bluez/bluez/commit/022aba4af5ce76618fa3612352c0d9ac0b60e353
Author: Andrew Sayers <kernel.org@pileofstuff.org>
Date: 2025-06-03 (Tue, 03 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.
Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
Compare: https://github.com/bluez/bluez/compare/de6ced6bf6fe%5E...022aba4af5ce
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-03 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/968319/000000-022aba@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox