Ubuntu 19.04 with all updates installed, using Ubuntu on Wayland desktop session.
I believe I reproduced the issue: - click sidebar to launch Firefox (Firefox gets keyboard focus without further actions; ok) - click sidebar to launch Files (keyboard focus remains on Firefox which is below Files; fail) Using Terminal instead of Files fails the same way. Firefox is an X11 application, the rest are Wayland applications, so to me it seems the issue is specifically about not moving focus from an old X11 window to a new Wayland window. I cannot get it to fail otherwise, and the failure seems to be reliable for me. After upgrading to: libmutter-4-0: 3.32.1-2ubuntu1~19.04.1 I can no longer reproduce the issue I described above. I would propose to change the tag from verification-needed-disco to verification-done-disco. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826176 Title: Applications do not receive focus in Wayland sessions Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Bug description: [ Impact ] On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. [ QA ] No further verification as this is a fix coming with a GNOME micro release update that is covered by this exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ---- ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
