Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1051780: focus-follows-mouse doesn't work with gnome-shell/mutter 45-rc
39 views
Skip to first unread message
Roderich Schupp
Sep 12, 2023, 8:50:05 AM9/12/23
to
Package: libmutter-13-0
Version: 45~rc-4
Severity: normal
X-Debbugs-Cc: roderic...@gmail.com
I use focus-follows-mouse, ie. gsettings
org.gnome.desktop.wm.preferences focus-mode 'mouse'
org.gnome.desktop.wm.preferences focus-new-windows 'smart'
org.gnome.mutter focus-change-on-pointer-rest false
but gnome-shell/mutter 45-rc behaves as if focus-mode is set to 'click'.
No change in behaviour, when I set focus-mode to 'sloppy' or toggle
focus-change-on-pointer-rest.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.2 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libmutter-13-0 depends on:
ii adwaita-icon-theme 44.0-1
ii gsettings-desktop-schemas 45~rc-1
ii libatk1.0-0 2.49.91-2
ii libc6 2.38-3
ii libcairo-gobject2 1.17.8-3
ii libcairo2 1.17.8-3
ii libcanberra0 0.30-10
ii libcolord2 1.4.6-2.2
ii libdrm2 2.4.115-1
ii libegl1 1.6.0-1
ii libeis1 1.0.901-2
ii libfontconfig1 2.14.2-5
ii libfribidi0 1.0.13-3
ii libgbm1 23.1.7-1
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libgl1 1.6.0-1
ii libglib2.0-0 2.78.0-1
ii libgnome-desktop-4-2 44.0-2
ii libgraphene-1.0-0 1.10.8-1
ii libgudev-1.0-0 238-2
ii libharfbuzz0b 8.0.1-1
ii libice6 2:1.0.10-1
ii libinput10 1.23.0-2
ii libjson-glib-1.0-0 1.6.6-1
ii liblcms2-2 2.14-2
ii libpango-1.0-0 1.51.0+ds-2
ii libpangocairo-1.0-0 1.51.0+ds-2
ii libpangoft2-1.0-0 1.51.0+ds-2
ii libpipewire-0.3-0 0.3.79-2
ii libsm6 2:1.2.3-1
ii libstartup-notification0 0.12-6+b1
ii libsystemd0 254.1-3
ii libudev1 254.1-3
ii libwacom9 2.7.0-1
ii libwayland-server0 1.22.0-2.1
ii libx11-6 2:1.8.6-1
ii libx11-xcb1 2:1.8.6-1
ii libxau6 1:1.0.9-1
ii libxcb-randr0 1.15-1
ii libxcb-res0 1.15-1
ii libxcb1 1.15-1
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.1-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxi6 2:1.8-1+b1
ii libxinerama1 2:1.1.4-3
ii libxkbcommon-x11-0 1.5.0-1
ii libxkbcommon0 1.5.0-1
ii libxkbfile1 1:1.1.0-1
ii libxrandr2 2:1.5.2-2+b1
ii libxtst6 2:1.2.3-1.1
ii mutter-common 45~rc-4
ii mutter-common-bin 45~rc-4
libmutter-13-0 recommends no packages.
libmutter-13-0 suggests no packages.
Versions of packages libmutter-13-0 is related to:
ii libegl-mesa0 [libegl-vendor] 23.1.7-1
ii libgl1-mesa-dri 23.1.7-1
ii libglx-mesa0 [libglx-vendor] 23.1.7-1
-- no debconf information
Version: 45~rc-4
Severity: normal
X-Debbugs-Cc: roderic...@gmail.com
I use focus-follows-mouse, ie. gsettings
org.gnome.desktop.wm.preferences focus-mode 'mouse'
org.gnome.desktop.wm.preferences focus-new-windows 'smart'
org.gnome.mutter focus-change-on-pointer-rest false
but gnome-shell/mutter 45-rc behaves as if focus-mode is set to 'click'.
No change in behaviour, when I set focus-mode to 'sloppy' or toggle
focus-change-on-pointer-rest.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.2 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libmutter-13-0 depends on:
ii adwaita-icon-theme 44.0-1
ii gsettings-desktop-schemas 45~rc-1
ii libatk1.0-0 2.49.91-2
ii libc6 2.38-3
ii libcairo-gobject2 1.17.8-3
ii libcairo2 1.17.8-3
ii libcanberra0 0.30-10
ii libcolord2 1.4.6-2.2
ii libdrm2 2.4.115-1
ii libegl1 1.6.0-1
ii libeis1 1.0.901-2
ii libfontconfig1 2.14.2-5
ii libfribidi0 1.0.13-3
ii libgbm1 23.1.7-1
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libgl1 1.6.0-1
ii libglib2.0-0 2.78.0-1
ii libgnome-desktop-4-2 44.0-2
ii libgraphene-1.0-0 1.10.8-1
ii libgudev-1.0-0 238-2
ii libharfbuzz0b 8.0.1-1
ii libice6 2:1.0.10-1
ii libinput10 1.23.0-2
ii libjson-glib-1.0-0 1.6.6-1
ii liblcms2-2 2.14-2
ii libpango-1.0-0 1.51.0+ds-2
ii libpangocairo-1.0-0 1.51.0+ds-2
ii libpangoft2-1.0-0 1.51.0+ds-2
ii libpipewire-0.3-0 0.3.79-2
ii libsm6 2:1.2.3-1
ii libstartup-notification0 0.12-6+b1
ii libsystemd0 254.1-3
ii libudev1 254.1-3
ii libwacom9 2.7.0-1
ii libwayland-server0 1.22.0-2.1
ii libx11-6 2:1.8.6-1
ii libx11-xcb1 2:1.8.6-1
ii libxau6 1:1.0.9-1
ii libxcb-randr0 1.15-1
ii libxcb-res0 1.15-1
ii libxcb1 1.15-1
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.1-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxi6 2:1.8-1+b1
ii libxinerama1 2:1.1.4-3
ii libxkbcommon-x11-0 1.5.0-1
ii libxkbcommon0 1.5.0-1
ii libxkbfile1 1:1.1.0-1
ii libxrandr2 2:1.5.2-2+b1
ii libxtst6 2:1.2.3-1.1
ii mutter-common 45~rc-4
ii mutter-common-bin 45~rc-4
libmutter-13-0 recommends no packages.
libmutter-13-0 suggests no packages.
Versions of packages libmutter-13-0 is related to:
ii libegl-mesa0 [libegl-vendor] 23.1.7-1
ii libgl1-mesa-dri 23.1.7-1
ii libglx-mesa0 [libglx-vendor] 23.1.7-1
-- no debconf information
Roderich Schupp
Sep 14, 2023, 6:10:05 AM9/14/23
to
Forgot to mention it before: the broken behaviour is in a gnome-wayland session.
Focus-follows-mouse works as expected in a gnome-x.org session.
Cheers, Roderich
Roderich Schupp
Sep 17, 2023, 1:00:05 PM9/17/23
to
The problem has been fixed in upstream release 45.0.
You may close this bug.
Cheers, Roderich
Simon McVittie
Sep 17, 2023, 1:40:04 PM9/17/23
to
Control: tags -1 + fixed-upstream
On Sun, 17 Sep 2023 at 18:54:30 +0200, Roderich Schupp wrote:
> The problem has been fixed in upstream release 45.0.
> You may close this bug.
mutter 45.0 isn't in Debian (or Ubuntu) yet, so this bug should not
be closed just yet; but it can be closed when 45.0 is uploaded to
experimental, which I assume the developers working on GNOME Shell 45
will want to do next week.
Sorry, I'm not yet working on GNOME Shell 45 myself, so I haven't done
that upload: I've spent all of today on updates to versions 43 and 44,
trying to keep those versions working until 45 is ready. Version 45
cannot go to testing/unstable until the GNOME team has coordinated a
suitable upload timeline with the release team and the maintainers of
other affected packages like budgie-desktop.
Please try to keep a descriptive subject line like the bug title when
replying to bug reports: I realise it's appealing to change the subject
line to something like "more info" or "fixed upstream" if the bug is the
only one you are communicating with, but maintainers will often receive
a message like this one completely out of context, and will not know
which bug it is, or even which package it refers to, until they look up
the bug number.
Thanks,
smcv
On Sun, 17 Sep 2023 at 18:54:30 +0200, Roderich Schupp wrote:
> The problem has been fixed in upstream release 45.0.
> You may close this bug.
be closed just yet; but it can be closed when 45.0 is uploaded to
experimental, which I assume the developers working on GNOME Shell 45
will want to do next week.
Sorry, I'm not yet working on GNOME Shell 45 myself, so I haven't done
that upload: I've spent all of today on updates to versions 43 and 44,
trying to keep those versions working until 45 is ready. Version 45
cannot go to testing/unstable until the GNOME team has coordinated a
suitable upload timeline with the release team and the maintainers of
other affected packages like budgie-desktop.
Please try to keep a descriptive subject line like the bug title when
replying to bug reports: I realise it's appealing to change the subject
line to something like "more info" or "fixed upstream" if the bug is the
only one you are communicating with, but maintainers will often receive
a message like this one completely out of context, and will not know
which bug it is, or even which package it refers to, until they look up
the bug number.
Thanks,
smcv
0 new messages