From: Szymon Janc <ext.szymon.janc@tieto.com>
To: Andrey Aleksandrovich <andrey.aleksandrovich@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Possibly Bug in recent Bluez
Date: Mon, 18 Jan 2016 16:03:31 +0100 [thread overview]
Message-ID: <3174796.fSnHrpqxly@leonov> (raw)
In-Reply-To: <1557825.6tL2oa3vnP@leonov>
Hi,
On Monday 18 of January 2016 12:40:40 Szymon Janc wrote:
> Hi,
>
> On Sunday 17 of January 2016 11:42:04 Andrey Aleksandrovich wrote:
> > Hi, I have Gentoo Linux, KDE on laptop with Bluetooth.
> > And I find out that it doesn't working after some time ago.
> >
> > # dmesg | grep 4-1.5
> > [ 475.204004] usb 4-1.5: New USB device found, idVendor=8086,
> > idProduct=0189 [ 475.204014] usb 4-1.5: New USB device strings: Mfr=0,
> > Product=0, SerialNumber=0
> >
> > # lsusb | grep 009
> > Bus 004 Device 009: ID 8086:0189 Intel Corp.
> >
> > # cat /var/log/everything/current | grep bluetoothd
> > Jan 16 18:52:51 [bluetoothd] Bluetooth daemon 5.37
> > Jan 16 18:52:51 [bluetoothd] Starting SDP server
> > Jan 16 18:52:51 [bluetoothd] Bluetooth management interface 1.9
> > initialized
> > Jan 16 18:52:51 [bluetoothd] Failed to obtain handles for "Service
> > Changed" characteristic
> > Jan 16 18:52:51 [bluetoothd] Not enough free handles to register service
> > Jan 16 18:52:51 [bluetoothd] Error adding Link Loss service
> > Jan 16 18:52:51 [bluetoothd] Not enough free handles to register service
> > Jan 16 18:52:51 [bluetoothd] Current Time Service could not be registered
> > Jan 16 18:52:51 [bluetoothd] gatt-time-server: Input/output error (5)
> > Jan 16 18:52:51 [bluetoothd] Not enough free handles to register service
> > Jan 16 18:52:51 [bluetoothd] Sap driver initialization failed.
> > Jan 16 18:52:51 [bluetoothd] sap-server: Operation not permitted (1)
>
> At least sap-server plugin shouldn't be enabled at all (unless you run it on
> supported platform ie STE u8500, which you most likely don't). So this is a
> (quite common it seems) packaging bug.
Ahh, it looks like this is enabled by common 'experimental flag.
> > It doesn't affect only me, here is some links:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1259827
> > https://bugs.gentoo.org/show_bug.cgi?id=566004
> > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499858
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
BR
Szymon Janc
next prev parent reply other threads:[~2016-01-18 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 9:42 Possibly Bug in recent Bluez Andrey Aleksandrovich
2016-01-17 12:56 ` Luiz Augusto von Dentz
2016-01-18 11:40 ` Szymon Janc
2016-01-18 15:03 ` Szymon Janc [this message]
2016-01-21 11:14 ` Marcel Holtmann
2016-01-21 22:35 ` Szymon Janc
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=3174796.fSnHrpqxly@leonov \
--to=ext.szymon.janc@tieto.com \
--cc=andrey.aleksandrovich@googlemail.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