E. A. (Ed) Graham, Jr.

In my opinion, the use of `tinylog` makes more sense for "constrained" devices -- thus makes sense as a default. If one has SLF4J dependencies, then just make sure `logback`...

This still occurs with 1.2.5 and still requires the workaround.

> Taking a look - the amTracing instance variable is a little unusual. That's kind of common practice to ensure that specific instructions are _not_ run when a method is...

> just so we all know, however, I'm pretty sure I'm on solid ground on this one. tinylog does not invoke the lazy parameter Supplier functions unless the logging is...

There is a "workaround" which does pretty much what the above suggests, but I think it would probably be better suited to the device factories themselves. ```java NativeDeviceFactoryInterface factory =...

Actually, since I tried out _two_ multiplexers, this notion is pretty terrible and should not be included as a "base option" -- the "workaround" above is better suited to those...

> I have built a radio for my kids, running on a Raspberry Pi Zero 2W. @MrTolchock I _just_ built a Pirate Audio using a Pi Zero and all of...

``` $ ./OrcaSlicer_Linux_V2.0.0.AppImage /tmp/.mount_OrcaSlkEBvfp/bin/orca-slicer: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory ``` This is the same issue as #5007

> Try installing package `libwebkit2gtk-4.0-37` on the host system and see if it helps: That did fix it for my case.

**NOTE** This is _not_ reproducible using "plain ol'" CP -- I put the same SSD1306 display on an RP2040 via the STEMMA port with the following packages: ``` Found device...