This bug was fixed in the package mutter - 3.34.1-1ubuntu1
---
mutter (3.34.1-1ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update
Fixed upstream(?)
https://gitlab.gnome.org/GNOME/mutter/merge_requests/834
** Tags added: fixed-in-3.34.1 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845031
Title:
gnome not remem
Prior to filing a bug myself I searched launchpad for "num lock", so
this bug with "numlock" in the title did not show up. The bug I filed
is Bug #1846249. I am experiencing the same issue under 19.10 when
logged in with Wayland. The problem is not present in an X session. In
fact I can do the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845031
Title:
gno
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845031
Title:
gnome not remembering numlock state in eoan
To manage notifications about
