Slack Current: XFCE4 no shutdown, suspend,switch user permissions w/sudo rights
 

I have not used xfce4 in a long while. but I do remember if I have sudo rights it just gives me the ability to do more than just logout of my session without any other adjustments to the system needed to gain them rights.

User created, and uses xfce4 where root privileges are needed to gain permissions to reboot, and shut down system. User is given sudo (no passwd). This is using that little message box that comes up and gives user an option to do theses things when selecting to logout etc...

Why is it not working?

root premissions is only needed when using the command shutdown or reboot from console. I will work with control alt del, to reboot or use the power button to shutdown.
my user are in thous groups It works for me, I don't know what you did. Maybe you need to be in the group power?
I dont think you should need sudo just to reboot or power off, but if you want it configured that way.. its up to you

let me check my groups, I did give them defaults and added wheel, but too giving more thought to this, I might have a corrupted home, (if that might have anything to do with it).

users lp wheel floppy audio video cdrom input plugdev power netdev scanner

I'm running stuff, so I cannot hit the three button salute to see what happens, but I know I can push my power button then it shuts down. It is just that when selecting logout from the menu that all of the other options are shaded out, whereas they use to never be when a user has sudo permissions(?) from what I remember. At least that was my logical assumption that was the reason behind the options being shaded out because it is a 'normal' user and they are not to be allowed to reboot, or shut down the system. Because in reality even though Linux maybe being used as a one person Operating System, it is still a server Based system and all of the rules still apply.

A user without root privileges has no rights to shutdown or reboot the system, therefore the options are shaded out, unless, in polkit they have been modified(?) otherwise, for example with mounting drives, ie. automount for USB ports. Because root is the only one that is suppose to have rights to mount and unmount drives as well. So the same principles apply to rebooting and shunting down the system.

I deleted myself from my wheel group then added myself back
now I have the same problem... those buttons that used to shutdown and reboot the computer are grayed out
maybe this is a bug. this xfce is really old

if you dont use xfce with startx, if you use an login manager are the problem still there?
if it is I think this is a serious problem. im not using current its 14.2

Just to test it, I just created a new user and selected all the defaults, and started Xfce. Log out, Reboot, Shutdown and Suspend are all there and working as they should.
Based on that it looks like the problem maybe self-inflicted?
:scratch:

right now I am using startx. as I usually use this for the default desktop upon first installation of Slack before I install or go to something else, like installing e16 as this is what I am using now, whereas it use to be WindowMaker. XFCE4 it is easier to get wifi started with less steps involved. ie installing a system tray, starting it, then starting the applet, then selecting the provider.

nevertheless, this too is not DVD install iso, it is the one that alien bob made of current, though that should have nothing to do with this. I do not remember ever having an issue with this regardless if I use startx or a login manager. this might turn out to be just a quirk, and go away. After I get a chance to 'play with this' as it stand at the moment I am running something, and I don't want to have to stop it, then start it all over again at the moment. Putting that off until this is solved. This is a lower priority then what I am running.

the version XFCE is whatever is the latest that slack installs and updates. Version 4.12 dis by Slackware is in the about gui.

do what I did and tell me, yes it works if you dont leave you sudo group while you logged into xfce. dont do it if you dont want to brake this. yes you can cal it self inflicted if you would know. and it can be ignored. if you dont know then it could be a problem

Hey I tested with KDM and there is no problem I can reboot shutdown from xfce,s log out menu.
So this is just when we use startx or startxfce4, its a strange behavior but its not a problem cus we can shutdown/reboot after we log out ;)

that is your option.

opinion? Yes and what is yours my friend? :)

No, it should work if one has privileges to it, it is more convent. call it lazy or time management.

btw I don't know what i did, but I ended up rebooting and then it worked. sooo... time management is now in play. ;) cheers!

There are certain features of XFCE which work depending on the session manager used for Init4 login. If you use KDM or AlienBob's SDDM v15 then you should find that the power down, switch user, and suspend will work. If you use startX from Init3 or XDM from Init4 they won't work. Some have reported that if you use LDM that it will work, I don't know because I don't have LX on my system. My test are on 14.2 x64. Since KDM is slated to be replaced, hopefully by SDDM, it might make sense to ask AlienBob if he has worked out any bugs with the latest version of SDDM. He can probably provide more information about SDDM and also if he has those XFCE functions working in his -current LIVESLAK versions. HTH Cheers, BrianA_MN

I've always used the dvd iso install, and whenever I've ever used xfce4 I have never had it not work, using startx or login a manager, lxdm, this was AlienBob current iso, and I just seen that it wasn't working with this install. as I've only installed slack using AlienBob iso two or three times now, as of late, and this was the only time I've noticed it not working, but too, I switched to fluxbox on my other installs, because network manager is already set up as an executable and all I did was it ctrl f2 and start nm-applet, got my wifi up and finished setting up.

I got them back too, I didn't do anything...
I edited /etc/set_rlimits.conf
Okej I agree this should just work, or at least be the same so one know what to expect.
there is something unstable going on here.