[48.2] XWayland apps not registering mouse press after changing workspace

Desktop
1

Hello everyone :wave:

Thanks for the recent 48.2 update :two_hearts:

I’m encountering a weird bug :lady_beetle: where if I change the workspace, then all XWayland apps stop registering mouse presses. Mouse actions do not work, but keyboard continues to work.

Steps to reproduce issue:

  1. Open an XWayland app, for example VSCode or Chrome with default settings
  2. Move to different workspace and back
  3. XWayland app does not register mouse presses, keyboard works.

So far I’ve found that opening the Gnome settings app any new app window within the same workspace as the XWayland app restores the mouse functionality. :face_holding_back_tears:

System:

pavin@suse-pc:~> gnome-shell --version
GNOME Shell 48.2
pavin@suse-pc:~> mutter --version
mutter 48.3
pavin@suse-pc:~> lsb_release -a
LSB Version:	n/a
Distributor ID:	openSUSE
Description:	openSUSE Tumbleweed-Slowroll
Release:	20250601
Codename:	n/a

Let me know if any additional info is required to troubleshoot, hopefully a less annoying workaround can be found to restore mouse function after changing workspace.:crossed_fingers:

2

Tried of Google Chrome.

Works fine for me on gnome-shell 48.2 / mutter 48.2.

Is the issue reproducible after disabling all shell extensions (if any) ?

1 Like
3

That’s a bug in mutter 48.3 which got fixed in 48.3.1.

2 Likes
4

That’s great news, thanks for all the awesome work! :tada: