Display Frozen After Wake from Standby (Wayland)

Support Graphics & Display
1

Continued issue from thread here. Starting a new topic as advised.

When trying to wake my computer from Standby, the display comes back on and the keyboard lights up as if it has woken up, but is completely unresponsive. The screen has a black background instead of my desktop image. The panel I have appears as gray and all the the task manager app icons and system tray icons are black. The mouse cursor does appear, but again, is unresponsive.

This is an improvement after upgrading and moving from x11 to wayland. Before the monitor would wake and then go back to sleep.

Hibernate works without issue.

My system is up to date and I just updated my BIOS to the latest version.Output from inxi -zv6:

System:
  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: H470M-STX serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends
    v: P2.20 date: 08/06/2021
Memory:
  System RAM: total: 16 GiB available: 15.24 GiB used: 2.75 GiB (18.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR4 size: 8 GiB speed: 2667 MT/s volts: 1
    note: check manufacturer: G.Skill part-no: F4-3000C16-8GRS
  Device-2: ChannelB-DIMM0 type: DDR4 size: 8 GiB speed: 2667 MT/s volts: 1
    note: check manufacturer: G.Skill part-no: F4-3000C16-8GRS
CPU:
  Info: 6-core model: 11th Gen Intel Core i5-11500 bits: 64 type: MT MCP
    arch: Rocket Lake rev: 1 cache: L1: 480 KiB L2: 3 MiB L3: 12 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 65112
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] vendor: ASRock
    driver: i915 v: kernel arch: Xe ports: active: HDMI-A-1
    empty: DP-1,DP-2,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:4c8a
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-1 model: HP W2072a res: 1600x900 hz: 60 dpi: 92
    diag: 508mm (20")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
    device-ID: 8086:4c8a display-ID: :1.0
  API: Vulkan v: 1.4.335 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:4c8a
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel vendor: ASRock driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:f1c8
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4d
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-14:5 chip-ID: 8087:0aa7
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.03 TiB used: 65.18 GiB (6.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDBA3V5000ANC-WRSN
    size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 37.9 C
  ID-2: /dev/nvme1n1 vendor: TeamGroup model: T-FORCE TM8FFE512G
    size: 476.94 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 40.9 C
  ID-3: /dev/sda vendor: PNY model: CS900 120GB SSD size: 111.79 GiB
    speed: 6.0 Gb/s serial: <filter>
  Message: No optical or floppy data found.
Partition:
  ID-1: / size: 94.73 GiB used: 13.89 GiB (14.7%) fs: btrfs dev: /dev/sda2
    label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
  ID-2: /boot/efi size: 299.4 MiB used: 664 KiB (0.2%) fs: vfat
    dev: /dev/sda1 label: N/A uuid: 2F1E-A295
  ID-3: /home size: 468.38 GiB used: 51.29 GiB (11.0%) fs: ext4
    dev: /dev/nvme1n1p1 label: Home uuid: 3683cd15-0c99-4854-a7b6-e062d58a296d
  ID-4: /var/cache size: 94.73 GiB used: 13.89 GiB (14.7%) fs: btrfs
    dev: /dev/sda2 label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
  ID-5: /var/log size: 94.73 GiB used: 13.89 GiB (14.7%) fs: btrfs
    dev: /dev/sda2 label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
Swap:
  ID-1: swap-1 type: partition size: 16.77 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3 label: N/A uuid: 348b79f5-1b76-4b4e-ab10-1d73b13dedfe
Unmounted:
  ID-1: /dev/nvme0n1p1 size: 200 MiB fs: vfat label: N/A uuid: 402B-42A3
  ID-2: /dev/nvme0n1p2 size: 16 MiB fs: <superuser required> label: N/A
    uuid: N/A
  ID-3: /dev/nvme0n1p3 size: 366.69 GiB fs: ntfs label: N/A
    uuid: F0182C43182C0AE4
  ID-4: /dev/nvme0n1p4 size: 735 MiB fs: ntfs label: N/A
    uuid: C0A8CC20A8CC1736
  ID-5: /dev/nvme0n1p5 size: 98.14 GiB fs: ntfs label: Storage
    uuid: B0C406C6C4068F32
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002
  Hub-2: 1-6:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    lanes: 1 chip-ID: 05e3:0610
  Device-1: 1-6.1:4 info: Logitech M-U0007 [Corded Mouse M500] type: mouse
    driver: hid-generic,usbhid rev: 2.0 speed: 1.5 Mb/s lanes: 1
    chip-ID: 046d:c069
  Device-2: 1-6.2:6 info: BY Tech Gaming Keyboard type: keyboard,HID
    driver: hid-generic,usbhid rev: 2.0 speed: 12 Mb/s lanes: 1
    chip-ID: 258a:0049
  Device-3: 1-9:3 info: ASRock LED Controller type: HID
    driver: hid-generic,usbhid rev: 1.1 speed: 12 Mb/s lanes: 1
    chip-ID: 26ce:01a6
  Device-4: 1-14:5 info: Intel Wireless-AC 3168 Bluetooth type: bluetooth
    driver: btusb rev: 2.0 speed: 12 Mb/s lanes: 1 chip-ID: 8087:0aa7
  Hub-3: 2-0:1 info: super-speed hub ports: 8 rev: 3.1 speed: 10 Gb/s
    lanes: 1 chip-ID: 1d6b:0003
  Hub-4: 2-6:2 info: Genesys Logic Hub ports: 4 rev: 3.2 speed: 5 Gb/s
    lanes: 1 chip-ID: 05e3:0626
Sensors:
  System Temperatures: cpu: 28.0 C pch: 58.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 303 Power: uptime: 13m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: 1274 pm: pacman pkgs: 1260 pm: flatpak pkgs: 14 Compilers:
    clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40
2

Found a command to run to check the sleep/suspend logs:

journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"

And here is the output:

Jan 06 19:18:09 rem49x systemd[1]: Starting System Suspend...
Jan 06 19:18:09 rem49x wpa_supplicant[675]: p2p-dev-wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 06 19:18:09 rem49x wpa_supplicant[675]: p2p-dev-wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 06 19:18:09 rem49x wpa_supplicant[675]: nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
Jan 06 19:18:09 rem49x systemd[1]: user.slice: Unit now frozen.
Jan 06 19:18:09 rem49x systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Jan 06 19:18:09 rem49x systemd-sleep[8809]: Successfully froze unit 'user.slice'.
Jan 06 19:18:09 rem49x systemd[1]: session-1.scope: Unit now frozen-by-parent.
Jan 06 19:18:09 rem49x systemd[1]: user@1000.service: Unit now frozen-by-parent.
Jan 06 19:18:09 rem49x systemd-sleep[8809]: Performing sleep operation 'suspend'...
Jan 06 19:18:09 rem49x kernel: PM: suspend entry (deep)
Jan 06 19:18:09 rem49x kernel: Filesystems sync: 0.013 seconds
Jan 06 19:18:09 rem49x wpa_supplicant[675]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 06 19:18:09 rem49x wpa_supplicant[675]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 06 19:18:09 rem49x wpa_supplicant[675]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jan 06 19:18:21 rem49x kernel: Freezing user space processes
Jan 06 19:18:21 rem49x kernel: Freezing user space processes completed (elapsed 0.000 seconds)
Jan 06 19:18:21 rem49x kernel: OOM killer disabled.
Jan 06 19:18:21 rem49x kernel: Freezing remaining freezable tasks
Jan 06 19:18:21 rem49x systemd-sleep[8809]: System returned from sleep operation 'suspend'.
Jan 06 19:18:21 rem49x kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 06 19:18:21 rem49x kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 06 19:18:21 rem49x kernel: e1000e: EEE TX LPI TIMER: 00000011
Jan 06 19:18:21 rem49x kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Jan 06 19:18:21 rem49x kernel: ata3.00: Entering standby power mode
Jan 06 19:18:21 rem49x kernel: ACPI: PM: Preparing to enter system sleep state S3
Jan 06 19:18:21 rem49x kernel: ACPI: PM: Saving platform NVS memory
Jan 06 19:18:21 rem49x kernel: Disabling non-boot CPUs ...
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 11 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 10 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 9 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 8 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 7 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 6 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 5 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 4 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 3 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 2 is now offline
Jan 06 19:18:21 rem49x kernel: smpboot: CPU 1 is now offline
Jan 06 19:18:21 rem49x kernel: ACPI: PM: Low-level resume complete
Jan 06 19:18:21 rem49x kernel: ACPI: PM: Restoring platform NVS memory
Jan 06 19:18:21 rem49x kernel: Enabling non-boot CPUs ...
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 06 19:18:21 rem49x kernel: CPU1 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 06 19:18:21 rem49x kernel: CPU2 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 06 19:18:21 rem49x kernel: CPU3 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Jan 06 19:18:21 rem49x kernel: CPU4 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Jan 06 19:18:21 rem49x kernel: CPU5 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Jan 06 19:18:21 rem49x kernel: CPU6 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Jan 06 19:18:21 rem49x kernel: CPU7 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Jan 06 19:18:21 rem49x kernel: CPU8 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Jan 06 19:18:21 rem49x kernel: CPU9 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Jan 06 19:18:21 rem49x kernel: CPU10 is up
Jan 06 19:18:21 rem49x kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Jan 06 19:18:21 rem49x kernel: CPU11 is up
Jan 06 19:18:21 rem49x kernel: ACPI: PM: Waking up from system sleep state S3
Jan 06 19:18:21 rem49x kernel: nvme nvme0: 12/0/0 default/read/poll queues
Jan 06 19:18:21 rem49x kernel: nvme nvme1: 12/0/0 default/read/poll queues
Jan 06 19:18:21 rem49x kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 06 19:18:21 rem49x kernel: sd 2:0:0:0: [sda] Starting disk
Jan 06 19:18:21 rem49x kernel: ata6: SATA link down (SStatus 4 SControl 300)
Jan 06 19:18:21 rem49x kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jan 06 19:18:21 rem49x kernel: ata3.00: configured for UDMA/133
Jan 06 19:18:21 rem49x kernel: ata4: SATA link down (SStatus 4 SControl 300)
Jan 06 19:18:21 rem49x kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jan 06 19:18:21 rem49x kernel: OOM killer enabled.
Jan 06 19:18:21 rem49x kernel: Restarting tasks ... 
Jan 06 19:18:21 rem49x kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Jan 06 19:18:21 rem49x kernel: done.
Jan 06 19:18:21 rem49x kernel: random: crng reseeded on system resumption
Jan 06 19:18:21 rem49x kernel: PM: suspend exit
Jan 06 19:18:21 rem49x systemd[1]: user@1000.service: Unit now thawed.
Jan 06 19:18:21 rem49x systemd[1]: session-1.scope: Unit now thawed.
Jan 06 19:18:21 rem49x systemd[1]: user-1000.slice: Unit now thawed.
Jan 06 19:18:21 rem49x systemd[1]: user.slice: Unit now thawed.
Jan 06 19:18:21 rem49x systemd-sleep[8809]: Successfully thawed unit 'user.slice'.
Jan 06 19:18:21 rem49x systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 06 19:18:21 rem49x systemd[1]: Finished System Suspend.

This time my display did not even wake up. Keyboard came back on. Was able to turn num lock on and off, so it seems like it may be waking up and not outputting anything to the display.

3

Just another update as I discover things. Accidentally left the Sleep settings on while I was listening to playback on a recording and the computer when to sleep. After waking up, the music started back up and kept playing. My monitor was active, but there was nothing but a black screen, not lit up at all. I was able to adjust the volume from my keyboard.

I’m thinking this is a display output issue as the computer appears to be fully awake with my session restored.

4

Don’t pin me down on this, but I believe it’s a bug in the recent Plasma version, and that KDE have a fix for it coming down the pike. :crossed_fingers:

1 Like
5

Wayland has been giving too many bugs these days… and yet the recent version has aggressively taken down X11 leaving Wayland being the only option. Crazy as it seems, but I just want games running smoothly, screen doesn’t go black when waking from sleep, and no tears and flickers (TearFree is with X11 which now no longer becomes an option). Who knows how long until there is a fix… Oh and the Adaptive Refresh Rate (or VRR) with KWin is always buggy, especially with my Samsung 57". It’s a disaster.

Anyone else having these issues altogether? Churn. :face_with_diagonal_mouth:

6