you well maybe right in my case, BUT I state my case:

Through my experiences have I ever seen where I am having this same problem only when I am not attached to the wheel or sudo group (the later one was being long ago). When network manager even was asking for a password because it needs root permissions to get to the network. add myself to the wheel and I've never had this problem surface.

so my logical brain then tells me, wheel must be the reason why. Because that is the only difference I've made to my user, and my system.

this also goes for xfce4 allowing me the options to reboot, and shut down the system via my user, when it had wheel group added to the user.

If the user is not attached to wheel is when I do not get these root privileges needed options.

So there is plausible doubt in what you have told me and others on this matter of root privileges and having a user be attached to the wheel group to get them not being a solution.

I've just connected to my Logitech H800 headphone in bluetooth mode. wheel not required.

Attached Thumbnails

 

I confirm that it is necessary neither to include the user in the wheel group nor to start pulseaudio manually. As a reminder, the recommended setting is to have in rc.d all these scripts: rc. alsa, rc.alsa-oss and rc.pulseaudio not executable. pulseaudio should automatically start for each user as soon as logged in, which you can check typing:

from my googling around on this matter, because I do not even use bluetooth let alone have a headset to use it even. I was just trying to help. that being said, I see a lot of Slackware issues with people not being able to get their bluetooth to work, but I never had an issue with it, because I can look at my icon and see that it is working in my Slack. So I have it just in case I need it.

I did find one slack issue where the person said something about his plugdev group was not registering properly but somehow he did not explain in the LQ post but he got it working.

either way it is an issue that Slack should not be having.

You may have doubt, but that is just because you don't understand how wheel and sudo interact with a system. If you were to do more research, you'd understand, like I do, that belonging to the wheel group does absolutely nothing, unless you set up your /etc/sudoers to allow the wheel group the ability to run commands via sudo. You wouldn't even have to use the wheel group... you could use admin, sudo, or even kingme (checkers reference) groups instead of wheel. The wheel group has absolutely no power unless you set it up with sudo, and even then, you still have to use sudo to benefit from that power.

I have created new thread about my issue: bluetooth-headset-works-only-on-root

Please move/copy your reply there to preserve thread integrity. I thought that the problem is same as this thread author described but looks like my issue is different in some way. Thx!

I am no longer commenting on this situation especially in this post, it needs to be closed maybe as I already marked it solved, and he started a new thread in his own user name with the same question. Now he finaly reviles he has old config files that might be causing this problem he is having due to upgrades .. something he left out in the begining. ????

But I do wonder why the user is given the ability to shut down and reboot the system with the xfce4 menu when attached to wheel but if he is not then he does not get these options. the only thing different is the user having wheel and the other not. it maybe a polkit condistion. I do not dig that deeply into this. Unless I am having problems and I have to.

oh I do know that the word wheel is just a word and it can be changed.. it is called a variable it is the same methodology.

For your information, in Slint we use wm-logout to shutdown|reboot|hibernate|suspend as any user from twm, fvwm, blackbox, fluxbox, windowmaker. Only root is a member of wheel.

No issue to shut down or reboot the system from xfce either. I didn't fiddle with sudoers at all.

just a rocker huh?

Slint (Linux) is a new one to me. now I got to go see what that one is all about. I suppose it is a Derivative of Slackware.

Index of /slint/x86_64/slint-14.2/iso - Slackware UK

would that be it???

Yes, see here. I just hope hope that the the rock band won't sue me...

What's a matter, you can't hold a tune, or copy write infringements?

did you author this version?

@Didier Spaier

I have been looking for a different Distro to take up this space I was using for another one, that I do not want on my Laptop. How does it play with using the same home user directory across different distros?

I have Slackware and Void Linux sharing my same Home user Directory nicely.

The Slint version, yes. But see the acknowledgments at the bottom of the home page.

Oh yeah well that is your user name isn't it then?
Imagine that plain as day too. loo loo loo

I'll be checking it out tomorrow I suppose. I'm stuck in windows and itunes right now.

advice
using the dd method, or methods used to get in on to a USB stick / DVD to boot into install mode. you might want to add that for newbies and alike.

I rarely use xfce, so I'm not sure with this, but... my first guess is that there was something misconfigured or enabled/disabled in your system and you changed that around the time you set up your user with sudo. A second (albeit, less likely in my book) guess is that xfce will attempt to detect if your user is a member of the wheel group and if so, provide you a shut down/reboot option. But this does not seem to be a very smart idea because: 1. Just because a user is assigned wheel, doesn't mean that wheel has the ability to reboot the system (depending on how you have it set up in /etc/sudoers). 2. Depending on how /etc/sudoers is set up, you may need to type a password to even use sudo, so xfce would need to pop up a dialog to accept said password. 3. As said above, wheel doesn't have to be wheel. You can have full access to all commands with sudo by just setting up your user to have access within /etc/sudoers, not needing to ever use the wheel group. Or you could have a completely separate group called reboot that you set up in /etc/sudoers to have the ability to run the reboot, shutdown, and halt commands.

With the flexibility of Linux, sudo, and xfce, I find it hard to believe that they set up their DE to only detect the wheel group and then to present the user shutdown/reboot options. However, developers sometimes do things that I don't understand, so it is still possible they have this. All I know is KDE (my preferred DE) is able to reboot/shutdown without needing sudo and without requiring a user to be in the wheel group. Maybe if I get a chance over the next week, I can try creating a new user and see what I'm present with when logging into xfce.