Bug#803265: bluetooth.service: sap-server: Operation not permitted (1)

[Michal Suchanek]

Package: bluez
Version: 5.33-1
Severity: normal
File: bluetooth.service

Hello,

I tried to use bluetooth headphones.

However, bluetooth does not start.

There are missing configuration files. I did not remove thsese so
probably some upgrade script did.

● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Fri 2015-10-23 18:34:06 CEST; 4 days ago
Docs: man:bluetoothd(8)
Process: 27310 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=0/SUCCESS)
Main PID: 27310 (code=exited, status=0/SUCCESS)
Status: "Quitting"

Oct 23 18:32:36 iscsi bluetoothd[27310]: Sap driver initialization failed.
Oct 23 18:32:36 iscsi bluetoothd[27310]: sap-server: Operation not permitted (1)
Oct 23 18:32:36 iscsi bluetoothd[27310]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Start operation timed out. Terminating.
Oct 23 18:34:06 iscsi bluetoothd[27310]: Terminating
Oct 23 18:34:06 iscsi bluetoothd[27310]: Stopping SDP server
Oct 23 18:34:06 iscsi bluetoothd[27310]: Exit
Oct 23 18:34:06 iscsi systemd[1]: Failed to start Bluetooth service.
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Unit entered failed state.
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Failed with result 'timeout'.


-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (500, 'oldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bluez depends on:
ii dbus 1.10.0-3
ii init-system-helpers 1.23
ii kmod 18-3
ii libc6 2.19-22
ii libdbus-1-3 1.10.0-3
ii libglib2.0-0 2.46.0-2
ii libreadline6 6.3-8+b3
ii libudev1 215-17+deb8u2
ii lsb-base 9.20150917
ii udev 215-17+deb8u2

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory: u'/etc/init.d/bluetooth'
/etc/init/bluetooth.conf e6b0122c1e5cd56016859a0767a8cfcb [Errno 2] No such file or directory: u'/etc/init/bluetooth.conf e6b0122c1e5cd56016859a0767a8cfcb'

-- no debconf information

[Michal Suchanek]

Package: bluez
Version: 5.33-1
Followup-For: Bug #803265

Hello,

purging everything bluetooth and reinstalling fixed the problem.

● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)

Active: active (running) since Tue 2015-11-03 13:31:15 CET; 1min 4s ago
Docs: man:bluetoothd(8)
Main PID: 23714 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─23714 /usr/lib/bluetooth/bluetoothd

Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Current Time Service could not be registered
Nov 03 13:31:15 iscsi bluetoothd[23714]: gatt-time-server: Input/output error (5)
Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Sap driver initialization failed.
Nov 03 13:31:15 iscsi bluetoothd[23714]: sap-server: Operation not permitted (1)
Nov 03 13:31:15 iscsi bluetoothd[23714]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
Nov 03 13:31:15 iscsi bluetoothd[23714]: Endpoint registered: sender=:1.998 path=/MediaEndpoint/A2DPSource
Nov 03 13:31:15 iscsi bluetoothd[23714]: Endpoint registered: sender=:1.998 path=/MediaEndpoint/A2DPSink

The error message persists so it is in fact just warning that should not
prevent bluetooth from starting. As to the bluetooth service hang on
start there is no useful diagnostic. I suspect it might be caused by
dbus problem but it's working now so I cannot really tell.

Thanks

Michal

-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (500, 'oldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bluez depends on:
ii dbus 1.10.0-3

ii init-system-helpers 1.24
ii kmod 21-1

ii libc6 2.19-22
ii libdbus-1-3 1.10.0-3

ii libglib2.0-0 2.46.1-1
ii libreadline6 6.3-8+b3
ii libudev1 227-2
ii lsb-base 9.20150917
ii udev 227-2

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory: u'/etc/init.d/bluetooth'

-- no debconf information

[Norbert Lange]

On Fri, 10 Feb 2017 11:09:43 +0100 Laurent Bonnaud
<L.Bo...@laposte.net> wrote:
> Hi,
>
> according to this:
>
> https://raspberrypi.stackexchange.com/questions/40839/sap-error-on-bluetooth-service-status
>
> the error messages about SAP can be avoided by starting bluetoothd with the "--noplugin=sap" option.
>
> Since SAP is probably of little use in Debian and since it does not work anyway, how about disabling it by default?
>
> --
> Laurent.

This repeatedly bites me,
now the path changed from /usr/lib/bluetooth/bluetoothd to
/usr/libexec/bluetooth/bluetoothd,
causing the override to be invalid.

Please figure out why this is an issue, if you can get it to work with debian,
and if not disable it.

Norbert

[SHERYLL GOEDERT]

Dobry dzien

Pilnie mam dla Ciebie darowizne w wysokosci €2.000.000,00 EUR, poniewaz wybralem Cie na odbiorce mojej dobrej woli.
Popros o darowizne na adres vacation.l...@gmail.com

Pozdrowienia i uwolnij sie od Covid-19,
SHERYLL GOEDERT

[SHERYLL GOEDERT]

[Sergio Zamora]

With the bluetooth adapter down on the Gnome GUI, some startups fail and freeze totally without being able to continue starting the laptop.

Debian 11.-

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)

     Active: active (running) since Mon 2021-07-05 14:28:14 -04; 9min ago
       Docs: man:bluetoothd(8)
   Main PID: 18528 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18812)
     Memory: 816.0K
        CPU: 33ms
     CGroup: /system.slice/bluetooth.service
             └─18528 /usr/libexec/bluetooth/bluetoothd

jul 05 14:28:14 debian bluetoothd[18528]: Bluetooth daemon 5.55
jul 05 14:28:14 debian systemd[1]: Started Bluetooth service.
jul 05 14:28:14 debian bluetoothd[18528]: Starting SDP server
jul 05 14:28:14 debian bluetoothd[18528]: Bluetooth management interface 1.18 initialized
jul 05 14:28:14 debian bluetoothd[18528]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
jul 05 14:28:14 debian bluetoothd[18528]: sap-server: Operation not permitted (1)
jul 05 14:28:14 debian bluetoothd[18528]: Failed to set mode: Blocked through rfkill (0x12)
jul 05 14:28:14 debian bluetoothd[18528]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/sbc
jul 05 14:28:14 debian bluetoothd[18528]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/sbc
jul 05 14:28:14 debian bluetoothd[18528]: Failed to set mode: Blocked through rfkill (0x12)

--

[Matti Kurkela]

In the context of Bluetooth, "sap" refers to the SIM Access Profile,
designed to allow mobile phones to lend the use of their SIM or USIM
cards over Bluetooth to car handsfree kits that have their own mobile
phone radio module, which may have greater transmitter power and a
better antenna for use on the road than a hand-held phone in the user's
pocket.

The BlueZ stack attempts to register a SAP server, which will be useful
only if the system has a mobile phone SIM or USIM card and the user is
willing to lend its use to external devices.

As packaged, the SAP server component no longer has any actual
implementation to access a card reader: the upstream removed the last
actual implementation (for the long-dead STE U8500 platform) in
2017-07-13. Only the dummy implementation in sap-dummy.c is left:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/sap?id=3a140aa35b7b7dc1d7b031eec40590187f70a980

The dummy implementation will attempt to register a D-Bus interface
"org.bluez.SimAccessTest1", which is not covered by the packaged D-Bus
configuration file (src/bluetooth.conf). As a result, registering the
SIM Access Profile will always fail.

The failure of the SAP driver won't normally stop BlueZ bluetoothd from
operating, but it often results in the first error message from BlueZ
even in situations where the Bluetooth radio is not operable (e.g.
because of missing firmware), so it tends to confuse users who don't
know what the Bluetooth SAP profile is, and lead them astray in their
troubleshooting.

Sharing access to a SIM/USIM card is a security-sensitive operation, as
with it, an external device equipped with a mobile phone radio module
could place and receive calls and/or transfer data over the mobile phone
network, which could incur costs to the card owner. The SIM/USIM keys
can sometimes also be used to allow access to WiFi networks (see
wpa_supplicant and its EAP-SIM functionality).

It could also provide access to contacts information stored on the card,
which is often highly personal data.

The SAP profile allows raw APDU access to the SIM card, so it would
enable any arbitrary SIM card operations to be performed.

For all these reasons, it might be a good idea to default to have the
SIM Access Profile cleanly disabled unless the user explicitly wants to
enable it.

Starting bluetoothd with the option "--noplugin=sap" by default (as
already suggested) would be one way to do it. Another way would be to
patch the `bootstrap-configure` file in the source root directory, to
change `--enable-sap` to `--disable-sap`.

In its current form, the SIM Access Profile support of BlueZ is only
useful for developers, and even that requires modifying
/etc/dbus-1/system.d/bluetooth.conf before it will do anything other
than display an error message on Bluetooth service start-up. This is
true of both the version in bullseye and the current unstable version.

--
Matti....@iki.fi

[priyanka patel]

Welcome to ERP2CONNECT Greetings!!   We providing SAP Server Access for the trainer, trainee, corporate training, Rented SAP sandbox system for the corporate projects. Our Top Product: S4HANA 2020, 2022 SAP ECC EHP8 - ABAP, FICO, SD, MM, HR, SAP MDG SuccessFactor Cloud BI/BW on HANA, ABAP on HANA Eclips SAP CRM, SAP SRM, SAP SCM SAP ISU, Healthcare and many more SAP GRC12, SAP Security, SAP GRC with HANA Functionality: We provide pre-installed SAP IDES Sandbox system which available to use directly after purchase. Now no more wait, start practice immediately on SAP. Backup Facility with minimum system downtime. High-speed servers - 100 to 500 users load capacity. Flexibility to choose OS/DB and SAP Versions. Pay as per use (Minimum 1 Month Subscription). AWS / Azure Cloud Option Available. 24/7 SAP BASIS and Infra support. 99% Server Uptime. Benefits: No Hardware and Maintenance cost. No Electricity Labor Maintenance cost. No IT Infra/ SAP Manage cost No OS / SAP Application / DB licenses cost AMC cost. Includes SAP BASIS and Infra Manage Support. Start Using SAP server immediately SAP System Accessible from Anywhere using SAPGUI and RDP. 24/7 Infra SAP BASIS support. ­ Buy Now ­ Need Support?         Email: erp2c...@gmail.com | Mobile: +918460584007

[CloudQuick Serverr]

Greetings!!

I hope this email finds you well. I wanted to take a moment to introduce you to our SAP server access services, which are specifically tailored to meet the needs of trainers, trainees, and corporate training programs. Additionally, we offer rented SAP sandbox systems that are ideal for corporate projects.

Our Top Product:  S4HANA 2020, 2022 SAP ECC EHP8 - ABAP, FICO, SD, MM, HR, SAP MDG SuccessFactor Cloud BI/BW on HANA, ABAP on HANA Eclips SAP CRM, SAP SRM, SAP SCM SAP ISU, Healthcare and many more SAP GRC12, SAP Security, SAP GRC with HANA

Functionality: We provide a pre-installed SAP IDES Sandbox system. The system is available for use directly after purchase, eliminating any waiting time. Our system offers a backup facility that ensures minimal system downtime. We offer high-speed servers that can handle a load capacity of 100 to 500 users. You have the flexibility to choose the operating system, database, and SAP version that best suits your needs. We provide a pay-as-you-go model with a minimum one-month subscription. Our system can be used on AWS or Azure Cloud for added convenience. We offer 24/7 SAP BASIS and infrastructural support. Our servers boast an uptime of 99%.

Benefits: There are no hardware or maintenance costs. There are no electricity, labor, or maintenance costs associated with our system. You don't need to manage any IT infrastructure or SAP, as we take care of it for you. There are no costs associated with licenses for the operating system, SAP application, or database, nor any annual maintenance costs. Our system includes SAP BASIS and infrastructural support. You can start using the SAP server immediately, without any waiting time. The SAP system can be accessed from anywhere using SAPGUI and RDP. We provide 24/7 infrastructural and SAP BASIS support.

Buy Now

Thank you for considering our services. If you have any questions or require further information, please do not hesitate to contact us.

[Max Nikulin]

Control: tag -1 + patch

On Wed, 17 Nov 2021 16:36:58 +0200 Matti Kurkela wrote:
> As packaged, the SAP server component no longer has any actual
> implementation to access a card reader: the upstream removed the last
> actual implementation (for the long-dead STE U8500 platform) in
> 2017-07-13. Only the dummy implementation in sap-dummy.c is left:
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/sap?id=3a140aa35b7b7dc1d7b031eec40590187f70a980

[...]> Starting bluetoothd with the option "--noplugin=sap" by default (as

> already suggested) would be one way to do it. Another way would be to
> patch the `bootstrap-configure` file in the source root directory, to
> change `--enable-sap` to `--disable-sap`.
>
> In its current form, the SIM Access Profile support of BlueZ is only
> useful for developers, and even that requires modifying
> /etc/dbus-1/system.d/bluetooth.conf before it will do anything other
> than display an error message on Bluetooth service start-up. This is
> true of both the version in bullseye and the current unstable version.

It seems since

<https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=1d76b2ee1f098f144c006e83e9de04f91b1ec9b3>
"build: Add option to enable SAP profile"
2016-11-17 14:15:42 +0200

the SAP plugin is not built by default.
Ubuntu does not have --enable-sap in their
https://git.launchpad.net/ubuntu/+source/bluez/tree/debian/rules
for a long time, see
https://git.launchpad.net/ubuntu/+source/bluez/commit/debian/rules?id=3df71d750c11c4fffdaa59e56064ae3471e60b8c

I suggest to drop --enable-sap from debian/rules (see the attached
patch) to not confuse users troubleshooting their bluetooth issues.

As an alternative, src/bluetooth.service.in may be patched to disable
this plugin:

ExecStart=@pkglibexecdir@/bluetoothd --noplugin=sap