Bug 1397724

Summary: mouse coordinates not updating when hovering over gtk3 window
Product: [Fedora] Fedora Reporter: robert
Component: waylandAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 25CC: ajax
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:25:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Reproduction in Action none

Description robert 2016-11-23 09:26:59 UTC
Created attachment 1223081 [details]
Reproduction in Action

Description of problem: I noticed when debugging guake, a gtk2 program, that the mouse coordinates do no update when hovering over gtk3 windows. This causes a bug where the terminal does not open on the expected monitor. In the attached video hovering Chrome and Atom both update the mouse position; however, hovering over the desktop or gnome-terminal does not.


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. sudo dnf install guake
2. start guake
3. hit F12 to show/hide
4. when hovering over a monitor with a gtk2 app, it will appear on the right display. When hovering over the desktop or a gtk3 app, it will use the last display you hovered over a gtk2 app.

Actual results: Debugging with the logger revealed this line is the issue:

x, y, _ = screen.get_root_window().get_pointer()

It does not update mouse coordinates until you actually hover over a gtk2 app.

Expected results: The coordinates should have updated to the x, y of the other monitor


Additional info: See video

Comment 1 robert 2016-11-23 09:31:17 UTC
Clarification: This works as expected in X

Comment 2 Fedora End Of Life 2017-11-16 19:55:02 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:25:38 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.