Mouse/touchpad settings not applied on hotplug/reconnect/resume

Thank you for your bug report, could you report the issue upstream on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues ?

Done: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/559

See also bug 865791, bug 1874528, and maybe others.

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

This might turn out to be the same issue as bug 1899206.

I think I am also experiencing this bug.

I have a bluetooth trackpad (Magic Trackpad 1 by Apple), and since a few weeks ago, the scrolling direction is reversed by default, and the tap to click feature is disabled.

I can go to the trackpad settings and everything is alright. I can disable and re-enable these settings, and it works fine once again, but only until the next reboot, where I have to do the same thing again.

Possibly fixed in mutter 3.38.2 by:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1553

That upstream fix seems to be for Xorg sessions, so try using 'Ubuntu on Wayland' to see if it avoids the bug.

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

---------------
mutter (3.38.2-1ubuntu1) hirsute; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1908158):
    - Apply input device settings on hotplug / reconnect and resume
      (LP: #1899206)
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Refreshed as per upstream changes

mutter (3.38.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - Don't crash during screencasting if cursor is not available
    - Don't crash if a kernel bug results in appearing to have multiple
      builtin panels
    - Log warnings instead of crashing if user-defined keymap is
      misconfigured
    - Don't forget we have a touchscreen if a non-touchscreen input device
      is connected
    - Log warnings instead of crashing if invalid barriers are created
    - Otherwise functionally equivalent to 3.38.1-4
  * Drop patches cherry-picked from upstream or applied upstream
  * d/gbp.conf: Use upstream 3.38.x branch.
    Version 40~alpha was already released, so it's misleading to say that
    3.38.x is the latest.
  * Standards-Version: 4.5.1 (no changes required)
  * d/rules: Don't run tests if built with nocheck option
  * Upload to unstable

mutter (3.38.1-4) experimental; urgency=medium

  * Team upload
  * Update to upstream gnome-3-38 branch, commit 3.38.1-50-gc70610c43
    - If cursor theme is missing, draw a grey semi-transparent square
      instead of crashing
    - Allow primary GPU to be overridden with a udev rule
    - Fix fullscreen toggle for some applications (Closes: #975453)
    - Only schedule frame drawing for each surface (window) according to
      one stage view (monitor)
    - Fix size hints for client-side-decorated windows
    - Avoid adding input devices too soon
    - Performance optimizations
    - Do not disable the X Security extension if Xwayland was built with it
  * Don't depend on transitional libgdk-pixbuf2.0-dev
  * Explicitly build-depend on gdk-pixbuf.
    Previously it was pulled in by some other dependency (presumably
    gnome-desktop3 and gtk), but mutter's build system checks for it, so
    we should build-depend on it here too.
  * d/p/clutter-frame-clock-Schedule-a-frame-at-least-once-per-se.patch:
    Add proposed patch to ensure frame clock does not stop (Closes: #974172)

mutter (3.38.1-3) experimental; urgency=medium

  * Team upload
  * Update to upstream gnome-3-38 branch, commit 3.38.1-33-g067af969c
    - Prevent a use-after-free on (virtual) device removal
    - Prevent crash on startup caused by dispatching libinput events too
      early
    - If Wayland subsurfaces have circular relationships, disconnect the
      client instead of crashing
    - When resizing terminals interactively, don't offset the position
    - Fix broken timestamp behaviour if X11 timestamps overflow
    - Fix a memory leak
    - Ensure clock is updated when going from fullscreen app to overview
    - Fix artifacts around GNOME Shell magnifier cursor
    - Fix monitor tiling on X11
    - Configure input devices correctly in X11
      (LP: #1899206, LP: #1899509)
    - Avoid spurious warnings in lo...

Hello Brennan, or anyone else affected,

Accepted mutter into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.38.2-1ubuntu1~20.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

This bug is a duplicate. Let's handle the verification at bug #1899206.

Marking this as verified to not block migration.

This bug was fixed in the package mutter - 3.38.2-1ubuntu1~20.10.1

---------------
mutter (3.38.2-1ubuntu1~20.10.1) groovy; urgency=medium

  * No-change backport to groovy
  * debian: Prepare gbp.conf and control references to groovy branching

mutter (3.38.2-1ubuntu1) hirsute; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1908158):
    - Apply input device settings on hotplug / reconnect and resume
      (LP: #1899206)
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Refreshed as per upstream changes

mutter (3.38.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - Don't crash during screencasting if cursor is not available
    - Don't crash if a kernel bug results in appearing to have multiple
      builtin panels
    - Log warnings instead of crashing if user-defined keymap is
      misconfigured
    - Don't forget we have a touchscreen if a non-touchscreen input device
      is connected
    - Log warnings instead of crashing if invalid barriers are created
    - Otherwise functionally equivalent to 3.38.1-4
  * Drop patches cherry-picked from upstream or applied upstream
  * d/gbp.conf: Use upstream 3.38.x branch.
    Version 40~alpha was already released, so it's misleading to say that
    3.38.x is the latest.
  * Standards-Version: 4.5.1 (no changes required)
  * d/rules: Don't run tests if built with nocheck option
  * Upload to unstable

mutter (3.38.1-4) experimental; urgency=medium

  * Team upload
  * Update to upstream gnome-3-38 branch, commit 3.38.1-50-gc70610c43
    - If cursor theme is missing, draw a grey semi-transparent square
      instead of crashing
    - Allow primary GPU to be overridden with a udev rule
    - Fix fullscreen toggle for some applications (Closes: #975453)
    - Only schedule frame drawing for each surface (window) according to
      one stage view (monitor)
    - Fix size hints for client-side-decorated windows
    - Avoid adding input devices too soon
    - Performance optimizations
    - Do not disable the X Security extension if Xwayland was built with it
  * Don't depend on transitional libgdk-pixbuf2.0-dev
  * Explicitly build-depend on gdk-pixbuf.
    Previously it was pulled in by some other dependency (presumably
    gnome-desktop3 and gtk), but mutter's build system checks for it, so
    we should build-depend on it here too.
  * d/p/clutter-frame-clock-Schedule-a-frame-at-least-once-per-se.patch:
    Add proposed patch to ensure frame clock does not stop (Closes: #974172)

mutter (3.38.1-3) experimental; urgency=medium

  * Team upload
  * Update to upstream gnome-3-38 branch, commit 3.38.1-33-g067af969c
    - Prevent a use-after-free on (virtual) device removal
    - Prevent crash on startup caused by dispatching libinput events too
      early
    - If Wayland subsurfaces have circular relationships, disconnect the
      client instead of crashing
    - When resizing terminals interactively, don't offset the position
    - Fix broken timestamp behaviour if X11 timestamps overflow
    - Fix a memory leak
    - Ensure clock is updated when going from fullscreen app to overview
    - Fix artifacts around GNOME S...

The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.