MX-23 beta 2 feedback thread

[shmu26]

After the errors with MXPI, the desktop freezes

Even after a couple reboots, the desktop no longer loads properly and is unusable.
Posting from a different distro...

[siamhie]

I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:

Code: Select all

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

Code: Select all

Init: SysVinit

Boot to systemd, not sys-v.

[shmu26]

I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:

Code: Select all

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

Code: Select all

Init: SysVinit

Boot to systemd, not sys-v.

And maybe I should uninstall this Appimage Launcher?

[shmu26]

I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:

Code: Select all

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

Code: Select all

Init: SysVinit

Boot to systemd, not sys-v.

The desktop is still broken after booting to systemd.
I think the issue is this one, which I reported once upon a time:
viewtopic.php?t=74421

[Adrian]

That has nothing to do with having the desktop broken.... what do you mean by broken, does it boot to CLI?

[shmu26]

That has nothing to do with having the desktop broken.... what do you mean by broken, does it boot to CLI?

Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen. So that makes it hard to do anything.
Right now I am chrooted into MX from another distro.

[Adrian]

Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.

Doesn't sound related to MX PackageInstaller at all.

Run the package installer with -s "sudo mx-packagesinstaller -s" (see --help)

[shmu26]

Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.

Doesn't sound related to MX PackageInstaller at all.

Run the package installer with -s "sudo mx-packagesinstaller -s" (see --help)

I ran a system restore to fix my desktop, and then ran your suggested command

Code: Select all

sudo mx-packageinstaller -s

MXPI works correctly, that way.

[4ps4all]

This is a guide for MXlinux to install protonvpn
https://protonvpn.com/support/official- ... -mx-linux/

The guide to install protonvpn work well with MX21,instead with MX23 the part of "Linux system tray icon" of proton-vpn-gui doesn't work.( the guide ton install for debian seems the same ).

In the guide say to install this package "gir1.2-appindicator3-0.1" but this package does not exist.

It would be great to add "protonvpn" in mx-packageinstaller.

[shmu26]

I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:

Code: Select all

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

Code: Select all

Init: SysVinit

Boot to systemd, not sys-v.

The desktop is still broken after booting to systemd.
I think the issue is this one, which I reported once upon a time:
viewtopic.php?t=74421

I succeeded in fixing MXPI using the same suggestion as @Adrian made in the other thread
viewtopic.php?p=716854#p716854
where you said

Sorry, I think the config file is read from /root/.config/MX-Linux/mx-packageinstaller.conf (it might depend how you launch the program), so add the "skiponlinecheck=true" there too.