checkbox ticks not shown in Tomcat 8.5 Server view in STS-4.8.0 on Ubuntu Budgie 20.04

[robvarga]

I am not sure if this is a Spring Tool Suite issue, or an upstream WST issue, but I post it here for now.

I use Ubuntu Budgie 20.04 with default settings and STS 4.8.0.

I use the out-of-the-box launcher for STS and I did not change the JDK used to launch STS, so it runs with the one in the tarball.

I create a new Tomcat 8.5 server in the Servers view (assigned an already existing Tomcat 8.5 Runtime entry to it).

I get no error messages.

When I try to click on any of the enabled checkboxes in the "Server Options" checkbox group, nothing happens in the screen, I do not get a tick in the checkbox, but I do not get an error dialog either.
Apparently setting the checkbox gets recorded in the server configuration file when I save the server config, I can see the corresponding attributes set to true in the .server XML file.
When closing server config and then reopening it, the checkbox is still not ticked in.

So probably this is a UI issue, but I am not sure which project the issue belongs to.

I don't see any new error messages appearing in the workspace .log file either at clicking the checkbox or at saving the server config.

[kdvolder]

This sounds like a typical issue with SWT widgets. Happens quite often when version of GTK changes, or version of Eclipse changes. Eclipse SWT widgets are aparantly rather fragile and break quite a lot. I've seen many such bugs over the years and even reported some. The typical thing that happens is various kinds of widgets don't display properly or become a little 'glitchy'. So what you are describing seems to be that kind of thing exactly.

If you want to try filing a bug with Eclipse about this, I'd file it against SWT. This is a component of Eclipse 'Platform'.

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform

This is almost certainly not a bug in STS specifically. If you report the bug to Eclipse, it helps a lot if you have a method to reproduce the buggy behavior using only Eclipse components (i.e. to avoid discussions around whether this bug is really Eclipse or is somehow caused by STS).

If you file a bug, please share a link here.