since i had no luck with any of the previous bluez versions i installed: net-wireless/bluez-4.21 USE="doc examples -old-daemons usb -alsa -cups -debug -gstreamer -test-programs" looks good, less errors, needs to config than other versions, except it does not create pan1 bridge by default. bluetoothd -d -n ... bluetoothd[5577]: Adapter /org/bluez/5577/hci0 has been enabled bluetoothd[5577]: child 5579 exited bluetoothd[5577]: Computer is classified as desktop bluetoothd[5577]: Current device class is 0x0a2104 bluetoothd[5577]: Setting 0x000104 for major/minor device class bluetoothd[5577]: link_key_request (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) bluetoothd[5577]: kernel auth requirements = 0x00 bluetoothd[5577]: stored link key type = 0x00 bluetoothd[5577]: adapter_get_device(00:1E:45:32:D1:45) bluetoothd[5577]: hcid_dbus_bonding_process_complete: status=00 bluetoothd[5577]: adapter_get_device(00:1E:45:32:D1:45) bluetoothd[5577]: hcid_dbus_bonding_process_complete: no pending auth request bluetoothd[5577]: Added new connection: bnep0 bluetoothd[5577]: Can't add bnep0 to the bridge pan1: No such device(19) Reproducible: Always net-misc/bridge-utils-1.4 net-wireless/bluez-gnome-1.8
Please post output of 'emerge --info' as well (for instance, it will show kernel version and architecture)
Created attachment 174532 [details] emerge --info
the same situation with: net-wireless/blueman-0.5 net-wireless/bluez-gnome-0.28 net-wireless/bluez-libs-3.36 net-wireless/bluez-utils-3.36 net-wireless/gnome-bluetooth-0.11.0 x11-themes/blueglass-xcursors-0.4 server started from blueman Jan 18 13:30:06 anubis hcid[3609]: link_key_request (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) Jan 18 13:30:07 anubis hcid[3609]: Added new connection: bnep0 Jan 18 13:30:07 anubis hcid[3609]: Can't add bnep0 to the bridge pan1: No such device(19) Jan 18 13:30:07 anubis /etc/init.d/net.bnep0[4415]: net.bnep0: not allowed to be hotplugged Jan 18 13:30:07 anubis hcid[3609]: link_key_notify (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) Jan 18 13:30:09 anubis /etc/init.d/net.bnep0[4441]: net.bnep0: not allowed to be hotplugged
I suggest you to ask for help in http://www.bluez.org/development/lists/ :-)
BlueZ 4.21 is not on portage anymore. Can anyone reproduce this bug on bluez-4.39-r2 or the 4.60 ebuild attached on bug #270859?
anubis ~ # qlist -Iv bluez dev-python/pybluez-0.16 dev-ruby/rbluez-0.1 net-wireless/bluez-4.39-r2 with net-wireless/blueman-1.21 Group Network and Network Access Point checked on NAP settings: dnsmasq, NAT enabled trying to connect with the phone, the syslog: Jan 20 20:17:45 anubis bluetoothd[3203]: link_key_request (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) Jan 20 20:17:46 anubis bluetoothd[3203]: Added new connection: bnep0 Jan 20 20:17:46 anubis kernel: device bnep0 entered promiscuous mode Jan 20 20:17:46 anubis kernel: device bnep0 left promiscuous mode Jan 20 20:17:46 anubis bluetoothd[3203]: Can't add bnep0 to the bridge pan1: Invalid argument(22) Jan 20 20:17:46 anubis kernel: usb 2-2:1.0: uevent Jan 20 20:17:46 anubis kernel: usb 2-2: uevent
> trying to connect with the phone, the syslog: > Jan 20 20:17:45 anubis bluetoothd[3203]: link_key_request > (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) > Jan 20 20:17:46 anubis bluetoothd[3203]: Added new connection: bnep0 > Jan 20 20:17:46 anubis kernel: device bnep0 entered promiscuous mode > Jan 20 20:17:46 anubis kernel: device bnep0 left promiscuous mode > Jan 20 20:17:46 anubis bluetoothd[3203]: Can't add bnep0 to the bridge pan1: > Invalid argument(22) > Jan 20 20:17:46 anubis kernel: usb 2-2:1.0: uevent > Jan 20 20:17:46 anubis kernel: usb 2-2: uevent please, send the complete dmesg.
those are the related rows from dmesg. the complete dmesg would be irrelevant
(In reply to comment #4) > I suggest you to ask for help in http://www.bluez.org/development/lists/ :-) > Did you finally asked there? They will probably know much more about where the problem could be. Good luck! :-)
> trying to connect with the phone, the syslog: > Jan 20 20:17:45 anubis bluetoothd[3203]: link_key_request > (sba=11:11:11:11:11:11, dba=00:1E:45:32:D1:45) > Jan 20 20:17:46 anubis bluetoothd[3203]: Added new connection: bnep0 > Jan 20 20:17:46 anubis kernel: device bnep0 entered promiscuous mode > Jan 20 20:17:46 anubis kernel: device bnep0 left promiscuous mode > Jan 20 20:17:46 anubis bluetoothd[3203]: Can't add bnep0 to the bridge pan1: > Invalid argument(22) > Jan 20 20:17:46 anubis kernel: usb 2-2:1.0: uevent > Jan 20 20:17:46 anubis kernel: usb 2-2: uevent > Please, try to load the bridge kernel module, it is called bridge, the kernel option is CONFIG_BRIDGE IIRC, then restart bluetoothd.
the bridge module was loaded, i saw pan1 in ifconfig
(In reply to comment #11) > the bridge module was loaded, > i saw pan1 in ifconfig > So how will we fix this bug? I think it's not worth load bridge module when we load bluetoothd.
(In reply to comment #12) > So how will we fix this bug? I think it's not worth load bridge module when we > load bluetoothd. > I still don't know. The module is loaded in Balint's case and it is supposed to be autoloaded anyway. Balint, I have some ideas about this, could you run bluetoothd tracing all calls to ioctl's? something like this would do: sudo strace -e trace=ioctl bluetoothd -dn Trying with a current kernel would be useful too. Anyway, feel free to drop by #bluez-users at freenode and ping me, my nick is vcgomes.
Any news on this? Have you tried with 4.61? If still fails, please ask on linux-bluetooth@vger.kernel.org mailing list (I think that you don't need to subscribe to it, you can simply ask for help there) Thanks and good luck!
Created attachment 220399 [details] strace sorry for the late reply. my current bluez is net-wireless/bluez-4.61 the straceis attached
Did you asked in mailing list?
no, i use my phone's wifi. sorry
Have you tried with most recent kernel? (2.6.33)
(In reply to comment #18) > Have you tried with most recent kernel? (2.6.33) > ping! :-)
(In reply to comment #19) > (In reply to comment #18) > > Have you tried with most recent kernel? (2.6.33) > > > > ping! :-) > no, and i can't in the near future.
I has the same issue and I tried "strace -e trace=ioctl bluetoothd -dn" with the following result when my mobile is connecting using bluetooth: ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(24, 0x800448d3, 0xbfda26f8) = -1 ENOENT (No such file or directory) ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 bluetoothd[32359]: link_key_request (sba=11:11:11:11:11:11, dba=00:24:EF:1B:53:60) ioctl(23, 0x800448d7, 0xbfda29c7) = 0 bluetoothd[32359]: kernel auth requirements = 0x04 bluetoothd[32359]: stored link key type = 0x00 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 bluetoothd[32359]: adapter_get_device(00:24:EF:1B:53:60) ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(24, 0x800448d3, 0xbfda26f8) = -1 ENOENT (No such file or directory) ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(24, 0x800448d2, 0xb771d958) = 0 ioctl(24, 0x800448d3, 0xbfda1584) = 0 ioctl(23, 0x800448d4, 0xb770f240) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 bluetoothd[32359]: BNEP: incoming connect from 00:24:EF:1B:53:60 ioctl(9, 0x400442c8, 0xbfda22e0) = 0 bluetoothd[32359]: Added new connection: bnep0 ioctl(24, SIOCGIFINDEX, {ifr_name="bnep0", ifr_index=27}) = 0 ioctl(10, 0x89a2, 0xbfda22dc) = -1 EINVAL (Invalid argument) bluetoothd[32359]: Can't add bnep0 to the bridge pan1: Invalid argument(22) ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(24, 0x800448d2, 0xb771db80) = 0 ioctl(24, 0x800448d3, 0xbfda1584) = 0 ioctl(23, 0x800448d4, 0xb771d958) = 0 bluetoothd[32359]: hcid_dbus_bonding_process_complete: status=00 bluetoothd[32359]: adapter_get_device(00:24:EF:1B:53:60) bluetoothd[32359]: hcid_dbus_bonding_process_complete: no pending auth request ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0 ioctl(23, 0x800448d3, 0xb770e7a8) = 0
Can you please forward this to upstream mailing list as asked in comment #14 ? Thanks
Please try with bluez-4.67, it includes a fix for device detections on some setups
