I just had my first crash and reboot on this system since I installed TW on it 9 months ago. System has been running fine and I was using it at the time it occurred with Chrome, VMWare Player, konsole, and my editor running. In the approximately 20 minutes before the crash / reboot I found lots of the following journal messages: kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' About 10 minutes before the crash / reboot, snapper-timeline.service ran to cleanup snapshots and completed without an issues. 4 minutes later the following journal messages occurred, the video went black, and system rebooted. I was typing at the time this occurred. plasmashell[1773]: file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:34:43: QML ScrollBar: Binding loop detected for property "visible" kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kernel: loop: module loaded kernel: lp: driver loaded but no devices found kernel: PPP generic driver version 2.4.2 kernel: tun: Universal TUN/TAP device driver, 1.6 kernel: watchdog: watchdog0: watchdog did not stop! kernel: watchdog: watchdog0: watchdog did not stop! kernel: VFIO - User Level meta-driver version: 0.3 kernel: watchdog: watchdog0: watchdog did not stop! kernel: watchdog: watchdog0: watchdog did not stop! System booted back up fine and I ran checks on all the drives and there were no issues. TW was updated to 20211201 on 12/03/2021. System is on 24/7 and has only been booted 2 times since then (for normal reasons, not because of problems). System is an i7 with 32 GB ram using Intel HD internal graphics. I believe this is what caused the crash: file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:34:43: QML ScrollBar: Binding loop detected for property "visible" but am wondering why all the meta key issues are being reported??? The meta key has been working fine. Anyone else seen this issue?