Terminal breaks visually after suspend

[dmitryrn]

Note: I'm posting it here since I didn't find an issue in alacritty's github and this also reproduces with kitty.

Output of awesome --version:

awesome --version
awesome v4.3-1647-ge6f5c7980-dirty (Too long)
• Compiled against Lua 5.4.6 (running with 0.9.2)
• API level: 4
• D-Bus support: yes
• xcb-errors support: no
• execinfo support: yes
• xcb-randr version: 1.6
• LGI version: /usr/share/lua/5.4/lgi/version.lua
• Transparency enabled: yes
• Custom search paths: no

How to reproduce the issue:

I launch awesome through xinitrc with ly. I run sudo systemctl suspend. I wake the computer from sleep.

Actual result:

After waking up from sleep, alacritty is messed up:

I can still type in it, the cursor moves but the text is invisible. Kitty is also messed up but in a different way:

Only the specific instances of a terminal get messed up, I can open a new one and it works fine.

I can also switch to another virtual console (alt+ctrl+f1) and back to awesomewm and terminals get fixed.

Expected result:

A terminal doesn't get messed up after suspend.

System information
.xinitrc:

xrdb -merge ~/.Xresources
exec awesome --no-argb

.Xresources

Xft.dpi:144

alacritty: 0.13.1-1 (stable)
note: the same exact thing happens with alacritty-git and the kitty terminal.

xorg-server: 21.1.11-1

paru -Qs nvidia | rg local | rg nvidia

local/lib32-nvidia-utils 545.29.06-1
local/nvidia-dkms 545.29.06-1
local/nvidia-settings 545.29.06-1
local/nvidia-utils 545.29.06-1

My laptop is Legion 5 Pro, I only have the nvidia GPU enabled. I use proprietary drivers.

sudo lspci -v:

...
01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q]
	Flags: bus master, fast devsel, latency 0, IRQ 127, IOMMU group 15
	Memory at 5e000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 4000000000 (64-bit, prefetchable) [size=8G]
	Memory at 4200000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 5000 [size=128]
	Expansion ROM at 5f080000 [virtual] [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Legacy Endpoint, MSI 00
	Capabilities: [b4] Vendor Specific Information: Len=14 <?>
	Capabilities: [100] Virtual Channel
	Capabilities: [250] Latency Tolerance Reporting
	Capabilities: [258] L1 PM Substates
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [420] Advanced Error Reporting
	Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Capabilities: [900] Secondary PCI Express
	Capabilities: [bb0] Physical Resizable BAR
	Capabilities: [c1c] Physical Layer 16.0 GT/s <?>
	Capabilities: [d00] Lane Margining at the Receiver <?>
	Capabilities: [e00] Data Link Feature <?>
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia
...

uname -a

Linux archlinux 6.7.0-zen3-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 13 Jan 2024 14:36:54 +0000 x86_64 GNU/Linux

The output of alacritty --print-events > log1.txt 2>&1 that went through the suspend-wakeup procedure:
log1.txt

[dmitryrn]

It took me one more google search to dig a bit through arch forums, and it led me here: https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend. I just enabled nvidia-suspend service and not the issue is fixed.

[dmitryrn]

fixed