Comment 1 Alexander Kurtakov 2017-12-14 17:54:16 EST

What is the gtk version you have? Is it wayland or x11?

Comment 2 Daniel Murphy 2017-12-18 23:15:01 EST

Ah - setting the gtk version to 2 fixes this. I'm using x11 I think?

Comment 3 Eric Williams 2017-12-19 09:46:33 EST

(In reply to Daniel Murphy from comment #2)
> Ah - setting the gtk version to 2 fixes this. I'm using x11 I think?

GTK2 will run on X11, yes. However due to limited manpower GTK2 is not a priority in SWT any more, so we are encouraging people not to use it.

Please let us know what version of GTK3 this bug happens with.

Comment 4 Pierre-Charles David 2017-12-22 08:47:56 EST

Not sure it's the exact same bug, bug this reminds me a lot of bug #517671.

Comment 5 Daniel Murphy 2018-01-12 16:42:39 EST

it's set to org.eclipse.swt.internal.gtk.version=3.22.24

I just did a machine reflash and it's still occuring. It might have something to do with me using the i3 window manager.

I can provide more information if you need, just let me know.

Comment 6 Lutz Wrage 2018-01-21 13:24:17 EST

I see this with

Eclipse Oxygen.2
GTK 3.22.25
Kubuntu 17.10
Plasma 5.10.5
Qt 5.9.1
X11, not wayland

There is no flickering when running with SWT_GTK3=0, so it seems to be a GTK3 issue.

Comment 7 Daniel Murphy 2018-02-07 18:35:08 EST

I tried using a compositor like compton, and this fixes the issue for other stuff like gedit, but still happens in eclipse.

Comment 8 Lutz Wrage 2018-04-17 10:33:43 EDT

After updating to Oxygen.3 I don't see the flickering any longer.

Comment 9 Lutz Wrage 2018-04-20 14:11:43 EDT

I wrote my last comment too fast, the flickering is still there.

Comment 10 Eric Williams 2018-04-20 14:32:51 EDT

(In reply to Lutz Wrage from comment #9)
> I wrote my last comment too fast, the flickering is still there.

What about with Photon? 4.8 M6?

Comment 11 Yan Pas 2018-08-07 08:11:58 EDT

Mee too. I noticed it after installing 4.8 photon. I'm using KDE and ubuntu 18.04. After enabling `SWT_GTK3=0` i.e. using gtk2 backend do not face this issue.

Comment 12 Yan Pas 2018-08-07 08:14:32 EDT

Created attachment 275303 [details]
screenscast

Comment 13 Eric Williams 2018-08-07 10:31:29 EDT

Does this happen when using GNOME?

Comment 14 Yan Pas 2018-08-31 11:15:00 EDT

yes

Comment 15 Eric Williams 2018-08-31 11:31:00 EDT

Are you using any GTK modules like XIM? This might be a dupe of bug 517671.

Comment 16 Yan Pas 2018-08-31 14:40:05 EDT

I don't know what is it. I use stock kubuntu, every gtk app works fine.

Comment 17 Pierre-Charles David 2018-09-03 04:53:12 EDT

(In reply to Yan Pas from comment #16)
> I don't know what is it. I use stock kubuntu, every gtk app works fine.

You can check by opening a terminal and typing:

% echo $GTK_IM_MODULE

if the answer is "xim", this is probably the same as bug 517671. In that case there is a simple workaround of unsetting the variable before launching eclipse (or choosing a different input method like "ibus"):

% cd the/directory/where/eclipse/is/insalled
% unset GTK_IM_MODULE
% ./eclipse

I don't know how the setting can be configure globally and permanently in Kubuntu though.

Comment 18 Eric Williams 2018-12-14 13:40:27 EST

No response in awhile so I'm going to mark this as a dup of bug 517671. Please file a new bug if the issue occurs on GTK3.22/24 with SWT 4.10.

*** This bug has been marked as a duplicate of bug 517671 ***