Unable to log back into GNOME after the screen locks due to inactivity (Fedora 42, Wayland)

Ask Fedora
, , ,
1

Problem Summary

After my laptop goes to sleep because of inactivity, I can wake the display, move the mouse, but cannot type my password in the lock‑screen dialog. The mouse cursor works, and i can interact with the top menu yet the password field stays unresponsive (feels like keyboard is not working at all). I have to force a shutdown (pressing the power button) to get back to my desktop.

System Details (generated on 2025‑08‑25)

Hardware Information:

  • Hardware Model: Lenovo IdeaPad Slim 3 15ABR8
  • Memory: 16.0 GiB
  • Processor: AMD Ryzen™ 5 7530U with Radeon™ Graphics × 12
  • Graphics: AMD Radeon™ Graphics
  • Disk Capacity: (null)

Software Information:

  • Firmware Version: KYCN39WW
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.15.10-200.fc42.x86_64

What I’ve Tried So Far

  1. Basic checks – verified that the password is correct and that the keyboard works in other contexts (e.g., at the login manager after a reboot).

  2. Keyboard layout - confirmed the layout is still US‑QWERTY after waking.

  3. Updates - ensured the system is fully up‑to‑date (dnf upgrade --refresh).

What I’m Looking For

  • Possibly causes (e.g., known bugs with GNOME 48, Wayland input handling, kernel regressions, firmware quirks), power mode related issues.

  • Work-arounds that let me regain keyboard input without shutting down.

Additional Context

  • The issue appears after x length of inactivity (not for short periods).

Any guidance, similar experiences, or pointers to relevant bug reports would be greatly appreciated!

1 Like
2

Can you switch to a virtual terminal with Ctrl+Alt+F3? Do you have a spare USB keyboard that you could connect and try?

It sounds like your keyboard is not waking with the rest of the system. There might be some helpful log messages near the end of sudo jounalctl -b -1. The only workaround I can think of would be to disable power-management/suspend and just manually power off your system when it is not in use.

1 Like
3

  • Apparently I’m not able to access the “Virtual Terminal” , also I’m unable to force a restart with the key combination of: Ctrl+Alt+PrtSc+R+E+I+S+U+B

  • The sudo journalctl -b -1 command returns:

    Details
    • Journal file /var/log/journal/ba52c54e6b02478a9d4c099c507966fc/system@00063d23a3acdbaa-f232adad07d19fa9.journal~ is truncated, ignoring file.
      Αυγ 25 20:57:56 fedora kernel: Linux version 6.15.10-200.fc42.x86_64 (mockbuild@14a33d64645143cab3659d13>
      Αυγ 25 20:57:56 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt5)/vmlinuz-6.15.10-200.fc42.x86_64 root=>
      Αυγ 25 20:57:56 fedora kernel: BIOS-provided physical RAM map:
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfffff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009db0fff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000009db1000-0x0000000009efffff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f0efff] ACPI NVS
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000009f0f000-0x00000000c6a7dfff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000c6a7e000-0x00000000cac7dfff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000cac7e000-0x00000000ccd7dfff] ACPI NVS
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000ccd7e000-0x00000000ccdfdfff] ACPI data
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000ccdfe000-0x00000000cdffffff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000ce000000-0x00000000cfffffff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000fdc00000-0x00000000fdcfffff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe0fffff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x00000003ae2fffff] usable
      Αυγ 25 20:57:56 fedora kernel: BIOS-e820: [mem 0x00000003ae300000-0x000000042fffffff] reserved
      Αυγ 25 20:57:56 fedora kernel: NX (Execute Disable) protection: active
      Αυγ 25 20:57:56 fedora kernel: APIC: Static calls initialized
      Αυγ 25 20:57:56 fedora kernel: efi: EFI v2.7 by Phoenix Technologies Ltd.
      Αυγ 25 20:57:56 fedora kernel: efi: ACPI=0xccdfd000 ACPI 2.0=0xccdfd014 SMBIOS=0xc8b56000 SMBIOS 3.0=0xc>
      Αυγ 25 20:57:56 fedora kernel: random: crng init done
      Αυγ 25 20:57:56 fedora kernel: efi: Remove mem67: MMIO range=[0xfdc00000-0xfdcfffff] (1MB) from e820 map
      Αυγ 25 20:57:56 fedora kernel: e820: remove [mem 0xfdc00000-0xfdcfffff] reserved
      Αυγ 25 20:57:56 fedora kernel: efi: Remove mem68: MMIO range=[0xfe000000-0xfe0fffff] (1MB) from e820 map
      Αυγ 25 20:57:56 fedora kernel: e820: remove [mem 0xfe000000-0xfe0fffff] reserved
      Αυγ 25 20:57:56 fedora kernel: efi: Not removing mem69: MMIO range=[0xfed80000-0xfed80fff] (4KB) from e8>
      Αυγ 25 20:57:56 fedora kernel: secureboot: Secure boot enabled
      Αυγ 25 20:57:56 fedora kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
      Αυγ 25 20:57:56 fedora kernel: SMBIOS 3.3.0 present.
      Αυγ 25 20:57:56 fedora kernel: DMI: LENOVO 82XM/LNVNB161216, BIOS KYCN39WW 04/17/2025
      Αυγ 25 20:57:56 fedora kernel: DMI: Memory slots populated: 2/2
      Αυγ 25 20:57:56 fedora kernel: tsc: Fast TSC calibration using PIT
      Αυγ 25 20:57:56 fedora kernel: tsc: Detected 1996.260 MHz processor
      Αυγ 25 20:57:56 fedora kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
      Αυγ 25 20:57:56 fedora kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
      Αυγ 25 20:57:56 fedora kernel: last_pfn = 0x3ae300 max_arch_pfn = 0x400000000
      Αυγ 25 20:57:56 fedora kernel: MTRR map: 6 entries (3 fixed + 3 variable; max 20), built from 9 variable>
      Αυγ 25 20:57:56 fedora kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
      Αυγ 25 20:57:56 fedora kernel: last_pfn = 0xce000 max_arch_pfn = 0x400000000
      Αυγ 25 20:57:56 fedora kernel: esrt: Reserving ESRT space from 0x00000000c34b1698 to 0x00000000c34b1720.
      Αυγ 25 20:57:56 fedora kernel: e820: update [mem 0xc34b1000-0xc34b1fff] usable ==> reserved
      Αυγ 25 20:57:56 fedora kernel: Using GB pages for direct mapping
      Αυγ 25 20:57:56 fedora kernel: secureboot: Secure boot enabled
      lines 1-48
4

I did a quick search and found this:

https://www.lenovo.com/us/en/glossary/how-to-fix-locked-laptop-keyboard/?orgRef=https%253A%252F%252Fduckduckgo.com%252F

A little bit weird that there’s a whole page dedicated to it, which makes me think this is a common thing with these Lenovo laptops?

Also found this on the forum, which was solved. So worth looking at:

3 Likes
5

try to delete .Xauthority file in your home folder. Worked for me.
So for me case was similar, mouse works, but you can type nothing on password field. Even using display keyboard. Use ctlr-alt-f2, login, and delete .Xauthority.

I’m not sure, but for me the cases on my computers appeared after power blackout.