Why is Plasmac and QTplasmac pausing at the end of a cut for no reason?

Thanks, Greg. Some very useful links there.
Like you, I usually do a RIP install but this time, I wanted to use the buildbot.
Your screen dump shows the words PREEMPT_RT and this format has changed and it is not searchable.
You need to know to search for linux-image
In Tommy's instructions forum.linuxcnc.org/9-installing-linuxcnc...installation?start=0
he usesThis  command uses Python 2.7 and its been deprecated and I could not get it to install so I had to set the repositories up in Synaptic. This is not documented on the buildbot anymore. I thought it used to be. Its been a long time since I used synaptic!
And due to changes in the linux security model, it refuses to allow us to use the use of our key server from the buildbot so this does not work
Fortunately, Phill came to the rescue earlier in this thread and this works
So all in all, its not that straight forward

Finally, I was really surprised to see that the QT installation scripts spent ages installing Python 2.7 modules. I thought that was being removed from Master branch so does that mean that script needs to be reworked?
 

tommylight wrote:

Why are you discussing MX Linux here ???
It would be more usefull making a new topic about it.
I will try to add the howto to my "to do in this lifetime" list!

Well, it was here where it was first mentioned. I did not expect it was going to be so hard. I thought all I needed was the package to install in synaptic!

I think we will move it to a new thread once its nutted out.  

oops now I see the buildbot still discusses synaptic.

The Qt install script uses the default version of python that the distro has set. Master branch is still using 2.7 as well. If you want python3 then you have to set it up. You would need to set the default version to 3 using something like update-alternatives:
linuxconfig.org/how-to-change-from-defau...sion-on-debian-linux

You then need to configure master branch to build using python3:
./configure --with-realtime=uspace --with-python=python3 --with-boost-python=boost_python3-py37

Or you could use master-gtk3 branch which doesn't need the extra commands and is reasonably up to date as it had master branch merged into it recently.
 

Thanks, I was more interested in installing from the debs without building Linuxcnc.
I just assumed becasue the scripts took so long to execute that it may have been installing Python 2.7.

I've got both Python 3 and Python 2 installed now.

So what should a new user do?  Can he use Python 3 now?
What will happen on an upgrade for this new user once Python3 gets into master?

AFAIK all debs are still python2.7.

You can build and run python3, I "think" Greg does now, I do the occasional python3 build just for testing but I won't fully move to python2 until the official change over.