Hi Roky, for what it's worth, I hadn't run into the exact issue you were experiencing on any of my antiX or MX instances (at least not the ones I have been running recently), but I have recently run into two separate, and possibly unrelated issues.

One involved Debian Sid, and I got that one taken care of over the weekend. On Sid, my CPU usage was running out of control, and I suspected something afoul with the graphics driver interaction with the kernel. When I finally got a little bit of time to experiment with it, I went into console mode on the Sid system (stopping the X server while I did so). That made the system more responsive, and just prior to that, I was able (after several minutes of waiting) to execute a command that showed that indeed it was X that was burning up all of my available CPU time on this one Sid instance.

So I ran smxi, which I happened to have on the Sid-based system, and I first performed all of the package updates that were available. Then I used the smxi feature that calls its graphics subsystem, and I had it completely rebuild the X server, including the core Xorg package and the Intel graphics driver for it. When the rebuild completed, I went back into graphical user mode and the issues were gone, so there definitely was some kind of issue between the kernel version I was running and the graphics setup I had until I explicitly fixed it, then it worked.

The other issue I sometimes run into - and I haven't quite isolated where it's right and where it's wrong is when I want to shut down my system. In the past, when I'd perform the normal shutdown, a"shutdown" was interpreted as stopping all of the activities on the system, then physically powering down the computer. In contrast, a reboot would halt the processor then reboot the computer into whatever system image you selected at the boot menu. Previously, when I'd halt, both halt and poweroff would do essentially the same thing. More recently, however, halt and poweroff are NOT the same. Both will stop the system from actively processing, but halt by itself does stop processor activity without physically shutting off power, whereas poweroff performs both a halt processor and a poweroff activity.

Turns out that the shutdown command on many systems performs differently than in the past. A shutdown -h now, at least on one of my system instances will halt the processor, but that's it, in spite of what the docunentation suggests. A shutdown -hP now will halt and poweroff. That may account for the difference in behavior that I have experienced. It may also be some subtle changes in the manner in which the command works because of changes in the way that init works depending on which init system is being used.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://man7.org/linux/man-pages/man8/shutdown.8.html"
linktext was:"http://man7.org/linux/man-pages/man8/shutdown.8.html"
====================================
documents the shutdown command (but I've noticed that the actual behavior on systems with systemd is not always in sync with what this page suggests), and that's why I have recently been using shutdown -hP now to poweroff my system.