** Also affects: bluez via
https://bugzilla.kernel.org/show_bug.cgi?id=199127
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565940
Title:
I have reported this issue at
https://bugzilla.kernel.org/show_bug.cgi?id=199127
** Bug watch added: Linux Kernel Bug Tracker #199127
https://bugzilla.kernel.org/show_bug.cgi?id=199127
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
OK, I can finally reproduce the problem, but I had to manually kill my
bluetoothd before I could make it fail. I guess a Kubuntu session is
similar to that environment. Confirmed, but low priority.
For a better idea that avoids bluetoothctl see comment #12.
Finally, please log the bug with the
With bluez version 5.48-0ubuntu3 from Kubuntu 18.04 Beta1 (Bionic), the
issue is still there :
The command 'bluetoothctl' displays 'Waiting to connect to
bluetoothd...', then hangs.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> My particular use case is to detect, inside a shell script, if there
is any bluetooth hardware at all.
I suggest a better way to detect Bluetooth hardware is to check with the
kernel directly:
if /sys/class/bluetooth/ exists and is non-empty then ...
The directory is created when the first
I can reproduce the bug in 16.04 but it seems to be fixed in 18.04:
$ echo '' | bluetoothctl
No agent is registered
$
$ bluetoothctl < /dev/null
[bluetooth]# quitt to bluetoothd...
No agent is registered
$
I'm going to declare this fix released and nominate 17.10 for a fix
(whatever the fix
With bluez version 5.46-0ubuntu3 from Ubuntu 17.10 (Artful), the issue
is still there :
The command 'bluetoothctl' systematically hangs.
** Tags added: artful
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Now I understand your use-case.
You probably could achieve similar with $ systemctl status
bluetooth.service. Also hcitool can tell if the adapter is up and
running but keep in mind that hcitool is depreciated and no longer
maintained by the upstream.
As for the man entry suggestion yes that
My particular use case is to detect, inside a shell script, if there is
any bluetooth hardware at all.
Since 'bluetoothctl' systematically hangs when there is NO bluetooth
hardware, I can NOT use the 'bluetoothctl' command to achieve this use
case.
But I have found a good alternate method :
if
I'm afraid that this is how the bluetoothctl is designed. This tool is a
command-line interface to the bluetoothd and requires it up and running.
It will not quit however when it is not running for a situations where
the daemon might come back online.
Ubuntu does not do anything special here, the
With bluez version 5.43-0ubuntu1 from Ubuntu 17.04 (Zesty), the issue is
still there :
The command 'bluetoothctl' displays 'Waiting to connect to
bluetoothd...', then hangs.
** Tags added: zesty
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached
end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: New
With bluez version 5.41-0ubuntu3 :
The command 'bluetoothctl' displays 'Waiting to connect to
bluetoothd...', then hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565940
Title:
bluetoothctl
The problem is still the same with bluez version 5.37-0ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565940
Title:
bluetoothctl systematically hangs when there is no bluetooth hardware
To
15 matches
Mail list logo
