Bugzilla – Full Text Bug Listing
| Summary: | [GTK2] GTK: Combobox hard to read on Ubuntu 17.10 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thomas Singer <eclipse> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P5 | CC: | akurtakov, daniel_megert, ericwill, Lars.Vogel, lshanmug, peter, sravankumarl | ||||
| Version: | 4.7 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 530841 | ||||||
| Attachments: |
|
||||||
|
Description
Thomas Singer
Created attachment 271239 [details]
SWT 4.7 on stock Ubuntu 17.10
Can you try the ControlExample? Do you see the same problem, does it happen only with READ_ONLY style? Can you pls check if this happens with any of the native GTK apps? How do native ubuntu combo boxes look like on Ubuntu 17.10? Btw, is this ubuntu with Gnome or another desktop manager (Unity?) Thomas, can you provide an example in the standard SDK for this? The screenshot seems to be using a custom preference configuration. I can reproduce the problem with Snippet26 when having set the envionment variable SWT_GTK3=0. So this happens with GTK2 only, not with GTK3? Thomas, please switch to GTK3, AFAIK the team is only enhancing GTK3. GTK3 support is still to unstable, hence we need to use GTK2. (In reply to Thomas Singer from comment #8) > GTK3 support is still to unstable, hence we need to use GTK2. In this case, I believe you have to provide patches for GTK2, IIRC the SWT GTK team does not work on GTK2 anymore, except that they do Gerrit reviews. (In reply to Thomas Singer from comment #8) > GTK3 support is still to unstable, hence we need to use GTK2. IMHO, this is a case of GTK2 port being unstable too - in its most often way, a custom theming engine breaking SWT. The approach of of custom drawing engine doing theming is broken beyond repair at idea level even and one of the reasons why GTK2 support is in "as long as it works" mode. See https://didrocks.fr/2017/11/09/welcome-to-the-ubuntu-bionic-age-a-new-ubuntu-default-theme-call-for-participation/ for a clear statement that Ubuntu 17.10 introduced new theme engine for GTK2 - "The GTK3 and GTK 2 theme. The first one is using css, the second is some C code.". While we can influence GTK3 theming in a sane way, GT2 is entirely different case for which sighnificant engineering effort would be required as this new drawing code is probably broken in multiple places just like most such "themes". Triaging Gtk2-only bugs. Please see Bug 530841 for details. If this bug is not gtk2-specific, please indicate. Thank you for your bug submission. Please note: GTK2 support for SWT is being dropped in Eclipse 4.10 / SimRel 2018-12 release. See the following mail for more info: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15783.html Marking the bug as duplicate of the GTK2 tracker as no work for GTK2 issues will happen. Please reopen if you still face the issue using GTK 3.x. *** This bug has been marked as a duplicate of bug 530841 *** |