Solved Linux MX Error message

Solved issue
$ ps -p 1 -o comm= init
Check your typing again. The word "init" is not part of the command.

Oops, I'm sorry. I think the word "init" is the response to the command! It should be!

Give the command as shown above, ending with comm= .... then hit Enter. It should respond with "init" (no quotes) on the next line below. Init is the SysV init system by default on MX-Linux.
 


Check your typing again. The word "init" is not part of the command.

Oops, I'm sorry. I think the word "init" is the response to the command! It should be!

Give the command as shown above, ending with comm= .... then hit Enter. It should respond with "init" (no quotes) on the next line below. Init is the SysV init system by default on MX-Linux.
It is working correctly but I have no Idea how it impacts with appimage files which wont open at all. I have now completely removed the appimage launcher through the Synaptic Package Manager. Will see what happens with the next upgrade they inform me of.
 
The problem is your AppImage Launcher most likely needs systemd to run and since you are init it doesn't for AppImages on init to run right click on the Appimage select properties, then put a check mark in the box "Allow this file to run as a program"

here is one Appimage of mine it is for Stellarium
1.png


2.png


now you can right click on the file again and you should see the word "Execute" or "Open" depending on your File Manager on the Xfce desktop it is Thunar so you should see "Execute"
click that - does the Appimage work
 
Thanks for all the support and encouragement without getting, never mind. I have been on some sites where people get really nasty. Good news for a change. I have managed to make a Ventoy Usb stick for multiple ISOs to change and try other distros and Windows by using only one drive instead of utilising a seperate drive for each ISO. Works like a charm!:)
 
The problem is your AppImage Launcher most likely needs systemd to run and since you are init it doesn't for AppImages on init to run right click on the Appimage select properties, then put a check mark in the box "Allow this file to run as a program"

here is one Appimage of mine it is for Stellarium
View attachment 21367

View attachment 21368

now you can right click on the file again and you should see the word "Execute" or "Open" depending on your File Manager on the Xfce desktop it is Thunar so you should see "Execute"
click that - does the Appimage work
I did that. I still have one appimage file which I did that with and makes no difference. I have deleted appimagelauncher entirely now as it seems I don't need it anyway.
 
Is this where you got your Appimage Launcher - https://github.com/TheAssassin/AppImageLauncher
If so - that has not been upgraded since 2020 and is getting dated

One more thing I thought of - open your synaptic package manager and search for the file binfmt-support
From the Appimage website is this
  • Use the binfmt_misc support in the Linux kernel to register AppImageLauncher as an "interpreter" for AppImage files
    • similar to how OpenJDK registers itself as an interpreter for executable JARs
    • example call: update-binfmts --package appimage --install appimage_type2 /usr/bin/AppImageLauncher --magic 'AI\x02' --offset 8
    • advantages:
      • it doesn't matter how the AppImage is called (Terminal, double click in file manager, call via desktop environments' launchers, ...)
    • disadvantages:
      • AppImages need to be made executable in order to use AppImageLauncher. If they are not, then binfmt_misc is not used
most likely this binfmt-support file is not in your kernel since it is a Debian based Kernel for MX
If that file is not there then the Appimage Launcher was not registered to open Appimages so it does not work

Go here to check compatibility for OS versions and scroll down a bit - https://github.com/TheAssassin/AppImageLauncher
 

Members online


Top