No mouse reaction on gnome activities search panel

After upgrade to 22.04.1 from 20.04:
When I push a SUPER key and type something in Gnome’s activities search bar all displayed results are not highlighted under mouse. When I click any of them system returns to normal desktop. When I use tab key every works fine - results are highlighted sequentially.
When I click menu (activities) icon every works fine, it seems that problem appears after typing in search bar.
Here is a inxi output:
Kernel: 5.15.0-47-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
Desktop: GNOME 42.4 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: PRIME B560M-A v: Rev 1.xx serial:
UEFI: American Megatrends v: 1017 date: 07/12/2021
Battery:
Device-1: hidpp_battery_0
model: Logitech Wireless Mobile Mouse MX Anywhere 2S
charge: 55% (should be ignored) status: Discharging
Memory:
RAM: total: 15.46 GiB used: 4.61 GiB (29.8%)
Array-1: capacity: 64 GiB slots: 4 EC: None max-module-size: 16 GiB
note: est.
Device-1: Controller0-ChannelA-DIMM0 size: No Module Installed
Device-2: Controller0-ChannelA-DIMM1 size: 8 GiB speed: 2400 MT/s
type: DDR4
Device-3: Controller0-ChannelB-DIMM0 size: No Module Installed
Device-4: Controller0-ChannelB-DIMM1 size: 8 GiB speed: 2400 MT/s
type: DDR4
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
arch: Rocket Lake rev: 1 cache: L1: 480 KiB L2: 3 MiB L3: 12 MiB
Speed (MHz): avg: 800 high: 802 min/max: 800/4400 cores: 1: 801 2: 802
3: 800 4: 801 5: 801 6: 801 7: 800 8: 800 9: 801 10: 800 11: 800 12: 801
bogomips: 62208
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: Gigabyte driver: nvidia
v: 510.85.02 bus-ID: 01:00.0
Display: server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution:
1: 1920x1080~60Hz 2: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 510.85.02 direct render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3
Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 01:00.1
Sound Server-1: ALSA v: k5.15.0-47-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6
IF: eno1 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 465.76 GiB used: 239.59 GiB (51.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB
temp: 25.9 C
Partition:
ID-1: / size: 456.89 GiB used: 239.58 GiB (52.4%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 26 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 39%
Info:
Processes: 350 Uptime: 14h 31m Init: systemd runlevel: 5 Compilers:
gcc: 11.2.0 Packages: 2318 Shell: Sudo v: 1.9.9 inxi: 3.3.13

Hi @michal ,
I tried it in Debian 11…which has Gnome 3.38.5.
It works fine either with Superkey or from the activities menu.

Your Gnome is a much later version.

There have been other problems with Ubuntu 22 and some of them involve nvidia cards
It looks like you have the nvidia drivers, not the nouveau drivers?
It seems to be Xorg, not Wayland.

The only things I can suggest are change the drivers or change the Gnome version. You would not want to go back to Ubuntu20 just for that.

If you do anything, do a backup first.

Regards
Neville

1 Like

Thank you for quick response - I’ve done a HDD backup with Clonezilla before upgrade but after all I don’t want to back to 20.04. There may be some other issues with other drivers than Nvidia, this is important machine which I use in my business and I don’t want to make experiments. Because this problem is now quite burdensome (I can use TAB key) I will do nothing at this time

Do another backup now of Ubuntu22 before you fiddle with anything.
You at least have Ubuntu22 working. Preserve it. The future may be worse.

1 Like