SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(or you may want to use existing 'netdev' or 'plugdev' groups)
Second, write a udev rule to make that bluetooth (device) owned and writable by the "blue" group. Here are good materials to learn how to write udev rules this and this, easy reading and quick to learn.
Still trying to understand udev rules well enough not to screw everything up.
BUT, here's a puzzler. I'm running Slack 14, but I also have Slack 13.1 on my HD. Booted it up, and guess what...blueman-manager runs as user without a hitch. Nothing unusual to see in /etc/udev/rules.d either. Only difference I can see is Python 2.6 with Slack 13.1 vs 2.7.3 with Slack 14.
BTW, I read "man hcitool" and "man hciconfig" and it's not at all clear (to me) how one might pair a Bluetooth cellphone with the linux box via the command line.
I'm tired of wasting more time on this; I'll just have to be content with running blueman-manager as root.
Careful with this, because if you leave out the -a then your user will be a member of the blue group but lose all the other groups. I believe the preferred tool in Slackware is gpasswd, so
Code:
gpasswd -a user group
might be better.
Also, don't forget that you need to log out and log back in for the new group assignments take effect. Similarly you might try to restart udev or reload the rules after you make changes.
Code:
udevadmn control --reload-rules
does that. According to the man pages this "is usually not needed" but easy to try. I may be just pointing out the obvious...hope it helps.
OK, I marked this SOLVED but it should have been marked KLUGED. I couldn't forget that my Slack 13.1 didn't have this problem, without any special udev rules. So, I did a quick-and-dirty:
Add /etc/modprobe.d/blacklist.conf with
Quote:
blacklist bluetooth
blacklist btusb
Add /etc/modprobe.d/bluetooth.conf with
Quote:
options btusb reset=1
Now to use bluetooth I just run:
Quote:
bluetoothd
modprobe btusb
I start blueman-manager as root, do the pairing juju, and I can run all the obexftp commands as a normal user. Not elegant, but works for me.
Not sure if it is still interesting for you but this is how it works for me (running blueman-manager as a non-root user). Check if the user is in the lp group (why - see https://wiki.archlinux.org/index.php/Blueman). If not - add the user to the lp group. A standard sequence logout, login after adding group doesn't work so you can use a brute force method (reboot) or try to restart messagebus daemon (/etc/rc.d/rc.messagebus). It can also need restarting your window manager and maybe bluetooth daemon.
Thanks for your continued interest. I *am* a member of the 'lp' group. I've just accepted that I need to start blueman-manager as root, but I can still be an ordinary user for the obexftp stuff.
Of course it's not a big problem but still strange. I am running Slackware 14.1 but it seems that the bluez and blueman packages are almost identical as in 14. Best regards.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.