Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse events occassionally sent to window behind popup window, instead of popup window itself #7702

Closed
greenrd opened this issue Aug 19, 2022 · 3 comments
Assignees
Labels
C: gui-virtualization fixed-by-wayland Bugs that would not appear if Qubes OS used Wayland instead of X11 P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@greenrd
Copy link

greenrd commented Aug 19, 2022

Qubes OS release

4.1.1

Brief summary

Occasionally, I'll get a popup, e.g. from Google Calendar in Chromium, that does not respond to clicks. However, it is clear that Qubes is sending the click events to the window underneath the popup window, because things happen that would have happened if I had clicked at that place on the screen and the popup window had not been present.

Steps to reproduce

I don't know how to reproduce this, it only happens occasionally.

Expected behavior

When I click on a button in the popup window, it should behave as normal

Actual behavior

Popup window stays there, and if there is something at the same place in the window behind it, the application will do what it would have done if I had been able to click there.

@greenrd greenrd added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug labels Aug 19, 2022
@DemiMarie DemiMarie added this to the Release 4.1 updates milestone Aug 19, 2022
@DemiMarie DemiMarie self-assigned this Aug 19, 2022
@unman
Copy link
Member

unman commented Aug 19, 2022 via email

@DemiMarie
Copy link

Yes, which is itself a duplicate of #3267.

This is a fundamentally hard problem because of the use of a nested X server. The correct solution is to send events to windows directly, instead of relying on Xorg’s event routing. This is probably not feasable for X11. However, this is simply a non-issue under Wayland, since the Wayland agent is the display server there.

@DemiMarie DemiMarie closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2022
@DemiMarie DemiMarie added R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. fixed-by-wayland Bugs that would not appear if Qubes OS used Wayland instead of X11 labels Aug 19, 2022
@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. If anyone believes this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong removed this from the Release 4.1 updates milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: gui-virtualization fixed-by-wayland Bugs that would not appear if Qubes OS used Wayland instead of X11 P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Development

No branches or pull requests

4 participants