Hi, On Wednesday 21 of January 2015 22:43:35 M Ren wrote: > Johan, > Iam afraid bluetoothd is running, since , hcitool and hciconfig work well . > I will make confirm tommorow . > btw, is there some debug way ? Those tools don't require bluetoothd to be running. Just use 'ps' to check if daemon is up. > Szymon, > I am using 5.24 , so , can u help providing the commit id ? http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=36d674036359a8e30546bd7799fca87fb903d181 > > 2015-01-21 22:33 GMT+08:00 Szymon Janc <szymon.janc@xxxxxxxxx>: > > Hi, > > > > On Wednesday 21 of January 2015 16:25:47 Johan Hedberg wrote: > >> Hi, > >> > >> On Wed, Jan 21, 2015, M Ren wrote: > >> > I encounter the issue. > >> > after I type bluetoothctl in shell, > >> > shell shows the [bluetoothctl] prompt, > >> > and then hang-up, like dead, > >> > do not respond to any input, include ctrl c .. > >> > I have to close the terminal window , or kill bluetoothctl in another > >> > terminal window. > >> > >> Usually this may happen if you don't have bluetoothd running (which > >> bluetoothctl expects to talk to). Waiting for D-Bus to be set up before > >> processing stdin is so that bluetoothctl can be scripted. > > > > Also not being able to close bluetoothctl in such case should be already > > fixed (since 5.22). > > > > -- > > Best regards, > > Szymon Janc -- Best regards, Szymon Janc -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
