I just installed Fedora 43 Workstation (Gnome) on my laptop. The problem I face is that I use my system as would normally do and then after lets say no more then 30 mins (it feels like clockwork its almost the same time every time) I open an app and it freezes. Force quitting does not work and it slowly freezes the whole sysyem. I tried baiting the error and being prepared with system monitoring but that freezes too when the apps star freezing. The apps that dont freez lose functionality. The app launcher doesn’t show the Icons properly and I cant launch new apps, power options dont work the only option is force shut down from the button and then rebooting only for it to happen again. Journal doesn’t seem to show anything special. This happend with gnome terminal, gnome software store and with firefox as the first stuck app. I reinstalled the system twice successfull. I updated the system after installing. Nothing seems to stop this. I am on a Thinkpad P16s gen 1 with ryzen cpu and integrated gpu. I updated the firmware on the first install as per the os’s request. What can I do to fix this?
How much RAM do you have?
I have 32Gb, 2Tb of ssd
Well it’s not a RAM issue then 
Is it always the same app that sets the failures in motion, or different apps, at the half hour mark?
Use journalctl (Journal Control) to see whats up.
journalctl --since="10 minutes ago"
I will check with journalctl also but from what I observe its not the same app. I have the problem happen multiple times with gnome store, once with the default terminal and once with firefox
EDIT:
This is what journalctl -b -1 -p 3 gives after rebooting after failure.
journalctl -b -1 -p 3
Mar 12 00:22:41 fedora kernel: nxp-nci_i2c i2c-NXP1001:00: NFC: Read failed with error -121
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #1 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #2 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #3 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #4 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #5 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #6 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #7 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #8 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #9 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #10 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #11 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #12 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #13 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #14 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #15 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #1 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #2 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #3 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #4 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #5 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #6 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #7 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #8 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #9 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #10 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #11 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #12 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #13 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #14 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #15 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #16 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #17 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #18 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #19 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #20 (No such file or directory)
Mar 12 00:22:42 fedora alsactl[1369]: /usr/sbin/alsactl: set_control:1373: failed to obtain info for control #21 (No such file or directory)
Mar 12 00:22:43 fedora bluetoothd[1308]: Failed to set default system config for hci0
Mar 12 00:22:55 fedora gdm-password][3457]: gkr-pam: unable to locate daemon control file
Mar 12 00:22:59 fedora kernel: i2c_hid_acpi i2c-ELAN0689:00: i2c_hid_get_input: incomplete report (14/60419)
Mar 12 00:22:59 fedora polkitd[1318]: Error converting subject to JS object: Process 2064 terminated
Mar 12 00:29:36 fedora kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Mar 12 00:29:36 fedora kernel: rcu: Tasks blocked on level-0 rcu_node (CPUs 0-15): P262/1:b..l
Mar 12 00:29:36 fedora kernel: rcu: (detected by 6, t=60002 jiffies, g=53837, q=9314 ncpus=16)
Ok so I found the fix (I hope). Changing the kernel from kernel-6.18.16-200.fc43.x86_64 to kernel-6.17.1-300.fc43.x86_64 seems to have solved the issue. I will update this thread if that was not the case but at the moment I’ve been going strong for like an hour or so.
EDIT: ~4 hours in no problems. Surely the kernel version was the problem.
Unless you report the kernel regression you are seeing you are trusting to luck that the bug gets looked at and fixed.
A new kernel sometimes inadvertently introduces bugs that only affect a small fraction of systems, and some kernel changes require firmware updates. Linux developers generally don’t have access to older hardware, so it is up to users with older hardware to provide bug reports with a) enough detail to allow others to reproduce the issue, and b) relevant details from logs. When I have encountered such bugs, others had usually already filed bug reports, but adding a “me too” helps to rule out broken hardware and gets the attention of developers who work on the parts of the kernel where the error occurs.