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 Shell magnifier cursor
- Fix monitor tiling on X11
- Configure input devices correctly in X11
(LP: #1899206, LP: #1899509)
- Avoid spurious warnings in log
- Event does not have a stage: discarding
- assertion 'CLUTTER_IS_STAGE (stage)' failed
- Make sure build fails if Xwayland -initfd is requested but not
available (not relevant in Debian, we don't request this yet)
- Update translations: pt
* d/p/backend-Don-t-pull-generated-headers-indirectly.patch:
Add a patch from upstream git master to fix parallel builds
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Tue, 15 Dec 2020
02:50:32 +0100
** Changed in: mutter (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
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 mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Released
Status in mutter source package in Groovy:
Fix Released
Status in mutter source package in Hirsute:
Fix Released
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
