Update: after googling a lot more about java apps and Wayland, it's becoming clear that my problem isn't specifically my touchscreen setup or bookworm/wayland. It's that java isn't really integrated into Wayland as of yet so running through XWayland is likely the source of the slowness/bugs/crashing. What this says is "Hey, rpi core devs: leave X11 as an option, please!"
When using Wayland window manager with a 22" touchscreen (ViewSonic TD2230) on an rpi5 (latest OS), the touches are quite slow to respond and sometimes result in screen flashing and strange behavior. This does not happen at all with X11 as the window manager.
It's particularly bad when using an application called JMRI, which is a java-based GUI app for model railroads. In many cases, the entire window manager just crashes. I know java is a real resource hog, but it works fine with X11, so...?
I had this same problem with the previous release (Bullseye) when trying Wayland with an rpi4B. I was hoping that moving to an rpi5 with Bookworm would solve it but it's still bad.
My current workaround is to always use X11. But when searching this forum for how to do that programmatically, I came across This post in which @tdewey said that X11 will be going away... so how do I debug/fix this?
When using Wayland window manager with a 22" touchscreen (ViewSonic TD2230) on an rpi5 (latest OS), the touches are quite slow to respond and sometimes result in screen flashing and strange behavior. This does not happen at all with X11 as the window manager.
It's particularly bad when using an application called JMRI, which is a java-based GUI app for model railroads. In many cases, the entire window manager just crashes. I know java is a real resource hog, but it works fine with X11, so...?
I had this same problem with the previous release (Bullseye) when trying Wayland with an rpi4B. I was hoping that moving to an rpi5 with Bookworm would solve it but it's still bad.
My current workaround is to always use X11. But when searching this forum for how to do that programmatically, I came across This post in which @tdewey said that X11 will be going away... so how do I debug/fix this?
Statistics: Posted by connelly38 — Mon Jun 23, 2025 8:16 pm — Replies 1 — Views 65