topic title: Cannot shutdown or reboot from Log Out gui
6 posts
• Page 1 of 1
-
Posts: 21
- Joined: 04 Apr 2013
#1
I am using antix12, live usb with persistence. Originally OK, but now cannot shutdown from Log Out gui. If I click shutdown button, Log Out window freezes. I tried BitJam's suggestions in can-t-shut-down-nor-reboot-t3425.html, but they did not help. I can shutdown using terminal command halt.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#2
Instead of editing /etc/sudoers edit /etc/sudoers.d/antixers
/etc/sudoers should look like this :
/etc/sudoers.d/antixers like this
/etc/sudoers should look like this :
Code: Select all
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
Defaults mail_badpass
Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification
root ALL=(ALL:ALL) ALL
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
# See sudoers(5) for more information on"#include" directives:
#includedir /etc/sudoers.d
Code: Select all
# sudoers file.
%users ALL=(root) NOPASSWD: /sbin/halt
%users ALL=(root) NOPASSWD: /sbin/reboot
%users ALL=(root) NOPASSWD: /sbin/blkid
%users ALL=(root) NOPASSWD: /sbin/fdisk.distrib
%users ALL=(root) NOPASSWD: /usr/bin/ceni
%users ALL=(root) NOPASSWD: /usr/local/bin/persist-config
%users ALL=(root) NOPASSWD: /usr/local/bin/persist-save
-
Posts: 21
- Joined: 04 Apr 2013
#3
/etc/sudoers.d/antixers does not have"%users ALL=(root) NOPASSWD: /usr/bin/ceni". Should I add it?
It also has"#%users ALL=(root) NOPASSWD: /usr/bin/rox".
/etc/sudoers is correct.anticapitalista wrote:Instead of editing /etc/sudoers edit /etc/sudoers.d/antixers
/etc/sudoers.d/antixers does not have"%users ALL=(root) NOPASSWD: /usr/bin/ceni". Should I add it?
It also has"#%users ALL=(root) NOPASSWD: /usr/bin/rox".
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#4
Ok, those do not really matter, as long as you have the reboot/halt options.
Something else is wrong with the logout script.
Open a terminal and type extantix.sh and then click on reboot and see what message is in the terminal
Something else is wrong with the logout script.
Open a terminal and type extantix.sh and then click on reboot and see what message is in the terminal
-
Posts: 21
- Joined: 04 Apr 2013
#5
I think this problem involves saving rootfs. I booted using rollback hoping that a previous linuxfs would not have this problem. Now, if I boot with homefs enabled and rootfs disabled, I can reboot or shutdown with no problem. If I boot with rootfs enabled, problem appears - I cannot use gui to reboot or shutdown.
This is what I found with rootfs enabled: I opened the gui and clicked reboot. The gui froze. I then opened antixcc, clicked save root persistence, and got an error message"Another copy of remaster-me or persist-save is running. If you are certain this is not so then delete the file: /live/config/locked and try again." I deleted locked and was then able to access save root persistence. With the /live/config directory open, I clicked on reboot in the gui, the locked file immediately appeared in /live/config, and the gui froze. So it seems the rootfs file is not saving at gui reboot or shutdown and preventing either of those actions.
I typed extantix.sh in root terminal and got"bash: extantix.sh: command not found". Did I not do this correctly? When I clicked on reboot, gui froze as previously.anticapitalista wrote:Open a terminal and type extantix.sh and then click on reboot and see what message is in the terminal
I think this problem involves saving rootfs. I booted using rollback hoping that a previous linuxfs would not have this problem. Now, if I boot with homefs enabled and rootfs disabled, I can reboot or shutdown with no problem. If I boot with rootfs enabled, problem appears - I cannot use gui to reboot or shutdown.
This is what I found with rootfs enabled: I opened the gui and clicked reboot. The gui froze. I then opened antixcc, clicked save root persistence, and got an error message"Another copy of remaster-me or persist-save is running. If you are certain this is not so then delete the file: /live/config/locked and try again." I deleted locked and was then able to access save root persistence. With the /live/config directory open, I clicked on reboot in the gui, the locked file immediately appeared in /live/config, and the gui froze. So it seems the rootfs file is not saving at gui reboot or shutdown and preventing either of those actions.
-
Posts: 21
- Joined: 04 Apr 2013
#6
Update:
I had forgotten that I had recently selected the"semi-automatic" option for rootfs save at reboot or shutdown. When I changed the option to"automatic" in persist-config.conf, I can now reboot or shutdown using the gui. When I use the"semi-automatic" option and try to reboot or shutdown, I do not get the popup offering me the choice to either save or not. Since I do not get the popup and therefore cannot select a choice, the logout gui appears to freeze when it actually is waiting for me to select a choice. Has anyone else had this problem?
I had forgotten that I had recently selected the"semi-automatic" option for rootfs save at reboot or shutdown. When I changed the option to"automatic" in persist-config.conf, I can now reboot or shutdown using the gui. When I use the"semi-automatic" option and try to reboot or shutdown, I do not get the popup offering me the choice to either save or not. Since I do not get the popup and therefore cannot select a choice, the logout gui appears to freeze when it actually is waiting for me to select a choice. Has anyone else had this problem?