After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 598734 - Left mouse button click in java applications does not work
Left mouse button click in java applications does not work
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
2.18.x
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-10-16 21:47 UTC by Nikita
Modified: 2018-02-10 04:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nikita 2009-10-16 21:47:06 UTC
I experience problem with single clicks on certain buttons.
Some buttons when clicked looks like pressed, but when mouse button is released
the application button (picture) is also released and nothing happens, like the click action was somehow cancelled.

Downgrading to libgtk2.0-0_2.16.1-0ubuntu2 fixes problem for eclipse, but crashes firefox.

DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: libgtk2.0-0 2.18.2-1
SourcePackage: gtk+2.0
Uname: Linux 2.6.31-14-generic x86_64
Comment 1 Andrew Cowie 2009-10-17 05:26:22 UTC
I spend most of my day in Eclipse; there were some rendering problems presumably related to the client side windows patch landing in GTK 2.18 but as of this writing the GTK and Eclipse in Ubuntu's version K  are all behaving quite nicely; I'm not experiencing [and have not experienced] any mouse clicking problems. You *are* using your distro's Eclipse package, right?

As an aside, Eclipse is a nightmare because they have their own widget toolkit (SWT) that tries to be all things to all people and pretends it's native on various platforms — and since the people writing Eclipse user interface modules are working in SWT and not GTK itself, all kinds of horrible impedence mismatches crop up. There may or may not be anything the GTK developers can do to help in such cases.

If you were to write a small Java program that used SWT as its user interface toolkit that demonstrated the problem, then we might be able to get a clearer idea of what the problem you're experiencing is caused by.

AfC
Comment 2 Marcin Konarski 2009-10-17 10:07:43 UTC
Hello.

I am the original reporter for Ubuntu.

Answering your question regarding eclipse version.

I use eclipse package from eclipse.org (not supplied with the
distribution). I tried both galileo M7 and galileo SR1 with the same
effect.

I do not see however how it is relevant to libgtk+2.0-0 2.18 problem,
as the same behavior (canceled left-clicks) is experienced with flashplugin.

Unless of course you changed API and both eclipse.org and adobe.com
simply lags behind.

Best regards.
Comment 3 Frank Arnold 2009-10-25 10:07:39 UTC
Confirmed with the package from eclipse.org 
Ubuntu installs his own libswt-gtk so may be, this is a problem only with the packages from eclipse.org?
(have not tested this with the Eclipse packages supplied with Ubuntu).
Comment 4 Frank Arnold 2009-10-25 11:35:29 UTC
Ok... It's working with the libswt-gtk shipped and installed with the distributor. Tested with Eclipse 3.5.1 and libswt-gtk-3.5-java (3.5.1 Ubuntu Karmic) and libswt-gtk-3.5-jni (3.5.1 Ubuntu Karmic).
Comment 5 Cyril Jaquier 2009-10-29 08:18:57 UTC
I also had this issue with non-SWT java applications like Android SDK Tools. I also experience it with flash.

Starting Eclipse with GDK_NATIVE_WINDOWS=true seems to fix the problem.

This bug can be reproduce easily with Eclipse (from eclipse.org) or Vuze (Azureus) which is also based on SWT. AWT seems also to affected as I notice the same problem in the Android SDK Tools. The Adobe Flash plugin seems to suffer from it too.

Strange enough, this does not happen with every buttons.
Comment 6 Matthias Clasen 2018-02-10 04:39:47 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.