All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Laurent Vivier <laurent@vivier.eu>, linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth printer connection error
Date: Wed, 09 Dec 2020 12:00:45 +0100	[thread overview]
Message-ID: <e885258a0b9a3ba15640553e9f002cdfc89f4b79.camel@hadess.net> (raw)
In-Reply-To: <3a6fa942-bec5-5e5f-391d-197d1c1eafa6@vivier.eu>

On Tue, 2020-12-08 at 22:25 +0100, Laurent Vivier wrote:
> Hi,
> 
> TL;DR:
> 
> I can pair my bluetooth printer but it fails to connect:
> 
>   $ bluetoothctl connect DC:0D:30:90:23:C7
> 
>   Attempting to connect to DC:0D:30:90:23:C7
>   [CHG] Device DC:0D:30:90:23:C7 Connected: yes
>   [CHG] Device DC:0D:30:90:23:C7 ServicesResolved: yes
>   Failed to connect: org.bluez.Error.NotAvailable
> 
> What do I need to add to my system to have this working?

As I mentioned in the original bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1904686

I don't expect the "connect" command to do anything. There's nothing to
"connect" to, as bluez doesn't create rfcomm device nodes automatically
when "connecting" to devices with serial profiles (otherwise one
couldn't connect to them with other applications without going through
the device node...).

If the printer has uses the SPP or HCRP printing profiles, you should
see it when using:
/usr/lib/cups/backend/bluetooth
without any arguments.

Otherwise any apps or driver that supports the printer should be able
to create a serial link directly to the device without creating a
device node in /dev.

FWIW, looks like the printer uses a proprietary protocol between their
own app and the printer, and that they don't provide Linux support.
Short of reverse engineering that protocol, the printer is unlikely to
work with Linux.

Cheers


  reply	other threads:[~2020-12-09 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 21:25 Bluetooth printer connection error Laurent Vivier
2020-12-09 11:00 ` Bastien Nocera [this message]
2020-12-09 11:14   ` Laurent Vivier
2020-12-09 11:34     ` Bastien Nocera
2020-12-09 19:04       ` Laurent Vivier
2020-12-09 20:27         ` Bastien Nocera
2020-12-09 21:45           ` Laurent Vivier
2020-12-10  9:35             ` Bastien Nocera
2020-12-10  9:41               ` Laurent Vivier

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=e885258a0b9a3ba15640553e9f002cdfc89f4b79.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=laurent@vivier.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.