Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3880465pxu; Wed, 9 Dec 2020 03:04:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJwrfye8X5KRnqlaiMTq699pp4z2bLKMaiKqBuMz7Rzi3NBr01PuXjy80grb4gzoULPbyS/f X-Received: by 2002:a17:906:8151:: with SMTP id z17mr1610919ejw.48.1607511840670; Wed, 09 Dec 2020 03:04:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607511840; cv=none; d=google.com; s=arc-20160816; b=zfUZbxmwiW0Y/1nLuinde6tp5nhw/17YfVnw9zybTvctbjTyohLFae8p83D0BpnGo8 Wo/uh5Kbuj7y2i79UX2bz1uR0+7TRRy0LajBGeAzt5PWU4i57xn9j0TrtTDj+zOP0qSl lFHNRS9nWtqnEkknfZAXLDhcCc3CL0rm0NP6UZTX9TpgcVPdB9rV8q3l3zFNfq9ZzeZL IKYnNz/cdYyTACU+4lH7J8hQUl8l+A3rIN9X4TDZ+eTyowOrUGKZ9UZoxb+2cIPnMpVP D6ucSc2uGYVmZbTLpWZRq95XZZka6gz7R4eS2Wjm5QgdZavbPC8n6UYIUHCBrU0xlTkx 9CpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:to:from:subject:message-id; bh=SryQlP60L4X1Byh6PuDsiZDhezcE3uPZMAGezpKHlv4=; b=ETG0FDohw6oUxcoUWMaGilDF91ctI9XaMkvDF8YYQF/aF9i3WQ6ZnPQ25MmvKQdk39 I+cU+2DFAMA7BuQNjC8PmnvhpRLXDeLFtgiVYnNVzP4qlN7TvXCmw7iL9GjKLVgs/iyt E/qNTxOUWa3oDVHlaMLZsYJSSeeqBzdNNAJPDQdHYw/a/ezY4Qc5J9YrYqnQUbD8i5Jp +fjb05oawxMsAx3720W4sH0oyNzeCZGRPUsFmH36IjTPeYdbMBugj97OcuMJg18Ejm4Z H2ckKWMIXSFz5OYEvINbY7AAWBV67WXiFk/bZ3O7SjH0SMqHyFLRwkw6MB4TSxYJQJE0 5pMw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b21si661664ejz.649.2020.12.09.03.03.17; Wed, 09 Dec 2020 03:04:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730263AbgLILB3 (ORCPT + 99 others); Wed, 9 Dec 2020 06:01:29 -0500 Received: from relay11.mail.gandi.net ([217.70.178.231]:58835 "EHLO relay11.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730217AbgLILB3 (ORCPT ); Wed, 9 Dec 2020 06:01:29 -0500 Received: from [192.168.0.28] (lns-bzn-39-82-255-60-242.adsl.proxad.net [82.255.60.242]) (Authenticated sender: hadess@hadess.net) by relay11.mail.gandi.net (Postfix) with ESMTPSA id 0CBD8100014; Wed, 9 Dec 2020 11:00:46 +0000 (UTC) Message-ID: Subject: Re: Bluetooth printer connection error From: Bastien Nocera To: Laurent Vivier , linux-bluetooth@vger.kernel.org Date: Wed, 09 Dec 2020 12:00:45 +0100 In-Reply-To: <3a6fa942-bec5-5e5f-391d-197d1c1eafa6@vivier.eu> References: <3a6fa942-bec5-5e5f-391d-197d1c1eafa6@vivier.eu> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.1 (3.38.1-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org 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