Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm writing in today because my Lenny installation has decided to deny me the right to shutdown the machine. What happens is the shutdown button on my panel is grayed out, and there are no 'Shutdown,' 'Restart,' etc options in the 'System' menu (I'm using Gnome).
It's been doing this for about a week, and I can't remember what exactly I was doing before this happened. I'm not sure if I updated or not...the only real power-using I've done recently is set up a 32-bit chroot, that's about it.
I've been shutting down as root in a terminal, which is rather cumbersome for me. Does this sound like some sort of permissions issue? I love my current installation, and hope I don't have to reinstall...
Any advice is most welcome and appreciated!
PS - I've seen this happen when being dumped into a terminal upon boot-up, and using the 'startx' command as user, but GDM is starting with a script.
I don't know about Debian, but in Slackware you can use the setuid bit to run /sbin/halt as a normal user. Take a note of the actual /sbin/halt permissions in case it won't work and then run:
I had something like this once where there was an unstopped process running, I identified the process by executing ps from the command line and then killing the process that was causing my problem.
Well, I went ahead and checked the permissions on /sbin/halt, and users had read access, which seems correct, then I tried the setuid command, but nothing has changed, unfortunately.
And thanks for the tip on the possibility of a process causing this. I wouldn't even know what to look for if I were to try to isolate it. An interesting thing to note is that when I shutdown as root in a terminal using "shutdown now," it drops to a maintenance shell instead of going down. If I use "shutdown -h now," (with the halt argument), it works correctly. "shutdown -r now" also works okay. Also, I feel I should mention that if I log out and am sitting in front of the GDM login screen, I still cannot shutdown. In theory, all my processes should have terminated, right? Maybe I'll switch over to a virtual terminal while my user is logged out and run "ps -U root -u root -N"? That shows processes which are not owned by root, am I right?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,588
Rep:
Well, in KDE you have a users/groups (or security) menu / module (I forgot in which one exactly it resides) where you can determine for the KDE-shutdown button who may use it. Maybe you could give a try in the depths of the Gnome menu tree...
GNOME Users: Starting GNOME Power Manager with your GNOME Session
=================================================================
1) Add yourself to the powerdev group; this group is created by hal >= 0.5.6+cvs20060219-1.
2) Open System -> Preferences -> Sessions
3) In the Startup Programs tab, click Add
4) Type "gnome-power-manager", click OK.
5) Log out of your gnome session, and log back in again.
Interesting, that. Problem is, I installed Fedora on another partition, which did an SELinux relabel, which I believe borked my Debian installation.
When I attempt to start it now, it quickly halts after the "kernel alive" message, and reads:
/bin/sh: can't access tty; job control turned off
(initramfs)
and I can't do anything further. I'd try turning SELinux off and doing another relabel, but I've uninstalled Fedora and put something else on that partition already.
Can this be fixed easily? I could always just reinstall Lenny, but it would be nice to avoid that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.