GNOME Bugzilla – Bug 694401
mouse click makes a selection but not click
Last modified: 2018-05-02 15:36:14 UTC
Its very frustrating to work with 2.8.4! The mouse click doesnt work anytime. Very often a mouse click on buttons does effect only in a selection and not click. For example in layer window the move up/down with mouse click on green arrow buttons doesnt work anytime, the button is selected but not clicked (click with spacebar works). Same with tool selection in tool window, sometimes ok, often not. This effects every window in gimp! Win 7 Prof. x64 SP1 german I have set the gui scaling to 130% in Windows 7.
What happens if you don't scale the GUI?
Created attachment 237181 [details] Gimp 2.8.4 - Tool window - mouse click makes only selection
Comment on attachment 237181 [details] Gimp 2.8.4 - Tool window - mouse click makes only selection Reset to 100% scale has no effect. See attached image, if MOVE is active and i click with left mouse button on TEXT (A) the active is not changed, the TEXT only gets the focus (pointed frame). If i click on gimp window title and then on TEXT it gets active. But click on other tool only effects in focus again.
There have bee reports that some screen capture software (iirc Camtasia), or applications like Teamviewer and Skype (because of their screen-sharing abilities) can cause this. Even if they aren't really in use at that time. Could it be anything like this?
SLOVED: I have running "Monitor Bright" from http://www.jockersoft.com/english/smallbutuseful.php in autostart to reduce bright. After closing this, gimp works fine. Thanks Michael!
Got this from the tool's author: > all this little program does is creating a window (.net form), adding > the WS_EX_TRANSPARENT extended window style, and changing the form opacity. So there's a window, covering the whole screen...
This might be something in GTK+ - even if there is a window over the whole screen, other applications - probably all non-gtk+ ones - presumably work.
I and other users at my facility have been encountering this problem intermittently in various GTK+ applications including GIMP, Inkscape, and a custom application that we publish in-house. Today I encountered the problem with Inkscape and finally managed to find this bug report through a long chain of links. Based on input from various bug reports, I decided to try closing some windows-manager apps. After I closed Divvy, Inkscape's mouse clicks started working again. I reopened Divvy and Inkscape was still working. However, as soon as I actually used Divvy to resize a window, the bad button behavior came back. I will discontinue use of Divvy, and report back if the problem returns. Note that I haven't had any problems with non-GTK+ apps when using Divvy. Also, I have had other users here report this problem for our custom app, and they are not using Divvy.
Ok.. major progress in figuring this out. I have one Windows 7 computer which suffers from this problem 100% of the time with our custom GTK+ app. It doesn't have Divvy, Monitor Bright, Teamviewer, or anything else like that. I closed all but essential processes and the problem did not correct itself. One of the only things remaining was dwm.exe -- "Desktop Window Manager". This is part of Windows 7. It's the compositing window manager for Windows. I tried killing the process but Windows immediately started it again, and I still was unable to properly click buttons in the application. To disable as much of DWM as possible, I opened Performance Options in Control Panel and selected "Adjust for best performance" in the Visual Effects tab. This disables all the window effects like Aero, smooth scrolling, etc. This setting immediately fixed mouse click behavior in the malfunctioning application. So it appears GTK+ does not play nicely with Windows' compositing window manager.
Note that Inkscape users are reporting similar issues: https://bugs.launchpad.net/inkscape/+bug/1131428 So, it seems to be a global issue with GTK+ indeed. I also have the same problems with both Inkscape and Gimp on my system (Windows 8, 64-bit).
So this is what we track in bug 780979 and bug 658842.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/417.