Created attachment 164833 [details] Xorg log SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After updating to kernel version 6.5.0-14 on Kubuntu 22.04.3 LTS, active session demonstrates erratic behaviour. Sometimes, opening an app causes the error; sometimes scrolling inside an app does. In all cases, the error either causes me to get kicked back to the login screen (session closes unexpectedly) or the entire thing comes crashing down to a black screen and perhaps remains so until I press the power button, at which point the kubuntu logo appears briefly as in a normal shutdown (OS crashes entirely). STEPS TO REPRODUCE 1. Clean install and update Kubuntu 22.04.3 LTS 2. Reboot to finish updates 3. Attempt to trigger bug - this could be caused by opening Discord (after installing via Discover) for the first time, opening System Settings or scrolling the System Settings left menu items (2/2 times in my experience). OBSERVED RESULT System is highly unstable and often, but not systematically, kicks user out of session or hard crashes. EXPECTED RESULT System behaves in a stable fashion, as prior to update. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Kubuntu 22.04.3 LTS (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I have verified that this error occurs outside of my actions; a clean install of Kubuntu 22.04.3 LTS which is then updated through Discover started showing symptoms after barely any manipulation (chaging appearance to Breeze Dark, installing Discord). (Some) PC hardware specs are listed below. Also uploading Xorg logs in case they're remotely useful. CPU: Intel i9-9900K GPU: AMD/ATI Vega 10 XGA (Radeon Pro Vega 48)
Created attachment 164834 [details] Previous Xorg log (just in case)
Revision 17 (bit after the dash in the kernel name) of the kernel seems to have fixed it.