Hello Weston, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.7+git20201123-0.20.04.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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: mutter (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1899206

Title:
  Input device settings not applied on hotplug/reconnect/resume in Xorg
  sessions

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  Mutter 3.36.2 breaks custom input settings

  [ Test case ]

  - Set custom settings using gnome-control-center (set custom Delay and
    Speed in Settings > Accessibility > Repeat Keys) or gnome-tweaks (under
    Additional Layout options)
  - Unplug / replug the input device or suspend / resume
  - Input device settings should be preserved

  [ Regression potential ]

  Devices added or removed may be not noticed by gnome-shell.

  ---

  I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
  seems to have been introduced within the past couple of weeks. I have
  a couple custom keyboard settings configured in Tweaktool "Additional
  Layout Options". These settings work great.

  I have a USB keyboard plugged into the machine. If I have the keyboard
  plugged in when I start my Gnome session, the customized keyboard
  layout options are correctly applied to the USB keyboard. If I unplug
  and reconnect the keyboard, the keyboard does will _NOT_ have the
  customized keyboard settings.

  If I restart my Gnome session (using Alt-F2 -> "r"), the customized
  settings are applied to the keyboard.

  I think this behavior is something new. Before, I was able to
  unplug/reconnect my keyboard and it would apply my customized keyboard
  settings on reconnect. Is there anything I can do to force the
  application of the custom keyboard tweaks on USB keyboard reconnect?

  Is anyone else able to reproduce this? I don't have any other machines
  with Ubuntu 20.04.1 to test with.

  Thanks!

  (This is also cross-posted at askubuntu:
  https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
  layout-options-not-working)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to