tiger1001 wrote: Sat Feb 01, 2020 2:19 pm
maybe you know where i have to ask the problem with the microphone with mx-linux on a acer-nitro ?
As mentioned do open a new Thread and describe your issue,including do post "Quick System Info" (found with the menu).
OK, with those information and the error message within your post above trying to uninstall:
"Entfernen von appimagelauncher (2.1.0-travis897~d1be7e7+bionic) ..."
we have a better picture of the situation.
So you downloaded from
https://github.com/TheAssassin/AppImage ... r/releases
this
deb-package appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb
And you installed it with MX-19 and now you are got stuck.
OK, first comment, packages marked for Ubuntu might simply not run in Debian based MX Linux.
Next, looking into the deb-packages, it appears the deb-packages is intentionally written in way,
that it will only install and run when booted with systemd boot option.
So now what -- how to get out of this mess?
If your intention is to get rid / uninstall, do this
Open as normal user a Terminal and run this:
Code: Select all
sudo rm /var/lib/dpkg/info/appimagelauncher.postrm
sudo apt purge appimagelauncher
OTHO, I've tested further this deb-package, and it appears to work well, despite it is intended for Ubuntu.
So, if you want to keep it. Do this.
Reboot and select with GRUB menu Advanced -> the systemd menuenty.
Now purge and re-install again, e.g from command line:
Code: Select all
sudo apt purge appimagelauncher
sudo apt install ./appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb
OK, now take a Appimage and see whether you can run it.
Some appimages, mainly those big fat Electron based apps like Rambox-0.7.3-linux-x86_64.AppImage
will not start, unless you do some further adjustments.
Most of those do have a chromium-sandbox issue, and chromium recently introduced stopping
running without a proper "secure" sandbox.
You might find some "smart" advises out there to run
with those "insecure" kernel options like "kernel.unprivileged_userns_clone=1"
or even start with option --no-sandbox
Don't do that! It's highly not recommended esp. for Apps going out into the internet.
The recommended way would be to enable sandbox-feature of the kernel itself.
You would do this with MX Linux by installing either of those 5.x kernels:
Liquorix 64 bit ... 64 bit latest from MX TEST repo
antiX 5.x 64 bit ... antiX 5.x 64 bit
Which you can do using MX Package Installer -> Populare Apps -> Kernels
MXPI-Kernels.png
After you installed either of those do reboot and select the systems-menu entry
for those kernel, which would currently look like this
MX 19 patito feo, with Linux 5.4.0-13.3-liquorix-amd64 (systemd)
or
MX 19 patito feo, with Linux 5.2.21-antix.2-amd64-smp (systemd)
mx-19-kernel-5x.png
And you AppimageLauncher will work
even with those Appimgages like Rambox-0.7.3-linux-x86_64.AppImage
which do require a secure sandbox.

EDIT: some adjustments re kernel versions
You do not have the required permissions to view the files attached to this post.