I'd like to request adding an upgrade to xserver-xorg-core 2:1.19.6-1 from Debian Buster/Testing (https://packages.debian.org/search?keyw ... -xorg-core) (or, alternately/additionally, a downgrade option to xserver-xorg-core 2:1.16.4-1+deb8u2) because of the problems with the Wacom 4-minute booting delay.

I've had this problem with Thinkpad x60t and x61t with both antiX- and MX- since 17 (16.x works fine) as per this thread: ( viewtopic.php?f=104&t=43631 )

I now see that there's a new antiX forum thread ( https://www.antixforum.com/forums/topic ... post-10864 ) and the links therefrom seems to say that the xserver-xorg-core very well may be the problem and either needs to go to a newer one (post 2:1.19.2-1+deb9u2, which is in the MX17.1 stable Stretch repo, present in my computers that have this time delay bug) or an older one (I know that 2:1.16.4-1+deb8u2 works from the MX-16.1 Jessie stable repo, present in my computers that do not have this time delay bug).

Hopefully being able to change this will finally fix this annoying boot time delay bug.

(FWIW, I did a sudo reboot and whisker menu reboots both worked with the reduced boot, then did a MX Updater dist-upgrade and rebooted now looking in Synaptice it also has xorg-server-source, xserver-xephyr, xserver-xephyr-dbgsym, xserver-xorg-core-dbgsym:i3, and xserver-xorg-dev available as 2:1.19.6-1~mobs, and and xserver-xorg-legacy was also installed.)

(FWIW, I did a sudo reboot and whisker menu reboots both worked with the reduced boot, then did a MX Updater dist-upgrade and rebooted now looking in Synaptice it also has xorg-server-source, xserver-xephyr, xserver-xephyr-dbgsym, xserver-xorg-core-dbgsym:i3, and xserver-xorg-dev available as 2:1.19.6-1~mobs, and and xserver-xorg-legacy was also installed.)

Awesome! Is there anything else I can do to test this?

What does "inxi -G" report now?

I actually build MX 17 packages first, and if we put them into the repo they'll be seen as upgrades (~mx17+1 is greater than ~mobs), but I was a bit leary of putting them in there, since some people will upgrade everything as it comes into the test repo. Are there any other antiX and MX users that were suffering the problem?

I really appreciate all of your hard work help with this, this is a huge fix for me I was having to use either MX16.1 or an Ubuntu XFCE distro for these computers now MX is almost completely dominant and bug free for all of my machines -- my eternal Thanks!