| View previous topic :: View next topic |
| Author |
Message |
Unb0rn
n00b
Joined: 12 Jun 2012
Posts: 63
|
 Posted: Wed Jan 25, 2017 1:14 pm Post subject: Gnome ~amd64 bluetooth issues |
 |
|
Hello!
I've already asked a similar question in another thread, but it turned out that it is more gnome-related and looks like a bug to me.
I've installed latest GNOME (~amd64) and now I am having issues with either gnome-bluetooth or gnome-settings.
I am seeing these(BT-related) strings in my logs:
| Code: | bluetoothd[2068]: Failed to set mode: Blocked through rfkill (0x12)
gnome-settings-[2313]: Could not open RFKILL control device, please verify your installation |
and these:
| Code: | bluetoothd[2068]: Failed to obtain handles for "Service Changed" characteristic
pulseaudio[2064]: [pulseaudio] bluez5-util.c: Found duplicated D-Bus path for adapter /org/bluez/hci0 |
I've tried to unblock BT via rfkill manually or even to build a kernel without rfkill at all-nothing helps. After manual unblock(or if using a kernel without rfkill) I can use bluettoth in bluetoothctl or hcitool, but not in gnome.
After pairing with my phone via bluetoothctl, bluetooth icon and menu appeared in upper right corner, but were still non-functional(buttons did nothing) and bluetooth applet in settings still reported "No bluetooth found"
It looks like a Gnome bug to me, but I have no idea where should I report it. Which logs do I need to attach? Any help is appreciated. |
|
| Back to top |
|
 |
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria
|
| Posted: Mon Jan 30, 2017 11:35 pm Post subject: |
|
|
| is this a notebook? |
|
| Back to top |
|
|
Unb0rn
n00b
Joined: 12 Jun 2012
Posts: 63
|
| Posted: Tue Jan 31, 2017 5:33 am Post subject: |
|
|
| Roman_Gruber wrote: | | is this a notebook? |
Yes. It's a Lenovo Yoga 3 Pro. |
|
| Back to top |
|
|
Shoaloak
n00b
Joined: 05 Nov 2016
Posts: 48
|
| Posted: Tue Jan 31, 2017 12:06 pm Post subject: |
|
|
Unb0rn,
Have you done the steps described on the Bluetooth wiki page?
I also had problems with Bluetooth on my Gnome /w Systemd machine. But got it (semi)working after messing about with the stuff described on the wiki.
Don't recall exactly anymore what i did, think I just set kernel options to y and i have net-wireless/bluez
installed. However my Bluetooth stuff on gnome doesn't work flawlessly.
What i mean by this is that i can always connect to my headset, but sometimes i can't put the audio to output on my headset using Gnome sound.
Had figured out a hackish way to do this with the command-line. But as i said, it's been some time and I forgot how.  |
|
| Back to top |
|
|
Unb0rn
n00b
Joined: 12 Jun 2012
Posts: 63
|
| Posted: Tue Jan 31, 2017 12:42 pm Post subject: |
|
|
| Shoaloak wrote: | Unb0rn,
Have you done the steps described on the Bluetooth wiki page?
I also had problems with Bluetooth on my Gnome /w Systemd machine. But got it (semi)working after messing about with the stuff described on the wiki.
Don't recall exactly anymore what i did, think I just set kernel options to y and i have net-wireless/bluez
installed. However my Bluetooth stuff on gnome doesn't work flawlessly.
What i mean by this is that i can always connect to my headset, but sometimes i can't put the audio to output on my headset using Gnome sound.
Had figured out a hackish way to do this with the command-line. But as i said, it's been some time and I forgot how. |
According to this page everything should work "out of the box". (Except kernel config, of course) I have all the options listed on this page enabled, my device (USB BT on Intel 7265) is getting deteced during boot. If I plug standalone USB BT dongle, it would be detected. I can see those devices with rfkill, hcitool or bluetoothctl, I can even scan with bluetoothctl or hcitool(it discovers devices nearby without problems). I even managed to pair with my phone with bluetoothctl. Only two problems left. First-BT devices don't get unblocked automatically during boot(only Wi-Fi does) and, even after rfkill unbllock all and/or replugging USB BT dongle, Gnome applet won't see any bluettoth devices and will simply print "No bluetooth found. Plug in a dongle to use bluetooth" |
|
| Back to top |
|
|
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria
|
| Posted: Tue Jan 31, 2017 1:07 pm Post subject: |
|
|
Are you using the latest kernel.org kernels?
Have you checked the staging / hidden section of the latest kernel.org kernel?
same for teh userspace.
bluetooth has issues. you may try an earlier version of bluez.
gnome has also many many issues. My opinion gnome is broken by design
bluetooth is a weird standard, it works sometimes. look at cars for example! sometimes its the phone fault, sometimes its the car fault, basically bluetooth is not the best standard, or these implementations are just buggy ...
| Quote: | | pulseaudio[2064]: [pulseaudio] bluez5-util.c: Found duplicated D-Bus path for adapter /org/bluez/hci0 |
components which may influence, and should be looked into
kernel
pulseaudio
systemd / udev / dev
bluez
... just gives you a hint already => duplicated D-Bus path |
|
| Back to top |
|
|
Unb0rn
n00b
Joined: 12 Jun 2012
Posts: 63
|
| Posted: Tue Jan 31, 2017 1:32 pm Post subject: |
|
|
| Roman_Gruber wrote: | Are you using the latest kernel.org kernels?
Have you checked the staging / hidden section of the latest kernel.org kernel?
same for teh userspace.
bluetooth has issues. you may try an earlier version of bluez.
gnome has also many many issues. My opinion gnome is broken by design
bluetooth is a weird standard, it works sometimes. look at cars for example! sometimes its the phone fault, sometimes its the car fault, basically bluetooth is not the best standard, or these implementations are just buggy ...
| Quote: | | pulseaudio[2064]: [pulseaudio] bluez5-util.c: Found duplicated D-Bus path for adapter /org/bluez/hci0 |
components which may influence, and should be looked into
kernel
pulseaudio
systemd / udev / dev
bluez
... just gives you a hint already => duplicated D-Bus path |
Thanks for your hints.
Yes, I'm running latest 4.9.6 kernel (gentoo-sources) with experimental patches. 7265 is rather old(it won't even have updated firmware anymore), should I enable staging drivers? (I feel like I'm stuck here)
Bluez-I've tried both 5.43 and 5.43-r1 ~amd64 versions, neither works...
Running latest (232) ~amd64 version of systemd with the latest virtual/udev.
Tried both stable 9.0 and new 10.0 of PulseAudio, still nothing.
I thought, if I am able to use it from shell with hcitool and bluetoothctl, then it should be userspace and gnome-related problem... Will be grateful for any specific ideas. |
|
| Back to top |
|
|
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria
|
| Posted: Tue Jan 31, 2017 3:46 pm Post subject: |
|
|
Yes enable staging drivers. Some stuff will be only in staging drivers and than removed. I had it several times for some of my laptop components in the past. Other stuff has to be build extra in external packages, because they will never be moved (accepted) in the main kernel tree.
| Code: | roman@ASUS-G75VW ~ $ equery y bluez
Keywords for net-wireless/bluez:
| | u |
| a a p s a n r | n |
| l m h i p p m r m i i s | e u s | r
| p d a p a p c a x i m 6 o s 3 | a s l | e
| h 6 r p 6 p 6 r 8 p 6 8 s c 9 s | p e o | p
| a 4 m a 4 c 4 c 6 s 4 k 2 v 0 h | i d t | o
---------+---------------------------------+---------+-------
4.101-r9 | o + + + o + + o + o o o o o o o | 5 o 0 | gentoo
---------+---------------------------------+---------+-------
5.39 | o + + + o + + o + ~ ~ o o o o o | 6 # 0/3 | gentoo
5.43 | o + + + o + + o + ~ ~ o o o o o | 6 o | gentoo
5.43-r1 | o ~ ~ ~ o ~ ~ o ~ ~ ~ o o o o o | 6 o | gentoo
|
I talk about the 4.xxx version, not the 5.xxx version. |
|
| Back to top |
|
|
|
Desktop Environments
