Additonally all what the desktop was left with is shown 100% for a while, sometimes even 10 or so seconds. The open browser for example.
Managed to read messages in Telegram too in that time and more. The screen asking the password appears much later. Thjis is on Budgie desktop and the laptops specs are:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz
CPU family: 6
Model: 37
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
Stepping: 2
Frequency boost: enabled
CPU(s) scaling MHz: 56%
CPU max MHz: 2534.0000
CPU min MHz: 1199.0000
BogoMIPS: 5054.29
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht
tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon p
ebs bts rep_good nopl xtopology nonstop_tsc cpuid aperf
mperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est t
m2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_l
m pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept
vpid dtherm ida arat vnmi flush_l1d
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 64 KiB (2 instances)
L1i: 64 KiB (2 instances)
L2: 512 KiB (2 instances)
L3: 3 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: KVM: Mitigation: VMX disabled
L1tf: Mitigation; PTE Inversion; VMX conditional cache flushe
s, SMT vulnerable
Mds: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer
sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIB
P conditional, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
To me this is an absolute critical bug or whatever it is and i have seen this reported and i think the developers asked for hardware information so there is mine a ThinkPad T410. Please say if even more info is required. I think this problem should be solved ASAP.