Sometimes I get an error when launching Steam where the entire screen goes black. Needs hard reset
journalctl from last boot
Dec 09 22:45:55 batpc gnome-shell[4898]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1852321 error_code 3 request_code 25 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Dec 09 22:45:56 batpc systemd-coredump[153799]: [��] Process 4898 (gnome-shell) of user 1000 dumped core.
Specs
CPU: Intel i5-12400
GPU: Nvidia(I know) 5070 Ti (Undervolted but survived one hour OCCT 3d adaptive)
Mobo: MSI Pro b660m-a wifi ddr4
RAM: 96gb @ 2133
Image
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia-gnome:stable
Digest: sha256:eeca4cc98dca85101a0879050f2ca6fc47df8729fe49c0fe20a7705c86fc4e76
Version: 43.20251127 (2025-11-27T17:55:40Z)
LayeredPackages: coolercontrol linuxtoys liquidctl
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia-gnome:stable
Digest: sha256:eeca4cc98dca85101a0879050f2ca6fc47df8729fe49c0fe20a7705c86fc4e76
Version: 43.20251127 (2025-11-27T17:55:40Z)
LayeredPackages: coolercontrol liquidctl
Is there anything I should do, or other logs I can look at to find the cause?
Dec 09 22:45:55 batpc gnome-shell[4898]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1852321 error_code 3 request_code 25 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Dec 09 22:45:56 batpc systemd-coredump[153799]: [��] Process 4898 (gnome-shell) of user 1000 dumped core.
Specs
CPU: Intel i5-12400
GPU: Nvidia(I know) 5070 Ti (Undervolted but survived one hour OCCT 3d adaptive)
Mobo: MSI Pro b660m-a wifi ddr4
RAM: 96gb @ 2133
Image
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia-gnome:stable
Digest: sha256:eeca4cc98dca85101a0879050f2ca6fc47df8729fe49c0fe20a7705c86fc4e76
Version: 43.20251127 (2025-11-27T17:55:40Z)
LayeredPackages: coolercontrol linuxtoys liquidctl
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia-gnome:stable
Digest: sha256:eeca4cc98dca85101a0879050f2ca6fc47df8729fe49c0fe20a7705c86fc4e76
Version: 43.20251127 (2025-11-27T17:55:40Z)
LayeredPackages: coolercontrol liquidctl
Is there anything I should do, or other logs I can look at to find the cause?
