ASUS TUF A16 - System hangs on KDE login
I've been having troubles for the past few weeks now (see https://discord.com/channels/1072614816579063828/1087140957096517672/1336852421728665610), any time I attempt to update my Laptop (an ASUS TUF Gaming A16 FA617XS).
As soon as I attempt to login to KDE following an update, the system almost always hangs, with the loading wheel freezing, and the desktop never appearing, no matter how long I leave the system.
On rare occasions, the system does actually login following an update, but while it swiftly move to the desktop in those instances, this is accompanied with continuous extreme graphical artifacts (similar to what was reported here - https://discord.com/channels/1072614816579063828/1339306326521544745/1339306326521544745), which make the system basically impossible to use effectively.
I'm able to use the system for now by rolling back to the last known working image (bazzite-asus:stable-41.20250106.3), which doesn't suffer from of these issues. That's obviously not a long-term working solution though, so I'm hoping someone might be able to identify what it is in the images since this which could be causing the problem.
System Info:
ASUS TUF Gaming A16 FA617XS (Australian version - https://www.asus.com/au/laptops/for-gaming/tuf-gaming/asus-tuf-gaming-a16-advantage-edition-2023/techspec/)
CPU: AMD Ryzen 9 7940HS
RAM: 16GB DDR5-4800 SO-DIMM
iGPU: Radeon 780M Graphics
DGPU: AMD Radeon RX 7600S, up to 95W(SmartShift), 8GB GDDR6
2 Replies
Following up on this, I heard about the issue described on the Bazzite reddit (https://www.reddit.com/r/Bazzite/comments/1ic2bvn/psa_you_may_be_unable_to_update_here_is_the_fix/) where some people were unable to update, and went to with the command. Seems I have that composefs source in here as described in that reddit post. Going to try the fix mentioned there and see if I'm able to update properly afterwards.
Performing the fix as described in the reddit post above, doing an update (while on that same working image), rebooting into the updated version of that image, then rebasing to stable and rebooting again appears to have fixed it! Now on the latest version, no screen tearing issues at all.