[KDE] Not able to enter password for few seconds at login screen in Kubuntu 23.04

[alokmahor]

I am using Kubuntu 23.04 on HP Pavilion laptop.
Everything is working fine except one problem at login screen.

I am not able to type a password for the first few seconds(around 10 seconds). Nothing gets typed in the input box of password at the login screen. After a few seconds the input box start taking input.

I try clicking on input field still not able to type password. I have to wait for few seconds to type password.

I am facing this in both X11 and Wayland.

How can I trubleshhot and fix this bihaviour?

I observed errors in journalctl related to kwin_libinput and xkbcommon

Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kernel: Restarting tasks ...
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2561]: kwin_libinput: Libinput: client bug: timer event6 tap: scheduled expiry is in the past (-128ms), your system is too slow
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2561]: kwin_libinput: Libinput: client bug: timer event6 hold: scheduled expiry is in the past (-268ms), your system is too slow
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2561]: kwin_libinput: Libinput: client bug: timer event6 tap: scheduled expiry is in the past (-61ms), your system is too slow
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2561]: kwin_libinput: Libinput: client bug: timer event6 hold: scheduled expiry is in the past (-201ms), your system is too slow
Jul 23 07:36:46 alok-HP-Pavilion-Laptop-14-dv0xxx kernel: done.​

Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx kernel: br-a31a159f0d45: port 1(vethe405932) entered blocking state
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx kernel: br-a31a159f0d45: port 1(vethe405932) entered forwarding state
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:39:34: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:40:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:41:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:42:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:43:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:44:27: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:45:27: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:46:27: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:47:27: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:48:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: string literal is not a valid UTF-8 string
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: too many errors
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: failed to parse file
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx krunner[3645]: qt.qpa.input.methods: failed to create compose table
Jul 23 08:05:38 alok-HP-Pavilion-Laptop-14-dv0xxx systemd[1]: systemd-fsckd.service: Deactivated successfully. zz0.aklubqgsj5ozz

Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: No backend specified, automatically choosing drm
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:39:34: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:40:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:41:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:42:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:43:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:44:27: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:45:27: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:46:27: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:47:27: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:48:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:49:29: string literal is not a valid UTF-8 string
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:49:29: too many errors
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: /usr/share/X11/locale/iso8859-1/Compose:49:29: failed to parse file
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: OpenGL vendor string: Intel
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2)
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: OpenGL version string: 4.6 (Core Profile) Mesa 23.0.2
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: OpenGL shading language version string: 4.60
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Driver: Intel
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: GPU class: Tiger Lake
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: OpenGL version: 4.6
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: GLSL version: 4.60
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Mesa version: 23.0.2
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Linux kernel version: 6.2
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Requires strict binding: no
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: GLSL shaders: yes
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Texture NPOT support: yes
Jul 23 08:05:25 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: Virtual Machine: no
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2790]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2814]: (WW) Option "-listen" for file descriptors is deprecated
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2814]: Please use "-listenfd" instead.
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2814]: (WW) Option "-listen" for file descriptors is deprecated
Jul 23 08:05:26 alok-HP-Pavilion-Laptop-14-dv0xxx kwin_wayland_wrapper[2814]: Please use "-listenfd" instead.​

Output of sudo systemd-analyze critical-chain is

alok@alok-HP-Pavilion-Laptop-14-dv0xxx:~$ sudo systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @9.217s
└─multi-user.target @9.217s
└─docker.service @5.646s +3.570s
└─network-online.target @5.572s
└─NetworkManager-wait-online.service @1.817s +3.755s
└─NetworkManager.service @1.788s +26ms
└─dbus.service @1.736s +49ms
└─basic.target @1.729s
└─sockets.target @1.729s
└─snapd.socket @1.727s +1ms
└─sysinit.target @1.666s
└─snapd.apparmor.service @1.574s +91ms
└─apparmor.service @1.535s +35ms
└─local-fs.target @1.535s
└─run-docker-netns-412a5bd66398.mount @8.031s
└─local-fs-pre.target @535ms
└─systemd-tmpfiles-setup-dev.service @523ms +11ms
└─systemd-sysusers.service @515ms +7ms
└─systemd-remount-fs.service @507ms +4ms
└─systemd-journald.socket @488ms
└─system.slice @399ms
└─-.slice @399ms​​

Output of sudo systemd-analyze blame is

3.755s NetworkManager-wait-online.service
3.570s docker.service
3.347s fwupd-refresh.service
3.286s fwupd.service
2.756s apt-daily-upgrade.service
782ms snapd.service
472ms snapd.seeded.service
289ms dev-nvme0n1p4.device
211ms apport.service
188ms systemd-journal-flush.service
144ms containerd.service
127ms [EMAIL="user@1000.service"]user@1000.service[/EMAIL]
121ms dev-loop5.device
120ms dev-loop3.device
120ms dev-loop6.device
119ms dev-loop4.device
119ms dev-loop2.device
117ms dev-loop7.device
116ms rsyslog.service
116ms dev-loop1.device
106ms udisks2.service
98ms dev-loop0.device
97ms plymouth-quit.service
95ms ua-timer.service
93ms accounts-daemon.service
93ms systemd-udev-trigger.service
91ms snapd.apparmor.service
88ms dev-loop9.device
85ms dev-loop8.device
79ms systemd-udevd.service
76ms ModemManager.service
71ms update-notifier-download.service
63ms systemd-modules-load.service
59ms systemd-resolved.service
58ms avahi-daemon.service
57ms systemd-journald.service
56ms bluetooth.service
51ms power-profiles-daemon.service
49ms dbus.service
49ms polkit.service
48ms systemd-logind.service
45ms gpu-manager.service
42ms cups.service
38ms upower.service
38ms [EMAIL="systemd-fsck@dev-disk-by%5Cx2duuid-788B%5Cx2d6455.service"]systemd-fsck@dev-disk-by\x2duuid-788B\x2d6455.service[/EMAIL]
36ms thermald.service
36ms secureboot-db.service
35ms apparmor.service
33ms snap-firefox-2916.mount
31ms snap-gnome\x2d42\x2d2204-120.mount
31ms alsa-restore.service
30ms systemd-tmpfiles-clean.service
29ms smartmontools.service
28ms systemd-timesyncd.service
27ms snap-gnome\x2d42\x2d2204-68.mount
27ms e2scrub_reap.service
26ms keyboard-setup.service
26ms NetworkManager.service
26ms snap-gtk\x2dcommon\x2dthemes-1535.mount
25ms snap-snapd-18596.mount
25ms docker.socket
24ms snap-snapd-19457.mount
23ms boot-efi.mount
23ms snap-core22-806.mount
23ms snap-bare-5.mount
23ms systemd-tmpfiles-setup.service
22ms snap-core22-817.mount
22ms var-snap-firefox-common-host\x2dhunspell.mount
21ms snap-firefox-2517.mount
19ms dev-hugepages.mount
18ms kerneloops.service
18ms dev-mqueue.mount
17ms plymouth-start.service
16ms sys-kernel-debug.mount
15ms [EMAIL="systemd-backlight@backlight:intel_backlight.service"]systemd-backlight@backlight:intel_backlight.service[/EMAIL]
15ms sys-kernel-tracing.mount
13ms grub-common.service
13ms wpa_supplicant.service
12ms systemd-binfmt.service
11ms plymouth-read-write.service
11ms systemd-tmpfiles-setup-dev.service
10ms systemd-sysctl.service
9ms kmod-static-nodes.service
8ms [EMAIL="modprobe@configfs.service"]modprobe@configfs.service[/EMAIL]
7ms systemd-user-sessions.service
7ms grub-initrd-fallback.service
7ms proc-sys-fs-binfmt_misc.mount
7ms systemd-sysusers.service
6ms [EMAIL="modprobe@fuse.service"]modprobe@fuse.service[/EMAIL]
5ms systemd-random-seed.service
5ms [EMAIL="user-runtime-dir@1000.service"]user-runtime-dir@1000.service[/EMAIL]
5ms [EMAIL="modprobe@drm.service"]modprobe@drm.service[/EMAIL]
5ms console-setup.service
4ms systemd-update-utmp.service
4ms systemd-remount-fs.service
4ms systemd-update-utmp-runlevel.service
3ms sys-kernel-config.mount
3ms sys-fs-fuse-connections.mount
2ms systemd-rfkill.service
2ms sddm.service
2ms rtkit-daemon.service
2ms motd-news.service
1ms ufw.service
1ms [EMAIL="modprobe@efi_pstore.service"]modprobe@efi_pstore.service[/EMAIL]
1ms setvtrgb.service
1ms snapd.socket

[Schwarzer Kater]

You could use journalctl in the Konsole terminal emulator to view log files.
See man journalctl for options, e.g. journalctl -b -a to see entries for the current boot or sudo journalctl -k to see kernel messages only.
Press [q] to exit.

You could also use systemd-analyze critical-chain or systemd-analyze blame (press [q] to exit) to find a culprit.

[alokmahor]

You could use journalctl in the Konsole terminal emulator to view log files.
See man journalctl for options, e.g. journalctl -b -a to see entries for the current boot or sudo journalctl -k to see kernel messages only.
Press [q] to exit.

You could also use systemd-analyze critical-chain or systemd-analyze blame (press [q] to exit) to find a culprit.

I have added output of systemd-analyze in question

[Schwarzer Kater]

Looks OK to me… Perhaps Docker has something to do with it (wild guess…)?

Check log files, too.

[alokmahor]

Looks OK to me… Perhaps Docker has something to do with it (wild guess…)?

Check log files, too.

I have added journalctl logs which have errors.

[Schwarzer Kater]

Please post your terminal output within CODE tags (the "#" button) including the command you used - this is much easier to read and understand for others…

[alokmahor]

Please post your terminal output within CODE tags (the "#" button) including the command you used - this is much easier to read and understand for others…

I have edited my question to use CODE tag

[Schwarzer Kater]

Could not spot anything in your updated original post that makes sense to me regarding the long time before the login prompt is ready either (but perhaps someone else should have a look, too).
There might be more log files to go through, like Xorg…

If you are using Wayland consider also trying out the Kubuntu Backports, perhaps this can fix something if it is KDE Plasma / Frameworks related - but this also is just a wild guess.
https://www.kubuntuforums.net/forum/...untu-backports

Otherwise I am out of ideas for now (I assume this does not happen when you boot from a Kubuntu 23.04 live ISO, or does it?).