[Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace

I just notice that this happens with WebStorm + PhpStorm windows randomly!
I have no idea this is a gnome-shell bug or IDE itself ...

I can't seem to reproduce it with standard GNOME apps. Can you provide a test case using the default apps installed with Ubuntu?

@vanvugt
I'm also have no problem with gnome apps,
As i said, i have this with JetBrains IDE windows :(

Status changed to 'Confirmed' because the bug affects multiple users.

The root cause here may also relate to bug 1944065.

Fix proposed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2402

This sounds like LP: #1971693 so I'm marking this a duplicate.

We will be pushing a proposed fix for that bug soon.

Please let us know if that update doesn't fix this issue for you.

This bug is where all the action was and what we've been linking to for weeks so this should remain the primary bug.

the sru upload uses 1971693 though..

This bug was fixed in the package mutter - 42.1-1ubuntu1

---------------
mutter (42.1-1ubuntu1) kinetic; urgency=medium

  [ Jeremy Bicha ]
  * Merge from Debian unstable. Remaining changes:
    - Add triple-buffering patch
    - Add x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr
    - Add ubuntu/wayland-data-device-Allow-any-drag-timestamp....patch
      + Allow any drag timestamp as drag start serial
    - Add backends-native-kms-crtc-Don-t-compare-gamma-values-on-un.patch
      + Avoid memory errors when comparing gamma values
    - Add monitor-manager-Ensure-monitors-settings-after-backend-ha.patch
      + Ensure privacy screen settings are applied on startup
    - Add patches from GNOME !2364
      + Fix X11 selection related crash when Xwayland died
    - debian/libmutter-10-0.symbols: Add symbols for triple buffering patch
  * Refresh triple buffering patch with latest version

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Adapt expected messages to new domains

mutter (42.1-1) unstable; urgency=medium

  * New upstream release
    (LP: #1972726, #1967274, #1965557, #1969574, #1948410, #1967219, #1971693)
  * Drop patches applied in new release
  * debian/libmutter-10-0.symbols: Add new symbol
  * debian/libmutter-10-0.symbols: Drop a symbol that was only in experimental
  * Add Breaks against old gtk3 & gtk4 versions.
    See Ubuntu bug 1972721
  * Release to unstable

mutter (42.0-5) experimental; urgency=medium

  * Team upload
  * d/patches: Update to upstream commit 42.0-74-g6c8e8fbba
    - Bug fixes targeted for 42.1
    - d/p/clutter-stage-Repick-when-pointer-actor-goes-unmapped.patch:
      Replace with the version that was applied upstream
    - d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
      Mark as applied upstream

mutter (42.0-4) unstable; urgency=medium

  * Team upload
  * d/patches: Update to upstream commit 42.0-55-gbe9deeba0
    - Update translations
    - Update upstream status of cherry-picked patches
    - Add various bug fixes including LP: #1959888, LP: #1964037
  * d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
    Add patch proposed upstream to fix grabs vs. system-modal prompts.
    This is particularly annoying when using pkexec, or when using gcr as
    a passphrase prompt for PGP, ssh and/or sudo.
    (Closes: #1008998, LP: #1964442)

 -- Jeremy Bicha <email address hidden> Fri, 13 May 2022 09:14:41 -0400

Even though https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971693 seems to be resolved with the latest update (with mutter 42.1), the use case described in this ticket still doesn't work as expected every time. Here are the steps to reproduce the issue for the attached minimal Java application:

1. sudo apt install default-jre
2. Download attached file TwoFrames.java
3. From a terminal run the app
java Downloads/TwoFrames.java
4. Press Super (Window) key on the keyboard and click with mouse on frame 1. Then press Super, and click on frame 2. Repeat several times.

At some point, the focus switch will fail, with previously selected frame staying in focus.

I'm attaching the source code for a sample X client application, for which the problem can be reproduced reliably. The application uses 'globally active' input focus model, just like Java (AWT/Swing) applications, but also waits for 10 milliseconds before reacting to WM_TAKE_FOCUS message. If such an artificial delay isn't performed (just comment out 'usleep' call in the source code), the problem can be reproduced as well, but only with a certain probability.

The sample app can be compiled and launched using the following command:
gcc twoFrames.c -lX11; ./a.out

I have also noticed the behavior mentioned in https://bugs.launchpad.net/gnome-shell/+bug/1969574/comments/12.

It fails approx 50% of the time for me, which is an improvement from before, but still not ideal.

Note that Alt-Tab does not seem to be affected, just selecting via the workspace.

The upstream bug is still closed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5395

If you find a problem with the fix then please mention it UPSTREAM. If not in the above link then in a new bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/new

Looks like this could be handled better by https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2489 but it's still in the works.

Let's assume this is not fixed still and that https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5395 was a different problem.

Anyone still experiencing this bug, please report it upstream and then tell us the new issue ID.

As per the above request, I've created a new upstream ticket for this problem - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5834