Arch Linux

OK, since I can't get much of a response on the forum thread, is this broken with the default GTK3 theme?

I have not been able to make Mars work in Plasma5: I set the Default theme for GTK3 in the System Settings panel (in the kde-gtk-config KCM) but it still gave the reported problems. So I installed Gnome3 and in this desktop environment the GTK3 backend works well, although it feels a bit less responsive than GTK2 (both in Plasma5 and Gnome3).

Set it to Adwaita

I installed gnome-themes-standard and set the GTK3 theme to Adwaita in the GTK KCM, but the problem persists. I also get a lot of errors like this in the terminal:

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

which anyway were there also with other themes.

Furthering the GTK3 woes, I can't get eclipse to even start on the latest version. On a fully up-to date system, eclipse will fail to run immediately, however downgrading to my previous gtk3 version, gtk3-3.18.8-1, fixes the problem and eclipse starts normally.

The console output is below, and I've saved a core dump (although I don't know if it will help if the error is reported asynchronously)

** (eclipse:18043): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connecti\
on was broken.

#####The warning above occurs with GTK3-3.18 as well, but does not cause failure##############

(eclipse:18043): Gdk-ERROR **: The program 'eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 123 error_code 1 request_code 131 (XInputExtension) minor_code 45)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

As an alternative workaround you can start eclipse with `eclipse --launcher.GTK_version 2`

Well, I am a KDE user with Plasma-5.8.3 and kf-5.27. When I boot eclipse-jee 4.6.1, then open a project in workspace, eclipse just broke down. Usually, I use terminator to launch eclipse. So I can see a failure log in log file. Following attachment is the failure log. Currently the updated gtk3 version is 3.22.3. But When I downgrade it to 3.20.9(the version is only selected by date before I updated last time.) with makepkg command, the phenomenon didn't happen.

Setting the env var in Eclipse did not work for me, instead I had to edit eclipse.ini, adding the lines:

'--launcher.GTK_version
2'

This still happens in Oxygen. Have to switch to GTK 2.