Open japalvia opened 1 year ago
Is your monitor plugged in to Display Port? This might be related to some serious issue with Rapid Hotplug Detect or Deep sleep spec and about 50% of monitor manufactures not reading the spec correctly, or Linux not handling it correctly.
https://www.reddit.com/r/nvidia/comments/66opvp/this_displayport_hotplug_madness_finally_needs_to/
Is your monitor plugged in to Display Port?
I'm using HDMI (this NUC model doesn't have DP). There's only Intel GPU if that's relevant info.
Please fill out the following:
Sway Version: sway version 1.8.1
Debug Log: sway_debug_zsh.log alacritty_zsh_debug.log sway_debug_bc.log alacritty_bc_debug.log
Configuration File: Using Arch Linux default
/etc/sway/config
Stack Trace: bc:
zsh:
Steps to reproduce in my system:
alacritty -e zsh
bc
swaymsg "output * dpms off" ; sleep 10 ; swaymsg "output * dpms on"
Expected result: after display resumes, bc and zsh are running without issues Actual result: bc crashes (100 % reproducible), zsh crashes frequently
I reported this first to https://github.com/alacritty/alacritty/issues/6773 where the following error was observed in
WAYLAND_DEBUG=client
logs:Other ways to crash zsh after resume: Type "journalc" and complete with Tab --> immediate crash.
The crash is not specific to zsh. I used to get this randomly with bash after dpms. I think I've had this since moving to Wayland and alacritty (~ 2 years).
I cannot reproduce using urxvt or kitty. Also, I cannot reproduce this issue in Weston.
Other info: This setup is Intel NUC with DELL U3818DW on HDMI. There's no additional display configuration tool like kanshi on this machine. I have identical installation on a laptop with external 4K display (using kanshi) where the issue doesn't seem to happen ever.