Screen Locker Is Broken After Leaving The PC On

Today When I rebooted to my PC after my installation from the usb media , I was greeted by the setup assistant for further setup.

I started the setup and it prompted me to update my
installation, after which a terminal opened asking
for password and typical y or n prompts for installation.

After I had completed the prompts , the installation for a
massive 2 gig update started and I went for a walk .

I returned an hour later , hoping the update was completed so I could set it up further , but to my surprise I got a error saying :
The screen Locker is broken press alt+f2 etc. I looked it up on the web and it seemed to be a kernel issue .

I did leave my system on without any interaction for a long period of time after the update had started .
Not sure if this caused the error.

When the update was going on , I was on the 6.2 kernel zen which seemed to cause issues with distorted screen after sleep / suspend .

After this error I reinstalled Garuda on my PC , fully set it up with setup assistant and rebooted after which my kernel version got updated to 6.5 .

This issue seems to be kernel related and it occured while running 6.2 so I hope that now after full setup and updating it is fixed ? What could have caused this issue?
If it is not resolved then what steps should I undertake?

inxi output from my new garuda installation after the screen Locker error on my pc:

System:
Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9d750a54-b219-4c20-a924-ee720db0507f rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: HP product: HP All-in-One 22-df0xxx v: N/A
serial: <superuser required> Chassis: type: 13 serial: <superuser required>
Mobo: HP model: 87A4 v: 10100 serial: <superuser required> UEFI: AMI
v: F.36 date: 08/07/2023
CPU:
Info: model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake
gen: core 10 level: v4 note: check built: 2019-21 process: Intel 10nm
family: 6 model-id: 0x7E (126) stepping: 5 microcode: 0xBC
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 160 KiB desc: d-2x48 KiB; i-2x32 KiB L2: 1024 KiB desc: 2x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 692 high: 990 min/max: 400/3400 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 990 3: 400 4: 981
bogomips: 9523
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Iris Plus Graphics G1 vendor: Hewlett-Packard driver: i915
v: kernel arch: Gen-11 process: Intel 10nm built: 2019-21 ports:
active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:8a56 class-ID: 0300
Device-2: Luxvisions Innotech HP TrueVision HD Camera driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:6
chip-ID: 30c9:0013 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: HP ALL-in-One serial: <filter> built: 2019
res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 476x268mm (18.74x10.55")
diag: 546mm (21.5") ratio: 16:9 modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (ICL GT1)
device-ID: 8086:8a56 memory: 7.36 GiB unified: yes
API: Vulkan v: 1.3.269 layers: 3 device: 0 type: integrated-gpu name: Intel
UHD Graphics (ICL GT1) driver: mesa intel v: 23.2.1-arch1.2
device-ID: 8086:8a56 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_icl
bus-ID: 00:1f.3 chip-ID: 8086:34c8 class-ID: 0403
API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw_8821ce v: N/A modules: rtw88_8821ce
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:c821 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:5 chip-ID: 0bda:b00a
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 960.76 GiB used: 14.5 GiB (1.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-60WN4A1 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A03 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: Cruzer Blade
size: 29.25 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 243.1 GiB size: 243.1 GiB (100.00%) used: 14.5 GiB (6.0%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 513 MiB size: 512 MiB (99.80%)
used: 580 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 243.1 GiB size: 243.1 GiB (100.00%)
used: 14.5 GiB (6.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 243.1 GiB size: 243.1 GiB (100.00%)
used: 14.5 GiB (6.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 243.1 GiB size: 243.1 GiB (100.00%)
used: 14.5 GiB (6.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.53 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 193 Uptime: 1m wakeups: 0 Memory: total: 8 GiB note: est.
available: 7.53 GiB used: 1.48 GiB (19.6%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1329 libs: 385 tools: octopi,paru Shell: fish v: 3.6.1
default: Bash v: 5.2.15 running-in: konsole inxi: 3.3.31
Garuda (2.6.17-1):
System install date:     2023-11-06
Last full system update: 2023-11-06
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

Thanks,
LolFlasherNoobX

EDIT: The screen suspend issue is fixed as I was dumb enough to not reboot after setting up my new installation after the screen Locker error from Garuda Setup Assistant.

Can you provide your

garuda-inxi

Even if it from the live usb installation media

2 Likes

Provided the inxi output in the main post

Also please check the post as there have been some massive edits made

Probably you’re good to go now:

Last but not least, this release improves the lock screen to no longer break and display a “the screen locker is broken” screen, which was caused by a QML cache corruption due to running out of disk space. The devs say that the lock screen can still break because of other issues, which are currently being tracked down as well.

3 Likes

Thanks

1 Like

@LolFlasherNoobX You might try adding this kernel parameter .
Add in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=" split_lock_detect=off"
Then: sudo update-grub
Reboot.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.