-
-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new desktop bazzite update crashes or freezes my laptop severly #1360
Comments
I have this problem as well, in my case it seems to be a game-update in steam (~46 gb). While updating it says "error writing on disk" and the pc freezes. I have to switch the pc off and then change the boot order in bios, because its shuffled around. |
Can confirm this issue on a 2024 GPD Win Mini, it happens randomly, but whenever it does writes fail and then the system freezes. Last time it happened to me while trying to save a game. |
I have a similar issue that I suspect is a hardware/storage issue. I switched it out my NVME because I thought it was faulty, but it may have overheated. |
Hi, @Nisarg000. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
I wish I could try out in the new version but this issue was so prevalent I uninstalled and went with windows |
The issue still exists on the latest Bazzite build. Both my GPD Win Mini 2024 and ROG Ally (Z1E) is affected, one runs on a 2TB WD SN740 2230 NVMe drive, while the other runs a 4TB Crucial P3+ 2280 NVMe drive. Getting logs beyond the initial write error is difficult as the whole system essentially enters a deadlocked state. I haven't bisected the issue, but rolling back to Bazzite 39 solves this issue. If you absolutely need to use Bazzite, maybe consider rolling an older build for now, as for me, I'm very close to jumping ship for something like Nobara, as daily-driving Bazzite no longer seems to be an option. |
Checking in @Black-Seraph - do you know if this issue was ever resolved? |
Describe the bug
Anytime I
I cannot open terminal or use any shortcut keys during that moment. I get forced to restart my system by holding the power key.
Here I am going to paste the output of journalctl -xb commands log to show what happened
error.txt
What did you expect to happen?
For instance if I use cleaners like bleachbit to perform a deep scan or download a huge file using pip from terminal I expect my system to not bug out(freeze) and allow me to interact.
Output of
rpm-ostree status
Hardware
So um here is the output through sudo inxi -Fxz:
hardware.txt
Extra information or context
No response
The text was updated successfully, but these errors were encountered: