Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 12:24 pm
Even after a couple reboots, the desktop no longer loads properly and is unusable.
Posting from a different distro...
Posting from a different distro...
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Even after a couple reboots, the desktop no longer loads properly and is unusable.
shmu26 wrote: Tue Jul 11, 2023 12:03 pm 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 downCode: Select all
Init: SysVinitAnd maybe I should uninstall this Appimage Launcher?siamhie wrote: Tue Jul 11, 2023 1:23 pmshmu26 wrote: Tue Jul 11, 2023 12:03 pm 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 downBoot to systemd, not sys-v.Code: Select all
Init: SysVinit
The desktop is still broken after booting to systemd.siamhie wrote: Tue Jul 11, 2023 1:23 pmshmu26 wrote: Tue Jul 11, 2023 12:03 pm 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 downBoot to systemd, not sys-v.Code: Select all
Init: SysVinit
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.Adrian wrote: Tue Jul 11, 2023 1:55 pm That has nothing to do with having the desktop broken.... what do you mean by broken, does it boot to CLI?
Doesn't sound related to MX PackageInstaller at all.Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.
I ran a system restore to fix my desktop, and then ran your suggested commandAdrian wrote: Tue Jul 11, 2023 2:15 pmDoesn't sound related to MX PackageInstaller at all.Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.
Run the package installer with -s "sudo mx-packagesinstaller -s" (see --help)
Code: Select all
sudo mx-packageinstaller -sI succeeded in fixing MXPI using the same suggestion as @Adrian made in the other threadshmu26 wrote: Tue Jul 11, 2023 1:47 pmThe desktop is still broken after booting to systemd.siamhie wrote: Tue Jul 11, 2023 1:23 pmshmu26 wrote: Tue Jul 11, 2023 12:03 pm 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 downBoot to systemd, not sys-v.Code: Select all
Init: SysVinit
I think the issue is this one, which I reported once upon a time:
viewtopic.php?t=74421
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.