MX Linux Forum

Snapshot created on: 20240225_1318
System: Kernel: 5.10.0-28-amd64 [5.10.209-2] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-28-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
dm: LightDM 1 ...

Snapshot created on: 20240225_1318
System: Kernel: 5.10.0-28-amd64 [5.10.209-2] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-28-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
dm: LightDM ...

ISO was created with MX Snapshot.

I've created live usb with MX Live USB Maker (MX-21.3_x64 Wildflower with all latest updates). System loads quickly (Dell OptiPlex 3050), I can log in. For a moment, 1-2 seconds, I can see desktop then system log me out and I'm again at logging panel. When I'm in logging panel I can't switch off or ...

If yes, you can use "MX Tweak" to turn panel to defaults.


There must be a bug in "MX TWEAKS" (?). When I tried to change the position of the panel to horizontal, it disappeared along with the menu. Situation as described above. Fortunately, there is an option "Restore backup panel configuration ...

To fix the systemd-warning and the site-packages warning do this:
fix gufw:
sudo sed -i.orig -e '1!d;' -e 'apkexec gufw-pkexec $(whoami)' /usr/bin/gufw
and
fix gufw-pkexec
sudo sed -i.orig -e '1!d;' -e 'a/usr/bin/python3 /usr/share/gufw/gufw/gufw.py $1' /usr/bin/gufw-pkexec

This two ...

In fact , the non-working one is just the gui, probably ufw is ok (you can try in terminal as in that thread.)

Meanwhile, those errors are normal (ignorable) cause it's the same on live session (official MX iso) and it still gets launched with just gufw (without sudo) at the end.

https://i.ibb ...

This thread may be useful (it was solved with the patch (posts #11 - 13 )

https://forum.mxlinux.org/viewtopic.php?t=70979


Thanx. I've read this thread. In the end, the patch didn't seem to fix problems. It removed the original error but generated new problems.
It's weird by the way. After ...

Quick system info, please, thank you.


System: Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-18-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7
dm ...

Before the line: "/usr/bin/gufw: line 2: [: =: unary operator expected"

"System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: The device is turned off
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect ...