This is not a crash. Nothing crashes. It just disconnects immediately
after connect and bluetoothctl is frozen without sudo.
After running apport-collect bluetooth started working without sudo, but
it still failed to connect. This is weird, since I did not use the GUI
applet to connect.
Thank
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932691/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932679/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
bluetooth stopped working after some update, probably to bluez5
before it was working flawlessly following
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
now $ bluetoothctl shows
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932685/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932690/+files/rfkill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932689/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932686/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932688/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932687/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932684/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932683/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932681/+files/Lspci.txt
--
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/1710601
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932680/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1710601/+attachment/4932682/+files/Lsusb.txt
--
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/1710601
bluetoothd is still running after the problem occurs.
there is a /var/crash/_usr_lib_blueman_blueman-rfcomm-watcher.0.crash which in
my opinion refers to an unrelated incident involving blueman. if you want I can
upload the file.
--
You received this bug notification because you are a member
** Description changed:
- bluetooth stopped working after some update, probably to bluez5
- before it was working flawlessly following
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
- now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well
until
Public bug reported:
bluetooth stopped working after some update, probably to bluez5
before it was working flawlessly following
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well
until I try to
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.
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.
20 matches
Mail list logo
