[Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Daniel van Vugt
daniel.van.vugt at canonical.com
Fri Dec 15 02:05:59 UTC 2017
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:"
Thus the original bug title was just a mistake, which has been
It is inappropriate to commandeer and change the direction of a bug from
the intent of the original reporter because at any stage they do have
the right to change it back, or to proclaim that some eventual fix does
or does not resolve the original problem.
There are only 28 people, not 128, really subscribed to this bug. I'm
sure one of you could just follow this link and open a new bug:
It is actually pretty common for people to say "hey that bug you closed
doesn't fix the problem for me". However the bug should still remain
closed unless those people happen to be the original reporter. So in
that case, yes, if TJ was willing to change the description of this bug
to be about the problem you describe rather than the original problem
s/he reported then that's possibly OK.
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
15:10 and 16.04: bluetoothd "Failed to start discovery:
org.bluez.Error.NotReady" after bluetoothd restarted
To manage notifications about this bug go to:
More information about the Ubuntu-bluetooth