Hi at all
I have installed Garuda with LXQT.
In the last few days after a period of 2 hours of screen locked, when I try to type the password, the field seems to be disabled.
The keybord it's working, because if I enable the capslock, the login screen send the warning , but I can't type the password and I don't have the virtual keyboard on screen to try with the mouse.
The only solution is to power off.
Do you have any suggestion?
Hi there, welcome!
First off, please provide your system specs with the output of
inxi -Fza as text, formatted with 3 ~ before and after.
Thanks for the quick response.
This is the output:
System: Kernel: 5.13.13-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=16d49e4d-ca23-4f5c-bb1a-8f3cda8b0866 rw
[email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
Desktop: LXQt 0.17.1 tk: Qt 5.15.2 info: cairo-dock, lxqt-panel wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux
base: Arch Linux
Machine: Type: Desktop System: ASUSTeK product: A4320A6420 v: 0502 serial: <filter>
Mobo: ASUSTeK model: A4320A6420 v: Rev 1.xx serial: <filter> UEFI: ASUSTeK v: 0502 date: 01/14/2016
CPU: Info: Dual Core model: Intel Core i3-4170 bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3C (60)
stepping: 3 microcode: 28 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 29534
Speed: 3692 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 3692 2: 3692 3: 3692 4: 3695
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:041e class-ID: 0300
Device-2: IMC Networks USB2.0 UVC HD Webcam type: USB driver: uvcvideo bus-ID: 2-1.5:5 chip-ID: 13d3:5654
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel unloaded: modesetting
alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1013x285mm (39.9x11.2") s-diag: 1052mm (41.4")
Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") diag: 551mm (21.7")
Monitor-2: HDMI1 res: 1920x1080 dpi: 92 size: 530x300mm (20.9x11.8") diag: 609mm (24")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.1 compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
Sound Server-1: ALSA v: k5.13.13-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.34 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: e000
bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel
port: e000 bus-ID: 04:00.0 chip-ID: 168c:0036 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth: Device-1: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-1.4:111 chip-ID: 04ca:300f
Report: bt-adapter ID: hci0 rfk-id: 243 state: up address: <filter>
Drives: Local Storage: total: 223.57 GiB used: 150.8 GiB (67.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Intel model: SSDSC2KW240H6 size: 223.57 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 036C scheme: GPT
Partition: ID-1: / raw-size: 223.31 GiB size: 223.31 GiB (100.00%) used: 150.8 GiB (67.5%) fs: btrfs dev: /dev/sda2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 223.31 GiB size: 223.31 GiB (100.00%) used: 150.8 GiB (67.5%) fs: btrfs dev: /dev/sda2
ID-4: /var/log raw-size: 223.31 GiB size: 223.31 GiB (100.00%) used: 150.8 GiB (67.5%) fs: btrfs dev: /dev/sda2
ID-5: /var/tmp raw-size: 223.31 GiB size: 223.31 GiB (100.00%) used: 150.8 GiB (67.5%) fs: btrfs dev: /dev/sda2
Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 5.71 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info: Processes: 258 Uptime: 44m wakeups: 0 Memory: 5.71 GiB used: 2.52 GiB (44.2%) Init: systemd v: 249 tool: systemctl
Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1688 lib: 486 Shell: fish v: 3.3.1 default: Bash v: 5.1.8
running-in: alacritty inxi: 3.3.06
Personally, I don't think I can help you much.
At a quick search on the Internet I did not find anything helpful (similar cases, but without solution).
In the LXQt wiki I see "If you want to disable screen locking upon suspend / sleep it is under LXQt> Preferences> LXQt Settings> Session Settings> Lock screen before suspending / hibernating checkbox."
Maybe you could test it (if the PC goes in suspend/sleep after that time) and consider it as a workaround, or as long as someone else doesn't have better ideas?
I don't want disable the screen locking, it's a matter of security, I'm testing garuda on my PC at work.
In the last month all it's working fine.
Maybe could be a recent update.
I'll keep searching.
Ah, this is an important info.
Maybe you could give a look at
/var/log/pacman.log If there was a recent update on a package which might relate to this topic (sddm, some kind of screen lock)?
If it's too late to restore a snapshot from timeshift (maybe this started too long ago), you could check if this relates to a recent kernel update by switching to the
I found an update for sddm-kcm this morning, but the first time it's happened was monday.
Maybe this fix the problem, i'll see tomorrow.
Do you know how to enable virtual keyboard on lock screen?
I'm not on the system today, but if I remember correctly there is a virtual keyboard button embedded in SDDM (bottom left in KDE, maybe somewehere else for you).
I installed (but very rarely use)
onboard, but I don't think it can be used before login.
I think sddm-kcm just integrates SDDM configuration into the System Settings, so most likely this is something different. Anyway, good to (re)check...
I have had a similar problem But have also had it when I was running Mint. For me it seems to be something with the Num-lock key.
If I dont touch the Num-Lock key, I cannot enter numbers but can alternate between guest and user (left-right keys).
However if I turn num-lock off (sometimes pushing the button twice) and then turn on again, I am able to enter my login.
My 2 cents...
Maybe I found the solution.
I have disabled the random wallpaper for the screen lock and after several days everything seems to be ok.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.