Bug 534857 - [GTK3] Warn user if GDK_CORE_DEVICE_EVENTS is not set
Summary: [GTK3] Warn user if GDK_CORE_DEVICE_EVENTS is not set
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-05-18 05:14 EDT by Simeon Andreev CLA
Modified: 2019-08-23 15:39 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simeon Andreev CLA 2018-05-18 05:14:30 EDT 
As seen in bug 534759, without GDK_CORE_DEVICE_EVENTS bug 435742 is seen again.

Since the problems observed in bug 435742 are severe and very difficult to understand or track down, it would be good if Eclipse users are warned in some way when GDK_CORE_DEVICE_EVENTS is not set.

E.g. an error log entry at start-up would help.
Comment 1 Alexander Kurtakov CLA 2018-05-22 14:34:08 EDT 
Do we have bugs for issues when it's not set? I'm afraid that too much effort goes into ensuring we set some non-default env variable and we will be in big problems once this env variable no longer has effect.
Comment 2 Alexander Kurtakov CLA 2018-05-22 14:36:15 EDT 
Furthermore GDK_CORE_DEVICE_EVENTS is X11 specific one https://developer.gnome.org/gtk3/stable/gtk-x11.html so are the issues visible on wayland ?
Comment 3 Simeon Andreev CLA 2018-05-23 02:21:40 EDT 
(In reply to Alexander Kurtakov from comment #1)
> Do we have bugs for issues when it's not set? I'm afraid that too much
> effort goes into ensuring we set some non-default env variable and we will
> be in big problems once this env variable no longer has effect.

The only bug for unresolved random input problems that we are aware of is bug 435742, and it was closed as fixed. The fix was to use this variable.

Without the variable (-nosplash enabled) we observe the problems on GTK 3.14; maybe they are fixed on GTK 3.22. But we don't know for sure since most of our user base is on GTK 3.14 at the moment.

From my perspective, as long as Eclipse relies on the variable to provide working editors (which really is the most basic of functionality), Eclipse should also be vocal if the variable is not set. We lost 2 weeks until we ran into bug 435742 by luck alone. This is not very nice.
Comment 4 Eric Williams CLA 2019-02-08 16:02:50 EST 
Simeon, is this still something you experience?
Comment 5 Simeon Andreev CLA 2019-02-11 02:22:36 EST 
Well, we have set the variable in the script which launches our product. So even if Eclipse fails to set it, we should be good.

If there are no resources / good way to add a warning if the variable is missing, I guess this can be closed as "won't do". Its a very nasty surprise though: if the variable is not set, the resulting behaviour is very difficult to understand. It definitely wouldn't hurt for SWT to be vocal if the variable is not set.
Comment 6 Eric Williams CLA 2019-08-23 15:39:46 EDT 
Do you still experience this on GTK3.22 or newer? I.e. please check in your product without the env variable and see what happens.