Keeping Linuxcnc 2.9 current on Debian Bookworm

Tommy, the 99linuxcnc-uspace file is critical to the ongoing process because it sets the repository priorities.

The version of linuxcnc-uspace in the Bookworm repos is a few months old so it's not up to date.
You can't just put the buildbot repo's address in sources.list as the Debian repo will take priority so you won't get any linuxcnc updates as they are built.
By applying the priorities, you are telling Debian that the buildbot debs will always take priority over Debian's version.

In the past it was enough to just put the buildbot address in sources.list which worked perfectly when linuxcnc-uspace was not in the Debian Repos but now it is,  we need to work a bit harder to make sure we get updates from the correct source.

As for your Raspi problem, that's for you to solve as we specifically say to use XFCE as it's built on Xorg so it bypasses any Wayland issues. I think they are solved in linuxcnc now, but that area of Linux in general is built on shaky foundations. I believe it's a massive job to update linuxcnc as it's such an old application. So we play safe.

If you followed the first post here, you should have downloaded the attached file, renamed it by removing the .txt extension
Then you should have copied that file to it's correct location.

Yeh, I suspect the priority is undefined without the 99 rules Bound to bite one day!

The Wayland issue is described (and fixed for now) here: github.com/LinuxCNC/linuxcnc/issues/2264
It is nothing to do with QT as Gmocappy was affected.

​​​​​​Keep it up Tommy. and you'll soon have more PC's running Bookworm than me!

Knowing your love of large monitors, and now you are running 2.9, I can highly recommend you play with qtdragon. Once you try it, you will never want to run Axis again

Mods, this can be unstickied as it's incorporated into 
forum.linuxcnc.org/9-installing-linuxcnc...c-on-debian-bookworm