Freeze On Wake When Display Is Starting

Seems about 2-3 weeks ago a new issue started and I wanted to share my workaround.

The Issue: When waking up the computer with the HDMI display plugged in but turned off, the desktop is drawn on screen and machine OS freezes (mouse cursor won't move for example) after turning on the display.

The Workaround: Make sure the display is turned on first and fully ready (mine says "no signal" once it's ready) and then wake the computer.

Kernel: 6.1.43-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=e0430201-0931-4d49-a5a8-f8a1445e4ab0 rw rootflags=subvol=@
rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=ae0cdb3c-2994-4db6-8822-7960e6e25fe8 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Laptop System: Apple product: MacBookAir7,2 v: 1.0
serial: <superuser required> Chassis: type: 9 v: Mac-937CB26E2E02BB01
serial: <superuser required>
Mobo: Apple model: Mac-937CB26E2E02BB01 v: MacBookAir7,2
serial: <superuser required> UEFI: Apple v: 476. date: 09/06/2022
ID-1: BAT0 charge: 50.7 Wh (97.9%) condition: 51.8/54.3 Wh (95.3%)
volts: 8.5 min: 7.6 model: SMP bq20z451 type: Li-ion serial: N/A
status: full cycles: 692
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Info: model: Intel Core i5-5350U bits: 64 type: MT MCP arch: Broadwell
gen: core 5 level: v3 note: check built: 2015-18 process: Intel 14nm
family: 6 model-id: 0x3D (61) stepping: 4 microcode: 0x2F
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 2300 high: 2900 min/max: 500/2900 scaling:
driver: intel_cpufreq governor: performance cores: 1: 2900 2: 1700 3: 2900
4: 1700 bogomips: 14407
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Device-1: Intel HD Graphics 6000 vendor: Apple driver: i915 v: kernel
arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: HDMI-A-1
off: eDP-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1626
class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.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: 507x285mm (19.96x11.22")
s-diag: 582mm (22.9")
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: LG (GoldStar) TV
serial: <filter> built: 2019 res: 1920x1080 hz: 120 dpi: 30 gamma: 1.2
size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes:
max: 4096x2160 min: 720x400
Monitor-2: eDP-1 note: disabled model: Apple Color LCD built: 2015
res: 1920x1080 dpi: 128 gamma: 1.2 size: 286x179mm (11.26x7.05")
diag: 337mm (13.3") ratio: 16:10 modes: 1440x900
API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel HD Graphics 6000 (BDW
GT3) direct-render: Yes
Device-1: Intel Broadwell-U Audio vendor: Apple driver: snd_hda_intel
v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0
class-ID: 0403
Device-3: Broadcom 720p FaceTime HD Camera driver: facetimehd v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:1570
class-ID: 0480
API: ALSA v: k6.1.43-1-lts status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.77 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
Device-1: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple
driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 14e4:43a0 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Device-1: Apple Bluetooth USB Host Controller driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3.3:10
chip-ID: 05ac:828f class-ID: fe01
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Local Storage: total: 233.76 GiB used: 164.64 GiB (70.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Apple model: SSD SM0256G
size: 233.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3A0Q scheme: GPT
ID-1: / raw-size: 224.66 GiB size: 224.66 GiB (100.00%)
used: 164.64 GiB (73.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 224.66 GiB size: 224.66 GiB (100.00%)
used: 164.64 GiB (73.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 224.66 GiB size: 224.66 GiB (100.00%)
used: 164.64 GiB (73.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 224.66 GiB size: 224.66 GiB (100.00%)
used: 164.64 GiB (73.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.66 GiB used: 938.9 MiB (12.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 maj-min: 8:3
System Temperatures: cpu: 61.0 C pch: 69.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 248 Uptime: 18h 0m wakeups: 31 Memory: total: 8 GiB
available: 7.66 GiB used: 3.83 GiB (49.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 15.0.7
Packages: pm: pacman pkgs: 2237 libs: 603 tools: octopi,pamac,paru,pikaur
Shell: fish v: 3.6.1 running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
System install date:     2022-12-02
Last full system update: 2023-08-08
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut(custom) mkinitcpio
Windows dual boot:       No/Undetected
Failed units:

My display is an LG C9.

I can't mark the OP as the "solution"? (probably because it's designed to be referenced to the original)

Check the power saving settings of the monitor. Some monitors are configured with a default setting to power off entirely if an "inactive" signal is received from the connected device (to save electricity), but oftentimes there are other settings available. See if there is a "standby" setting you can use instead when an inactive signal is received.


Thanks, I've already disabled that setting a while ago, the display will remain on for a very long time even without signal. It used to show a screen saver, I turned that off.

I would be curious to hear what behavior is observed when resuming a Wayland session, if you would be willing to give that a try.


Another related issue I forgot to mention that was also happening, very similar. I would open the laptop lid and press the power button for the TV at the same time and I would have a black screen "no signal" but the laptop would still be responsive as I could toggle caps lock. I would sleep the laptop via the sleep key on my keyboard, then press a key to wake it again and the display then works. Turning on the TV and waiting for it to be fully ready also prevents this issue. It was doing this for a few weeks before the hard lock/freeze started happening.

I'm trying with a Wayland session and so far unable to get it to freeze but I can reproduce the black screen without freeze issue and the need to sleep/wake once more.

It happened with Wayland.

Check to see if there is a firmware update available for your TV. Software, Firmware & Driver Downloads | LG USA Support

You may need the model number of the TV to find it. I tried to look up a refrigerator on their website a few months ago and it was maddening because they seem to list only models currently in production. [EDIT: I was actually thinking of the Samsung website with that refrigerator comment.]

1 Like

Looks like the firmware gets updated with the OS updates. Updating the OS again and will see what happens.

Still crashes, thanks for the suggestion though.

For what it's worth the issue doesn't happen when the display is off, only when it's starting up.

Hey, check this out:

It looks like some folks have incorporated it into scripts to power on/off their TVs according to wake/suspend events in the computer:


Aww dang, it requires the TV to be on the network. I do NOT keep this spyware of a display on my network normally, ONLY to update it. Thanks though, sounds neat! (when I cannot see source code I assume the worst, thus the "spyware" claim without evidence)

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