From: Bernie Innocenti <bernie@codewiz.org>
To: linux-bluetooth@vger.kernel.org
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Bernie Innocenti <bernie@codewiz.org>
Subject: [PATCH BlueZ v2 0/2] cups: Make printer discovery work again
Date: Mon, 16 Nov 2026 20:29:29 +0900 [thread overview]
Message-ID: <20261116112931.1598858-1-bernie@codewiz.org> (raw)
In-Reply-To: <CABBYNZL1Hn8dyNfd+xMkXxyVvZxqLH=ZcbSCtjKqLXi6RFeNew@mail.gmail.com>
The CUPS backend lists no printers, so add-printer dialogs never show
Bluetooth printers and the URI has to be typed by hand:
https://github.com/bluez/bluez/issues/2287
Patch 1 reads the IEEE 1284 device ID over SDP, patch 2 moves discovery
to GDBusClient. Discovery runs for a fixed 10 seconds.
Changes in v2:
- Read the device IDs during discovery asynchronously, so that a known
printer that is switched off no longer stalls the listing; printers
whose ID has not arrived by the deadline are listed without one
(the Copilot finding Luiz pointed out).
Tested on Fedora with bluez 5.88, CUPS 2.4.19 and a Phomemo PM-241-BT
label printer (SPP + HCRP): discovery lists it with its device ID, and
with the printer off the listing still ends after 10 seconds. With v1
installed, lpinfo -v showed it and a job sent to that URI printed; the
print path is unchanged in v2. The printer was bonded, so I have only exercised
the known-devices path, not a printer found by the scan.
Bernie Innocenti (2):
cups: Read the IEEE 1284 device ID over SDP
cups: Port printer discovery to the ObjectManager API
profiles/cups/cups.h | 3 +
profiles/cups/main.c | 671 ++++++++++---------------------------------
profiles/cups/sdp.c | 109 +++++++
3 files changed, 262 insertions(+), 521 deletions(-)
--
2.56.1
next prev parent reply other threads:[~2026-11-16 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 9:34 [PATCH BlueZ 0/2] cups: Make printer discovery work again Bernie Innocenti
2026-11-13 9:34 ` [PATCH BlueZ 1/2] cups: Read the IEEE 1284 device ID over SDP Bernie Innocenti
2026-11-13 16:35 ` Luiz Augusto von Dentz
2026-11-16 11:29 ` Bernie Innocenti [this message]
2026-11-16 11:29 ` [PATCH BlueZ v2 " Bernie Innocenti
2026-11-16 11:29 ` [PATCH BlueZ v2 2/2] cups: Port printer discovery to the ObjectManager API Bernie Innocenti
2026-11-17 8:43 ` [PATCH BlueZ 1/2] cups: Read the IEEE 1284 device ID over SDP Bernie Innocenti
2026-11-13 9:34 ` [PATCH BlueZ 2/2] cups: Port printer discovery to the ObjectManager API Bernie Innocenti
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=20261116112931.1598858-1-bernie@codewiz.org \
--to=bernie@codewiz.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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