- This topic has 14 replies, 5 voices, and was last updated Feb 25-3:19 am by psionl0.
-
Posts
-
psionl0
After a recent antiX update (using antiX updater from the menu) the shutdown option broke. If I click on “Logout” in the main menu, nothing happens.
This means that to shutdown the computer, I have to use the terminal command “sudo shutdown -h now”. Although this works and backs up the persistence, it doesn’t do an rsync so it is less than ideal.
Is there a way I can find out why the shutdown option is no longer working?
anticapitalista
I have seen this happen (very rare), but have no idea why.
/etc/sudoers has probably become corrupted.
Easiest/quickest way to fix is to boot the live iso and copy /etc/sudoers on the live iso to the installed one (via mount directory as root user)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
sybok
If the above suggested by @anticapitalista does not help, then please run ‘desktop-session-exit’ from terminal and report the results (inlcuding text printed to console).
Also, posting more information on your system (‘inxi -Fxz’) and the ‘/var/log/apt/history.log’ with the details of the update might help to identify the issue.Suggested reading: There was an issue in ‘sid’ (already fixed) recently related to Python update.
https://www.antixforum.com/forums/topic/logout-menu-broken-after-recent-upgrade/There doesn’t appear to be anything wrong with the sudoers file. It correctly allows me to use the sudo command. And I can’t find the inxi-Fxz file.
However, I have uploaded the /var/log/apt/history.log file. The interesting thing is that after each upgrade, I get the message: “Sub-process /usr/bin/dpkg returned an error code (1)”. However, this message has been generated on every update in the file and shutdown broke 2 or 3 upgrades ago (I was hoping that a subsequent upgrade would fix the problem).
Hmmm, this forum won’t let me upload the history.log file. So I will have to do it the long way:
EDIT copy/pasting didn’t work but it appears that is couldn’t upload the history.log file because it was owned by root. I have now created a copy and assigned ownership to demo. (Third time’s the charm).
@#$%!!!#@%!
Maybe if I change the file name to history.txt this site will allow me to upload it.
sybok
Run ‘sudo apt install –fix-broken’. You already did that (or something sufficiently close, ‘apt-get install -f’) in the past according to the log.
This might help to fix the error displayed during updates (appearing already in the 1st record of the log file).If that does not fix your shutdown problem, how about running ‘desktop-session-exit’ from the command-line and posting the output?
Also, posting ‘inxi -Fxz’ might help.PS: Yes, adding attachments can be challenging – renaming to TXT usually works.
anticapitalista
Please post the output of inxi -r as well as requested inxi -Fxz
Which version of antiX are you using?Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
The outputs from ‘sudo apt install –fix-broken’, ‘inxi -Fxz’ and ‘inxi -r’ are attached.
The output from ‘desktop-session-exit’ is shown below:
$ desktop-session-exit
demo@antix1:~
$ Traceback (most recent call last):
File “/usr/local/lib/desktop-session/desktop-session-exit.py”, line 3, in <module>
import gtk
ModuleNotFoundError: No module named ‘gtk’The last line from ‘sudo apt install –fix-broken’ says:
Processing triggers for menu (2.1.47+b1) …
File “/usr/local/bin/desktop-menu”, line 81
“”” % sys.argv[0]
^
SyntaxError: invalid syntax
demo@antix1:~I might add that I am booting antiX 19.3 from a thumb drive but I have persistence enabled and I have the two persistence files set up in a partition on the hard drive. I understand that as long as I regularly upgrade, I am running the latest version of antiX-19.
sybok
@desktop-session-exit:
Did you remove some programs installed by default?
If not, then your system got corrupted.
Another likely candidate is using backports in repositories.@broken syntax:
It is fix-broken preceded by double dash, it is displayed as a single longer dash, that’s probably what confused the ‘apt’
Please try ‘sudo apt install -f’ (single dash).Xunzi_23
Unsure of your hardware needs, Make a backup live stick. then.
Reinstall the complete package Realtek firmware, the problematic firmware-realtek:amd64 is contained in the
firmware package.
apt-get –reinstall install PackageNameHere
Do a full upgradeThen if needed try again to fix your logout problem. I recently encountered the same problem on testing
but as a quick and dirty fix reinstalled keeping home.- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
$ sudo apt-get –reinstall firmware-realtek
E: Command line option –reinstall is not understood in combination with the other options
demo@antix1:~
$According to the Package Manager, firmware-realtek is a Binary firmware for Realtek wired/wifi/BT adapters which seems unrelated to the shutdown issue.
Dave
Pretty much every entry in your apt history has an error with it which would make a compounding problem I am sure.
One of the upgrades with an error is from a while back, then several more attempts. The original one from the log is dated 2022-09-17 22:53:24 and involves the main python version 3.7 packages. I am not sure if your system still has the python2 packages or python3 or both now . But the updated apps for the logout menu (desktop-session-exit.py) and the menu generating script (desktop-menu) are showing errors indicating that they are still the python2/gtk2 versions which were updated in december 2019-2020 to python3/gtk3.I think buster still used the older version though, but then you would have somehow removed or updated the python gtk packages but I do not see this in the apt history log.
Similar issues from the past at that time
https://www.antixforum.com/forums/topic/dist-upgrade-warning/
https://www.antixforum.com/forums/topic/problem-with-power-off-suspend-log-off-etc/
https://www.antixforum.com/forums/topic/packages-does-not-appear-on-menu/
https://www.antixforum.com/forums/topic/whered-it-go/
https://www.antixforum.com/forums/topic/dolphin-oracle-antix-core-custom-install-videos/Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
@Dave, you solved my problem!
A couple of weeks ago, I created a soft link from python3 to python unaware that the shutdown menu runs a python script which assumes that python is linked to python2.
Restoring the original link fixed the problem.
Thanks very much everybody for your help.
- You must be logged in to reply to this topic.
