When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them

Bug #2011251 reported by Jonathan Kamens
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After the most recent Lunar updates (i.e., with the newest GNOME) my gnome-shell got into a state where clicking on the title bar of a window wouldn't raise the window (or do anything else), while clicking inside the window raised it as expected. The problem went away after I rebooted. I think this may have occurred after some other aberrant behavior, specifically the shell hanging for about 30 seconds (I will file a separate bug about that), so it's possible that things were in some sort of broken state because of that and this bug isn't actually specifically about the title bar, but I thought I should file a bug report about it just in case it's something other people start seeing so we can see how frequently it's happening.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 10 16:16:22 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1302 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
affects: gnome-shell (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: New → Confirmed
Changed in gnome-shell:
status: Unknown → New
Changed in gnome-shell:
status: New → Fix Released
Changed in mutter (Ubuntu):
status: Confirmed → Fix Committed
tags: added: fixed-in-mutter-44.1 fixed-upstream
affects: gnome-shell → mutter
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
mutter (44.1-1ubuntu1) mantic; urgency=medium

  * Merge with Debian (LP: #2020225, LP: #2012100, LP: #2012717,
    LP: #2013216, LP: #2019225, LP: #2006044, LP: #2015861, LP: #1999578,
    LP: #2011251, LP: #2016308)
  * Remaining changes:
    - Add x11-Add-support-for-fractional-scaling-using-Randr.patch
    - Add window-Add-ability-to-override-the-edge-constraints.patch
      + Make possible for extensions (such as Tiling Assistant) to override
        window constraints. (LP: #2007710, #2011611)

mutter (44.1-1) experimental; urgency=medium

  [ Jeremy Bícha ]
  * New upstream release
  * Drop bash patch applied in new release
  * debian/libmutter-12-0.symbols: Add new symbols

  [ Daniel van Vugt ]
  * Update triple buffering patch for Mutter 44.1

  [ Marco Trevisan (Treviño) ]
  * Fix issue with Firefox opening black window in wayland sessions
    - Add d/p/display-Set-compositor-selection-earlier-on-XWayland.patch
      (LP: #1987976)

 -- Jeremy Bícha <email address hidden> Fri, 19 May 2023 16:24:49 -0400

Changed in mutter (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jonathan Kamens (jik) wrote :

This issue is NOT fixed in 44.1-1ubuntu1. I don't know whether that's because the fix from upstream didn't get included in that package somehow, or whether the upstream bug is not actually the root cause of the issue reported here. If I launch an emacs window with the new version of mutter in mantic, clicking on the title bar still doesn't raise the window, whereas clicking on the title bar of a terminal window DOES raise it. I.e., the problem I initially reported above still exists.

Changed in mutter (Ubuntu):
status: Fix Released → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

While this was the first bug logged, we failed to notice when duplicate bug 2013216 was reported and most of the discussion has now occurred there. So we should use bug 2013216 as the primary bug. Feel free to reopen that too if you're confident that it's not fixed in Ubuntu 23.10.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It looks like this bug is specific to the setting you have:

  gsettings set org.gnome.desktop.wm.preferences focus-mode 'mouse'

So please try the default instead:

  gsettings set org.gnome.desktop.wm.preferences focus-mode 'click'

summary: - gnome-shell gets into state where clicking on window title bars doesn't
- raise them
+ When focus-mode=mouse is set, gnome-shell gets into state where clicking
+ on window title bars doesn't raise them
no longer affects: mutter
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

https://gitlab.gnome.org/GNOME/mutter/-/issues/2817 is kind of similar but is about:

  gsettings set org.gnome.desktop.wm.preferences focus-mode 'sloppy'

So basically it looks like the fix in 44.1 only works for the default:

  gsettings set org.gnome.desktop.wm.preferences focus-mode 'click'

Revision history for this message
Jonathan Kamens (jik) wrote :

OK, yes, it turns out that mouse focus vs. click focus is indeed the differentiator for me, but it's a bit more complicated than that. If I have focus set to mouse when I log in, then this bug manifests even if I change focus to click. If I have focus set to click when I log in, then this bug does not occur even if I change focus to mouse. So the deciding factor seems to be the focus setting that's active at the time the user logs in.

Changed in mutter (Ubuntu):
status: Incomplete → New
status: New → Confirmed
Revision history for this message
mike@papersolve.com (mike-papersolve) wrote :

It looks like the gnome bug does acknowledge it only works for 'click' mode (I use sloppy) so presumably when that gets fixed (and it looks like they're still thinking about it!) and released then both mine and yours will too.

tags: removed: fixed-in-mutter-44.1 fixed-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.