https://bugs.kde.org/show_bug.cgi?id=506831
Nicholas Page <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Nicholas Page <[email protected]> --- (In reply to TraceyC from comment #2) > If something froze, it may have crashed. We need a backtrace of it so we can > figure out what's going on. Can you look to see if there are core dumps, and > please attach a backtrace of the crash using the coredumpctl command-line > program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > Thanks! Thanks for the follow-up! Unfortunately, coredumpctl didn’t show any entries related to the crash. That said, I didn’t want to return empty-handed. I reproduced the issue again by enabling HDR in Wayland and then captured the system journal from the previous boot using journalctl -b -1. I’ve attached the resulting log file (wayland-crash.log) for your review. Here are the repeating messages that filled the journal at the moment of the freeze: kwin_wayland_drm: Atomic modeset test failed! Invalid argument kwin_scene_opengl: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" These errors seem to loop rapidly until the system completely locks up and must be power-cycled. They happen consistently whenever HDR is enabled on my ASUS XG27ACDNG (360Hz, HDR10, DisplayPort 1.4), and only on Wayland. X11 works without issue, even with HDR and 360Hz enabled. Let me know if there’s anything else I can capture or test! I’m happy to help however I can! -- You are receiving this mail because: You are watching all bug changes.
