FWIW, I also am running Ubuntu 22.04 with an nVidia adapter (RTX2060 or something like that). It works fine for me but this is laptop and I don't want the nvidia power pig running all of the time. The nVidia control panel allows for "on-demand" nvidia which means it usually uses the built-in graphics from the CPU. If I use that then Arduino IDE will bunch up the output from the compile and I can't read hardly anything. All text works fine when using the nVidia card all of the time. It has been like this for many Ubuntu versions. I'm not sure if I've messed something up or what. I've learned to just live with it. Long story, short, nVidia support on LINUX in general just sucks.
Back on topic, I've got Arduino 2.0.3 and this latest beta 158-3 installed and I tested it compiling and running a Teensy MicroMod program and it seems to be working fine. I don't see any regressions so far. I will note (I believe again) that it's super annoying that by default it warns me of how the behavior of things changed around GCC7. This fills up page after page of compile output for me.
Just to refresh the topic of what I don't like, here's one such warning:
Code:
/home/collin/.arduino15/packages/teensy/tools/teensy-compile/11.3.1-beta2/arm/arm-none-eabi/include/c++/11.3.1/bits/stl_vector.h: In member function 'virtual void RMSMotorController::setup()':
/home/collin/.arduino15/packages/teensy/tools/teensy-compile/11.3.1-beta2/arm/arm-none-eabi/include/c++/11.3.1/bits/stl_vector.h:1198:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<ConfigEntry*, std::vector<ConfigEntry> >' changed in GCC 7.1
1198 | _M_realloc_insert(end(), __x);
| ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
As fascinating as I find this warning, I'd rather not see it 100 times every time I compile. I'm sure there's a way to turn off this warning but I'm not really sure of the best way to set custom flags during a compile with the Arduino IDE.