[SOLVED] Bluetooth not working except for root

limpingstone · 03-30-2017, 04:44 PM

I am using Slackware64 14.2 pre-installed with blueman-manager (BlueZ).
Bluetooth works absolutely fine with root, but not my own account.
My account does not even start the manager after boot, and I tried to launch the manager manually using 'sudo'. Still, the manager cannot connect to my headset and smartphone, while showing this error message:

Connection Failed: DBusFailedError: Protocol not available

I doubt that it is because of having limited permission to hardware configurations. Any ideas how to solve it?

Thank you!

Skaendo · 03-30-2017, 04:51 PM

Is your user a member of the recommended groups?

This issue has been gone over and over.
Example: https://www.linuxquestions.org/quest...er-4175591462/

Recommended groups are:

Code:

audio cdrom floppy plugdev video power netdev lp scanner

BW-userx · 03-30-2017, 05:12 PM

yep

Code:

userx@slackwhere⚡~ $groups
users lp wheel floppy audio video cdrom plugdev power netdev scanner userx

my Bluetooth works.

and yep that was my post. learn from my mistake . lolololo hehe.

limpingstone · 03-30-2017, 06:03 PM

Nope, it still doesn't work.
And I also got this message trying to connect to my headset: (no sound)

Connection Failed: Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/blueman/services/meta/SerialService.py", line 29, in connect
port_id = create_rfcomm_device(Adapter(props['Adapter']).get_properties()['Address'], props['Address'], 1)
File "_blueman.pyx", line 218, in _blueman.create_rfcomm_device (_blueman.c:2127)
Exception: Can't connect RFCOMM socket

It did connect, but there is no sound coming out of the headphone.
BW-userx I noticed the wheel group you have. Is it because of the group you added?

Thanks!

BW-userx · 03-30-2017, 06:17 PM

Quote:

Originally Posted by limpingstone

Nope, it still doesn't work.
And I also got this message trying to connect to my headset: (no sound)

Connection Failed: Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/blueman/services/meta/SerialService.py", line 29, in connect
port_id = create_rfcomm_device(Adapter(props['Adapter']).get_properties()['Address'], props['Address'], 1)
File "_blueman.pyx", line 218, in _blueman.create_rfcomm_device (_blueman.c:2127)
Exception: Can't connect RFCOMM socket

It did connect, but there is no sound coming out of the headphone.
BW-userx I noticed the wheel group you have. Is it because of the group you added?

Thanks!

no I actually I only added wheel to get sudo.
you're using blueman-manager to pair your head set?

then if you get it paired you have to use pavcontrol to change the source to your headset to get sound.

Code:

usermod -aG users,wheel,floppy,audio,video,cdrom,plugdev,power,netdev,lp,scanner

I'd just reboot to keep it simple then try to pair your headset using blueman-manager.

you don't really need wheel I think it was only plugdev audio and maybe netdev that I tried to only add first time i went though this and it worked.

Code:

userx@slackwhere⚡/etc/xdg/autostart $cat blueman.desktop
[Desktop Entry]
Name=Blueman Applet
Name[ast]=Applet Blueman
Comment=Blueman Bluetooth Manager
Icon=blueman
Exec=blueman-applet
Terminal=false
Type=Application
Categories=

that is if it is not showing up in your desktop

limpingstone · 03-30-2017, 06:28 PM

Quote:

Originally Posted by BW-userx

no I actually I only added wheel to get sudo.
you're using blueman-manager to pair your head set?

then if you get it paired you have to use pavcontrol to change the source to your headset to get sound.

Well weirdly, I found that there are in fact two managers for bluetooth: blueman-manager and the system default manager in settings. I am rather confused which one I should use. And by the way, the one provided by the system seems like it's not even available. Is it another group that I need to add to make it work? For both of them works in root.

BW-userx · 03-30-2017, 06:37 PM

Quote:

Originally Posted by limpingstone

Well weirdly, I found that there are in fact two managers for bluetooth: blueman-manager and the system default manager in settings. I am rather confused which one I should use. And by the way, the one provided by the system seems like it's not even available. Is it another group that I need to add to make it work? For both of them works in root.

Thank you! It's my first time using Slackware and I have many to learn...

what WM are you using and are you getting the apple showing up in the apt tray? whichever one shows up click on it and go though its setup search with your Bluetooth device turned on for discovery. then just follow the prompts.

if you have to copy the one desktop to /etc/xdg/autostart

Code:

userx@slackwhere⚡/etc/xdg/autostart $ls /usr/share/applications/blue*
/usr/share/applications/blueman-adapters.desktop
/usr/share/applications/blueman-manager.desktop

Code:

sudo cp -v /usr/share/applications/blueman-manager.desktop /etc/xdg/autostart

logout and back in again to get it to load.

limpingstone · 03-30-2017, 07:02 PM

The default bluetooth manager (藍芽) is not working. And I still have to manually turn on blueman-manager.

Code:

sudo /usr/bin/blueman-manager

https://drive.google.com/file/d/0B5U...ew?usp=sharing

Is that the apple you're talking about?
So I believe I should stick to blueman-manager?

BW-userx · 03-30-2017, 07:15 PM

Quote:

Originally Posted by limpingstone

The default bluetooth manager (藍芽) is not working. And I still have to manually turn on blueman-manager.

Code:

sudo /usr/bin/blueman-manager

https://drive.google.com/file/d/0B5U...ew?usp=sharing

Is that the apple you're talking about?
So I believe I should stick to blueman-manager?

yes applet (typo - not an apple) and do not use the command line to start it. use the desktop file that is prob why it is erroring out on you.

AGAIN

Code:

sudo cp -v /usr/share/applications/blueman-manager.desktop /etc/xdg/autostart

logout then back in again after you've copied it into your xdg/autostart directory.

bassmadrigal · 03-30-2017, 08:01 PM

What is the output of the groups command for your user?

limpingstone · 03-30-2017, 08:50 PM

Quote:

Originally Posted by bassmadrigal

What is the output of the groups command for your user?

users lp wheel floppy audio video cdrom plugdev power netdev scanner

All I should have I believe. LOL

limpingstone · 03-30-2017, 09:23 PM

Quote:

Originally Posted by BW-userx

yes applet (typo - not an apple) and do not use the command line to start it. use the desktop file that is prob why it is erroring out on you.

AGAIN

Code:

sudo cp -v /usr/share/applications/blueman-manager.desktop /etc/xdg/autostart

logout then back in again after you've copied it into your xdg/autostart directory.

For some reason, blueman-manager.desktop is not picked up by the system when I login with KDE. That is why I started blueman-manager with Konsole. I even tried "chmod 755 blueman-manager.desktop" to make it executable, and it still does not run.

I tested the .desktop file with Konsole and it just gave me a list of "command not found". Perhaps the .desktop file is corrupted?

Richard Cranium · 03-30-2017, 10:00 PM

Maybe you should check your normal user's home directory for any files/directories that are owned by root. A sudo with the wrong command can do interesting things to your environment.

limpingstone · 03-31-2017, 12:21 AM

I think for now I'll deal with pavcontrol first and see if it works fine.

Thank you for all your answers!

BW-userx · 03-31-2017, 08:57 AM

Quote:

Originally Posted by limpingstone

For some reason, blueman-manager.desktop is not picked up by the system when I login with KDE. That is why I started blueman-manager with Konsole. I even tried "chmod 755 blueman-manager.desktop" to make it executable, and it still does not run.

I tested the .desktop file with Konsole and it just gave me a list of "command not found". Perhaps the .desktop file is corrupted?

check your desktop file and if you have to put the absolute path to the executable in the TryExec and Exec=/usr/bin/executable <-- like that . you could even try using the other desktop file for the other executable -- the main thing is letting the system start it and not you in the cli. it got a go through the proper channels it is after all a root permissions needed to run properly like the wifi and network connections.

This is all taken care of via (what should I call it?) the executable chain of command the polkit and other needed files that give out permissions for things like this.