The gnome-weather updates today fixed the weather data shown in the popover 
Is it just me or are the numlock keys always disabled when entering the session? They are disabled even though the numlock light is on by default. But that isnât necessarily GNOME/GNOME 3.34 relatedâŚ
Yep weather data issue has been fixed. Numlock works for me.
Also happening in Ubuntu 19.04 with GNOME 3.32.2-2ubuntu1~ubuntu19.04.1
This issue is being tracked here. Screen resolution isnât a factor, as I am on a 1080p panel. I did discover that installing dash-to-dock and disabling panel mode makes the issue go away, at the cost of not having your dock stretch across the screen, and that this issue does not happen without the extension installed. Not sure exactly where the problem is yet.
Guess what, I upgraded from 19.04 to 19.10 this morning on my desktop (cause I canât help myself). Now numlock is also not enabled for me, I have enable it manually. 
I found that on the net: https://bbs.archlinux.org/viewtopic.php?id=249301
For now it seems to be Wayland only and caused by an updated GNOME component. And not everybody is affected. Because of different keyboard layouts? I donât know.
Holding down Super key and pressing Q does not show the quick launch number on Ubuntu Dock. Does this happen to anyone else?
I will test that tomorrow.
The Numlock issue is already filed upstream against mutter: https://gitlab.gnome.org/GNOME/mutter/issues/714
On another note: the desktop right-click menu is now translated again after the locales update of today.
The only untranslated strings are now in the âsystemâ category of the g-c-c keybindings .
Another Numlock bug (probably a duplicate) would be https://gitlab.gnome.org/GNOME/mutter/issues/769
I am not too sure this is mutter related. If I change to tty3 (command line), the behavior is exposed as well.
My findings:
Please test this:
*Boot your machine up
*In GDM test the Numlock keys. For me they seem to work in the password field.
*Donât log in to the graphical session but switch to the tty2 or tty3 terminal
*After logging in on the terminal it doesnât work as expected and the bug is exposed.
Thus I guess that Mutter isnât started up at all in this scenario and it cannot be a Mutter bug. Or am I wrong? And probably not Wayland/X.org related either?
But which other package (Ubuntu and at least Arch) can have regressed this?
@gunnarhj, do you have any ideas?
@mohan-ram, BTW holding the WINDOWS key and pressing q doesnât do anything for me either.
As regards recent changes affecting numlock: No. With that said, numlockx is always available (but thatâs old stuff, of course).
Canât seem to rename folder, once create by dragging and dropping application the system assigns folder name. But now I have two Internet folders and no way to rename one of them (or at lease I canât seem to find a way).
Yes, I thought that was going to be part of the 3.34. Maybe mistaken, but couldâve sworn I saw a video online demonstrating that.
AFAICS it will, the ticket is open against 19.10. Take into account that itâs a downstream bug.
@mohan-ram, there is a numlock related fix pending upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/834#note_620344
I guess if that lands it might fix our numlock bugs.
Awesome, thanks for the update.
Mutter 3.34.1 is in the release pocket now.
And the numlock bug seems to be fixed for me.
The strange thing is: Switching to tty3 or tty4 from GDM still disables the numlock. I canât remember if that was always the case or if it is even expected behavior.
But at least switching to the GNOME Shell (=tty2) works now like before.
I noticed last night after doing system update, and reboot my machine, night light did not work under wayland. It works in X.org, and prior to last nightâs update it worked in wayland.
Thanks, marked it as effecting me.