Bug 486574 – net-wireless/bluez-4.101-r*: bluetooth device not always detected

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Anton Gubarkov 2013-09-30 13:01:43 UTC]

Created attachment 359790 [details]
emerge --info

after upgrade to nm suite to 0.9.8.4 (network manager and nm-applet) the bluetooth pan network is no longer on the nm-applet menu

[Comment 1 Anton Gubarkov 2013-09-30 13:07:03 UTC]

The list of connected BT device are no longer on the bluetooth menu.

BTW I use GNOME 3.8

[Comment 2 Anton Gubarkov 2013-09-30 17:34:51 UTC]

When I had put my laptop to sleep and woke it up, the BT section appeared in the nm-applet.

It also appeared in the output of the nm-tools. It seems to be the issue between the NetworkManager and Bluez, rather than nm-applet

[Comment 3 Pacho Ramos 2013-09-30 21:18:18 UTC]

Looks like you are having some problems with bluetooth detection and, then, it's not shown in nm-applet. But I am not sure where could be the problem :/ (bluez? kernel?)

[Comment 4 Anton Gubarkov 2013-10-01 06:11:32 UTC]

Created attachment 359852 [details]
systemlog

It seems to be associated with the power management somehow...

I again experienced this issue after waking up my laptop.
I captured the systemd journal of the issue. 

I woke up my laptop at 09:33:53 and I have seen no BT devices in the nm-applet. After this I toggled the BT enable switch back and forth - voila! The devices are back.

Looking thru the log, i can see 
09:33:54 MyT430 btusb 3-1.4:1.1: no reset_resume for driver btusb?

Might it be the reason for my problem?

[Comment 5 Pacho Ramos 2013-10-01 06:28:19 UTC]

I am not sure, did you update your kernel recently? Also try with bluez-4.101-r5 (the older one)

[Comment 6 Anton Gubarkov 2013-10-01 06:36:41 UTC]

No, I didn't update the kernel. However, I did update bluez:

20130921 20:03:29 MSK   >>> emerge (25 of 47) net-wireless/bluez-4.101-r6 to /
20130921 20:03:29 MSK   === (25 of 47) Cleaning (net-wireless/bluez-4.101-r6
20130921 20:03:29 MSK   === (25 of 47) Compiling/Merging (net-wireless/bluez-4.101-r6
20130921 20:03:56 MSK   === (25 of 47) Merging (net-wireless/bluez-4.101-r6
20130921 20:03:59 MSK   >>> AUTOCLEAN
20130921 20:03:59 MSK   === Unmerging... (net-wireless/bluez-4.101-r5)
20130921 20:04:01 MSK   >>> unmerge success
20130921 20:04:04 MSK   === (25 of 47) Post-Build Cleaning (net-wireless/bluez-4.101-r6

Trying to downgrade to net-wireless/bluez-4.101-r5.

[Comment 7 Anton Gubarkov 2013-10-01 14:38:33 UTC]

Created attachment 359908 [details]
kernel config

I attach kernel config to further analyze the issue with btusb

[Comment 8 Anton Gubarkov 2013-10-01 15:27:13 UTC]

I have Linux MyT430 3.10.7-gentoo #8 SMP Fri Sep 20 18:46:40 MSK 2013 x86_64 Intel(R) Core(TM) i5-3380M CPU @ 2.90GHz GenuineIntel GNU/Linux

I attached the kernel config. Maybe somebody could use this information to analyze the issue with net-wireless/bluez-4.101-r6?

[Comment 9 Pacho Ramos 2013-10-01 18:55:30 UTC]

What did occur with net-wireless/bluez-4.101-r5?

[Comment 10 Anton Gubarkov 2013-10-01 19:06:04 UTC]

It simply works with net-wireless/bluez-4.101-r5. Whatever I tried - rebooting, powering the machine on and off, putting it to sleep and waking - bluetooth is working always.

I need to mask net-wireless/bluez-4.101-r6 to avoid automatic upgrade of this package.

[Comment 11 Pacho Ramos 2013-10-02 19:13:22 UTC]

Will need to either add a USE flag to apply that reversion patch or have the two revisions with fixed systemd/consolekit handling :|

[Comment 12 Anton Gubarkov 2013-10-03 04:17:02 UTC]

Today I again observed non-working bluetooth adapter with the same symptoms after waking the machine from sleep. I still have blues 4.101-r5. It seems that the problem is less frequent on 4.101-r5, but still present.

[Comment 13 Pacho Ramos 2013-10-03 05:47:29 UTC]

Then, not sure where is exactly the problem :S

[Comment 14 Pacho Ramos 2013-10-03 06:11:34 UTC]

Please try with -r7

[Comment 15 Anton Gubarkov 2013-10-14 04:58:12 UTC]

After upgrade to -r7 the problem still happens sometimes after I wake my laptop from sleep. I never experienced this issue when booting up my laptop with -r7

[Comment 16 Pacho Ramos 2014-02-02 14:31:15 UTC]

Try with 4.101-r8 switching hid2hci flag

[Comment 17 Anton Gubarkov 2014-02-03 11:03:55 UTC]

I run 5.12 since Feb 02 2014 - so far so good. I ran -r8 since Dec 2 2013 and it was OK. 
5.12 doesn't seem to have hid2hci use flag.

Thanks for support.

[Comment 18 Pacho Ramos 2014-02-03 19:49:14 UTC]

Well, lots of changes landed in bluez-5... is it solved in both then?

[Comment 19 Anton Gubarkov 2014-02-04 04:31:41 UTC]

It seems that it is solved in both versions.

[Comment 20 Pacho Ramos 2014-02-04 07:04:10 UTC]

Nice to know :)