-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
UPSTREAM: Experiencing system freezing issues recently when running flatpak apps #397
Comments
I think you're hitting the same issue as https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/110 |
@1Naim yes, exactly! It is appears to be a severe kernel bug. Well this does not happen unless I use flatpak applications. But I use some of them as my daily driver apps like logseq. |
You can use |
There is also logseq in the repo btw |
https://lore.kernel.org/linux-mm/[email protected]/T/#t Seems to be introduced by 3eab9d7bc2f4 ("fuse: convert readahead to use folios") Hopefully upstream fixes it soon. |
I'll consider it, thank you. |
CachyOS/linux@39f05fc Fix queued for 6.13.2 |
This should already be fixed now in 6.13.2, closing. |
Summary
Hello.
I've been experiencing system freeze issues as of this week. When I launch some flatpak apps or use them the whole system freezes and becomes irresponsive even to the keyboard events. So I have to hard reset the computer and boot it up again in order to get it functioning.
I decided open an issue here after I had a look at
journalctl
output which was filled with kernel level system errors.System Info
Let me share the output of
sudo cachyos-bugreport.sh
command:https://paste.cachyos.org/p/744ac94.log
Journal
Here I also leave the
journalctl
's last 1000 lines:journal_20250207_1228.txt
I see many errors reported on CPU: 7 from the kernel. I think it has to do with the new kernel version and it looks severe.
Flatpak Apps That Makes System Freezing
The flatpak apps that cause freezing and I tried many times are:
I will keep trying with other flatpak apps and update this post upon a new information.
The text was updated successfully, but these errors were encountered: