Solved Linux MX Error message

Solved issue
E

Erik Groothuijzen

Active Member
Joined
Mar 3, 2024
Messages
136
Reaction score
57
Credits
1,225
When I update my system, I get the following message in mt terminal :
"System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down"
Any idea how I can correct this? I am not Terminal command savvy. This is the full terminal screen:
Preparing to unpack .../lo-main-helper_24.07.04mx23_all.deb ...
Unpacking lo-main-helper (24.07.04mx23) over (24.07.03mx23) ...
Preparing to unpack .../mx-packageinstaller-pkglist_24.07.04mx23_all.deb ...
Unpacking mx-packageinstaller-pkglist (24.07.04mx23) over (24.07.03mx23) ...
Preparing to unpack .../mx-snapshot_24.7.02_amd64.deb ...
Unpacking mx-snapshot (24.7.02) over (24.6) ...
Setting up calibre-helper (24.07.04mx23) ...
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
dpkg: error processing package appimagelauncher (--configure):
installed appimagelauncher package post-installation script subprocess returned error exit status 1
Setting up mx-packageinstaller-pkglist (24.07.04mx23) ...
Setting up lo-main-helper (24.07.04mx23) ...
Setting up mx-snapshot (24.7.02) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
appimagelauncher
E: Sub-process /usr/bin/dpkg returned an error code (1)

full upgrade complete (or was canceled)

this terminal window can now be closed

Press any key to close...
 


What it is say is that it can not install or upgrade appimagelauncher usually it means either it can not satisfy a dependency Or some other problem with the package. Every thing else should have been updated correctly though.
 
kc1di said:
What it is say is that it can not install or upgrade appimagelauncher usually it means either it can not satisfy a dependency Or some other problem with the package. Every thing else should have been updated correctly though.
Click to expand...
My update box still reflect that there are updates available though. Normally it also give a message that all updates have been successful, which it does not do now. Should I remove appimage launcher and try again?
 
if you don't really need it I would remove it and try again.
 
Erik Groothuijzen said:
I installed it to assist with appimage files, but it actually did not help much, so I'll just uninstall it.
Click to expand...
Ya, I just set the permissions and run the appimages I use directly and make an entry in my menu for them.
 
Did it work for you after uninstalling it?
 
For future reference, you can enable systemd on MX-Linux, if you wish.
 
If you are using MX Linux inside Windows using WSL, you will have SysV instead of systemd and your system will complain when you run the systemctl command (intended for Linux systems with systemd init system).
You may use this command to know the process name associated with PID 1 (the first process that runs on your system):

ps -p 1 -o comm=
Click to expand...
It should show init or sysv (or something like that) in the output. If you see init, your system is not using systemd and you should use the init commands

Here is mine below
1.png

My Expirion Linux is based on Devuan so it has no systemd and uses SysVinit

Basic Sysvinit commands:


sudo service service_name start
sudo service service_name stop
sudo service service_name restart
sudo service service_name status
sudo chkconfig service_name on
sudo chkconfig service_name off
Click to expand...
 
Last edited:
I don't have the experience with MX Linux but it uses either systemd or sysv init. So maybe for some reason you are upgrading sysv system with systemd?
This should be easy to fix.
 
Aristarchus said:
I don't have the experience with MX Linux but it uses either systemd or sysv init. So maybe for some reason you are upgrading sysv system with systemd?
This should be easy to fix.
Click to expand...
With MX you can choose at boot time which system , systemd or SysV you want to boot with. And it can be changed in the mx-control panel also.
 
atanere said:
For future reference, you can enable systemd on MX-Linux, if you wish.
Click to expand...
enable systemd brings me
Erik@LenovoW530:~
$ enable systemd
bash: enable: systemd: not a shell builtin
Erik@LenovoW530:~

Love Linux. It tells me system d is not enabled, then when you try to enable it, it tells me not a shell built in. Am I the crazy one. I try an appimage file, everybody tells me, click on it and it will open. Nothing happens. Rebooted int Mint on my USB, and voila, the appimage file opens. How now? Anything else I can try? I really want Linux to work as going back to Windows is not an option. I had to give up with my Garmin though because I could not get it to work with wine or any other way. Made a dual boot Windows 10 disk and can now update my Garmin at least.
 
GatorsFan said:
If you are using MX Linux inside Windows using WSL, you will have SysV instead of systemd and your system will complain when you run the systemctl command (intended for Linux systems with systemd init system).
You may use this command to know the process name associated with PID 1 (the first process that runs on your system):


It should show init or sysv (or something like that) in the output. If you see init, your system is not using systemd and you should use the init commands

Here is mine below
View attachment 21335
My Expirion Linux is based on Devuan so it has no systemd and uses SysVinit

Basic Sysvinit commands:
Click to expand...
This is what I got:
Erik@LenovoW530:~
$ ps -p l -o comm= init
error: process ID list syntax error

Usage:
ps [options]

Try 'ps --help <simple|list|output|threads|misc|all>'
or 'ps --help <s|l|o|t|m|a>'
for additional help text.

For more details see ps(1).
I don't run Linux MS inside Windows but as a new install on it's own.
 
Erik Groothuijzen said:
enable systemd brings me
Click to expand...
The "enable systemd" I gave you was not a command.... it was a link to the MX-Linux website where they tell you how to enable systemd. Systemd is not the default on MX-Linux, you have to enable it following their directions. It's a choice, you don't have to enable it. The AppImage Launcher was giving you an error because it needed to run under systemd, but you have now abandoned that program, so you no longer need systemd.


Erik Groothuijzen said:
This is what I got:
Erik@LenovoW530:~
$ ps -p l -o comm= init
error: process ID list syntax error
Click to expand...
You should learn to copy and paste commands to avoid typing errors. You can use CTRL-SHIFT-V to paste into the terminal after copying. The correct command given by @GatorsFan is:
Code: 
ps -p 1 -o comm=
The mistake you typed was replacing the " 1 " (one) with a " l " (lower case L or a capital I, I'm not sure).

Hang in there, you'll get the hang of it. Good luck!
 
Erik Groothuijzen said:
OK, I am still getting used to working with Linux, and all the different distros and different advice does not make it easy. It's like you hit a wall if the system cannot handle something somehow. :mad:
Click to expand...
Don't worry, no beginning is easy, I still recall my Linux hurdles, everything was alien to me but if you persist you'll understand it like your pocket.

Just follow @atanere 's post #17
 
atanere said:
The "enable systemd" I gave you was not a command.... it was a link to the MX-Linux website where they tell you how to enable systemd. Systemd is not the default on MX-Linux, you have to enable it following their directions. It's a choice, you don't have to enable it. The AppImage Launcher was giving you an error because it needed to run under systemd, but you have now abandoned that program, so you no longer need systemd.



You should learn to copy and paste commands to avoid typing errors. You can use CTRL-SHIFT-V to paste into the terminal after copying. The correct command given by @GatorsFan is:
Code: 
ps -p 1 -o comm=
The mistake you typed was replacing the " 1 " (one) with a " l " (lower case L or a capital I, I'm not sure).

Hang in there, you'll get the hang of it. Good luck!
Click to expand...
Erik@LenovoW530:~
$ ps -p 1 -o comm= init
error: unsupported option (BSD syntax)

Usage:
ps [options]

Try 'ps --help <simple|list|output|threads|misc|all>'
or 'ps --help <s|l|o|t|m|a>'
for additional help text.

For more details see ps(1).
I used small l. Changed the l to 1. No go. I do copy and paste if it is there to copy. Couldn't do it from your picture. Will check "help".
 
You must log in or register to reply here.

Members online

Total: 378 (members: 3, guests: 375)

Latest posts

Top