Bug on new Install

We just updated our table to version 2.10-016.084, Now when we pause mid cut the torch simply raises up and goes into reverse, backing along the cut path alll on its own. It does not pop up with the FWD and REV buttons that it used to. That does not work to well for us sometimes.....

Yes, here is the file. It might not be quite what you are looking for as we tried installing a little older version to try and get it going again, it acts almost the same with this version, now it stops when you hit pause, lifts up but nothing else. the FWD REV buttons come on momentarily then go away, it does not back up along cut path on its own but will not restart either, you have to hit stop and start all over. And once you have done that, the only way it will run a program is a program restart. If you run a program after fiddling with the pause it will only cut one pierce point, then raise the torch and sit until you hit stop, select the next point, run from line, etc etc. That was holes, I cant say whether or not it would do that on a nested drawing. 

Actually installed .deb file 2.10.0-pre0.6259.g34c07071bf_amd64.deb, it did not change QT tho, it is still on newest version. Update on action, it does not seem to have much of a schedule, back to reversing along cut path when I hit pause, it would be cute if it was younger but it used to be so well behaved The reason for update was a cut material bug we didnt like on the older version, Is there a way for me to find out which version I had been running?

Snowgoer, I helped Cutnweld with the upgrade. We are using Buildbot 2 on Debian Bookworm (MX Linux in this case). I upgraded the linuxcnc-uspace package using Synaptic Package Manager. The system has a lot of other OS and package updates that could be run but I opted not to do this -- last time we did, we had a huge nightmare getting networking up again due to Realtek NIC drivers compiled with DKMS. So I'm afraid to try kernel upgrades on a system that's working. 

Cutnweld's table has been running very happily for several years now but we wanted to address a bug related to material selection so hence the update to latest. That's when his problems started.

As he stated above, we downloaded deb 2.10.0-pre0.6259.g34c07071bf_amd64.deb and installed manually. The QtPlasmaC version displayed is the same as before, though. Let me know if you have any other technical questions and I'll try to answer them.

Thanks a ton, Greg. How soon will this hit Buildbot2, you figure?