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.
There is no point creating a "bluetooth" group because Slackware doesn't use it. If you want less hassles, you should add your user to the default Slackware groups. When creating a new user with adduser, you should press the "up arrow" when prompted and add the groups that are recommended (unless you really know what you're doing). But anyway, since you didn't do it, you can add them this way (as root);
Code:
usermod -a -G audio,cdrom,floppy,plugdev,video,power,netdev,lp,scanner userx
You can check the groups that your user is in with the simple groups command (or groups username). Then you need to make sure that "blueman-applet" is running on startup (for XFCE4 or whatever you use). It should automatically start, but if not, try that command from a terminal and see if it works.
One last thing, there's no need to cat files into grep Just;
Code:
grep userx /etc/group
will do. But simply 'groups' is enough.
yep checked out command line start applet .. posted, and yep their is more than one way to get the same results for listing groups for user, thanks
not able to log out or reboot at this momnet that is why I have not actually posted any results on this matter. .......
I think, and I could be wrong, but I think that the plugdev group is what you need to be added to since a lot of bluetooth cards etc. are recognized as USB devices. It could also be netdev since it is a network device as well.
I think, and I could be wrong, but I think that the plugdev group is what you need to be added to since a lot of bluetooth cards etc. are recognized as USB devices. It could also be netdev since it is a network device as well.
root has it and I know it is root so its gets everything where the user usually just like in this case does not automatically get what it should by default. I've added that user to everything minus, cd, and floppy which I do not know why Pat keeps that in there even. ver 14.2 and he is still using a floppy group?
nevertheless it is still not working even after a reboot. I know it is running, I know that xfce4 in the startup has it checked off to start, I run the applet from the command line and get errors for whatever reason, it has been posted. I am in Void right now, where everything works .. and tomorrow is another day.
which I do not know why Pat keeps that in there even. ver 14.2 and he is still using a floppy group?
Just because you don't have a floppy on your system doesn't mean that no one has a floppy. They're still readily available. Is there a good reason to remove the group just because you have no need for it?
Quote:
Originally Posted by BW-userx
nevertheless it is still not working even after a reboot. I know it is running, I know that xfce4 in the startup has it checked off to start, I run the applet from the command line and get errors for whatever reason, it has been posted. I am in Void right now, where everything works .. and tomorrow is another day.
Did you try the command I posted earlier to see if this is an xfce issue or an actual issue with your bluetooth on Slackware?
Just because you don't have a floppy on your system doesn't mean that no one has a floppy. They're still readily available. Is there a good reason to remove the group just because you have no need for it?
I didn't think anyone could still even get those things. It is not like you see them in the weekend shopper for best Buy.
Quote:
Did you try the command I posted earlier to see if this is an xfce issue or an actual issue with your bluetooth on Slackware?
Na I must have missed that post, I'll go back and run it tomorrow. k? IN void right now, and I am in the middle of a download.
MOD: found it
Code:
, try running hcitool dev to see if it is working properly.
OT: My server has a floppy drive installed, and I have 2 backups. They come in handy once in a while. Like BIOS updates that are most of the time Windows based, are really convenient to do from a floppy. Plus there is an option to use a boot floppy, which I have not tried, but am curious about. I just do not want to take my server offline to try.
I didn't think anyone could still even get those things. It is not like you see them in the weekend shopper for best Buy.
Best Buy is pretty limited in what they sell in stores as far as individual computer components. Since floppies are not common, it'd be a waste of space on their shelves when something else that is likely to sell could fill it. They even have a pretty slim selection of internal hard drives, and last I looked, I don't even think they had SSDs.
yep checked out command line start applet .. posted, and yep their is more than one way to get the same results for listing groups for user, thanks
Cool, but they're not entirely equivalent. For example, if you've just added a user to a group but they've not logged out of their environment yet, then grepping /etc/group and what is returned from the groups command will be different;
Code:
## as user 'abc'
bash-4.3$ groups
users
bash-4.3$ su
root@slack /home/abc # usermod -a -G plugdev abc
root@slack /home/abc # exit
bash-4.3$ grep abc /etc/group
plugdev:x:83:abc
bash-4.3$ groups
users
Obviously after a logout it will be in sync. Not a huge deal, but it's worth checking groups with the groups command, since it will tell you what groups you are really in at that moment. Your bluetooth problem seems like a permissions issue, but who knows. Good luck.
Last edited by drgibbon; 10-16-2016 at 08:26 AM.
Reason: oops
Just because you don't have a floppy on your system doesn't mean that no one has a floppy. They're still readily available. Is there a good reason to remove the group just because you have no need for it?
Did you try the command I posted earlier to see if this is an xfce issue or an actual issue with your bluetooth on Slackware?
Code:
userx@SlackDaddy & ~ >> $hcitool dev
Devices:
hci0 40:2C:F4:18:37:56
that it right there. it has an address, it is modular plugged into the mother board on my laptop... not usb
Your bluetooth problem seems like a permissions issue, but who knows. Good luck.
that is what I am thinking, pol-kat files or whatever they are called may need modifying. not one of my strong points. but I am not shy about it either.
I could throw myself onto Wheel and activate it and see what that does but i was kind of telling myself I get way from sudo in Slackware. and use su or su -
I have one like those too (Dell OCW725) (Broadcom), but I cannot seem to find any info on it in dmesg, lspci or lsusb.
if you are using the other one on PCIe mini it might be canceling it out, or it is not plugged in all of the way, may need a pull it out then push it back in ( that's what she said) solution. lol
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Just;
.. and tomorrow is another day.
