[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2020-03-15 Thread Daniel van Vugt
Ubuntu 18.04 should be getting automatic updates already. But that means bug fixes only, not the latest version. To ensure you have the latest updates run: sudo apt update sudo apt full-upgrade In April, Ubuntu 20.04 will be released with the very latest BlueZ version. You can try it early

Re: [Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2020-03-14 Thread raimundoguimaraes1
or a link to the most up-to-date bluez package ... most current version for Ubuntu 18.04 if any Em qui, 12 de mar de 2020 22:09, Daniel van Vugt < daniel.van.v...@canonical.com> escreveu: > ** Changed in: bluez (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2020-03-12 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery:

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2020-03-12 Thread raimundoguimaraes1
** Changed in: bluez (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery:

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2018-07-19 Thread Daniel van Vugt
The 100+ just means a lot of people made the same mistake, which is understandable. See comment #48. I asked over a year ago for someone to open a new bug if they want to discuss "Not enough free handles to register service". If it was important to anyone then I'm sure someone would have done it

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2018-07-19 Thread Jeremy Walker
Look, obviously you can't solve all bugs in a single ticket, or you'd never get anything done. However, if you've got more than a hundred people who will still have a problem after a bug is closed, that means there needs to be a new bug created for it, *by the maintainers*! Otherwise you're

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2018-03-08 Thread Daniel van Vugt
This bug is closed. If you have any issues at all, please log a new bug by running this command: ubuntu-bug bluez -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2018-03-08 Thread ken
first thing first: bluetooth device can be paired with command line. I have the same error on my eOS/ubuntu 16.04, "bluetoothd[17440]: Not enough free handles to register service", and have tried many many options, have desprated for a year. and today I've success connected my bluetooth headset

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-14 Thread Daniel van Vugt
Yes the bug title changed but the problem the original reporter was describing in the bug description did not. The original description and the current description both say: "On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices:"

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-14 Thread Jason Owen
The original bug title was '15:10: bluetoothd reports "Not enough handles to register service" at start', and the original bug description described both the "Not enough free handles to register service" problem and the "Failed to start discovery" problem[1]. Between #47 and #48, the title and

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-13 Thread Daniel van Vugt
Yes I understand you and most people are asking for a resolution to "Not enough free handles to register service". However it is better for a bug's resolution if we focus on the problem that the original reporter was trying to describe. And that's a very different, unrelated problem. We certainly

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-13 Thread WinEunuchs2Unix
Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b: Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service Changed" characteristic Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Error

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-13 Thread WinEunuchs2Unix
This bug effects 128 people and closing it because you don't like the title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug report in the hopes it will be solved: https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not- enough-free-handles-to-register-service-error

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-01 Thread JeWu
Same issue here with Mint 18.2 Cinnamon and HID Logitech Mouse M535. No matter which Kernel i used (from 4.8-x to 4.13.0-17) the same issue occured again. I finally got it working again by issuing the command sudo bluetoothctl >power off >power on >quit After that, wWhile running bluewho

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-09-17 Thread Daniel van Vugt
Everyone please open new bugs instead of commenting here. This bug is closed per comment #48. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-09-15 Thread gcchen
My laptop runs ubuntu 16.04. Linux: 4.4.0-93-generic I tried to debug this issue by compiling bluetoothd from source code. Surprisingly, this issue is fixed after executing newly compiled bluetoothd instead of /usr/lib/bluetooth/bluetoothd. Steps to build and run newly compiled bluetoothd is

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-31 Thread Rajesh
This may not be a bug. Even I faced this error which seems to be related to another error, blueman.bluez.errors.DBusFailedError for which I found the solution here: https://askubuntu.com/questions/801404/bluetooth- connection-failed-blueman-bluez-errors-dbusfailederror-protocol-no. Hope this may

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-30 Thread Daniel van Vugt
That appears to be a different bug. Also, this bug is closed. If you have any issues at all in future then please open a new bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-29 Thread doru001
I succeeded to connect only from GUI, Ubuntu 16.04, xfce4, from applet, probably using blueman-manager and associated GUI only commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-29 Thread doru001
https://stackoverflow.com/questions/29891254/bluez-5-30-not-enough-free-handles-to-register-service-error-in-starting-blue Apr 27 '15 "I dived into the code for debugging the issue a little bit. The attrib_db_find_avail(adapter, svc_uuid, size)[in function: gatt_service_add()] always return 0.

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-23 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery:

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-07-22 Thread abhijit
** Changed in: bluez (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: