When this happens, the kernel literally doesn’t allow the compositor to present to the screen anymore, so the screen is completely frozen forever
Yup, that sounds awfully familiar! Also the log reports from that seem quite familiar too, (Gnome/Wayland + 6.12.2 kernel over here). The 7900XTX seems less prone to the issue however so it doesn't happen to me too terribly often.
I've noticed it happens more often when I'm spawning / closing full screen 3d applications such as games, ie when working on mods.
Unfortunately they don't seem to have a solid plan on how to resolve performing a reliable reset on the driver and the work-arounds don't seem to reliably work. Guess I'll just have to be patient and save frequently.
@ProdigalFrog Interesting, also yes. Now if only I could read the bug report to see the details to see if I can resolve it without creating an account on their gitlab instance :/
@harrysbalzac Is it complaining that /media/extEXT4drive isn't mounting? If your root drive (/) is mounting and you have access to /etc/fstab, you can just edit that file with the new UUID of the drive.
bash
ls -lha /dev/disk/by-uuid/
To see what the new UUID is, (assuming you know the device path).
@ProdigalFrog
When this happens, the kernel literally doesn’t allow the compositor to present to the screen anymore, so the screen is completely frozen forever
Yup, that sounds awfully familiar! Also the log reports from that seem quite familiar too, (Gnome/Wayland + 6.12.2 kernel over here). The 7900XTX seems less prone to the issue however so it doesn't happen to me too terribly often.
I've noticed it happens more often when I'm spawning / closing full screen 3d applications such as games, ie when working on mods.
Unfortunately they don't seem to have a solid plan on how to resolve performing a reliable reset on the driver and the work-arounds don't seem to reliably work. Guess I'll just have to be patient and save frequently.